Major performance issues in V6

Thanks for checking on this JB. Hopefully - by hook or by crook - we can get @robinp - to test the display pipeline optimizations in 6.17.

Robin, I don’t hold out much hope for the lackluster performance in the Named Views and Materials panel…I really would like to get to the bottom of those. We’ve not been able to reproduce those on our end, unfortunately.

Hi Robin,

Can you run the “SystemInfo” command in Rhino 6 please and copy and paste the contents back in a reply here? I want to check that the sluggish performance you’re seeing isn’t related to your Rhino 6 not using the better graphics card in your machine. Thanks.

Hi Brian, I’ve only got the 13” one, so only the integrated GPU. I’ll get you the system info when I’m back at my computer.

I think the key thing is the dramatic difference between V5 and V6.


Have you downloaded and installed the released Mac 6?
The Beta shown in your screenshot can not be used to see if 6.17 works better.

To be honest, I’m saving the trial for when I really need it. For example if I find I really need to use a V6 file after the beta runs out.

Sadly, no plans to buy V6 for a number of reasons. Most important of which is money being tight right now and that V6 may only see us through until first half of next year at which point a single upgrade would bring us up to date. It’s simply not a compelling calculation right now.

That makes sense.
The unfortunate part is you will not get to see if the 6.17 (and subsequent) improvements help with your performance issues.

1 Like

I guess I will as and when I use the trial

There you go.
I have a 13" MBP with an Intel Iris chip myself.
It’s no speed demon but it is very usable with 6.17.
If I need speed, I use my Windows machine with an nVidia Quadro.

Hi Dan

Forgive me, but I’d like to be 100% sure that I understood. I currently have Rhino Beta 6.16 (with Rhino 5 license). Do you confirm that I CANNOT change to 6.17 without FIRST buying a Rhino 6 license?


Hi @Zsimon

My understanding is that is true. With the exception being that you get the latest version and access to the betas of the service releases with the 90 day trial.

Rhino 6 SR16 2019-7-10 (Public Build, 6.16.19191.20064, Git hash:master @ 4fd981cd026fa4d158ffae1c86df15124b0847ba)
License type: Beta, build 2019-07-10
License details: Cloud Zoo. In use by: Robin ()
Expires on: 2019-08-24

Apple Intel 64-bit macOS Version 10.14.6 (Build 18G87) (Physical RAM: 16Gb)
Mac Model Identifier: MacBookPro15,2
Machine name: Robin’s MacBook Pro
Language: en-GB (MacOS default)

Intel® Iris™ Plus Graphics 655 (OpenGL ver:4.1 INTEL-12.10.12)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: Intel Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 1536 MB
Graphics: Intel Iris Plus Graphics 655
Displays: Color LCD (298dpi 2x), DELL U2715H (109dpi 1x)

Graphics processors
Intel Iris Plus Graphics 655 (1536 MB)
Color LCD (1680 x 1050)
DELL U2715H (2560 x 1440 @ 59 Hz)

USB devices
Burr-Brown from TI: USB audio CODEC
Apple Inc.: iBridge DFR brightness
Apple Inc.: iBridge Display
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple: Headset
Apple Inc.: iBridge ALS
Apple Inc.: iBridge FaceTime HD Camera (Built-in)
Apple Inc.: iBridge

Bluetooth devices
Nordic Semiconductor:

Third party kernel extensions
com.astro-hq.driver.LunaDisplay (1.0.1) DA36D61E-DF34-3D59-84D2-781A01054D2D

Third party plugins

Rhino plugins
/Applications/ “RhinoCycles” 6.16.19191.20064
/Applications/ “Snapshots” 6.16.19191.1002
/Applications/ “Rhino Bonus Tools” 6.16.19191.1002
/Applications/ “Import_FBX” 6.16.19191.1002
/Applications/ “Grasshopper” 6.16.19191.20064
/Applications/ “PanelingTools” 6.16.19191.1002
/Applications/ “AnimationTools” 6.16.19191.1002
/Applications/ “Commands” 6.16.19191.20064
/Applications/ “Renderer Development Kit” 6.16.19191.1002
/Applications/ “RDK_EtoUI” 6.16.19191.20064
/Applications/ “Displacement” 6.16.19191.1002
/Applications/ “IronPython” 6.16.19191.20064
/Applications/ “Rhino Render” 6.16.19191.1002

Thanks for the system info Robin. There’s only one GPU in your Mac and it’s not that powerful, my first thought is to disconnect the second Dell 27 inch display as a test. Any difference in overall performance? The disabling of the skylight in the Rendering panel should also make the Rendered display mode similar to v5 for you.

Robin is correct, you can’t get the 6.17 service release candidate in the beta you still have. You’d have to download an evaluation of Rhino 6 for Mac in order to have access to 6.17. If you haven’t used a Rhino 6 evaluation on Windows before this will get you another 90 days without buying a license.

1 Like

Hi Brian

Thanks, but I rarely use the render viewport setting. At the moment I’m just copying and pasting a small object from from one file to the the main one I’m working on and I’m treated to beach balling and a long period of completely unresponsive rhino.

It is really tiresome.

The comparison is with V5 which seems to be incredibly smooth and fast.

Did disconnecting your second monitor make a difference?

In order to test out the 6.17 Release Candidate, you need to be running Rhino 6 for Mac 6.16. You can run Rhino 6 for Mac 6.16 by:

  1. Evaluating an RH60 license (if you have not done so already; you may have if you have evaluated Rhino 6 for Windows).
  2. Purchasing a license.

Take note: we hope to “graduate” the 6.17 Release Candidate into a full-fledged Service Release sometime soon (no promises as to when, though, but the hope is soon).

Ok Dan. Thank you


Hi Brian

I’ve been testing with the external monitor not attached due to the other issue I was having as noted in the discussion with @John_Brock about by layer or by object material settings.

Anyway, as you might expect certain things are definitely a bit quicker without the external monitor. Somethings are still slow as molasses.

Things that are better than before:

  • Material panel
  • General viewport performance (still way less smooth than V5 even with the external monitor attached)
  • OBJ import seems a bit better (speed and reliability)

Things that are still painfully slow during this short test:

  • Copying and pasting a fairly small file into another
  • Changing the viewport from raytrace to any other viewport setting (or pausing raytrace)
  • Closing a file and choosing to ‘revert’ changes (beach ball bonanza)
  • Named views panel


Thanks for trying that Robin. For general veiwport perfomance, make sure that the display mode settings in Rhino 6 match what is being used in Rhino 5 as that version couldn’t do the same things in the display.

I’d agree with John B. that having you test 6.17 when you can is the best way to see if things have improved on a Mac like yours. My only other suggestions regarding what is slow still without trying to run an external monitor, would be to check that the named views are not using Raytraced or Rendered modes as those will take more system resources. If you do use Rendered mode in any of them, make sure the settings are the same as those in Rhino 5 for a better comparison.

If you can post any small file that takes longer to copy and paste from Rhino 6 than it did from Rhino 5, please do so. I’ll need to reproduce that here for a bug report. Please indicate the exact steps such as if you are pasting to/from Rhino 5 or Rhino 6 and what objects are being selected.

Raytraced uses a lot of system resources and was not available in Rhino 5 as you know. I can see that causing a delay on a system like yours which would only be able to utilize the CPU. The model size, lighting and materials as well as whether you are in a maximized view are also factors.

Waiting for ‘revert changes’ would be another one I’d want to see a file and specific steps for if possible. I’d need to reproduce it here for a report knowing exactly what was done in the file before deciding to close and revert those changes. One idea is to also check if the file was opened off of a network or cloud storage drive as that would be a factor too in any latency.

Hi @BrianJ

Re the performance problems when choosing to revert the file, I just don’t get why this is a performance issue at all. Rhino doesn’t need to do anything other than to NOT save changes.

We already know that autosave is not supported on NAS drives. I have checked the box to not be asked about it every time so I can’t recall the exact wording.

What is Rhino doing to these files for it to take so long to close?

Could it be linked to the save only file issue people are having when working on remote files? See here: Read-only file


I’m not sure what happens in the code when choosing Revert. I can still try to reproduce the delay here if you can provide a file. Email if it can’t be posted publicly or use and explain the steps to take in the comments.

@dan FYI in case you have more info on what Revert does.