Plan View Style - Incorrect hatch color when printing

VisualARQ
1

Hello,

Unsure if I have found a bug or am missing something,

20251206_Hatch Bug.3dm (5.0 MB)

When using the plan view command with a plan style that makes the hatch a specific color, in this instance red, the hatch color displays correctly (bug is for pattern line hatch) but when printed it just comes out black, can even check with “print display on” to see…

This is using a plan view and plan style.

image
image861×1917 47.2 KB
plan style view overrides pattern color set as red

image
image1811×1658 96.5 KB
normal display shows pattern as red, correct.

image
image1938×1809 101 KB
print preview and exports show pattern as black, incorrect.

3dm attached, if you switch print display on you will see what I mean.

Thank you as always,

Lourenco

PS: I have moved to a new studio, and am testing VA for our workflows and potentially getting a few licenses to get the studio started, I couldn’t find a thread regarding the floating licensing model and how it works for VA, is there an email I can contact with our questions?

Essentially, hypothetically if we buy 2 floating licenses and there are 3 rhino users, is there a way to choose who uses the license? or is it first come first serve?

2

Hi @lourencovp you are right, the hatch pattern in the plan view should print in red color. We will fix this issue in one of the next updates.

You can manage the VisualARQ license from the Rhino accounts, and run it in Cloud license mode. You can create a Teams in the Rhino accounts, so you can grant access to the VisualARQ licenses to different users, and view who is currently using them. The first person to load VisualARQ when using Rhino will be the first one to use the available licenses.
If you have further questions about this topic, you can write us to visualarq@asuni.com

3

Hello @fsalla, any updates on this issue?

Just updated VA & Rhino to the latest version and the bug is still present?

Thank you!

4

Hi @lourencovp no updates about this issue yet, unfortunately. I’ll keep you posted.