I just spent 6 hours building a scene, only to have unity crash to desktop due to a physics CUA. Not a big deal, it was a complex scene, and this sort of stuff happens with unity.
It wrote a crash dump before closing, which made me wonder, could a call to save scene code be made before the dump to save a new temp (random/whatever named) file to saves/scene? If the call is put within a try/catch it should be at least possible to attempt to add some point of recovery, I would assume. Even a partially corrupt scene would be better then loosing everything.
I would think almost every user of vam would have lost work, maybe this could be avoided fairly easily? Even if the save has issues not allowing for loading the temp scene, it's json, so manual editing in notepad could fix this.
Anyway, just a thought. May save many headaches, if the code can be called after a crash.
It wrote a crash dump before closing, which made me wonder, could a call to save scene code be made before the dump to save a new temp (random/whatever named) file to saves/scene? If the call is put within a try/catch it should be at least possible to attempt to add some point of recovery, I would assume. Even a partially corrupt scene would be better then loosing everything.
I would think almost every user of vam would have lost work, maybe this could be avoided fairly easily? Even if the save has issues not allowing for loading the temp scene, it's json, so manual editing in notepad could fix this.
Anyway, just a thought. May save many headaches, if the code can be called after a crash.
