MoveEdge/MoveFace, long wait, strange things

Rhino Rhino for Windows
, ,
1

Hello,

could someone explain what’s wrong with this geometry? (This has been like this for ages … I just never had energy to report it.)

Take one side of the object and try to do a MoveEdge operation sideways. See video.

move edge bug 01

(First I move the edges leftward … note the 20 sec wait.)

(Then I switch to Rendered Mode, not the 1 min 30 sec wait for creating meshes …)

whats wrong with this geometry 260318.3dm (835.2 KB)

Anyone that can explain what is going on? And how this could be done in a better way? (Yes, I could use four separate units grouped. Would be simpler. But why does this not work.)

Also, note in the 3dm file there are vertical lines on the geometry. These can’t be made to disappear using MergeAllFaces, but it should be possible.

Thanks

/Erik

2

Hi Erik, Please run systeminfo in the Rhino command line and post the results.

3

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: 96GB)
.NET 8.0.14

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 4090 (NVidia) Memory: 24GB, Driver date: 12-30-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 591.74

Accelerated graphics device with 4 adapter port(s)

  • Secondary monitor attached to adapter port #0
  • Windows Main Display attached to adapter port #1

Secondary graphics devices.
Intel(R) UHD Graphics 770 (Intel) Memory: 2GB, Driver date: 12-1-2025 (M-D-Y).

Integrated graphics device with 4 adapter port(s)

  • There are no monitors attached to this 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: 12-30-2025
Driver Version: 32.0.15.9174
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24564 MB

Rhino plugins that do not ship with Rhino

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.29.26063.11001
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\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 8\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.29.26063.11001
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.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\BlockEdit.rhp “BlockEdit” 8.29.26063.11001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\Calc.rhp “Calc”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

4

I can also add that it is not uncommon for Rhino to freeze and completely die while Moving the edges.

The render mesh creation can be cancelled. But the MoveEdge is not possible to interrupt. Meaning force quitting is the only way out.

There should be cancellation thread running separately, so that the user does not have to kill Rhino.

/Erik

5

I don’t know how this object was created but you have some odd surfaces in there - after exploding, it takes awhile to display mesh and I see this on the lower part of the frame:

image
image876×1050 83.5 KB

Turning on control points, I get this:

image
image1972×595 226 KB

This is probably the result of some subobject move that was non-planar, forcing Rhino to try and rebuild the surfaces to accomodate the move. That is what is taking the time.

If I section the profile I see this:

image
image1290×1413 15.6 KB

Very bad curves. Again, perhaps the result of already having pushed the objects around with subobbject editing.

I would try again with clean geometry.

6

This looks appears to be a regression of some sort. I can do the same operation in Rhino 7 in a few seconds.

Thanks for reporting RH-94117 Move edge long wait

7

you could use Sweep1 with history and prevent scaling the output:


clean-geo.3dm (748.9 KB)

Solid editing on anything but flat objects is often a bad idea. Keep your isocurves on to see when the model goes south.

8

Thanks.

I normally start with the sweep1 exactly like in your file. Just not using the History much, due to the fact that there are no visual clues that the geometry is “live” and how the underlying “crvs” are connected to the final 3D-object.

But now I’m using your stuff.

Thanks

/Erik