Rhino WIP Refresh rate

Using Rhino WIP (9) to view the same file side by side with Rhino 8 having noticed redraw performance issues.

(9.0.26097.12305, 2026-04-07)
(8.30.26096.12181, 2026-04-06)

In version 8 the graphics are silky smooth on even the largest files- Full screen at 4k.

In version 9 there is a perceivable frame refresh - the whole model steps as it rotates, with mouse and more noticably with spacemouse due to the fine control. The effect is like the screen is refreshing at a slow rate e.g. <20 frames per second

I use a space mouse, and run a Nvidia Rtx 4000 Ampere. Open Gl 4x antialias, but this applies to both open GL and DirectX

This is most apparent on large files> 100mb which i create regularly. and It relates to the amount of geometry on screen : take the same file, reducing the geometry speeds up the redraw.

It doesnt take much however to slow it down - load 2 stp files from an engineering package and the refresh slows way down.

Its most visible when zoomed into an object so its moving past the view quickly.

This applies to wireframe mode, shaded, ghosted. xray.
Its less noticible on Rendered, technical, Pen and arctic

Rendered seems to rotate without antialiasing, then apply the antialias when stopped. - this was not the behavior on V8.

Small files seem to be smoother - but not quite as smooth as 8.

It actually makes me feel queezy, so avoiding for now.. I first noticed around 1 month ago on previous wip.

Any thoughts? as is this is not usable for production - unless i keep a sick bag nearby.

did you ever “not experience” this? or did it get fixed for you?

my problem is different, but i think it MIGHT be related as it sounds like the renderer (even in opengl) got weird.

i’ve been trying to update my extension to rhino 9, but have spent hours debugging why the mouse input was weird. (a mouse view fly around camera, relying on smooth input).

I think that rhino 9 is either processing mouse inputs incorrectly (throwing half the buffer away) or something else. It’s not related to raw input congestion, and I even see this normally pivoting around a single cube in a document.

I even checked default/options/settings of mouse values like Rhino.Options.Mouse.MouseMoveTolerancewhich i dont know what does, but its defaults changed from 2 to 6 (but changing it has no effect).

I’ve also confirmed that it happens in opengl and direct3d, so something is fundamentally making the viewport “laggy”, which is noticeable on high hz monitors and if you’re used to smooth mouse input. (which was perfect in rhino 8).

I had a hunch it might be forced vsync or something else, but i don’t know.

The weirdest thing is in my extension, the mouse sensitivity i have (so cm per 360) is basically halfed without doing any different math, so i really do believe something in the renderer or viewport got changed fundamentally in some way.

And that is not related to the gumball, as that uses the relative position of the cursor and the viewport (i think). Where my plugin uses raw input and moves the viewpoint directly. I even tried the normal API to talk to it and move the camera, but that is slower (in both 8 and 9) and doesn’t solve the issue. (And the issue is there, without any extensions anyway).

When i have more time i might try to do some presentmon or some other tool to do dumps to see what is going on in the rendered view.

EDIT: was not the issue was my plugin that hit a thing in rhino9 that changed and exposed some issues, so my bad!