Rhino crashes frequently when starting it by opening (double-clicking on) a file. This error message shows up even though my version is actual:
my version is actual:
one example file that crashes rhino:
VORLAGE.3dm (2.8 MB)
You have more than one copy of Rhinoceros installed on your Mac, and double-clicking on a 3DM file is starting one of the obsolete versions.
To fix:
Start the 5.3.1 version of Rhinoceros.
Run the _TestFindAllRhinoApps command.
Use the dialog that appears to delete all the Rhinoceros apps except for the 5.3.1 version.
Just now Rhino 5.3.1 (actual, non-WIP version) did a really bad action.
Firstly I have to explain:
- We use a NAS in our company, which doesn´t support versions in the files saved on it.
- Yesterday, I used for some files the SaveAs with âoption: smallâ, which discardes all layer, hidden, and locked info on the whole file content (obviously).
When I clicked one of my files, Rhino crashed, AND somehow achieved to save the file and saved it as âsmallâ (just geometry).
So what I got was:
file opened, Rhino crashed, saved just geometry ( discardes everything else), and our file system has NO versions:
In one double-click Rhino killed all info despite just the geometry.
This is how the file quick look icon looks:
(file name blackened by myself)
VERY BAD. 
Did I do anything wrong?
Should we disable the autosave for Rhino for all our colleagues?
It doesnât actually, Save Small only discards the render meshes. Save âGeometry Onlyâ discards the layers, colors etc.
âMitch
Yes, that´s what I did, both (âSaveAsâ with âonly geometryâ, but just yesterday, not even once today.
Today i saved a lot of files just regularly, which worked correctly.
I also used the âduplicateâ feature from OS X (10.11.6) to work around possible unwanted âjust geometryâ saves.
Letâs solve one problem at a timeâŚ
Start the 5.3.1 version of Rhinoceros.
Click the New Model button on the splash screen.
Run the _TestFindAllRhinoApps command.
Post a screen shot of the dialog that appears.
OK, I´ll do when at work tomorrow.
Thanks for having a look at this!
â
Uli
Now I started Rhino a from the App Icon, and starting the file removed everything than the geometry â directly after opening my file from within the âRecentsâ section from splash screen.
I managed to save my file on the desktop prior to closing; afterwards I selected âDo not saveâ, though it saved the geometry-only file nevertheless.
That doesn´t seem to belong to the file location (NAS).
Even the same file on the desktop behaves the same.
Even on WIP 5.4
Maybe there´s some odd setting / bad content in the file.
Other files work for now âŚ
work-around:
Only force quitting Rhino from OS X 10.11.6 helps not to save the wrong file geometry.
But now I don´t know how to open my file in any way.
the crashing file from now:
CLIENTNAME Displays - MoĚbel Connect - EinhaĚngeteile (alle) (3).3dm (9.9 MB)
Software information
Software versions
Rhinoceros version: 5.3.1 (5D193)
IronPython version: 5.1.2015.131
Language: en
macOS version: Version 10.11.6 (Build 15G1217)
Plug-ins
/Library/Frameworks/3DconnexionClient.framework/Versions/A/3DconnexionClient
Third party kernel extensions
com.3dconnexion.driver (10.2.2) 598AA167-B9DE-3DFC-8288-33EEA0E4951B
com.getdropbox.dropbox.kext (1.8.6) 64ED2422-9A10-3C8A-AD9E-474ABB6E87EB
com.parallels.kext.usbconnect (11.2.2 32651) 6996036D-00B1-367C-8702-95DDF4182433
com.parallels.kext.hypervisor (11.2.2 32651) 1E4D9C3F-3A55-3F96-A377-7875345DA4B7
com.parallels.kext.netbridge (11.2.2 32651) E96BCE0A-C480-374F-A9F9-E81D2A631FC2
com.parallels.kext.vnic (11.2.2 32651) 7189C8F0-E8BA-3975-AFF8-2D1DA25E1E87
Hardware information
Computer hardware
Hardware model: iMac12,2
Processor: Intel Core i7-2600 CPU @ 3.40GHz
Memory: 16 GB
Architecture: Intel 64 bit
Video hardware
Graphics: AMD Radeon HD 6970M 1024 MB
Memory: 1024 MB
Screen size: 2560 x 1440
Displays: iMac (109dpi 1x)
USB devices
Apple Computer, Inc.: IR Receiver
Apple: Card Reader
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Bluetooth USB Host Controller
Bluetooth devices
Broadcom: Magic Keyboard
Broadcom: Magic Trackpad 2
OpenGL information
OpenGL software
OpenGL version: 2.1 ATI-1.42.15
Render version: 2.1
Shading language: 1.20
Maximum texture size: 16384 x 16384
Z-buffer depth: 24 bits
Maximum viewport size: 16384 x 16384
Implementation settings
Use texture compression: No
Appearance settings
Antialiasing: 4x
Mip map filtering: None
Anisotropic filtering: None
It looks like you have already deleted the obsolete versions of Rhino you had on your computer. I was hoping to see what old version of Rhino was causing the crash. Regardless, that fixed your crashing problem.
As far as the second problem, your sample model contains only geometry. When Mac Rhino opens that model it needs to create additional items like viewport definitions to be able to display the model. That incorrectly marked the model as changed. This will be fixed in the next WIP release.
Yes, but that wasn´t made up by me â or at least not what i intended to do.
As described before, somehow Rhino deleted all the info on starting the file (and starting Rhino with starting it), possibly because i saved with âonly geometryâ, but with other file(s), NOT THIS one:
Are you still having an issue with saving Rhino files? If so, please describe your process so we can duplicate it here.
We made some changes in the latest RhinoWIP (5E41w). Please give it a try. Is the behavior any better?
This attached newly created file makes Rhino crash when being dragged on the latest WIP version:
TEST 3 Boxes (Opening 2. Doubleclick).3dm (2.9 MB)
I also sent a report through Rhino.
Thank you for submitting a crash report. I wasnât able to duplicate this myself, but found the issue using the crash report. This will be fixed in the next WIP.
1 Like
This should be fixed in the latest RhinoWIP (5E44w). Give it a go.
Great to know that it helped to find the error, hopefully.
Thanks for your work!
It´s true. Totally true. You have to believe it.
Version 5E41w crashed my â3 Boxesâ file.
Version 5E44w now works. No crashes from dragging a file on the dock icon.
To be honest, the âflatteningâ of the file in my first entry here happened most likely by an accident; the flattening seems to not be caused by this error.