Glitches, Bugs, Rhino Mac 8

Hi Everyone,

I have been an adamant user of rhino for many years now, so I hope it comes with a bit of weight when I express my frustration with rhino 8 for mac now. I have sooooo many glitches and issues with this, my workflow feels completely stuck and its absolutely infuriating. It would take too long having to list everything here, but the main points are:

  • axis locking with tab doesnt work in a floating viewport
  • clicking most objects doesnt work at the first attempt and only actually ‘clicks’ once I click the second time
  • for some reason the inputs for commands dont work properly (say I want to draw a box with 80 / 80mm, for some reason it takes 8 as the first input and enters, so I end up drawing something with 8 and 0 as inputs)

and much much more. I would love to get someone from the team on a call and show them my issues and hopefully find ways to resolve this. Right now it is untenable.

Hi David,

Please run SystemInfo in your Rhino command line and post the result.

The most efficient way to resolve issues is to give the developers a small repeatable example.

https://discourse.mcneel.com/t/please-read-this-if-you-are-logging-a-bug-or-issue/173971/3

Rhino 8 SR13 2024-10-15 (Rhino 8, 8.13.24289.13002, Git hash:master @ 310800db9652d56ee534033b23cd53c62b5a1322)
License type: Commercial, build 2024-10-15
License details: Cloud Zoo

Apple macOS Version 14.0 (Build 23A344) (Physical RAM: 8GB)
Mac Model Identifier: Mac14,2
Language: en-GB (MacOS default)
.NET 7.0.0

Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M2
Color LCD (1710 x 1112 @ 60.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/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/swift/libswiftCoreAudio.dylib
/usr/lib/swift/libswiftCoreLocation.dylib
/usr/lib/swift/libswiftCoreMedia.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftCoreMIDI.dylib
/usr/lib/swift/libswiftAVFoundation.dylib
/usr/lib/swift/libswiftFileProvider.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftGameplayKit.dylib
/usr/lib/swift/libswiftMetalKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/usr/lib/swift/libswiftSpriteKit.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftCoreML.dylib
/usr/lib/swift/libswiftVision.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftVideoToolbox.dylib
/usr/lib/swift/libswiftObservation.dylib
/usr/lib/swift/libswiftWebKit.dylib
/usr/lib/swift/libswiftNaturalLanguage.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftMapKit.dylib
/usr/lib/log/liblog_network.dylib

Rhino plugins that do not ship with Rhino

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

okay we can start with the first small issue at hand. If I open a new floating window and work there (I like to work with a full screen window and hide all other windows) the tab axis lock simply wont work.

The input issue is the most aggravating one, however, this is hard to explain - I would need to show this to a developer in a call

I was able to repeat, thanks for reporting RH-84327

Assuming this is in a floating viewport as well? I did create an similar issue not long ago. RH-84324

no, this is very general issue and happens in many different instances.

I really believe it would be best if ww could jump on a 20min call and I can walk you through all issues. Now that you were able to repeat one of the glitches I mentioned I assume you can trust me with my assessment to a certain degree?

No lack of trust, we just need steps to repeat. If you are in Europe you can call the EU tech support line, the US line opens at 8AM pacific.

Hi, I’m finding the same issues described in 2 and 3 above. They seem both related to unexpected jumps in window focus that the user then has to fix i.e. either clicking additionally to change focus and select/register an input in the model space or by having to click and refocus on the command line to input more than a single character. Have these been logged/replicated?

yeah so this is a major major issue for my workflow right now. I feel like I am operating at 20% of the speed I have operated previously. @Japhy please please look into this further and try to get a fix asap

thanks for confirming this from your end as well!

David!

I’m still on V7 (Mac) and very happy with it.

At the time of the aggressive upgrade price, I bought a licence for V8 but have yet to install it.

With the elapse of three months, Is January’s Mac V8 better now? If so, how please?

In your experience, are there any things still to be wary since your October post?

Thanks.

In case you aren’t aware, you can get a legacy license for Rhino 7 so you can have both 7 and 8 installed and usable. This makes it possible to install Rhino 8 and still have Rhino 7 available for fallback if there are things about Rhino 8 that are making your work difficult.

Keep in mind that even thought your Rhino 7 procedures and habits will mostly work on 8 there will still be some effort and discovery to get familiar with the new things that 8 can do. If you are using the default Rhino 7 toolbars, etc Rhino 8 will be very familiar. If not then there will be some effort (and some would say frustration) in setting up 8 to work like your customized 7.

So, personally, I think that your best course of action would be to install your Rhino 8 and start to use it to see how far you can get before you are dissatisfied. With the ability to write Rhino 7 .3dm files from 8 and having 7 still installed there should be practically no downside to trying it out. Hopefully if there are things that you don’t like you will report them in detail here.

For my specific workflow Rhino 8 simply doesn’t work. My speed of execution drops to about 20% of what it was previously due to the bugs that I’ve outlined above. I paid for rhino 8 but in reality I am back to Rhino 7 and not touching 8 anymore. I am quite disappointed tbh, which I rarely am with Mcneel.

You might want to try the 8.16 release candidate next week. I just fixed an issue with floating viewports on Mac that sound related to several of the issues you reported above.

1 Like