Hello all. After the latest update, my rhino has a lots of bugs. It is getting very frustrating to work with it, although it was my main and favorite software. Maybe I can download older version somehow?
Hi Arminas -
Which version did you update from?
In the version that you are running now, please run the Rhino SystemInfo command and copy-paste its output here.
Can you give any information at all about the new bugs that you are running into? Start with the one that gives you most grief.
-wim
Hello,
Rhino 8 SR29 2026-3-4 (Rhino 8, 8.29.26063.11001, Git hash:master @ bbd126f84fcdaf7a974615b7c9f4f8667571c147)
License type: Commercial, build 2026-03-04
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 [100% battery remaining]
Hybrid graphics configuration.
Primary display: AMD Radeon™ 880M Graphics (AMD) Memory: 1GB, Driver date: 1-28-2025 (M-D-Y).
Integrated accelerated graphics device with 5 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce RTX 5070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 3-24-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 572.90
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: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-24-2025
Driver Version: 32.0.15.7290
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8151 MB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”
- Does not find center, mid or other points (everything is enabled).
- DupEdge creates weird lines (working with parametric/solid polysurfaces).
I have just tried to recreate the problems and make some printscreens, but it looks normal now.. Maybe this was something weird with the file itself…
Please post a Rhino file, not just images. Is your object by any chance very far from the origin?
Post. A. File. You’re not giving anyone enough information to even begin to help.
What else do you need? I can not upload the file, it’s my clients and it’s confidential.
There’s no way to diagnose a problem from your images without having the file. If you can’t upload it here, upload it to tech support via the website here along with an explanation of the steps to reproduce the problem and reference this Discourse topic.
Or, create/upload another non-confidential file that you created that illustrates the same problem.
Are you far from the origin (0,0,0) or outside the grid?
In that case, consider staying inside the grid or downscaling 10:1 or upscaling 1:10 if it is too small.
Just export a few of the surfaces that causes a reliable, repeatable issue and you are fine. A few surfaces are not confidential if they can’t reveal anything secret.
What software was this created with and have you scaled them after import?
@Arminas_Pauliukas How far from the Rhino world origin, not a local Cplane origin? Calculations in Rhino use the world coordinates, not the local Cplane coordinates?
The location of objects relative to the grid is irrelevant. The grid is centered around the Cplane origin which can be very far from the world origin. The size of the grid has nothing to do with any geometry or display calculations.
In that case, I isolate the surfaces with the problem and upload them.
I only upload the intersection of the surfaces. I isolated the issue and uploaded just a little piece. Then I double-check that the issue is triggered in the new file. That works fine.
For the isolation, I trim the surfaces and shrink them to reduce their size and CV information. So I do not spoil how the entire surface is done. I added a bug file number. This lets you and others track the bug.
Humm… Looks like a precision issue.