Friday
- last edited
yesterday
by
Laszlo Nagy
When I create GDL objects, I often combine scripted and saved elements. As such, my method always involves saving from or related to a position intentionally at/near 0,0,0.
I have a file, when saving objects at 0,0,0, it thinks they are saved -650,-1780 from the project origin.
I have checked the coordinates, there is no user defined origin I could be inadvertently saving from. I have checked the model primitives I'm saving, to ensure there is no cover fill handle or rotation axis/origin that is hundreds/thousands offset from 0,0,0.
View rotation is 0º in the plan view I am saving from.
...
Anyone else ever see an object save with absurd add commands in the resultant geometry?
My trouble is, if I place a scripted component or modify the script, it is virtually impossible to get things lined up with the saved geometry.
There has to be something I'm missing here!
Operating system used: Mac Apple Silicon
Saturday
Patrick, can you confirm this also happens in a clean file started from an OOTB template?
The only reason I can think of is that at some point you saved this file and opened it again, with elements far away from the actual origin. In this case Archicad recalculates an offset to mitigate the "too far from origin" issue. This can not be seen in the interface, but GDL still refers to the original origin.
Other than that I have not seen this before.