Auto-save feature or script.

JD_Mortal

I constantly crash... Usually at the point of rendering, but sometimes when just loading things.

Is there a script, or can a feature PLEASE be made, to do auto-saving, at specific moments...

For example, I tend to crash at render-time. I would like it to auto-save, prior to rendering, as a "Crash-recovery-save". (The whole scene, obviously.)

Also, at a set interval, like once every 15-30 minutes... Just because it takes that long to make-up some complex poses, and saving is the last thing you think of, when, "testing how it looks for a render".

Another great time would be, "before loading content"... Because some content erases the entire freaking scene, and replace it with just that one object. Not sure if it is scripts, but I know models do that by default, which is annoying, so I turned that option off. Spend half an hour setting-up a model, go to load another one, or change the model, and instead it erases everything and poof, new naked model and no "UNDO", to get it all back. (Some scripted things are like that too. Scenery, mostly. making it difficult to load two scenery settings at once. You can, but you have to do a second-mouse-click, to get the menu to do that, which is NOT what you think of doing, when "loading" anything. That replace option should be the thing in the second-mouse-menu, not "loading".)

But I digress...

This is kicking me in the behind, and making it a real pain to digest using Daz, as it is so crashy like this. Randomly, so after manually saving for a while, and not crashing, you eventually forget, and the second you forget, it crashes...

The error is the typical "Access violation" error. Never the same error number, or item failure. (No, it isn't bad RAM. Tested RAM several times. All 1's came back as 1's, all 0's came back as 0's. All bit-CRC's correction bits were correct.)

For "crash-detection", you simply write a file, "rendering.txt", and erase it when done rendering. If that file exists, Daz would know that the program crashed, and would reload the auto-save file, so you can "try again", or at-least attempt to cause it to crash again, to resolve the isolated issue.