Coordinate dimension error in schedules

[Anonymous]

There are new bug in AC20.
Earlier, I used schedules to create simple lists for coordinate points.
Now, in AC20 schedules shows incorrect, not updated view of coordinate objects.
I had to open each one object, change some criteria, then return to schedule. After this senseless action, my list was up to date.
Every new object was listed incorrectly again.

Any ideas?

[Gorazd]

You are using Coordinate object from the library, right? This object has been broken in AC19 and AC20. In AC18 you could list the real values of XYZ in schedules, but in later versions, this parameters are not accessible any more. What I have done is, that I have opened AC18, placed coordinate object 18 in plan, selected it in open a library part (CTRL+SHIFT+O). Then just save it with another name somewhere on your HD. Open AC19 or 20, load this new object with library manager and use this new/old object.
Hope it helps.

[Erwin Edel]

I think it got removed/broken because we got 3D guidelines.

[Laszlo Nagy]

It is also possible that the significant changes made in GDL in AC19 are the reason why they do not work they way they used to.
In any case, I will report this to GRAPHISOFT.

[sinceV6]

laszlonagy wrote:
It is also possible that the significant changes made in GDL in AC19 are the reason why they do not work they way they used to.
In any case, I will report this to GRAPHISOFT.

The "Compatibility Changes in GDL" document states that:

5. Scheduling the location/coordinates of the Coordinate Dimension object was used to document setout points. Has a new method been added to deal with this?
--Scheduling of these parameters was not reliable earlier, because the parameter script did not run when generating the schedules, so the results were inconsistent with the current state if someone moved the project origin at least once.
--We have changed the Coordinate Dimension element so that it provides reliable coordinate information on floor plan and in 3D, but scheduling is not possible anymore.

So it is not broken, just not available anymore.

But the grand scope of things tells me that it is not the just object what should have changed, but the general way of 2D/3D information of objects in relation to the environment they are placed.

I cannot possibly begin to talk without knowing the inner workings of the program, only the people behind AC can; but the reason for the change is not aligned with the rest of documentation because the Reference states that the "Project Origin" is a constant location that remains fixed for the life of the project (and that the inner calculation origin might be moved as explained in this thread), so AFAIK, the project origin cannot be moved by someone else resulting in wrong information in schedules (even in teamwork?)

Then, if the Coordinate dimension can be scripted to provide reliable coordinate information in 2D/3D, why can't this information be accessed by AC (in the schedules) if we are talking about the object's position (nevermind that there might be a bug in the 2D script that shows a wrong coordinate), and AC ALWAYS knows its position so it can be placed in the 3D window regardless of where the project/edit/user origin is at any given moment.

So... I would think the problem is in the way the parameter script and schedules work or integrate with the rest of the program.

In other words: major GDL changes and improvements are needed -and long overdue- to accommodate the ever growing complexities of the industry. I believe they are coming. I just hope -as I've said before- that GS gives a second thought on maintaining long backwards compatibilities that could keep AC from its full potential. The fact of the changes in GDL in AC19 and AC20 is -I think- proof of this.

Best regards.

[Anonymous]

I previously used such schedule to list my coordinates for intersecting axes.
These points have custom origin.

Sad, but there are no such parameter to pick, just symbol in 2D view.

[Anonymous]

I used these parameters

[Katalin Borszeki]

HI, as Pukisarch's comment correctly shows the the 'Object Inventory' criteria has changed. Rewrite the criterias, and the schedule will work just as well as in ARCHICAD19. Please see the screenshots. best, k