its the erratic nature of the error thats foxing me. i could potentially go around it by using grasshopper preview to have them show up and turning off the layer they are on- but before i do that i wanted to check if this is a bug or just me.
Thanks for confirming that.
Could you post a minimal 3dm file that illustrates the issue?
Also, are you up-to-date on your Rhino and VisualARQ versions?
-wim
okay now it does. very wierd. I rebuilt all of the elements around the offending spaces and it works fine now. (i.e they print correctly)
The bug that remains (francesc just addressed that) however is another one that i think i posted on a separate thread- the spaces detect boundaries from floors above and below. I have bypassed this problem temporarily by moving them away from each other.
thanks @fsalla. FYI I am unable to ‘sendtoback’ for the spaces while printing, so they end up hatching/colouring over objects like stairs in top view - i havent been able to subtract my stair from the space by using the elementunset command yet.
Hi Aditya,
We will revise the problem of “sendingback” the space pattern below the other 2D geometry in plan views.
Regarding the other issue, you need to use the vaSpatialObjectSet command (not the “unset” one).
I’ve tried it on your file, using a rectangle as new spatial object set, and it works fine. If it doesn’t work for you, please send me the model with the geometry involved.