I've said this before, but the script log comes really really close to implementing "journalling" which is the thing that made filesystems more robust in the 2000's. the binary dump emergency save thing is really kind of a silly way to attack the problem of replaying a journal of operations. If Autodesk realized this, they'd prioritize the completeness of command logging and build a simple toolset for replaying the unsaved operation journal.
I sent my "repeatHistory" plugin to the beta list a while ago and got crickets. Maybe I'll try again... All it does is parse the script log for the last open or save operation and them exec the remainder. It would work even better with an event that sets the script log path on scene open/save. On Friday, September 6, 2013, Jeremie Passerin wrote: > Got issue with the auto-recover lately, but the scene was actualy properly > saved before crashing. just needed to load it manually. > http://xsisupport.com/2011/10/15/crash-recovery-in-softimage/ > > > On 6 September 2013 13:18, Eric Thivierge > <[email protected]<javascript:_e({}, 'cvml', '[email protected]');> > > wrote: > >> You're doing it wrong... >> >> >> On September-06-13 4:15:36 PM, Eric Lampi wrote: >> >>> SoftImage: "Hey Eric, I see that you crashed.. How would you like to >>> recover your scene?" >>> >>> Eric: "Sure that would be great! Go right ahead, bring it on back!" >>> >>> SoftImage "You'll get nothing and like it!" >>> >>> Meh >>> >>> Eric >>> >>> Freelance 3D and VFX animator >>> >>> http://vimeopro.com/**user7979713/3d-work<http://vimeopro.com/user7979713/3d-work> >>> >> >> >
