Fusion Crashed, Auto-Recovery is Evidently Completely Non-Functional, and my Design is Gone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I saw plenty of other posts like this when I searched the forum, but none were in the last year and none had any real resolution.
I had just finished a 4 hour design and was excited to finally get to send it to the printer. I think I was just doing one final orbit of the model to inspect it and Fusion360 crashed. It was a fast crash, not a long one where it gets hung up on a computation or something. When I restarted the File Recovery dialog was kind enough to show me a small list of recovered files from over a month ago (I've worked on models almost every day for the last 6 months).
I also went through every folder and the offline cache shown in the data panel and I even tracked down the Autodesk Application Support folder where the actual recovery files are kept, and sure enough there is nothing recent there. Finally, I did triple check my preferences and Auto-Recovery is set for every 5 minutes and I've never changed that setting. It has saved me maybe once or twice a while back.
So... Is a completely non-functional Auto-Recovery feature still just normal thing with Fusion360? Is there something specifically that I did wrong? Is the only solution to manually press cmd+s every 15 minutes? Is it possible to create a user script that will press cmd+s for me, since literally every other software I've used personally or professionally in the last 7 years has rendered this habit unnecessary??
For real though, just make an auto-save option that uses the existing functional and reliable save command if the auto-recovery is difficult to make work. This is pretty frustrating to experience especially considering my application already crashes almost every single time I try to close the application. Just constant crashing and unreliability....
If there are any suggestions, last ditch efforts, or something simple I'm missing, please let me know.
Thanks,
Ryan