Opening Objects - should be kept or not as separate va objects?

The visualarq pipeline does not have openings elements as input type.

Also in the ribbon of VA the openings are missing.

They only are accessible from the Visualarq menu.

Do we need VA openings as separate objects from windows? Or should they are children of Windows?

BIM-IFCwise, which is the standard about opening?

If the va openings are going to be kept, the incosistences should be fixed IMO. Otherwise they should be removed and their functionality should be replaced from Windows objects.

Also the opening deconstruct does not work at all, and also it’s incosistent compared to windows and doors deconstruct components because the host walls output does not exist. I believe that a pass through all VA gh components functionality and consistency should be done, in order to fix the whole set of components incosistencies.

@GabrielB We may “kill” the opening object in future versions, since you can achieve the same result with a window object. Once this is done we will remove the corresponding components in Grasshopper.

By the way…

I don’t recognize this “DeconstructOpening” component. Is it VisualARQ’s?

The one to deconstruct an Opening works fine and it should look like this: