Why do you still allow Fusion to lose your work? - frequent crashes - unsaved

Why do you still allow Fusion to lose your work? - frequent crashes - unsaved

hoegge
Collaborator Collaborator
429 Views
2 Replies
Message 1 of 3

Why do you still allow Fusion to lose your work? - frequent crashes - unsaved

hoegge
Collaborator
Collaborator

As much as I love Fusion I also hate how often it crashes and how often you have to remember to make defensive saves (ctrl-shift-S is good to know).  In addition to the obvious lack of ability to see from undo list when you saved and lack of ability to delete redundant saved versions (only necessary because you have to do defensive saves), I really wonder why you have to lose a lot of work when Fusion crashes.

 

Why don't you save every operation to disk when they are executed so you never lose anything but the crashing operation? This way you could apply them to the last saved version after restarting Fusion, so no work is lost.

 

Each operation is for sure a lot less than 1 kB of data. Today I added a single edge to a fillet command and Fusion crashed / hung (forever) and the last 30 modifications was lost.

ScreenShot1146.png

0 Likes
430 Views
2 Replies
Replies (2)
Message 2 of 3

TheCADWhisperer
Consultant
Consultant

@hoegge wrote:

....and the last 30 modifications was lost.

 


First, I would try to determine why Fusion is crashing frequently.

What are your system specs?

Can you File>Export and then Attach a representative *.f3d file here?

 

Second, I have not lost 30 modifications on one file in the last 30 years - every time I do something right - I save it.

Yes, I save often.

In fact, my students printed up t-shirts that say - Save Often!

Message 3 of 3

hoegge
Collaborator
Collaborator

Frequently is ~once per day if you work a couple of hours in fusion. A program should crash once a month or less.

My system spec are ok. There is no difference whether I work on a Mac, Windows Laptop PC 5 years old Nvidia graphics, and plenty of RAM (32 GB) or a new PC with plenty of ram and NVIDIA 1050 graphics card. So has nothing to do with my PC. 

 

It is rarely 100% reproducible, but often happens when editing fillets. Have attached the file this example was fro, in which there is also another strange issue when trying to fillet:

https://knowledge.autodesk.com/community/screencast/4e1fedb8-d84d-4776-8cc5-c270e0b20afa

 

One of my points also is - there is no reason not to save every operation performed to disk so it can be reapplied to last saved version to restore all operations since last save.

 

Saving often is just a habit to workaround unstable software.

 

 

 

 

 

0 Likes