I am using Rhino 6 on Windows. When Windows does an auto update (which I cannot turn off, and which does not save anything), it appears that Rhino reads it as a close of the file with a choice to not save, so it erases the autosave file. Why does it do this? Why not just always overwrite the old autosave with the new one? Also, it of course should not be reading a Windows update as a safe close.
The only saving grace is that when Rhino erases an Autosave file, it goes to the recycle bin. So despite Rhino’s attempts at being thrifty with disk space, my recycle bin is full of tons of Rhino autosave files, and I can find it there. But damn is this a stupid system. Usually I have to go through a full panic before I rediscover that the deleted autosave is safely in the Recycle Bin.
I have been waiting to update until Rhino 8 comes out, because I also have an M2 Mac. But would be interested to know if this issue has been fixed in Rhino 7, or if others have Rhino 6 and have not had this issue (maybe there’s a bug). Also, I just wanted to vent a bit, maybe.
Thank you for replying. I understand that the main reason for Autosave is to protect in case of a crash, but it doesn’t seem unreasonable for it to also be set up to protect in case Windows decides to shut down without notice (especially given that this is something Windows 10 does, and cannot be turned off). Of course, I should remember to save frequently, that’s a given, but it’s not a solution to this problem. People forget to save frequently, and the Autosave feature should be robust enough to protect against this. It would be helpful to know if what I am describing is the intended behaviour, or if something weird is going on with my computer. If this is the intended behavior, then that’s a pretty big fail imo. In contrast, Grasshopper’s Autosave is very robust and does not have this issue.