I played arround with templates the last few days and came upon a bug - which should get fixed.
When I want to assign a layer to a visualarq element through the dialogue the layers in the dropdown get mixed up - it seems some of the don’t open / collapse the right way and thus the order gets freaky. As you can see in the screenshot the DOCOpack strangely takes the color (and the properties) of the Walls and then the error begins to run through all the layers.
I have to try to uninstall DOCOpack an see if it works then but, in the end its layers and should not collide with a plugin?
Anyway this way assigning a element to a layer is not possible, even if I use the right name in the dropdown, in reality the properties are wrong.
Best regards,
Sebowim
@fsalla
enric
(Enric Marquès)
March 28, 2026, 11:02am
2
Hi @Sebastian_Wimmer ,
I’ve just installed DOCOpack and couldn’t reproduce the issue.
Which version of VisualARQ are you using? I’m currently on VisualARQ 3.8.3.
Could you send me a 3DM model that demonstrates the problem? Feel free to delete all geometry beforehand.
Thanks,
Enric
thank you enric, for your response - I just went into weekend mode, I will check when I am back.
best regards
Hello @enric , I uninstalled DOCO and the problem still persists.
As you can see in the picture (and in the file) I made a bunch of nested layers and put the on top of the layers list - then I went into the wall settings and there again, the layers are messed up.
Best regards,
SeboWim
Layer_Mess_Up.3dm (4.8 MB)
Rhino 8 SR30 2026-3-23 (Rhino 8, 8.30.26082.23001, Git hash:master @ abea9e77e9bb144e00d8281bfa44e613abd9d918)
License type: Educational, build 2026-03-23
License details: Cloud Zoo
Windows 11 (10.0.26200 SR0.0) or greater (Physical RAM: 32GB)
.NET 8.0.25
Computer platform: LAPTOP - Plugged in [99% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) Iris(R) Xe Graphics (Intel) Memory: 2GB, Driver date: 11-21-2024 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Secondary monitor is laptop's integrated screen or built-in port
- Secondary monitor attached to adapter port #1
- Windows Main Display attached to adapter port #2
Primary OpenGL: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 3-4-2026 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 595.79
> Integrated accelerated graphics device with 4 adapter port(s)
- Video pass-through to primary display device
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: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-4-2026
Driver Version: 32.0.15.9579
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8188 MB
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp "VisualARQ"
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp "Tibidabo"
C:\Users\sebow\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\InstantSKP\1.0.1\InstantSKP.rhp "InstantSKP" 1.0.1.0
C:\Users\sebow\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Bullant\25.10.9.8\bullant.rhp "bullant" 25.10.9.8
C:\Users\sebow\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\BlockEditNew\2.1.4\blockeditnew.rhp "BlockEditNew" 2.0.0.0
C:\Users\sebow\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\ggRhinoIFC\26.3.27.8\net8.0-windows\ggRhinoIFC.rhp "ggRhinoIFC" 26.3.27.8
C:\Users\sebow\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Prism\0.3.1.1\net7.0-windows\Prism.rhp "Prism" 0.3.1.1
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp "Commands" 8.30.26082.23001
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\RhinoRenderCycles.rhp "Rhino Render" 8.30.26082.23001
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.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp "Snapshots"
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp "MeshCommands" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp "IronPython" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp "RhinoCycles" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp "Grasshopper" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp "RhinoCodePlugin" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 8.30.26082.23001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp "3Dconnexion 3D Mouse"
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp "Displacement"
C:\Program Files\Rhino 8\Plug-ins\Calc.rhp "Calc"
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp "SectionTools"
fsalla
(Francesc Salla)
April 7, 2026, 8:46am
5
Hi @Sebastian_Wimmer , this issue should be fixed in the VisualARQ 3.10 RC1 update (VisualARQ 3 - Version 3.10 RC1 released ).
Can you check it out?
1 Like