Whenever I use the nudge keys at all I have to restart the entire software, because any time I put in any command afterwards I get a tooltip pop-up with the nudge distance at cursor location, which is extremely distracting. Doesn’t even matter what kind of command, even just saving triggers it. Nudge settings are on default.
Hi Dominique,
Please run SystemInfo in the Rhino command line and post the results. Thanks!
Apologies, only just got home to my laptop
syteminfo results:
Rhino 8 SR25 2025-11-24 (Rhino 8, 8.25.25328.11001, Git hash:master @ 14cb4406ecadfa9b5d0230ac10bd86175bd37aff)
License type: Commercial, build 2025-11-24
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 [100% battery remaining]
Standard graphics configuration.
Primary display and OpenGL: Intel(R) UHD Graphics 620 (Intel) Memory: 1GB, Driver date: 11-20-2024 (M-D-Y). OpenGL Ver: 4.6.0 - Build 31.0.101.2134
Integrated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: Intel(R) UHD Graphics 620 (Intel) Memory: 1GB, Driver date: 11-20-2024 (M-D-Y). OpenGL Ver: 4.6.0 - Build 31.0.101.2134
Integrated (slow!) graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
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: Intel
Render version: 4.6
Shading Language: 4.60 - Build 31.0.101.2134
Driver Date: 11-20-2024
Driver Version: 31.0.101.2134
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 1 GB
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.25.25328.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.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.25.25328.11001
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”
Do you have another video card? This is the onboard default card, laptops typically ship hybrid gpu configurations, where you have a larger card as well.
Go to Device Manager in your windows settings > Display Adapters hopefully you have one that isn’t working.
Rhino is going to struggle with just a 1 gb card.
It’s just that one. Currently in the process of setting up another laptop as workstation (with RTX4070 GPU) but that’s been on the back burner since I’m not modeling anything too intense ATM.
But I’m wondering how graphic processing power could be causing my kind of issue?
It’s not the power it’s the terrible awful no good drivers.
Just double-checked on the other Laptop, everything exept basic setting files freshly installed, same bug persists.
new system info#
Rhino 8 SR25 2025-11-24 (Rhino 8, 8.25.25328.11001, Git hash:master @ 14cb4406ecadfa9b5d0230ac10bd86175bd37aff)
License type: Commercial, build 2025-11-24
License details: Cloud Zoo
Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 16GB)
.NET 8.0.14
Computer platform: LAPTOP - Plugged in [9% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 4070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 12-2-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 591.44
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 4070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 12-2-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 591.44
Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
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: 12-2-2025
Driver Version: 32.0.15.9144
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
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.25.25328.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.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.25.25328.11001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.25.25328.11001
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”
Does this happen in a new file or in a particular file?
What are the exact steps to repeat?
Hi Dominique,
Could be Rhino is just doing what it’s told. To stop it turn off the distance tooltip.
HTH
Jeremy
There aren’t really any super specific steps. Just Start with new file (default template)→ make primitive closed shape → select subobject face → nudge around a bit = and now every command that doesn’t natively start with a distance input (just saving, for example) pops up that annoying “0.2mm" tooltip for as long as the rhino session remains open
This does help.
If have tooltips turned on and sub select the tooltip stays on until the next action (click in the viewport) , which i think is normal behavior
What does your Cursor Tooltips settings look like? The default has Distance off.
I think I’ll record a video of the problem when I get home, because I feel like I’m not making myself clear. I don’t have an issue with having distance tooltips, or a problem with getting them to go away. My issue is that specifically the distance tooltip from nudge keeps coming back when executing completely unrelated commands. It’s not a massive issue, but it’s still really annoying and I feel like there should be a way to fix this without having to give up on ALL distance tooltips
I think I understand your issue, but i have to repeat it to get it in front of the devs. At the moment i can’t which is why i’m trying to nail down the variables.
Would it help if I send you the config files? Those were the only bits I kept between my attempts, haven’t tried to replicate it on a completely blank rhino instance yet (because if at all possible I would like to resolve this without losing all the adjustments I already put in, just to risk accidentally replicating the issue after starting to settle back in)
Dominique,
Please clarify whether after you do a nudge the distance appears
a) at the start of the following command but not the command after that or
b) at the start of every consecutive command.
I can repeat the former but not the latter.
Regards
Jeremy
At the start of every following command, as long as that command doesn’t start with a coordinate input (like lines, curves, for example stuff that has to be placed inside the work area), those seem to override the same space on the tooltip. But that only works during those commands, afterwards it’s straight back to “0.2mm" popping up everywhere
If, after you nudge something and get the distance tooltip, you click the mouse on an empty part of the canvas, what happens to the tooltip initially and then on executing a (non-coordinate) command?
My apologies, I made a few errors recounting from memory when I didn’t have my laptop to double check. It does seem to disappear after executing a different command, as long as it is one that creates/modify objects. It’s specifically commands that don’t interact with the construction area directly (saving, exporting, manipulating viewports, display modes, undo/redo, etc) that keep the nudge tooltips indefinitely, unless it’s interrupted by a new command that requires manual input in the construction area. Then it works again.
Looking at it more objectively, it is less annoying than I thought at first, with an understanding of the boundaries to work around, but still a bit distracting when you have to do a lot of the affected operations in a row (like during layer/property management)
The issue feels a bit like the software isn’t clearing previous data properly, like an e-ink display leaves some shadows when the screen does a partial refresh instead of a full one
I think the idea there is that nudging is typically a repeated action, nudge nudge nudge, then click off to cancel.
I guess, but it is still a bit awkwardly implemented with the way it lingers,
if it’s supposed to stay through- I’ll just call them ‘side-commands’ for now- (like nudge nudge, hold up, gotta change something, nudge nudge) it seems like it would be more functional for the tooltip to display the cumulative nudging distance, but that might just be preference.
Whatever the case, I believe I can kind of live with it now that I know how to work around them