Major performance issues in V6

I’m still on the V6 beta version (6.16.19191.20064, 2019-07-10).

As I’ve mentioned elsewhere, I have no intention of upgrading at present. Partly because V6 does not seem to be ready for prime time yet and partly because paying for an upgrade with 6-12 month lifespan is not especially attractive.

Anyway, I want to reiterate some major performance issues that I’m experiencing with this last beta version.

The issues are:

  • Incredibly slow / unresponsive material panel
  • Very slow named view panel
  • Very slow OBJ import (rarely keeps materials)
  • Importing of 3DS files normally results in a complete crash
  • General UI lag / slow navigation / slow viewport updating
  • Periodic issues with opening of files as read only

I’ve just gone back into V5 for the first time in a while and having got used to V6 I’m just blown away by how silky smooth and fast the whole thing feels.

I’m using a 2018 MacBook Pro, so it isn’t an old machine by any stretch of the imagination.

I would recommend updating to the 6.17 release candidate as there are many changes in that build.

Hi Steve

I think I’m right in saying that this is only available to those who have upgraded to V6?

Anyone who can currently use 6.16 should be able to use 6.17.

Not from what I can tell.

I’ve tried following the instructions in @dan’s post about RC17 but this is what I have currently. Any option to subscribe to a different ‘stream’ is greyed out.

I’m probably confused and @dan can help clear this up. You may have to install the 6.16 evaluation first before getting the 6.17 release candidate. Don’t take my word for that though; Dan would be a better source of truth.

@robinp is still on the Beta.
The Last Beta is 6.16 and is over.
There will be no new Beta builds.

To get to the Release candidate for 6.17, you need a permanent V6 license.

Or, you can wait until SR17 is released, and then get a 90-day eval license.

To get to the Release candidate for 6.17, you need a permanent V6 license.

@John_Brock I do not believe this is correct. I believe that - if @robinp or others have not yet evaluated an RH60 license - they have the opportunity to do so now with 6.16. This would allow you to switch to the 6.17 release candidate to test the optimizations that @stevebaer speaks about.

I see @robinp does have a V6 eval license.

In Rhinoceros > Preferences > General, can you change the update frequency to Service Release Candidate?

The screenshot they provided was the Beta.

1 Like

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.

Robin

@robinp
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?

-Simon

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
/usr/lib/log/liblog_network.dylib

Rhino plugins
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.16.19191.20064
/Applications/RhinoWIP.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/PlugIns/RhinoBonusTools.rhp “Rhino Bonus Tools” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/PlugIns/import_FBX.rhp “Import_FBX” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.16.19191.20064
/Applications/RhinoWIP.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.16.19191.20064
/Applications/RhinoWIP.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.16.19191.20064
/Applications/RhinoWIP.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.16.19191.1002
/Applications/RhinoWIP.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 6.16.19191.20064
/Applications/RhinoWIP.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.16.19191.1002