I am not sure this is a glitch or just some settings I should change on the viewport mode…
Basically, when working with worksessions the section hatches (for VA objects) only show for the active model, in most viewport modes apart from: Technical, artistic, pen & monochrome.
See below images:
When I try to print a PDF it gets even more random… Even printing from a viewport where all hatches are visible it will show them only in raster output, in vector output the passive model hatches disappear again.
I am puzzled as I cannot understand whether it is a VA or Rhino issue and/or if I need to change any settings in order to sort this out.
Can anyone help on this? I can upload the example files if needed.
Hi @Luigi_S This is a bug. It seems like section attributes are not displayed properly on VisualARQ objects when they are assigned by style. (If you assign them by object they are displayed correctly accross worksessions).
I’ll let you know when we fix this.
Hi @fsalla Thanks for your prompt reply.
I tried to switch the section attributes settings as suggested (selecting “by object” in VA properties and then setting the section style to “custom” in the Rhino properties panel).
The above works in most view modes (apart from the ones I listed in my OP, where it was working with VA section attributes), but it doesn’t work with the VA 2D plan and sections, where the hatches disappear again.
I found a better temporary solution, which is setting the section attributes to “by layer” in VA properties and then setting the section style inside Rhino layers panel.
In this way the passive VA model shows correctly in all views and it also prints correctly in PDF (both in vector and raster modes).
The only issue I have with this is that I need to create sublayers in order to differentiate, for example, solid walls in RC from those in blockwork.
It is still acceptable as I use rhino worksessions to separate “existing site” model from my new interiors model, therefore I don’t have to change the first model often, once it’s setup.
Is it an issue that would be resolved in future updates of VA3 , or is it due to a “clash” between Rhino and VA properties that can’t be easily resolved?
