Rhino 7 Feature: Display Performance Discussion

I’ll take a look at the V7 code. It’s possible that someone changed the command n V7 and broke the VSync setting


You definitely have the VSync enabled on your system…and if the TestMaxSpeed option to disable it isn’t working, then it’s most likely because you’ve got it “Always Enabled” in your GPUs Global Settings. And the only reason I can think of for why V6 doesn’t show the VSync Enabled, is because there is a “Rhino Profile” setup for the V6 “Rhino.exe” that is configured to turn the VSync OFF.

Any time you see a frame rate of (60.xx), it’s almost always the VSync…and you’ll always see it, no matter what the display mode or scene is. Even a blank scene using the Wireframe display mode will only yield 60.xx fps.

Look in your GPUs Control Panel applet, and try disabling VSync there.


Well if VSync = Virtical Sync, the nVidia app has 3 options, Use the 3D application settings, Off and On. It was set to the first. I set to off and restarted WIP7. Resulted in the same times of 59.XX

And you haven’t setup an NVidia Profile for Rhino? If you’ve turned off VerticalSync permanently and are still seeing 60fps, then something else is turning it back on. When I do the same thing here with V7 WIP, everything works as expected… and if I set NVidia to “Use the 3D application settings”, then Rhino’s “-TestMaxSpeed VerticalSync=Disabled” also works as expected.

If you’re seeing 60fps with an empty scene in a wireframe view, then I’m pretty sure you’re still experiencing the vertical retrace delay. I’m also not understanding how it’s possible that your V6 Rendered mode is faster than its Shaded mode…that makes zero sense…unless you’re not working with the default settings for either of those modes.


Typed in “-TestMaxSpeed VerticalSync=Disabled” Ran 3 times Rhino WIP. Got 130 to 133fps.

Options ( FrameCount=100 DisplayList=NoRebuild DynamicDraw=Disabled VerticalSync=Disabled )
Time to regen viewport 100 times = 0.77 seconds. (130.72 FPS)

The more computers I test this with, the more disappointed I am, to be honest. I updated to 10.15.4 on my MacBookPro13,3 (AMD Radeon Pro 460 OpenGL Engine) and I don’t see an appreciable difference using TessellationShaders (testing with CurvesDemo.3dm).

And do you have any ideas why Mac rhino is performing so badly compare to the windows one?

Yes, it is clearly an AMD driver performance difference for tessellation shaders. Windows uses one set of drivers; macOS another.

1 Like

Thanks, let’s hope you guys can solve it.

1 Like

I hope the OpenGL material mapping issues will be fixed in V7.

Hello Steve,

I used my 1.6 GB competition file, with a lot of Surface, Meshes, Linked Blocks , and Curves.

Did TestMaxSpeed.

Rhino 6
1- Shaded Mode = 66.19 (1.51 FPS) faster
2- Rendered Mode = 125.88 (0.79 FPS) slower

Rhino WIP
1- Shaded Mode = 70.88 (1.41 FPS) Slower
2- Rendered Mode = 118.61 (0.84 FPS) Faster.

I immediately noticed a better viewport shadows in the rendered mode which is a great thing. I like how the shadows looks much softer


Core i7 4970K + GTX 1080 + 32GB of RAM


Anything specific?


I’ve posted this bug, months ago, and it’s meaningful because we need the OpenGL mode to be accurate because Raytraced mode is too slow for aligning materials/textures/mappings. The top is not going to map anyway, but that’s okay, the side is the issue. To examine this, it’s like that material is applied, but Rhino thinks the mapping is not necessary because it’s out of view. I’ve seen this behavior before with transparencies, which I think were fixed.

Rendered (OpenGL) View:

Cycles View:

[I wish we could map textures, repeating along/per NURB H/V’s because it’s dozens of times faster than anything in Rhino. I checked out what I think you were working, on, and it;s not the same.]

I’m finding it difficult to understand what you are describing, but are you saying that OCS mapping in V7 doesn’t solve this?

And if I am going to solve a problem with mapping, I need an model with a repeatable case.


For one, it’s in my diner map file, do I need to send it again?
I could not find the OSC feature in the version of v7 I tried it on.

I am getting ready to make a video showing quite old texture mapping features that would make adding materials to objects much faster. I have to get screen capture set up on this computer.

[I am sorry, but things have been pretty sketchy here in the Valley, lately.]


I could never repeat the problem with th bricks in that file. And also, didn’t we agree that adding OCS mapping would solve that for you? That’s actually been done in V7.


RH-56789 is fixed in the latest WIP

1 Like

I have more time to play around with Rhino 7 now and I’m experiencing extreme lagginess when panning around Layout space. I trialed this back in Feb with a 1GB Rhino file and posted in this thread regarding the same issue. Now I’ve started from scratch, built myself a template file and after adding some geometry and going to draft the construction drawings I am again experiencing this glitchy panning in Layout space, and this time it’s only a 50mb file.

Any developments?

In theory panning should be much faster, but obviously something is not working on your system. Can you share a model with me that you are seeing poor panning performance in layouts?

Also, are you running Windows or Mac?