If Rhino says it is OK to Auto Save, then the second phase is initiated. If Rhino is in the middle of a command, Rhino will refuse the Auto Save, and the Auto Save operation is abandoned. When the Apple framework initiates this first phase, it asks Rhino if it is OK to Auto Save at that moment. If you constantly move the mouse, an Auto Save will never start. It will also initiate an Auto Save when enough time has passed (this seems to be about five minutes) and the program seems idle, i.e., no recent mouse movement or typing. The Apple frameworks initiate an Auto Save when you switch to another application. Some time after a Rhino model has been changed, the Apple frameworks decide it is time to start an Auto Save. The first phase is initiated by the Apple frameworks.
Well worth the high price tag!Īn Auto Save in Rhino for Mac happens in three phases. My machine is now blazing fast in ways I never imagined-including bootcamp into Windows in something like 20 seconds.
If you can turn it off, then you could at least test this theory.Īs a side note, after using an SSD for the past two years, I hope to never rely on a spinner again. Perhaps others know of a method either system-wide or for Rhino alone. A quick search to turn auto-save off did not reveal any easy methods. While I understand the reasoning behind these devices from the manufacturers’ point of view (economy), I’m suspicious of the benefits for large files which use auto-save versioning. I wouldn’t be surprised if the fusion drive turns out to be a large part (if not the root) of your problem. Sorry, thought you were using the commercial version and I was behind a version. Rhino 5.2 and Wip and must be downloaded separately, so it is normal that you do not be offered the update if you use the 5.1 commercial