Hi again!
I’ve been updating VisualARQ, and I guess this started happening in one of the latest releases.
The Section View is no longer generating hatches correctly. As you can see, I have a single clsoed polysurface, but the Section View only hatches some of the wall segments where the cutting plane passes through, instead of all of them.
Has anyone experienced this or knows how to fix it?
Any suggestions would be greatly appreciated. Thank you!
ERROR SECTION VIEW.3dm (20.5 MB)
Hi @mutarq I’ll forward this case to the development team. I’ve realized that if you break down that polysurface into smaller parts, the hatches appear in the section view.
Thank you for looking at this @fsalla ..
it is for sure something that happend in the latest updates.. either from from VIsualArq or Rhino itself.. because I have some drawings from a month ago and the sectionviews were working correctly
Hopefully you’ll find a solution or maybe I can dowgrade to rthe previous version.. becasue it si very time consuming to split all the polysurfaces where this is happening.
Thank you
Hi again,
Well, I just noticed that now the Section Views are also having issues maintaining the consistency of the section style.
As you can see, I configured this style so that anything not being cut by the section plane should be displayed in a very light gray with a very thin lineweight. Currently, it even fails to do that.
I’m attaching both a previous version of the same drawing and the current version so you can compare the results.
CORTES PREVIOS.pdf (208.8 KB)
CORTES_ACTUALES.pdf (208.7 KB)
By the way.. this is my current system information… unfortunately I have not tracked in which release of Rhino and VisualArq things were working fine…
Rhino 8 SR33 2026-7-7 (Rhino 8, 8.33.26188.13001, Git hash:master @ 482f88a83547c62cde64d78ea8a8690b7349f289)
License type: Educational, build 2026-07-07
License details: Cloud Zoo
Windows 11 (10.0.26200 SR0.0) or greater (Physical RAM: 31GB)
.NET 8.0.14
Computer platform: LAPTOP - Plugged in [96% battery remaining]
Hybrid graphics configuration.
Primary display: AMD Radeon™ 780M (AMD) Memory: 1GB, Driver date: 6-27-2023 (M-D-Y).
Integrated accelerated graphics device with 4 adapter port(s)
Integrated accelerated graphics device with 4 adapter port(s)
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: 6-11-2026
Driver Version: 32.0.16.1062
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:\Users\mutar\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\D5LiveSync (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\D5Conv.rhp “D5 Live Sync for Rhino”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Lands.rhp “Lands Design”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Common Files\McNeel\Rhinoceros\8.0\Plug-ins\Bella (813de3fb-18eb-405f-bfcd-b0b4d3da91fb)\25.3.0.0\bella_rhino.rhp “Bella” 25.3.0.0
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.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 8\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.33.26188.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.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\export_PDF.rhp “PDF Export” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\BlockEdit.rhp “BlockEdit” 8.33.26188.13001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”
C:\Program Files\Rhino 8\Plug-ins\NamedPositions.rhp “Named Position”
Hi @mutarq I could verify that this issue with the polysurface appeared in VisualARQ 3.9 update. We will try to fix it as soon as possible.
The other issues you report in the PDFs might be related or not. I may require the 3dm files as well to check it out.
@fsalla please let me know if you need the file
@mutarq Yes, please. Send me the files so I’ll test that as well. You can send them to visualarq@asuni.com
Hi @fsalla I sent the file few days ago to that email
Hi @mutarq,
The issue where 2D Section View didn’t show section hatches of a polysurface has been fixed.
You can download the latest VisualARQ version here: