And this is where I see the main problem with V8. It was delivered even though fundamental work is still being carried out on the user interface. Even the distributor says that I should wait with the update of our workstations until the UI is finally finished, otherwise there will be a lot of stress and double work.
That’s why V8 feels like a WIP version, it’s unfinished.
FYI: RH-81310 is also fixed in Rhino 8 Service Release 6
I agree on Mac Rhino 8 is a joke, that make me sad…Lot’s of pain to work !
Bugs Bugs Bugs
Please finish this version before asking me to try the 9th !
Pls run _Systeminfo in Rhino and post back the results.
If you encounter problems or bugs please report them. Preferably with a sample file that illustrates the bug and steps to reproduce. More info about that here.
hi thx …here is the result :Rhino 8 SR20 2025-6-6 (Rhino 8, 8.20.25157.13002, Git hash:master @ 73b00899cf43922900a763212f167c03dc6f27cc)
License type: Educational, version 2025-06-06
License details: Stand-Alone
Apple macOS Version 13.6.5 (assemblage 22G621) (Physical RAM: 16GB)
Mac Model Identifier: Mac14,9
Language: fr-FR (MacOS default)
.NET 8.0.14
Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M2 Pro
Color LCD (1512 x 982 @ 120.00Hz)
PL2770H (1920 x 1080 @ 120.00Hz)
GPU Vendor: Apple
USB devices
Realtek: USB 10/100/1000 LAN
Bluetooth devices
None
Third party kernel extensions
None
Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/usd/libIex.dylib
/usr/lib/usd/libHalf.dylib
/usr/lib/usd/libAlembic.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/usd/libosdCPU.dylib
/usr/lib/usd/libImath.dylib
/usr/lib/usd/libIlmThread.dylib
/usr/lib/usd/libIexMath.dylib
/usr/lib/usd/libtbb.dylib
/usr/lib/usd/libMaterialXCore.dylib
/usr/lib/usd/libMaterialXFormat.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/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftNetwork.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftAppKit.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftFileProvider.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftPrivate_BiomePubSub.dylib
/usr/lib/swift/libswiftPrivate_BiomeStreams.dylib
/usr/lib/swift/libswiftExtensionFoundation.dylib
/usr/lib/swift/libswiftCoreML.dylib
/usr/lib/swift/libswiftVision.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftExtensionKit.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswiftWebKit.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftMapKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/usr/lib/swift/libswiftFoundation.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.20.25157.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 8.20.25157.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp “MeshCommands” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/export_PDF.rhp “PDF Export” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rendu de Rhino” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/PlugIns/SectionTools.rhp “SectionTools” 8.20.25157.1002
/Applications/Rhino 8.app/Contents/PlugIns/Displacement.rhp “Displacement” 8.20.25157.1002
/Applications/Rhino 8.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 8.20.25157.1002
/Applications/Rhino 8.app/Contents/PlugIns/SolidTools.rhp “SolidTools” 8.20.25157.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 8.20.25157.13002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCodePlugin.rhp “RhinoCodePlugin” 8.20.25157.13002
@damien.sorrentino There is nothing in your system info that throws off any alarms, so the next best thing is to translate
into:
Bug 1 : <description> <steps to repeat> <model>
Bug 2 : <description> <steps to repeat> <model>
Bug 3 : <description> <steps to repeat> <model>
Any particular reason you haven’t updated your operating system? The last venture update was 13.7.6 and your computer is compatible with the latest OS 15 Sequoia. Apple driver updates are via their OS so typically being on the latest is recommended.
Hi…thx for your attention…the list of bugs will be too long to establish and document.. it s a work in itself ! sorry don’t have time now …so I switched back to 7 for now. I will try the next update…
Wish you a very nice day.
Start with one?
Ok some of the main …lot’s of pain working with multiple screens (main window vanish randomly as I use shortcuts)
Multiple instances of an object or line on top of each other when I’m doing array (polar or linear)
Basic rendering became pinkish …
You do know how reporting a bug works?
Yours is a rant (and it may very well be a legitimate rant, I don’t know) not a bug report.
How do you think your information is going to help McNeel to identify the problem, let alone solve it?
some people just dont have the time to create lengthy bug reports that try to outline repeatable steps for bugs one cant even put into words at times. i had that many times myself specifically in the beginning. lets not try to make people that are already frustrated look bad additionally. we definitely can agree that rhino8 carved quite some bone out of the users, even more so for the mac users in all regards.
He didn’t even narrow down his problems.
How is this going to help him, McNeel or anybody else other then him letting off some steam?
and it may very well be a legitimate rant, I don’t know
Rhino 8 lauch clearly had its problems, why not contribute to make it better?
telling someone they stepped on your foot makes it worse for whom? besides that i see some definitiv points quoted above, also users are nor responsible to keep the pay check of the developers low.
I don’t have any idea what you’re trying to tell me.
My point was that not at least roughly specifying the problem will not increase the probability of it being resolved.
You seem to see this in a different way. Good for you.
i dont, and even that does not make it any good(er) and that does not resolve the other side of this story which you entirely and cynically enjoy to ignore becoming an utter mcneel fanboy not only condoning the abusive and abrasive habit to flame frustrated users that dont have the nerve and time to spend a life time informing the developers how successfully they failed and still fail with v8 but even engage in it.
Woah, now you’re losing it completely.
This whole word salad doesn’t have anything to do with anything I wrote.
I hope you will at least agree that this is not a fruitful conversation and there is no reason to take this further.
You can book this a win, if it makes you feel better.