Rhino crashes instantly, I click the Rhino7 tab in my applications as I’ve always done, bang, crash, not even a splash screen appears, it’s instantanious. 2 things Ive done recently, 1- updated to OS Ventura, 2- Installed the latest Datasmith plugin to link Rhino to Twinmotion. I can’t even open Rhino to pull some system info out ??
Hi Milezee, sounds like an incompatible plugin, either uninstalling the offending plugin or manually moving the .rhp to a different location should get you back going.
Hi @Japhy , thanks for the swift reply. What’s the method or best way of doing that seeing that I can’t even open Rhino ?
Ideally you don’t have a lot of plugins, can you uninstall the Datasmith for testing?
Hey hey-
same problem is happening to me. @milezee were you able to solve it?
@Japhy I can’t seem to find the data smith .rhp in my “Plug-ins” folder. Any recommendations?
TIA!
Hi Epiphany -
Does the Rhino crash reporter pop up after the crash?
That would only be the case if you had installed Datasmith. Please post an image / images of your Plug-ins folder.
-wim
Hey Wim,
Thanks so much for your help.
The rhino crash reporter does pop up and I’ve sent a copy through with an explanation.
I installed the data smith plug in previously but it’s no longer visible in my folder!
Here’s my a screen grab of plug in folder contents:
TIA 
HI @Epiphany_Karopoulos apologies for the late reply, yes uninstalling the Datasmith plugin worked for me. It must have been fixed because now I have no issues with it. I think it was the early Twinmotion version of the plugin that was buggy. Anyway, hope you solved your issue 
Hello!
The same problem is happening to me. I downloaded the most recent Twinmotion Datasmith Plug-in for Rhino (Mac), and now Rhino crashes as soon as I open it. I have sent a couple of crash reports when it prompts them. I have also found my Plug-ins folder, and the Datasmith plug-in is not there for me to uninstall.
My first attempt to remove the plug-in was to move the installer to my trashcan and then empty it, but that did nothing. Would that have caused a problem?
This is a screenshot of my plug-ins folder. I have also searched my computer for any .rhp files, and the search found nothing.
Arielle
Hi Arielle -
Please run the Rhino SystemInfo command and copy-paste the result here.
I’m not finding any of those reports. Is it the Rhino crash reporter that is suggesting to send the report or the macOS crash reporter?
-wim
Hi Arielle,
Close Rhino take a look in this folder for the Twinmotion plugin
~/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/
Restart Rhino
Hello,
Thank you both for your quick responses!
@wim I can’t run any Rhino commands because the program crashes immediately upon opening.
Here is the window that appears when Rhino crashes.
@Japhy The only folder under ~Library/Application Support/McNeel/Rhinoceros is one called “6.0” which contains license info. I find it strange that there’s no “7.0” folder even though I currently use Rhino 7.
I’ve resolved this in the past by sending the uninstall instructions provided by the Twinmotion developers, although now it looks like the link is broken.
For anyone who needs this link in the future, this is the unbroken one that a Twinmotion employee sent to me:
That being said, the instructions also say to look in ~/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/ and to delete the offending .rhp file, but I still don’t have a “MacPlugIns” folder nor can I find any .rhp files on my computer at all.
I have figured out where I made a wrong turn! I had previously been searching for the files in the “Library” folder in my Macintosh HD rather than in my specific user’s Library. I actually thought I had checked both, but I must have been wrong. Both Libraries have ~Application Support/McNeel/Rhinoceros/ but only my user had the “PlugIns” folder that I needed. The complete path that got me to where I needed to be was Users/USER/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/.
I’m so glad the problem ended up being my own mistake rather than anything being seriously wrong!