Rhino 9 Beta – VisualARQ display and selection issues

Hi,

I opened an existing VisualARQ project in Rhino 9 Beta using VisualARQ 3.12 RC3 and noticed several display/selection issues.

In Plan Views:

  • Section hatches/fills are missing from walls and columns.
  • In Hidden display mode, walls and columns cannot be selected, either by clicking or with window/crossing selection.
  • If I switch to Wireframe, the objects can be selected normally, but the section hatches are still missing.

Dynamic Sections also don’t display correctly in Rhino 9 Beta. Section hatches/fills are missing there as well.

The same file works correctly in Rhino 8: the section hatches/fills are displayed and the objects can be selected normally in Hidden mode.

The hatch definitions themselves seem to be fine, since they are displayed correctly in the VisualARQ Style Editor preview.

The Cut Plane is enabled.

Rhino 9 Beta:

Rhino 8:

SystemInfo

Rhino 9 SR0 2026-9-1 (Rhino 9 BETA, 9.0.26244.12303, Git hash:master @ 5007fbd7b46c04cee8e766232af7a8896598fb4e)
License type: Commercial, build 2026-09-01
License details: Cloud Zoo
Expires on: 2026-10-16

Windows 11 (10.0.26300 SR0.0) or greater (Physical RAM: 15GB)
.NET 10.0.2

Computer platform: LAPTOP - Plugged in [97% battery remaining]

Non-hybrid graphics configuration using DirectX
Primary display: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 7-22-2026 (M-D-Y). DirectX(11)

Integrated accelerated graphics device with 4 adapter port(s)

  • Windows Main Display is laptop’s integrated screen or built-in port

Secondary graphics devices.
AMD Radeon 780M Graphics (AMD) Memory: 1GB, Driver date: 12-5-2023 (M-D-Y).

Integrated accelerated graphics device with 10 adapter port(s)

  • Laptop’s primary display device

DirectX Settings
Safe mode: Off

OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY Cooperlake MAX_THREADS=64.

Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 9 WIP\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxRhino.9.rhp “3DxRhino.9”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 9.0.26244.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”

Update: I did some further testing and found that the major display and selection issues described above occur when Rhino 9 is using DirectX.

When switching Rhino 9 to OpenGL, VisualARQ works almost correctly again: the section hatches/fills are displayed and selection works normally.

There are still some issues with annotations in OpenGL, so the result is not completely identical to Rhino 8.

After updating Rhino 9 Beta to 9.0.26272.12303 (Sep 29, 2026), VisualARQ (Tibidabo.rhp) fails to load.

Hi @badileanu thanks for reporting these issues. Indeed, most of them are happening when using Direct3D GPU Technology. We will fix this.

Can you provide more details about this?

Try to reinstall VisualARQ for R9. If the problem persists, go to Rhino Options > plugins > (plugins that do not ship with Rhino), select VisualARQ, do right click and load it. Then restart Rhino. Does that work?

I already reinstalled VisualARQ for Rhino 9, but the problem persists.

I also tried your suggestion. VisualARQ appears as Tibidabo in the Plug-ins list. After enabling it and selecting Load plug-in, Rhino gives me this error:

“Unable to load Tibidabo.rhp plug-in: no class derived from CRhinoPlugIn in plug-in file.”

C:\Program Files\Rhino 9 WIP\Plug-ins\Tibidabo\Tibidabo.rhp

This is with Rhino 9 Beta 9.0.26272.12303 and VisualARQ 3.12 RC3.

SystemInfo update

Rhino 9 SR0 2026-9-29 (Rhino 9 BETA, 9.0.26272.12303, Git hash:master @ b5f5102690615c89acabfc68e24eae200f3d735b)
License type: Commercial, build 2026-09-29
License details: Cloud Zoo
Expires on: 2026-11-13

Windows 11 (10.0.26300 SR0.0) or greater (Physical RAM: 15GB)
.NET 10.0.2

Computer platform: LAPTOP - Plugged in [97% battery remaining]

Non-hybrid graphics configuration using OpenGL
Primary display: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 7-22-2026 (M-D-Y). OpenGL(4.6.0 NVIDIA 610.88)

Integrated accelerated graphics device with 4 adapter port(s)

  • Windows Main Display is laptop’s integrated screen or built-in port
    Primary OpenGL: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 7-22-2026 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 610.88

Integrated accelerated graphics device with 4 adapter port(s)

  • Windows Main Display is laptop’s integrated screen or built-in port

Secondary graphics devices.
AMD Radeon 780M Graphics (AMD) Memory: 1GB, Driver date: 12-5-2023 (M-D-Y).

Integrated accelerated graphics device with 10 adapter port(s)

  • This device is not being used

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: 7-22-2026
Driver Version: 32.0.16.1088
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8188 MB

OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY Cooperlake MAX_THREADS=64.

Rhino plugins that do not ship with Rhino
C:\Users\badil\AppData\Roaming\D5 Lite for Rhino\engine\D5Conv.Rhino8.rhp “D5 Live Sync for Rhino”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoAI\net8.0\RhinoAI.rhp “RhinoAI” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxRhino.9.rhp “3DxRhino.9”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26272.12303
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”

Hi @badileanu I’m facing the same issue. I could work with a previous R9 Beta version. We will investigate what’s happening as soon as possible.

Thanks for confirming, Francesc. Good to know the issue is reproducible on your side as well.
I’ll leave it with you for now.

Hi @badileanu we have just published VisualARQ 3.12, which should load fine in Rhino 9 BETA. You can download from the website: Update - VisualARQ

Hi @badileanu these issues have been fixed in VisualARQ 3.12 (when using Direct3D GPU): Update - VisualARQ

Hi Francesc,
I tested the final VisualARQ 3.12 build further in Rhino 9, and everything seems to be working correctly now.

I tested the model with both OpenGL and Direct3D, and it displays correctly with both, including the VisualARQ section hatches. Direct3D also seems to perform slightly better in this model.

So far I haven’t been able to reproduce the display/crash issues I encountered with the earlier builds.

Thanks for looking into this!

R.