Level double-click visibility should respect Sub-level hierarchy

Hi,

another thing regarding the Level/Sub-level logic. This is related to these previous discussions:

Should sub-levels operate like levels in terms of constraints?

Walls are not affected by sublevels elevation

Please check the attached GIF.

level-manager-sublevels

When I double-click a main Level to make it current, some Sub-levels that belong to that Level but have elevations above it are switched off.

Is this intended?

My understanding is that a Sub-level has an actual parent/host Level, regardless of where it appears vertically in the Level Manager because of its elevation. So I would expect the double-click behaviour to respect that hierarchy as well: if I activate L00, its Sub-levels should remain visible as part of L00, even when some of them are positioned above its elevation.

At the moment it seems that the visibility logic follows mainly the elevation/order rather than the actual Level - Sub-level relationship.

I also noticed that VA 3.3 included the fix #14720 – Do not switch off the sub-levels of other levels when doing double click on a level, so maybe this is another variation of the same issue.

I think this connects again with the broader point from the previous topics: if Sub-levels have a parent Level, that hierarchy should ideally be used consistently by visibility, constraints and the rest of the Level Manager behaviour.

Hi @GabrielB Yes, this is the intended behavior. The double click on a level automatically hides the levels and sub-levels above. This is specially useful in plan views, where you need to switch from one level to another in the top viewport . Imagine this case: you have a sub-level located at i.e 2.3 meters above a floor called “Level 1”, (for drawing the ceiling). If the double click on the “Level 1” did not hide the sub-level, you would see it in the top viewport, instead of that "Level 1.

If you just need to change the construction plane on a level, to make it the current one, you can just click on the CPlane icon next to the level.

The level-sublevel relation is used mainly to keep the relative elevations between them.

This bug was a different case. Sub-levels of other levels hid when doing doing double click on a level (even those located below the level were you did the double-click)

Thanks @fsalla I think I understand the distinction now. I actually haven’t been using the CPlane icon directly — I was mostly using double-click to change the current working level.

Just to make sure I understand the visibility logic correctly: if I double-click L00, and the next Sub-level above it is for example TOP-OF-STRUCT-PATARI150, does the visible Level range effectively become L00 elevation → TOP-OF-STRUCT-PATARI150 elevation, rather than L00 → the next main Level?

If so, this raises another question for me. The double-click behaviour is essentially the same for a main Level and a Sub-level: it follows the elevation order, regardless of their hierarchy.

Doesn’t this reduce the usefulness of double-clicking a main Level when it contains several Sub-levels used as reference elevations? In my case I use Sub-levels for TOS/BOS, ceilings, reveals, etc., so they are useful references, but I don’t necessarily want each of them to redefine the visible floor range.

Is the intended workflow in this case to use the CPlane icon for normal navigation/working elevation, and reserve double-click mainly for elevation-based isolation?

And more generally, I am also trying to understand how much meaning the Level → Sub-level hierarchy is intended to carry in VisualARQ. At the moment, from what you explained, it seems to be used mainly to keep relative elevations rather than as a broader BIM/project hierarchy.

I would have expected that hierarchy to potentially become useful for other behaviours as well — visibility, constraints, selection scope, object association, etc. Otherwise a Sub-level is mostly an elevation reference linked to another elevation, rather than a stronger child of a Building Level.

Maybe this distinction is worth looking at more holistically for VA4: what information a Level/Sub-level relationship should actually carry, and which parts of the model should rely on that hierarchy.

level-manager222

Yes, that’s correct, except when you enable the Cut plane in that L00. In that case, the visibility status of sub-levels located between that level and its cut plane elevation is ignored, and the cut is performed in the L00 Cut plane elevation. I know that this could be counterintuitive, so we may consider removing the visibility and cut plane status of sub-levels in future versions.

The sub-levels are meant to be used to add additional CPlanes to your workflow, and also as “horizontal” guides where objects can get attached to (through the constraints). And they keep their elevation in relation to the parent level.

Keep in mind that VisualARQ objects (or Rhino geometry), don’t “belong” to any level. There’s no attachment of objects to levels. They are simply located in the model space, and are coincident to a certain level or sub-level elevation. You can move them up or down freely without caring about in which level they were located or having to edit a parameter. When using the level Constraints, VisualARQ checks for the objects sitting/ finishing on a level, or located within that level and the next one, and moves/stretches them accordingly.

In terms of IFC, VisualARQ exports the objects with the Building/Level information according to their elevation.

What do you mean?

Hi @fsalla

What I mean is that the Level/Sub-level relationship could carry more BIM information than just relative elevations.

For example, an object could explicitly belong to a Building/Level, while its base and top could independently reference specific Levels or Sub-levels. This would make the relationship more predictable when changing elevations, editing constraints, selecting objects by floor, or managing visibility.

This is also closely related to what @badileanu recently suggested here:

Wish: Duplicate Level – Option to Include Objects

How would VisualARQ reliably identify which objects belong to a Level if this relationship is determined only by their geometric position? And what about objects spanning multiple floors?

I am not suggesting removing the current spatial/magnet-based behaviour. Ideally, we could have both: explicit BIM associations where needed, and automatic spatial behaviour as a fallback.

For example, a Wall could belong to L00, have its base constrained to L00/TOS_SLAB and its top constrained to L01/BOS_SLAB. Those are three different relationships, and I think keeping them separate would make the system more reliable and easier to automate.

This also connects with the selection scopes and wall/level constraints we have discussed in other topics.

Since VA4 is being developed, I think this would be a good opportunity to look at these relationships together rather than addressing each behaviour separately.

Hi @GabrielB All right! all these suggestions make sense and are aligned with what we have in mind. We’ll take these comments into account when we work on these improvements.

Hi @fsalla

One more related issue came up while developing a more automated documentation workflow. This time regarding some differences between the native Level Manager, commands and API behaviour.

  • vaSetView > Level works in a model viewport, but doesn’t seem to work the same way within an active layout detail.

  • Setting the CPlane elevation and enabling the Cut Plane programmatically seems to be working, but doesn’t seem to produce the same result as using the native Level Manager.

  • Using the Level Manager’s CPlane control and activating the Cut Plane manually in the layout detail produces the expected result.

  • GetVisibleLevels returns an empty list for that detail, while GetLevelVisibility reports L00 as visible.

I also noticed a possible documentation mismatch: Set Current Floor mentions unhiding upper levels, while your explanation above describes hiding them.

Could you check the above for controlling Levels and Cut Planes programmatically within layout details? Am I missing a particular initialization or viewport-context step, or are there limitations in the current API?

Ideally, the native Level Manager, commands and API should provide consistent and predictable results, especially for automated drawing production.

This also connects with the broader Native–Grasshopper–API consistency we’ve discussed in other topics.

Hi @GabrielB

I’ve just tested this. It works well on my end. Can you show an example where it doesn’t?

What differences there are?

A script that includes these commands should work in the same way in the model space than when you are inside a detail. It won’t work directly in the layout space, since VisualARQ commands don’t’ work there. Please provide an example I can test to figure out what’s happening.

You are right. The explanation is wrong. The Set Current Floor unhides the levels below the selected level and hides the upper levels. I’ll correct this in the Help.