Lost project design changes in spite of doing regular saves

Lost project design changes in spite of doing regular saves

dcreedS77RE
Explorer Explorer
286 Views
1 Reply
Message 1 of 2

Lost project design changes in spite of doing regular saves

dcreedS77RE
Explorer
Explorer

After a Fusion 360 crash in August where I lost a large amount of design work I have been regularly saving my work. I know this isn't necessary and it creates a new version on each save however I didn't want this to happen again. This took my project from version 14 to version 29. During this time Fusion was not shut down until an unexpected PC shutdown in early September. Thinking my design was safe I didn't re start Fusion and didn't need to do any more work until today. Upon opening the latest project version (29) there haven't been any saved changes past version 13 so again a large amount of design work has been lost. So even though a new version was created during each save the design changes haven't been saved. It's hard to understand why this data hasn't been saved and whether it can somehow be recovered. Any help would be appreciated.

David

 

0 Likes
Accepted solutions (1)
287 Views
1 Reply
Reply (1)
Message 2 of 2

dcreedS77RE
Explorer
Explorer
Accepted solution

Problem solved. I have found all my design work up to and including V29. The problem is related to the dialog on starting Fusion that states that Fusion 360 did not shut down correctly and a recovery document has been created and do you want to open the recovery version which I did. While this recovery document was titled V29 it didn't contain any new design work past V13. I closed and reopened V29 and again was prompted to open the recovery document. However this time I said no and Fusion when responded that the recovery document will be lost if I proceed. I clicked yes to proceed without saving the recovery document after which V29 opened with all my current work. It would seem that the recovery document was in fact one created for V13. The fear of potentially loosing data lead me to click yes which was in fact the wrong way to proceed in this case.