topic Re: Wrong origin when stealing into 2D Script window in Libraries & objects

Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Wed, 24 May 2023 10:29:09 GMT

[Only recently started using 19 and maybe there is some new basic setting that I am missing, or maybe I am getting rusty and forgot something obvious:]

I place a hotspot on the origin (which I swear it is, the rulers show 0,0, etc.) in floor plan view. I drag it into the floating 2D Script window and get this:

pen 1
hotspot2 -127366.2544831, -121862.270517

?!

Re: Weirdness when stealing by dragging into 2D Script windo

Piotr Dobrowolski — Mon, 13 Mar 2017 17:59:25 GMT

Didn't the paste miss the E letter somewhere in Your coords? 😜

Yes it is the "problem" (I would call a bug) with snapping to a point accuracy.

If You want to be sure about 0,0...just have to move the object using the typed in coords.

Best Regards,
Piotr

Re: Weirdness when stealing by dragging into 2D Script windo

Ignacio Azpiazu — Mon, 13 Mar 2017 18:22:43 GMT

The paste did not miss anything. It seems as if the autoscript is thinking the origin is a couple hundred km away.

I tried with the hotspot placed at 1,1 and get

hotspot2 -127365.2544831, -121861.270517

which is coherent with the previous 0,0 as

hotspot2 -127366.2544831, -121862.270517

I had been using this method for ages.

Re: Wrong origin when stealing into 2D Script window

Barry Kelly — Tue, 14 Mar 2017 00:14:18 GMT

Maybe your origin is a 'user' origin rather than the 'drawing' origin.
Double click the origin button to reset the user origin and see if it moves.

Barry.

Re: Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Tue, 14 Mar 2017 01:40:12 GMT

Barry wrote:
Maybe your origin is a 'user' origin rather than the 'drawing' origin.

It is the real origin. You get used to doing stuff around the model origin when you want to steal into the script. And I am not sure that I could work ~170 km away from the origin even if I wanted to.

Re: Wrong origin when stealing into 2D Script window

Barry Kelly — Tue, 14 Mar 2017 02:11:41 GMT

Ignacio wrote:
It is the real origin.

Are you really sure it is not a user origin?
The rulers will still say 0,0 for a user origin.

The reason I ask is because this is the code I get if I place one hotspot at the drawing origin and another at a user origin and drag (steal) them into the 2D script.

pen         11
hotspot2 20.86856641983, 9.470493196231		!!hotspot at user origin

pen         11
hotspot2           -0,           -0			!!hotspot at drawing origin

Barry.

Re: Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Tue, 14 Mar 2017 02:20:55 GMT

I know what a user origin is. It is the model origin.

Re: Wrong origin when stealing into 2D Script window

Barry Kelly — Tue, 14 Mar 2017 02:51:18 GMT

Ignacio wrote:
I know what a user origin is. It is the model origin.

No the user origin is simply a user positioned origin.
It can be anywhere you choose and will be referred to as your 0,0 co-ordinates.
So you may well model around this user origin as if it is 0,0 (I guess what you are calling the model origin).
See attached image.

What you are looking for is the default origin.
I called it the drawing origin - its correct name is the 'Project' origin.
This can not be moved.

Please indulge me for a moment and try this.
From your hotspot (origin) that you are seeing as 0,0 in plan, move your cursor so you can see the co-ordinates +127366.2544831, +121862.270517
This is the exact opposite of your saved hotspot script.
Do you see a greyed out origin there?
If so that is the project origin that you need to use if you are expecting to get 0,0 for your hotspot when dragging it into the script.

Or just double click the 'Set user origin' button and see if the origin moves.

Barry.

Re: Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Tue, 14 Mar 2017 03:23:32 GMT

Barry: you asked
Are you really sure it is not a user origin?
and I replied
I know what a user origin is. It is the model origin.

Re: Wrong origin when stealing into 2D Script window

Barry Kelly — Tue, 14 Mar 2017 03:39:11 GMT

Ignacio wrote:
Barry: you asked
Are you really sure it is not a user origin?
and I replied
I know what a user origin is. It is the model origin.

Hey, I'm just trying to help.

What I am saying is the model (user) origin is not what you want.
To get the 0,0 co-ordinates you must use the Project origin.
I am 99% sure you are not using the project origin - but I could be wrong.

Have you double clicked the set user origin button to see if it resets the origin position?
If it doesn't then I am out of ideas.

Barry.

Re: Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Tue, 14 Mar 2017 04:25:11 GMT

I tried File>New, 'Use the same settings…' —and it opens to the funny view in the image attached. (When I open from a template, same Work Environment, it opens OK.)

Going over several saved previous versions of the file (on AC17) the problem is still there. I just found that at some point I merged a stupid DWG which happened to have all its content around x: -7000 km, y: -6000 km (it may have to do with it having Autocad Civil information with World Coordinates).

I recall reading that elements too far from the origin mess up stuff in Archicad. Maybe it has to do with that. Deleting the stories with the DWG does not fix the problem though —maybe the Archicad file is messed up forever when it adjusts who knows what in order to deal with those huge dimensions.

Re: Wrong origin when stealing into 2D Script window

Piotr Dobrowolski — Tue, 14 Mar 2017 09:28:05 GMT

AC is usually simplifying the coords when the data is placed far from the real origin, but a lot of problems show up when having data in the area of real origin of a file and somewhere very far from it.

Best Regards,
Piotr

Re: Wrong origin when stealing into 2D Script window

Anonymous — Fri, 17 Mar 2017 01:00:41 GMT

http://helpcenter.graphisoft.com/troubleshooting/3d-modeling/far-from-origin/

This is what causes problems in coordinates in Archicad sometimes.

Hopefully something in this article may help.

The important thing is Origins are counted during the opening of files. After you repaired the plan, it should be saved, closed and opened again to get the updated origins.

I don't know if you have got any information far from the origin that may affect the origin, but if you do, follow these instructions to potentially fix it.

Archicad would randomly reset the origin point when doing large models, and this would effect the export origins for Artlantis. I could never find a fix for that, but the work around was to move the origin in the Artlantis reference file, so i could continue to use the Artlantis work flow.

All you can Do is Try...(Anti-yoda)

Re: Wrong origin when stealing into 2D Script window

Ignacio Azpiazu — Sun, 19 Mar 2017 05:28:17 GMT

allanp wrote:
http://helpcenter.graphisoft.com/troubleshooting/3d-modeling/far-from-origin/

This is what causes problems in coordinates in Archicad sometimes.

I dragged everything so that it fits within ~10 km (as opposed to thousands with the original world coordinates) and the 'wrong' origin given when stealing for GDL is now some 4000 m off, which is much closer than before but still unusable without some processing in Excel or whatever.

I remember suffering that Artlantis export problem too. I fear what may happen with this one in Artlantis.

Thanks very much.