"Section Style" - Boundary - Width Scale | Unintuitive

Hello Rhino team,

Can we please change the “Width Scale” property under the layer “Section Style” into a normal property like “Print Width” instead of a multiplier like it is currently?

Why you may ask?

Because if one is setting drawings from a rhino view, it would be expected to be able to control the exact thickness of the cut line of a 3D object just like you can with normal projection print width.

Also this multiplier has also created issues with VA objects where it simply doesn’t register when exporting a pdf.

See last entry on this post: VA Object by Layer Section Style Bug - #6 by lourencovp

Or is there some smart reason on why its a scale/multiplier set up as is and I’m totally missing it?

Or perhaps have a “Display Scale” and a “Print Width”?

Thank you,

Lourenço

1 Like

HI Lourencovp,

We are looking to improve this in Rhino 9.

At the moment you can create a custom linetype for the boundary that is set to units & scale to 1.

2 Likes

Hi @Japhy thank you, I was not aware of this option!

I hope R9 comes soon then!

(Unfortunately I just checked the custom line weight for Boundary and still doesn’t play well with VA)

Other question, regarding printing in vector. Will there be a rework on the vector printing as a whole?

Currently the quality of the vector lines and more importantly the thickness is decided by the “Resolution” set which makes working and setting with mm thickness lines a very confusing affair as we are never sure how its going to look printed and depending on which computer used the resolution might be different (due to exporting jpegs diagrams etc.).

Which is odd as the whole point of vector is that its accurate and doesn’t have “pixels resolution” in it… and the results should be dependable no matter who prints the final set.

Let me know!

Thank you as always for all the hard work the team puts into Rhino

Lourenço

So there are a lot of issues here. I understand the request to use the mm for section style property.

i think in V9 we are trying to get away from resolution vs actual print width. V9 WIP is worth a try, today if you would like to see how it works.

Do you have examples we can add to our test suites?

3 Likes

Hi @scottd Im unsure if the problem is Rhino or VA or both together.

But currently something as a simple as a section boundary thickness in a vector printed pdf, simply doesn’t work. I really don’t think this is something that should be pushed to R9 as it is a fundamental basic operation in any CAD software that should just work…

Hopefully im just missing some simple solution but im starting to feel like im not.

See this separate post for file images/3D and explanations on my reply dated 2025/09/28

@fsalla

Let me know!

Hi @lourencovp as I’ve explained in this post, the “Width Scale” attribute in the Rhino Section Styles dialog, acts as a multiplier of the object’s Print width, but it’s not suitable for an accurate control of object’s print width in section, specially if your object has a print width set to “Hairline”.

Instead, you can use the VisualARQ’s “Print Width” attribute, at the Section Attributes section, in Rhino properties panel:

Also available in VisualARQ Object Styles dialog:

Hopefully McNeel developers implement this attribute also in the Section Styles dialog:

Hi Francesc,

Thanks for the clarification, I’ll follow this workflow moving forward. Apologies for the confusion earlier; it’s been a long year working with Autodesk products :face_vomiting: , and I’m eager to transition fully to VA. I didn’t quite grasp it the first time, so I appreciate your explanation.

Personally, I find organizing by layer more efficient. It allows me to control section and projection qualities for all elements tagged as “Concrete” in a single dialog. This includes various slab types and potentially even structural walls. In contrast, the current setup requires repeating the same settings across multiple instances of the same material. If anything changes, those adjustments have to be made individually for each element type, which can be quite tedious. That said, if the current method works well in practice, I’m happy to go with it.

Also, I understand the issues you mentioned stem from Rhino, not VA, I just wanted to make sure that distinction was clear.

On a separate note, regarding the print order of lines: I suspect this isn’t a VA issue either, but perhaps you’re aware of a workaround. Before printing, the line order appears correct, but once printed, hatches and various projection lines end up on top of the section line, which should always remain dominant.

What do you think?

1 Like

I agree. I hope McNeel can implement the Section Boundary “Print Width” in the Section Styles dialog, so you will be able to control the Print Width of objects by Rhino Layers.

Correct.

This is something other VisualARQ users reported already. We are waiting to revise this issue just in case we can help it from our side. I’ll keep you posted.

1 Like