Autosave Survey

As part of the never ending quest to keep making Rhino awesomer, I’m gathering some data to try and tune up our Autosave feature and hopefully make it more useful.

Please answer the following-

  1. Do you use Autosave?

  2. Has it actually saved work for you when you needed it?

  3. Have you ever lost work you were expecting Autosave to save for you? (If so do you have any specifics of what happened?)

  4. Do you know where to find your Autosaved files in the case of a problem?

  5. Does it do what you expected it to do? (If not why, and what did you expect?)

  6. Any other relevant thoughts specific to Autosave?

Thanks in advance.

1 Like
  1. Yes
  2. Yes
  3. I think so but not often, so I could be mixing it up with other software
  4. What I always do is go into options, check where it autosaves and copy the path from there to the file explorer.
  5. I think so

Teach Rhino to save files in the background
This is my most important thought on AutoSave in Rhino and saving files in general. This is probably the biggest bottleneck we face and speeding up saving times would be the largest time-saver imaginable over here:

  1. Yes
  2. Yes
  3. Yes
  4. Yes
  5. Yes
  6. See above (Rhino file saving speed problem)
  1. Yes
  2. Yes
  3. Yes, after that I activated the feature (I thought autosave was the default :smiley: )
  4. I think so, I usually search around a bit
  5. Yes
  1. Yes
  2. Yes
  3. No
  4. I always have to open Options and check the file path.
  5. Yes.
  6. a. Perhaps there could be a tab in _About so unpon startup Autosave files could be filed seperately and more easlily accessible?

If you find there is no AutoSave file in the configured folder, look in your Windows Recycle Bin. When old AutoSave files are deleted, that’s where they go.

  1. Yes
  2. Yes. Often.
  3. Yes. If a new file hasn’t been saved at all before something goes wrong. Typically what goes wrong is a plug-in causing a crash or loss of power on my laptop.
  4. Yes.
  5. I now know what to expect, so yes.
  6. Grasshopper’s autosave has much better UX. I would like Rhino’s autosave to work exactly like grasshopper’s. With rhino, if you crash, when you reopen, you get one prompt to restore the file that closed when you crashed. With Grasshopper, when you open any individual file that was unsaved before a crash or an unintentional power loss, you get a prompt about whether or not to restore that specific file, and that prompt is waiting for you even if you don’t reopen that specific file for weeks or months.
1 Like
  1. yes
  2. no
  3. no
  4. no
  5. yes

1 yes
2 yes
3 yes. Not often but it happens. Can’t remember any specifics
4 yes, but like others go to option and copy path
5 yes
6 I Would like having more easy access to the autosaves.

1 yes
2 yes. many
3 … I don’t remember …
4. I search the trash … if there is another place. you tell me
5 yes in general. but the only downside it takes a lot of time if the files are larger than 600 mo
6. you can program rhino to send reminders messages for saving genre (do you want to save the file yes / not) … the time between messages can be configured by the user in rhino
thank you

  1. Yes
  2. a few times
  3. no
  4. yes
  5. yes
  6. I wonder how many users realise the recycle bin is full of autosaves.

  1. Yes
  2. Yes
  3. I don’t think so, but it’s been quite a while since I needed to recover one. Probably V5 or earlier.
  4. No, but I know some places to look for the answer. Suggestion: Include a specific help item that summarizes where to look for the most recent and earlier ones in the help menu and make it part of the program file so it’s right there for the offline users, even the ones who haven’t downloaded the offline help.
  5. Yes, because I think I have a pretty good understanding of how it works so I know what to expect.
  6. I heartily agree that it takes a long time to autosave and it’s undesirable that it stops user activity until it’s done. I don’t think that it would be possible to take a snapshot to RAM and then save it in the background for anything but the smaller models, but for them it would probably work pretty well. For the larger models that would spill over into virtual RAM, it would be slower than writing it direct to disk in the first place.

Would there be any clever way of taking a “rolling” snapshot that doesn’t require copying the entire model to “core” (you can tell how long I’ve been around computers) at once? Since the time-consuming part of the “snapshot”/background writing scheme is the writing to storage, maybe the snapshots could be done in suitably sized chunks where user interaction is stalled for a few seconds, then the disk writing could take place in the background. When that’s done, another snapshot would be taken, etc. You wouldn’t end up with an integral snapshot but it would probably be a perfectly usable backup.

  1. Yes
  2. Yes
  3. Yes, Problem is that Autosave is saving the File using the Documentname. If i have open 2 Rhino parallel and in both are new Project without custom Documentname the Autosave is getting override from both instances
  4. Yes but it is hard to find
  5. Yes
  6. see 3.

1: Yes
2: Yes, numerous times!
3: Maybe back in the days, but it would be years ago.
4: Yes, but Rhino usually finds the file all by itself.
5: Yes
6: It’s a PIA on large files, since saving can take minutes - but I’ll take that over losing hours of work.


1 - Yes, a lot
2 - Yes, a lot
3 - Some times I just want to go back … It’s my fault, not a Rhino fault (stop responding for example)
4 - Yes… I go to the Options… but should be in other place… more clear
5 and 6 - No!
Please put a option to keep the last XX autosaves! That would be very usefull in architecture… For example in vectorworks I have the option to make autosave from 10 to 10 minutes and keep the last 50 versions… :grinning:

  1. yes
  2. no it has never worked the files are always too old.
  3. Yes but it’s the same as answered in 2 the file never reflects the modeling stages up to the crash.
  4. Yes but that’s a hassle as is all of where windows hides stuff on c
  5. Not really since it never helps in a crash
  6. Better than autosave is when you crash and reopen rhino you get a message: Rhino has a recovery file, that has worked well, but lately all my crashes haven’t generated a recovery file.
  1. Yes (didn’t realize you could even turn it off)
  2. YES!
  3. Nothing significant I can recall.
  4. It takes some digging to find it if you don’t get the crash prompt. I think less savvy users probably don’t know there’s a folder somewhere with their older autosaves.
  5. Yup
  6. Is there a way for autosave to happen in the background? I find Rhino gets unresponsive while Autosaving a large file. This is especially a problem if the file is opened from something like a slow network drive. Rhino becomes completely unresponsive for minutes in some cases while autosave is being completed.
1 Like
  1. Yes
  2. No
  3. No
  4. Now yes
  5. N/A
  6. Untill now, I thought that Autosave = Backup (.BAK). What is the difference between these two?
    I always assumed I could “open” the .bak file and resume working from the last saved status.
  1. Well, auto save is on.
  2. Well… it always auto saves when I switch back to the bloody program, instead of in the background.
  3. Yes, and the specifics is lost in time.
  4. After searching on these forums, apparently it’s automatically in the trash!?
  5. No. I don’t expect the file to be in the trash, and I don’t expect autosave to kick in when I want to start using the software!