Hello Ranga,
Graphisoft in there wisdom have disabled the use of Glob_User values in 3D (elevation) in version 12 as they told me there were problems with it - Although I had been successfully using it for the last 5 or so years.
Here is a link to a post when i first noticed the problem.
http://archicad-talk.graphisoft.com/viewtopic.php?p=125398&highlight=glob%2A#125398
Using the RETURNED_PARAMETERS option in the CALL statement did end up working for us once I used it properly.
But you are not calling any macros so I am not sure what your solution will be.
Except maybe writing to an external text file instead of a Glob_User variable.
This was the reply I got from David Shorter at GS AUS.
This is the latest comment from Ed Brown of Graphisoft with a partial explanation.
Basically they are saying that it didn’t work properly (and couldn’t be made to work properly)
AC 12 IN 2D GLOB_USER_... variable will pass values between object in 2d in a random way.
It is dependent on which element runs first. This functionality will be phased out, since it is considered dangerous.
In 3D GLOB_USER_... variables can NOT be used to pass values between objects, since the scope of the variable is only within the individual element.
AC 11 and earlier GLOB_USER_... variable could be used, but the order was not guaranteed
Unfortunately it seems you will need to find another way of doing what you want.
I had to change all of our door and window objects as they would not display in 3d because they couldn't get the Glob_User values.
Fortunately for me it was a fairly simple change in the script to call the value directly from the other object rather than pass it through a Glob_user.
Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11