topic Re: ac_toplevel / ac_bottomlevel and all relevant stories in Libraries & objects

ac_toplevel / ac_bottomlevel and all relevant stories

Anonymous — Mon, 14 Feb 2011 11:24:24 GMT

Hi!

I've read some threads about this.

In parameterscript I set ac_bottomlevel = Z~ and ac_toplevel = Z~+ZZYZX, so far, so good.

But,
Lets say I put my object on story 1, bottom and top are above story 1 but under cutlevel and under story 2.
Then change Show on story : all relevant stories, then my 2d part of my object are visible on my topfloor only, +18000 up, but my 3d is on right place, regardless of my "Floor plan cut plane" settings.

Is this the bug you are talking about in earlier thread about this or what goes wrong?

Regards Tobias

Re: ac_toplevel / ac_bottomlevel and all relevant stories

David Maudlin — Mon, 14 Feb 2011 13:14:08 GMT

Tobias:

See this thread, it may help, one of the developers chimed in:

All Relevant Stories for ArchiCAD Objects?

David

Re: ac_toplevel / ac_bottomlevel and all relevant stories

Anonymous — Mon, 14 Feb 2011 13:27:21 GMT

Thanks David, but I've read that thread and done the tip they talk about their.
My toplevel and bottomlevel are showing right value, even zzyzx, bottomlevel are = Z~ and toplevel are bottomlevel + zzyzx like I wrote above.

The problem is that the object start acting weird then I turn all relevant stories on. Even with normal setup in floor plan cut plane the objects shows only on topfloor even if bottomlevel and toplevel of object are on homestory of the object. And that story are 18 meters under topstory.

Parameterscript :

PARAMETERS ac_bottomlevel = Z~
PARAMETERS ac_toplevel = Z~+ZZYZX

Do I need to do some changes of my 2d script code?

Re: ac_toplevel / ac_bottomlevel and all relevant stories

Anonymous — Wed, 16 Feb 2011 21:37:42 GMT

Hej TurboGlider,

I think this should work, hoppas det fungerar.

!--new length type parameter 'gs_cutplane_height'
!--the item height is zzyzx

!--master script
eps= 0.001
gs_cutplane_height = GLOB_CSTORY_ELEV - GLOB_HSTORY_ELEV - GLOB_ELEVATION + GLOB_CUTPLANES_INFO[1]
parameters gs_cutplane_height= gs_cutplane_height

!--2D script
if (GLOB_CUTPLANES_INFO[1]+eps)>=0&(GLOB_CUTPLANES_INFO[1])<zzyzx then

!--we're cutting thru the item

else

if (GLOB_CUTPLANES_INFO[1]+eps)>0 then

!--we're cutting below the item

else

!--we're cutting above the item

endif

endif

Re: ac_toplevel / ac_bottomlevel and all relevant stories

ztaskai — Fri, 25 Feb 2011 11:54:16 GMT

Hi,

No wonder it works in a weird way. ac_toplevel and ac_bottom_level start from the object origin of the object. So when you use the SYMB_POS_Z global variable in them, you trigger their duplicated usage!

In a normal standing element the parameter script can be this simple:

PARAMETERS ac_bottomlevel = 0
PARAMETERS ac_toplevel = ZZYZX

In a hanging object/lamp the parameter script should contain this:

PARAMETERS ac_bottomlevel = -ZZYZX
PARAMETERS ac_toplevel = 0

And so on...

Regs,
Zsolt

TurboGlider wrote:
Thanks David, but I've read that thread and done the tip they talk about their.
My toplevel and bottomlevel are showing right value, even zzyzx, bottomlevel are = Z~ and toplevel are bottomlevel + zzyzx like I wrote above.

The problem is that the object start acting weird then I turn all relevant stories on. Even with normal setup in floor plan cut plane the objects shows only on topfloor even if bottomlevel and toplevel of object are on homestory of the object. And that story are 18 meters under topstory.

Parameterscript :
PARAMETERS ac_bottomlevel = Z~
PARAMETERS ac_toplevel = Z~+ZZYZX
Do I need to do some changes of my 2d script code?