Clicks sometimes not registering in shaded viewport

Rhino Rhino for Windows
1

For a while now I’ve been experiencing strange behavior when trying to select polysurfaces in the viewport. Quite regularly the clicks don’t register, unless clicking on an edge or isocurve. When clicking in between those, in some spots it will work, in others it doesn’t. When I move the viewport around, the locations where it will register, and where it won’t, will change somehow, but still stay in the same general area.
I’ve also just noticed that (in this case anyways) it happens when another object is intersecting the object I’m clicking on.

I have just moved to a new computer, and hoped it wouldn’t be the case anymore, but unfortunately it’s still happening. Result is that sometimes I’m clicking 4 or 5 times before my object is actually selected. It’s very frustrating and not helping getting past carpal tunnel.

Before I start shouting “BUG!”, I thought I’d ask first if it is perhaps a setting I am unaware of, that I inadvertently changed, and thus expected behavior

Attached a little screen recording of what happens, and a file that repeatedly has this issue on my system.

Rhino click issue.3dm (365.2 KB)

2

Hi Mark -

I’m afraid I can’t reproduce that behavior here.
Please run the Rhino SystemInfo command and copy-paste its output here.
-wim

3

Thanks for looking into it Wim.

Rhino 8 SR27 2025-12-23 (Rhino 8, 8.27.25357.11371, Git hash:master @ 4f7e78056cadbad051d03c30f40683a64dcc7a5d)
License type: Commercial, build 2025-12-23
License details: Cloud Zoo

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

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

Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 5070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 5-11-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 573.22

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 5070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 5-11-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 573.22

Integrated accelerated graphics device with 4 adapter port(s)

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

Secondary graphics devices.
Intel(R) UHD Graphics (Intel) Memory: 2GB, Driver date: 9-13-2024 (M-D-Y).

Integrated graphics device with 4 adapter port(s)

  • Secondary monitor is laptop’s integrated screen or built-in port
    DisplayLink USB Device (DisplayLink) Memory: 0MB, Driver date: 11-2-2025 (M-D-Y).

External USB display device with 4 adapter port(s)

  • Secondary monitor attached to adapter port #0
    DisplayLink USB Device (DisplayLink) Memory: 0MB, Driver date: 11-2-2025 (M-D-Y).

External USB display device with 0 adapter port(s)

  • There are no monitors attached to this device. Laptop lid is probably closed

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: 5-11-2025
Driver Version: 32.0.15.7322
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
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\GG_Progects_Manager\1.0\GG_Progects_Manager.rhp “GG_Progects_Manager” 1.1.0.0
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\GG_ToolBar\1.0\GG_ToolBar.rhp “GG_ToolBar” 1.0.0.0
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\Grasshopper_Gold_Tools\1.0\Grasshopper_Gold_Tools.rhp “Grasshopper_Gold_Tools” 2.0.0.0
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\ToolPanel\1.0\ToolPanelV2.rhp “ToolPanelV2” 2.0.0.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\SolidTools.rhp “SolidTools”
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.27.25357.11371
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\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.27.25357.11371
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.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\QuadRemesh\QuadRemesh.rhp “QuadRemesh” 8.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\MeshTools.rhp “MeshTools”
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.27.25357.11371
C:\Program Files\Rhino 8\Plug-ins\export_GHS.rhp “General Hydrostatics (GHS) Export”
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.27.25357.11371
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\SectionTools.rhp “SectionTools”

4

Hi Mark -
As a test, what happens when you disconnect the external displays and only use the laptop’s screen?
-wim

5

And the next thing to try after Wim’s suggestion would be to update your Nvidia driver. After that, if necessary, try disabling each of the plugins not shipped with Rhino one at a time to see if the problem is related to one of them.

6

I just noticed my main screen connected to HDMI isn’t shown in the log.
However, after disconnecting both screens, and restarting Rhino, the issue persists.

When opening the file I attached earlier, clicks aren’t registering on the red areas on the attached image. This is consistent and reproducible for me. It changes somewhat when I move the viewport.

I’ve tried AIW’s ideas as well: Latest Nvidia driver was already installed, and after turning off almost everything in the plugin manager and restarting Rhino, the issue still persisted.

7

Thanks for the input AIW. No luck thought. Latest drivers already installed. Turning off almost everything in the plugin manager and restarting Rhino also made no difference.

8

Hi,
I tried it in V7 and your supplied file worked as expected. But I see in your video at around 39.00 seconds and at the end you have another object/s in your file maybe that matters. Also before it happens I notice your mouse goes somewhere off the perspective viewport. It looks like you are doing that to show the cap object in lighter green. I tried the same but selection was fine. Don’t know if any of that matters just throwing it out there in case. Looks like your hardware is pretty beefy 5070. Maybe your mouse or mouse hardware?

RM

9

Thanks for thinking along. The attached file only contains the objects that mattered to show my issue. After exporting those 2 objects as a 3dm file I reopened the saved 3dm to make sure the issue was also present in the saved file with only the 2 objects, and it was.

Yes, mouse goes off the recorded part of my screen to turn on the layer that contains a cutter I intend to use for a boolean operation. The video shows there is no issue selecting the larger part with the cutter turned off, and when the cutter is turned on, it seems the clicks don’t register at certain points.

I don’t see it being a mouse driver or mouse hardware issue. The video clearly shows clicks being registered and executed by Windows by showing the yellow circle on each click. The problem also only exists within Rhino viewports. Not even in Rhino outside of the viewports.
It almost seems to me that it has something to do with how the part is intersected by another part.

10

@M118 is the display mode you are using an unmodified display mode? Does this happen in every opaque display mode? E.g Rendered/monochrome?

If it is modified and other display modes don’t show the same behavior, then it could be helpful to export the displaymode.ini and send it for inspection.

11

Rendered and Monochrome work fine, but unmodified Shaded and Shaded modified to remove iso curves both have the issue. Ghosted also has the issue, but it shows by also selecting the inner part while clicking next to it, rather than on it.
Attached a video of the behavior with all the above modes.

It seems like the issue in Shaded mode is where a polysurface intersects a (poly)surface, and only in spots where that polysurface is behind the surface I’m clicking on, and as long as there is no edge nearby.

12

@M118 pls run _Reset and click the “save settings for support” button. Then send the resulting zip to me in PM. I want to see if I can reproduce it with your settings.

13

@M118 I think I found why this is happening.

When I loaded your settings, in Shaded mode, color backfaces was checked. When this is checked, I see the bug, when I uncheck it, things work normally. But the weird thing is that I cannot simply reproduce by enabling color back faces after loading my own settings.

I suggest that you simply delete the Shaded mode and restart Rhino. Rhino will then recreate the Shaded mode and things should work normally from this point forward.

14

@Gijs I bet it only happens with a strange combination of a number of settings. Good news though! I’ve removed Shaded, and restarted rhino, and it seems to be fixed. Big relieve. This was bugging me for ages.
Massive thanks! :folded_hands: