Hi there - I can not figure out the Section View Style Overrides and would like to know if they are bugged or I am doing smth. wrong?
I am working mostly with Blocks inside Blocks so if this is the issue we know the culprit and I won’t be able to use the feature - if not:
The Section Hatch Pattern Colour Override to “By Object” only respects the colour of the top level block with the highest hierarchy - in addition it does not use the Object Colour of the Block but uses its Layer Colour.
What I want to achieve: I want a Override that respects the Objects Colour is it custom or defined by the layer and creates a Section with one universal hatch but different colours. Right now I can only achieve this by changing the Layer-Section-Styles but this is not practicable there I want to have a more fine control for the Section Style with NO override.
In the picture the TOP Section Style is with the override and the bottom is without.
the second picture is what I want to achieve with the override. (by not touching the Layer-Section-Style)
In additon the Override does not work for “Print Display ON” at all whereas this is crucial for a clean workflow.
@fsalla I was not able to find information with a quick-search on the forum maybe you can help me.
after trying out some stuff and delving deeper into using visualarq professionaly - I found another bug, this might have been reported but I am unable to find the thread.
when changin properties of a visualarq element, not by object but by layer for example - the clipping plane / section / level does not update the change - it only updated after a restart of rhino.
in the picture you see the 3d model but by the level manager, all is green - but the wall properties are different as you see in the second picture with the planview
I tried to reproduce the issue, but everything works fine on my end. When I change the section style attributes on a layer, the walls update the section display instantly.
Maybe I’m not running the right tests, or I might be misunderstanding the problem.
I’m using VisualARQ 3.8.3 in Rhino 8. Which VisualARQ and Rhino versions are you using?
@enric hmm strangely enough I can not reproduce this behaviour right now - I updated the graphics drive, but would not assume that that was the problem.
If I come across the bug again - I will keep you updated
Hello @enric Maybe this is the same problem, but slightly with a different appearance.
I am testing arround what configuration/settings of the visualarq elements seems to be the best and the most flexible - in the end I think getting all the configuration from a per layer - basis is speed and depth wise the best solution (even if we still can not control the hatch line width of sectionstyle when they are on a per layer state for the visualarq elements - hopefully this will get integrated soon)
anyway - in my previous pictures, the walls got most of their settings on a per layer basis although the sectionstyle was set to solid, with a fixed lineweight - the rest again, came from the layers / by projection which was set to by layer.
right now I switched back to “all by layer” because I need to speed to change stuff in the layer-panel (or by scripting) even if I (for now) lose the abillity to the the sectionstyle (hatch) boundary width.
long intro - now my problem: (picture1) you can see that the wall incorporates the section style pattern, but in the 3d view, cut by a level it uses the color of the wall (green) and not of the wall layer which is set (for example yellow = insulation)
on the other hand - when I use va-planview or export the layout via vaexporttodwg the colors are correct. In addition I am not sure why the plan in 3d (cut by level) shows a solid hatch underneath the hatch.
picture1: (wrong hatch color of the insulation: should be yellow)
PS: is there a way to configure spaces witch a semi transparent hatch? I like the idea of spaces and I know I could hide and unhide them by layers, but I think if we could set semi transparent hatches it would help with modelling - a hatch has always the problem that you can’t see whats under it, thus can be cumbersome while modelling
@Sebastian_Wimmer i am almost at exactly the same boat, both advocating the per layer workflow and making very similar choices like the ones you present, regarding per layer setup with the drawback of not controlling boundary and hatch plot width and getting mixed color preview results.
i hope these issues will get sorted out in version 3.
after some examination - I guess the displaycolor of the “wall layer” is funky because rhino does not really know what setting it is on, because the SectionSytle Dialogue in the LayersPanel, does not have a “ByLayer” setting. But I guess this is already known.
The main reason / hope why I am currently working on this is A) obviously to get better control in Rhino and B) because I stumbled into Rayon last week, which could be a nice graphical-editor for presentation plans (unfortunately non linked / associativ) → for the final touchup. I am currently working on methods to prepare the rhino export / planview with scripts / general workflows in a way that Rayon can read out most of the information and changing elements is fast (blocking same lines per element and so on)
working on something similar i found that Vaplans and sections are somewhat better exported to vectors compared to live plans and sections exported from layouts to dwg.
But my effort to automate the process with lines to polylines routines (for same layer, type objects), multiple geometry to block etc, sooner or later stumbled upon this bug, which persists to this day.
best,
alex.
ps. rayon seems very interesting, thank you for sharing it.
I mostly work in regular shaded, and only switch to wireframe or ghosted via a hotkey for certain obscured selections - otherwise complex models get crazy complicated to read.
I did not think about that shaded needs to render the surfaces - of course the bottom surface of the wall has a colour as I look “into” the wall - my bad.
