VisualARQ 3 - Incorrect Draw Order of Clipped Objects in Section Drawing

VisualARQ
,
1

Hello,

It seems VA or Rhino are drawing the wrong lines to be on top in a sectioned plan?
Meaning the clipped geometry lines are being drawn below the projected ones, at least that is my understanding.

The problem at hand is the cut line of my mullions on my awning windows that are behind their gray lines (projected).

Any thoughts on this?

image
image1995×1458 64.9 KB

PrintDisplay “On” on layout shows correctly

image
image1744×1366 47.4 KB

PDF print, Vector at 600dpi results in confusing lines and draw orders. this happens for both plans and sections on my test. :expressionless_face:

Sharing the 3D model where you can see the problem.

Let me know if Im missing something here…

Thanks,
Lourenço

FILE HERE:
VA Draw Order Bug.3dm (4.2 MB)

Also, small comment. every time I paste a VA object to different file. if that file has the VA Standard layers inside a sub layer, and then object gets pasted into another empty va file, it just resets all the VA object attributes and moves them to the standard template VA layers, I have never heard of copying an object into another file and it not sticking to the same layer (the correct layer gets copied but its empty)?

System Info: Rhino 8 SR20 2025-6-3 (Rhino 8, 8.20.25154.13001, Git hash:master @ 9c56e48aaab3834802c90f657a77687be5693a6f)
License type: Educational, build 2025-06-03
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 16GB)
.NET 8.0.14

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3060 (NVidia) Memory: 12GB, Driver date: 4-12-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 576.02
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-12-2025
Driver Version: 32.0.15.7602
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 12 GB

Rhino plugins that do not ship with Rhino
C:\Users\loure\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\D5LiveSync (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\D5Conv.rhp “D5 Live Sync for Rhino”
C:\ProgramData\McNeel\Rhinoceros\8.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino8.rhp “Datasmith Exporter” 5.5.4.0
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.20.25154.13001
C:\Program Files\Rhino 8\System\netcore\export_PDF.rhp “PDF Export” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.20.25154.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

1 Like
2

Hi Lourenço,

Thanks for the detailed explanation and for sharing the file.

Regarding the first issue with the draw order in sectioned plans, you’re right — this seems to be a bug. I’ll report it to our bug tracker, and I’ll keep you updated once it’s been fixed.

As for your second comment about VA objects being pasted into a different file and losing their attributes or layers: I didn’t fully understand the situation. To help you better, could you please send me a file where this issue occurs, so I can test it directly?

Thanks again for your feedback — it’s very helpful.

1 Like
3

Hi Melissa,

Thanks—that’s great news! Do you have an estimated timeline for the bug fix? At the moment, I’m unable to export a clean set of drawings because of it.

Regarding the second issue:
To illustrate the problem, imagine the VA layers have been reorganized—say, grouped under a single layer named “VisualARQ.” If you copy and paste a window (along with the wall it’s attached to) into a new VA template file—making sure units match—you’ll notice the red cut line reverts to the default black.

On inspection, the awning window appears to lose all its custom parameters, including layer assignments for each geometry and its “Section Style.”

In the attached image, you can see how both the layer and section style revert from their previously set values to whatever the VA system uses by default.

image
image1209×1048 92 KB

I hope that was clear?:slight_smile:
Thank you,

Lourenço

4

Hi Lourenço,

Thanks for clearly explaining the issue.

At the moment, I don’t have an estimated timeline for the bug fix. I understand how important this is, and I’ll let you know as soon as I have any updates from the development team.

Regarding the second issue, I tried copying a customized window into a new file on my side, and all the custom settings—like layers and section style—were kept correctly.

Could you send me the file where you’re copying the window and the custom settings are not being preserved? That way, I can check exactly what’s happening and help you better.

Best regards,
Melissa

5

Hi Melissa,

Its the same file I shared above

Thanks!

6

Hi @lourencovp,
When you copy an object from one file to another, if the style already exists, the layer attributes and style attributes in the target file prevail.
This is the expected behavior. And it works also this way with Rhino geometry.

If this is not working for you, can you indicate in the model you attached, which object are you copy and pasting, and also provide the target file were you are pasting it? (Or prepare two files that we can use to reproduce this error). That way we can try to reproduce any errors.
Thanks!

7

Hi Melissa,
Any news on the main printing bug?

1 Like
8

Hi @lourencovp
We’re still working on it — I’ll let you know as soon as I have an update.
Best,
Melissa

2 Likes