Nudging “solid points” is broken in the latest WIP. I can’t nudge more than one step at a time, I have to actually move the view or something else major like that in between each nudge.
Solid points could be the corners of a mesh box?
This works fine here.
Not working here.
Same problem here. (9.0.25357.12175, 2025-12-23)
Nudge a solid point. After one “nudge” that nudging does not work on that point until I either select something else (such as the object or a different solid point) and then go back to the first point which I can nudge another step -or- select a different view. Then I do another nudge step.
Incorrect. Solid points are points which allow limited editing of polysurfaces.
To make solid points visible use the command SolidPtOn
PointsOn | Rhino 3-D modeling
I don’t think they are well known.
How is that different from selecting sub-objects with Ctrl+Shift+LMB?
It gives you points? It’s irrelevant to this discussion, thanks.
Completely different.
Create a polysurface.
SolidPtOn
The solid points will become visible.
Select one or more solid points and drag/nudge/move/rotate the solid points.
Really? Ok.
Yes I can still move the points and I’m using Rhino 9 SR0 2025-12-23
System Info
Rhino 9 SR0 2025-12-23 (Rhino WIP, 9.0.25357.12175, Git hash:master @ 222d94a0469dc850b778eae09b4c35abd98fff4b)
License type: Commercial, build 2025-12-23
License details: Cloud Zoo
Expires on: 2026-02-06
Windows 11 (10.0.26200 SR0.0) or greater (Physical RAM: 128GB)
.NET 9.0.11
Computer platform: DESKTOP
Standard graphics configuration using DirectX
Primary display: NVIDIA RTX A5000 (NVidia) Memory: 24GB, Driver date: 12-7-2025 (M-D-Y). DirectX(11)
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
Secondary graphics devices.
NVIDIA Quadro K2200 (NVidia) Memory: 4GB, Driver date: 12-7-2025 (M-D-Y).
> Accelerated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!
DirectX Settings
Safe mode: Off
OpenBLAS: OpenBLAS 0.3.29 DYNAMIC_ARCH NO_AFFINITY Zen MAX_THREADS=64.
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\SolidTools.rhp “SolidTools”
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 9 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 9.0.25357.12175
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”
@martinsiegrist Perhaps not completely different but still different.
SolidPtOn makes the solid points visible and allows selection of the solid points using the usual selection tools such as crossing windows.
The Solid Points can be selected using Ctrl+Shift+LMB and position the cursor at a solid point location but does not make the points visible until selected.
One thing I see failing is consecutive nudging with the control key pressed after a subselection of a corner of a polysurface box.
The problem occurs when Nudge is set to work with the arrow keys.
It does not occure when Nudge is set to work with the alt+arrow keys.
The problem is unrelated to how the solid points are selected. In particular it occurs if SolidPtOn is used to make the solid points visible and points are then selected, and if Ctrl+Shift+LMB is used to select the points.
I recall seeing something previously about a problem with view manipulation using arrow keys in the WIP. Perhaps this is related.
@JimCarruthers Perhaps a new thread reporting the problem including the dependence on arrow keys only, without the discussion of SolidPtOn, etc, would be appropriate.
It does.
To me it seems there is an issue with transforming control points of polysurfaces or even just surfaces. Only one Ctrl+Alt nudge is executed.
I switched to arrow key nudge and the problem occurs instantly without having to press Ctrl. One nudge executes and then it fails.
Here is what I see:
Using arrow keys:
Arrow key - nudge works once.
Shift + arrow key - nudge works once.
Ctrl + arrow key - nudge works once.
Using Alt + arrow keys:
Alt + arrow key - nudge works properly. Multiple nudges work.
Shift + Alt + arrow key - nudge works properly. Multiple nudges work.
Ctrl + arrow key - nudge does not work.
@martinsiegrist Do you see anything different?
This is what I see too, but only for ‘points’ of surfaces or polysurfaces.
Nudging mesh vertices or regular points works fine.
@JimCarruthers we could change the topic title to ‘Surface / Polysurface control point nudge issue’
NO
Nudge works correctly with curve and surface control points, and with curve edit points.
“Solid points” are not control points. They are a different type of entity.
Ok, then maybe ‘Surface / Polysurface nudge issue’?
Here’s what I see with a surface or polysurface and Nudge set to Alt + Arrow keys:
Subselecting corners or edges or surfaces with Ctrl+Shift+LMB and then Ctrl+Alt +any arrow executes one nudge only and then fails. It does not seem to have anything to do with points but much rather with the subselection.
SolidPtOn shows four corners of a surface or eight points on a box. Ctrl+Alt nudge works fine.
Two untrimmed surfaces (not polysurfaces).
Control points are on for the blue surface.
Solid points are on for the green surface.
Two trimmed surfaces (not polysurfaces).
Control points are on for the blue surface.
Solid points are on for the green surface.
Polysurface (two joined surfaces).
Control points are not available for polysurfaces.
Solid points are on for the green surface.
It appears to be directly connected with “solid points” which are a distinct type of entity, different than control point or mesh vertices.
Subselecting an edge or face/surface of a polysurface and moving/nudging/etc that edge or surface gives exactly the same results as selecting the solid points on that edge or surface and moving/nudging/etc those solid points. My guess (since I don’t have access to the actual code) is there is shared code between solid point manipulaton and sub-object manipulation. So a bug relating to that shared code would show up in both solid point manipulaton and sub-object manipulaton.
Added: Selecting and nudging an entire polysurface or a stand-along surface works correctly. That does not surprise me because a translation of an object without changing the shape of the object is much simpler to code - it basically is just adding the appropriate amounts to the x,y,z coordinates of the object.