Hi. A new feature in VA 3, Level States has some problem. It only configures On & Off. It does not configure Elevation, Height, Cut Plane Level, and Top Offset.
Thanks.
Hi @Steven_Kim that’s correct. The Level States has been developed to only save the on/off status of levels, but it doesn’t keep the cut plane or top/bottom offset values. We can consider this option for future versions.
@Steven_Kim just a question. Are you sure you want the Elevation be saved in the Level States?
Hi. Francesc. I tried using the Level States feature to switch the cut plane level between the floor plan and ceiling plan, as you otherwise have to change the cut plane value manually every time you switch between them.
Thanks.
Hi Steve, why don’t you use a sub-level instead? it will let you have a new CPlane on the desired elevation, and sub-levels have their own Cut plane.
Hi. I could not get correct a result for RCP by using sub-level.
This is correct result for RCP. Elevation : 2,3 m, Cut Plane : 0
However, If I use 0 m for Elevation and 2.3m for Cut Plane, I got a wrong result.
When I use sub-level for RCP, none of the configuration did not get me a correct 2D representation.
Test.3dm (11.7 MB)
Did I miss something?
I
Hi Steve, indeed, there is something now working properly with RCP on sub-levels. We will revise these issues and get back to you when we fix them.
@Steven_Kim We have fixed the issues of RCP for sub-levels in VisualARQ 3.2, which has been relased today: VisualARQ 3 - Version 3.2 released
1 Like
1st Floor_RCP is a sub-level of 1st Floor, which is the floor plan. It seems that if I want to use a sub-level for the ceiling plan, I have to switch to the ceiling plan view when activating the sub-level. Then, when I switch back to the floor plan (1st Floor), I need to change the view to the floor plan view again. Did I understand this correctly?
What I actually want to do is set the floor plan view to 1st Floor and the ceiling plan view to 1st Floor_RCP, as shown in the image below.
If this isn’t possible, switching back and forth between the floor plan and ceiling plan becomes very time-consuming.
Thanks!
Hi @Steven_Kim
Yes, that’s correct. You need to switch from “Set Floor Plan” to “Set Ceiling Plan” each time you want to change what you want to see in each viewport. You can have two views, each one showing a different level in plan / ceiling view. Or you can use the Level States to restore each level settings in the view.
I don’t understand how the Level States can solve this issue. As far as I know, Level States can only save visibility. It can’t save the view, can it?
I would suggest that the Level Panel should look like the one below in a future version.
Thanks.
Hi @Steven_Kim the level states are meant to be used as a quick shortcut to show the view with different level settings. So you could save a view where you see a sub level in RCP, and another state that shows a level in normal Plan view. So you can quickly switch from one to another.
However, after revising the level states behavior, I’m seeing it is not consistent with sub-levels, and also it doesn’t remember the position of the CPlane. I’ll let you know when this works better.
I take note of your suggestion to display levels, and RCP in the Level Manager. Perhaps we should have a different panel for that (“View Manager”, “Plan Manager”, or similar for that). We need to study it.
Maybe you can provide more details of how the “Finish” floor plan and the “structural” floor plan should look like. Would they have any difference in the way objects are represented, or would they be just to have two different elevations for their construction plane?
I have same issue. Level State can’t restore view on my side.
If the finish level and structural level are not distinguished, you will have to manually adjust the insertion level every time you place furniture or structural elements.
It is very difficult to adjust the position of beams and girders in floor plan view because their location cannot be identified in the current plan view. The locations of the beams and girders should be identifiable in either the structural plan (structure) or the architectural plan (finish).
Thanks.
Hi @Steven_Kim thanks for these details. We will study the option to implement a Structural and a Finish elevation for VisualARQ levels in future versions.
Hi, Francesc
I noticed an issue when using sub-levels for RCP. When I change the active level to a lower one, the upper level remains visible. As a result, even after switching to the lower level, the floor plan view still displays the upper level.
I tried to use Level State to avoid turning off the upper level manually every time I switch to lower level, but the problem is it can’t restore the activated level. As a result the activated level is not changed.
It should be able to remember activated level and whether the view is set to floor plan or RCP as well, right? Is there anything I missed?
Thanks.
Hi Steven,
So if I understand you correctly, if you have this situation in the Level Manager:
And you double-click on the “Basement” level, the 1st floor doesn’t hide, is that correct?
The Level States only saves the on/off status of buildings and levels right now. It doesn’t keep the CPlane position, the Cut plane status, or if you were seeing a level in RCP or in Normal projection.
That’s correct. Should I turn off 1st floor level manually whenever I switch to Basement floor?
If then, what’s the use of Level State? Didn’t you say that Level State can save view? I think it also should be able to save the activated level as well like Layer State of Rhino.
The first floor should hide if you double-click on the Basement level. We will revise this error.
They are used to save building and level on/off status. We need to study if we implement also the Cut plane and CPlane status there, or we just add a new “View Manager/Browser” to handle a list of level views.
Yes, please.
I feel that the bugs in VA3 have not been properly fixed. Whenever I receive a notice saying that errors have been fixed, I test it, but I almost always encounter another error. Please release a service update only after thorough testing. I would like you to be aware that reporting bugs also takes a lot of time for users.
Thanks.
@Steven_Kim we have fixed this issue in VisualARQ 3.4 RC1: VisualARQ 3 - Version 3.4 RC1 released