Hi,
two-parts:
Minor bug.
The layer colors in Plan view Styles//Attributes//Basic//Layer are incorrectly distributed.
How can I define plan view line color ByLayer? This does not seem to work.
[model via worksession]
I emailed the files in question.
I’ve noticed the bug too. It happened just in the last update or so.
@Toni_Osterlund, @arcus the bug with the proper Layer order/assignment has been fixed in the next 3.9.1 update that will be published tomorrow.
This option has not been considered so far. Which Layer would you expect to be? the Layer where the plan view is? or the Layer of each object?
In fact, the View overrides are aimed at choosing one attribute or another to replace objects color (or any other attribute). If you want the objects to be displayed by their Layer color, you can set that directly to the objects, and do not rely on the View overrides.
Hi @fsalla,
I expected it to be on the layer where the plan view object is. My expectation was that I could override the object-based colours, and give the plan view a unified colour based on the layer it resides. The objective was to create a grey ‘background’ info plan view, and then a black ‘main’ plan view on top of that with the meaningful information.
I am aware that I can create this via style overrides (or object colours), but I assumed first that I could have a single style, and control the colour via layer colour.
…And as we are on the subject, in-house discussions led me realise a shortcoming in the current system. So, here’s a suggestion on improving the ‘plan view’ / ‘section view’ functionality.
Currently, the plan view is generated based on the layers and objects that are visible at the time of update. If I need to create varying views of the same model, I need to carefully manage layer states and _vaUpdate each corresponding view. Case example, facade elevations showing the 1) structural layer and 2) final layers as two separate views. If something is updated in the model, I need to revive the layer states and carefully update. The views are easily messed up, if not being careful.
Suggestion would be, that a ‘view’ object could alternatively contain the information about the layers it should show. For instance, one could define in the style settings, or object settings, the layer combo that result will be based on. This way, the update would be easily managed, and less error-prone.
@Toni_Osterlund @arcus I confirm the issue of the Layer order/assignment has been fixed in the recent VisualARQ 3.9.1 update: Update - VisualARQ
Hi @fsalla
I’m struggling with Overhead linetype scales on a plan view.
These are “Projection with Overhead” beams.
This is what it looks like in Model space.
The same location in 1:100 detail.
It’s not disastorous, but I cannot comprehend, why it’s different and where to control that..?
Hi @Toni_Osterlund the Overhead display attributes can be edited from the Document Properties > VisualARQ.
There you can select the linetype and color, but the scale of it is taken according to the corresponding Linetype settings in the Document Properties.
In VisualARQ templates, the Overhead representation is set to “Hidden” linetype by default, which has a Model space scale factor of 50, and 1 in layout space. For that reason you may see it tinier in the page layout.
@fsalla Perfect, thank you!
With all the options to adjust line’s visuals, I would not have thought about looking at the options page.
I have to admit I have lost understanding of Rhino linetype scales and section whatnots somewhere between 5-8, when they got more options.
I agree. Everything related to the scale factor for text, hatches, or linetypes in model space and layout space is a tricky / messy topic.
