DAZ Studio Feature request: autosave
In view of the fact that DAZ Studio (pretty much all versions) is relatively unstable and crashes without warning, it would be useful to have the program autosave, so that when it does crash we don't lose all the work over the last hour or so. Yes I know I can also manually save every two minutes, but really in modern software we should not have to be bothered with details like this. Take cars as an example; how many modern cars have a manual choke for cold starts? None! Why? Because modern cars have an auto-choke. Likewise, modern software should have autosave.

Comments
there is a script floating around somewhere
my GoogleFu not finding it sadly
but
every program I have that autosaves I disable if I can or swear loudly if I cannot
Zbrush drives me nuts with it as does iClone 6, Unreal Editor to name a few, the few times it helps me overwhelmed by the resource hogging
@IsaacNewton "In view of the fact that DAZ Studio (pretty much all versions) is relatively unstable and crashes without warning"
That is not universal behavior. It seems to be a more common complaint for hardware setups that are marginal for the tasks being asked. One may not want dozens of saves for a particular scene.
I7 hexacore, 64gb RAM, twin Nvidea 1080 12GB GTI.... hardly marginal when rendering a couple of figures and a few props.
No such thing as a 12Gb 1080.
No thank you if optional ok but I don't want DS saving when I don't want it to. And the only time I've had DS crash is because I've done something daft.
Yeah, you're right...I've lost my work so many times I've lost the count, and now I usually save everytime I do something relevant xD
I suppose it depends on one's workflow, but I would loathe Daz autosaving when I utterly don't want it to. Re crashes, once in a blue moon I'll get a crash just as I begin a render but when I reload the set it works fine, so I have no idea why it crashed first time around, plus currently I have an outfit with a fault re which as soon as I add a material I get and instant total crash (I need to submit a ticket re that), but otherwise I have no problems and I don't have top of the range nvidia.
Maybe they're 11gb... that could make all the difference, eh?
Then they wouldn't be 1080s. More about what the system actually is. While your system certainly isn't marginal, Studio isn't universally unstable.
Alas, niether is it universally stable. I do accept that specific hardware and software combinations can cause problems. What I would like to see is better error trapping in the DS software. If autosave is not possible then how about error trapping that allows you to save the current file before the program automatically shuts down. Since the current error trapping gives a warning that the program will close, how difficult is it to give an opportunity to save the current file? Maybe this will not always work, but a 50% chance is better than nothing.
And yes it would make a difference; Windows seems to steal some, and is one used as display? That further limits RAM; a scene needs to fit on both cards.
I think this thread should be closed, some people are getting fixated on the size of my GPU RAM rather than the original point of the post.
I honestly can't remember ever having Daz crash on me, and I run it on a laptop with an i7 4700MQ @ 2.4Ghz, 16Gb RAM, and NVidia GTX 765. The only thing I ever had occur was it would shut down my entire system during renders, and the only reason that happened was due to incorrectly using a mixture of MDL & RSL components in scenes. If Daz is crashing on you that much, there's either a problem with your settings in Daz/Windows, or you have other software interfering with it. You should be in touch with their tech support in order to troubleshoot whatever is going on to cause those crashes.
An autosave feature would probably eat up too much space on a system depending on how it was implemented, not to mention the potential to cause other problems.
I'd like the option for it to autosave before rendering an image. I don't find Daz crashes much when building a scene, but it happens more often when doing a render. Plus there are the (many) occasions when a long-running render has been crashed because Microsoft decide to run an update and reboot my PC. That's doubly annoying if I've forgotten to save the scene.
100% agree. Though it's not always only Studio; sometimes a script product, like Visual Menus for instance, will, without warning either lock up Studio or crash the program completely. It has happened to me fairly regularly, not hardware dependant. Some might not want to use an autosave; doesn't mean the option is not a good idea, especially given how incredibly feature rich some other parts of the software are. The forum software autosaves, for goodness sake. Studio shouldn't?
For myself, a save, auto or otherwise that saves everything, every setting, selectively based on a dropdown, would be a huge help. As a script product, I'd buy it.
Those reacting on the crash issue seem to be divided between mostly agreeing or mostly disagreeing. This suggests that hardware/software compatability might be an important factor. Unfortunately these are random events and so tracking the problem(s) down is difficult. To be quite honest, the best way might be for DAZ3d to take a survey of systems which have problems and those that don't, then look for the common features; essentially a Bulked Segregant Analysis. It is likely that there are multiple causes resulting in crashes at different stages. For example Chris-2599934 reports crashes mainly on rendering, whereas for me that pretty much never happens, rather crashes happen randomly during scene building. Perhaps nowefg has a point that an autosave feature could be made available via a script if DAZ3d won't build it in to DS itself. I also would buy that script.