Rhino 8 v16 keeps quitting whenever I want to use the "material tab"!

Rendering
1

I hate the v16!! I have a MacBook, I cant use most of the grasshopper plugins since I “upgraded” to the v16. and also rhino completely quits whenever I want to use the material tab, I cant change any property into a existing one or create a new material etc because the moment I touch “the material” tab, it quits immediately without even saving my file. I completely and truly hate this version and this has been going on for more than 2-3+ weeks and they haven’t solved anything and also I don’t know if I can go back to an older version. My entire master’s experience is in shambles because of this. I wish someone could solve these issues with this update or create a newer one that works fine.

Here is what I get when I run “systeminfo”:

Rhino 8 SR16 2025-2-11 (Rhino 8, 8.16.25042.13002, Git hash:master @ d0f731de6fe2c5fdcad78ad80faf154307815f18)
License type: Educational Lab License, build 2025-02-11
License details: LAN Zoo Network Node

Apple macOS Version 15.3.1 (Build 24D70) (Physical RAM: 18GB)
Mac Model Identifier: Mac15,6
Language: en-US (MacOS default)
.NET 7.0.0

Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M3 Pro
DELL U2415 (1920 x 1200 @ 60.00Hz)
Color LCD (1920 x 1200 @ 120.00Hz)
GPU Vendor: Apple

USB devices
None

Bluetooth devices
None

Third party kernel extensions
None

Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Builtin_float.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswift_errno.dylib
/usr/lib/swift/libswift_math.dylib
/usr/lib/swift/libswift_signal.dylib
/usr/lib/swift/libswift_stdio.dylib
/usr/lib/swift/libswift_time.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswiftsys_time.dylib
/usr/lib/swift/libswiftunistd.dylib
/usr/lib/swift/libswiftDistributed.dylib
/usr/lib/swift/libswiftObservation.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/swift/libswiftAVFoundation.dylib
/usr/lib/swift/libswiftCoreAudio.dylib
/usr/lib/swift/libswiftCoreLocation.dylib
/usr/lib/swift/libswiftCoreMIDI.dylib
/usr/lib/swift/libswiftCoreMedia.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftMLCompute.dylib
/usr/lib/swift/libswiftSynchronization.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftFileProvider.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftFoundation.dylib
/usr/lib/swift/libswiftSwiftOnoneSupport.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftSafariServices.dylib
/usr/lib/swift/libswiftSpatial.dylib
/usr/lib/swift/libswiftWebKit.dylib
/usr/lib/swift/libswiftAppleArchive.dylib
/usr/lib/swift/libswiftDataDetection.dylib
/usr/lib/swift/libswiftNaturalLanguage.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftVideoToolbox.dylib
/usr/lib/swift/libswiftGameplayKit.dylib
/usr/lib/swift/libswiftSpriteKit.dylib
/usr/lib/swift/libswiftPassKit.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftMetalKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/usr/lib/swift/libswiftMapKit.dylib
/usr/lib/log/liblog_network.dylib

Rhino plugins that do not ship with Rhino
/Users/asedates/Library/Application Support/McNeel/Rhinoceros/8.0/MacPlugIns/Enscape.Rhino8.Plugin.rhp “Enscape.Rhino8.Plugin” 4.2.0.1592

Rhino plugins that ship with Rhino
/Applications/Rhino 8.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp “MeshCommands” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/PlugIns/SectionTools.rhp “SectionTools” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/PlugIns/Displacement.rhp “Displacement” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 8.16.25042.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 8.16.25042.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCodePlugin.rhp “RhinoCodePlugin” 8.16.25042.13002

2

This started happening with MacOS Sequoia 15.3.1, it is a crash in the Metal drivers. Especially M3 hardware seems to be affected. I have notified our Apple contact about it.

3

Hi Nathan, thank you for your reply.

I had seen your response to the other person experiencing the same thing and took those steps you recommended but they did not change a thing. It still immediately quits whenever I touch the material tab which completely limits my ability to do anything with Rhino. I was kind of able to achieve what I wanted in Grasshopper without using the plugins that stopped working after “upgrading” to v16 but the material tab is so crucial to me that I am unable to use Rhino apart from using it as a 2-D cad software.

It looks like there won’t be an upgrade to v16 for a while and I don’t think this problem will be solved within v16 (considering it has been 3+ weeks and no change), is there a way to go back to using v15? I am totally down to deleting the app and then reinstalling it too but I think it’ll just download the latest version, which is v16? I am in my midterm week and I am not able to use the software I have been using for 8+ years for the first time just because I said yes to a pop-up about an upgrade.

Anyway, thanks again for your reply. I am waiting for a solution from the developers.

4

And you are absolutely sure that you have set the render device to CPU? Note that just selecting the tab page does not yet select the CPU device. You have to actually check it. Because the behaviour you describe is when the Metal device is set as render device.

Please ensure you send in the crash reports when our reporter dialog appears. I don’t see any crash reports associated with your account. This can help me verify and investigate what the problem could be in case you do have the render device actually set to CPU.

We release a new Service Release once every month on the second Tuesday of the month.

You can try updating to the latest Service Release Candidate: Rhino 8 > Settings > General. Set update frequency to Service Release Candidate. These will typically update every Tuesday.