Wishlist: Option to "Disable" Walls (or VAObj interacting with the Scene)

Problem: Making different versions of the same file (with or without specific elements like walls or windows), without saving a new file or duplicating the Building. There should be a way to keep elements in layer but stop their interaction (booleans) and just hide them.

Solution 1: A “Disable” checkbox in VAObject Properties. It should be available in any type of VAObject that interacts with the Scene (uses Booleans or other interaction).

Solution 2 (can work alone or as a second checkbox, together with Solution 1): A “Disable when Hidden” Checkbox, on all the aforementioned objects. When enabled, it will remove from the solution any VAObject that becomes hidden by it’s Rhino Layer. Hiding by isolating or Hide command it is better avoided.

What are your thoughts on it? Any other Solutions?

Hi @flatform,

We already have a feature in our to-do list to save versions of a building in the same file. We haven’t discussed how this will be made technically but the idea is that you can quickly change from one version to another, so I think this feature should have its own interface.

1 Like

A much simpler implementation that I would like to happen is to stop interaction (or cleanup as it is called in varq between walls) between visible varq layers with the hidden ones.

Something as simple as disable auto booleans between the layers “Walls _ option1” and “Walls _ option 2” or disable auto booleans between walls and columns etc

So a seperate feature for design options is not necessary.

Not everything needs to be complex.

Idk if this helps, but just putting out what I have in my mind @alfmelbev @fsalla

PS. Design options in revit is a madhouse and imo don’t want the same thing to happen in varq. It destroys the simplicity of this tool imo.

1 Like

Hello! Some years ago I asked if you could implement something like ArchiCAD’s intersection groups to solve this problem. It’s simply an index per object , and only objects that share the same index are taken into accound in the intersecting algorithm.
Setting the index to 0 in ArchiCAD means, these objects won’t intersect at all - which is practically the same what @flatform is asking.

Obviously ArchiCAD implements this index on a per-layer-basis. Not sure if new parameters per layer can be added in Rhino, but per-object would be fine, too.


Very nice to hear. As other people mentioned here, in some cases (this may be one) simplicity can be the best choice.

As an end user hiding things and keeping our own structure when versioning is intuitive and useful enough. So, for starts, or as an option, allowing for “disable inetraction when hidden”, sounds very compelling and easy to implement.

Looking forward to any solution on the subject anyway.

Keep up the good work.