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.

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.
