Save more often?
alan bard newcomer
Posts: 2,381
Of course.
When I ue the geometry editior and save before deleiing groups etc.
I save when I'm going to do something that moves a large scene.
But literally, the program is crashing when I select something in the scene menu or click on a character and start to move with the translate tool.
---
I just spent an hour taking a set of four characters adjusting their heights etc (and yes I saved before doing it)
and but apparently I need to save before doing simple things like lining characters up for Refence sheets / boards.
---
Most crash reporters ask: What were you doing when the program crashed?
Okay, I deleteting 10 gazillion facets . . . yeah save the scene first
I was selecitng an item in the scene list, huh, I do that dozens if not hundreds of times in a session.
---
If the program can dump all it's resisters etc for the dump why can't it save the last state of the items in the scene.
I literally just moving the characters into a face out row when it crashed.
===
We can"t save every time we do something as simple as selecting an object.

Comments
registers are few in number, and are usefful for diagnostics, and are provided by higher level tools as far as I know. A full scene, assuming it isn't corrupt (which is quite possible iif DS is crashing) is a lot of data to recover, and is managed by the crashing application itself. I am very doubtful that this would actually be possible.
Is there any consitency in what the crash report says the applcation was doing at the moment of the crash?
they are almost all aceess vilolations. My best guess, basing on my years of programming, is the interface lets me move to down something, like a quick selecion or another more right after another, but that the internal processing hasn't caught up so when I move back to the scene file and select something, internally it's not ready, and wham.
---
One of my my games used to hang up the computer forcing a restart Photoshop the next time you open will have the same fils that wee open as recovered files and you can save them. my photoshop files can approach a gigabyte.
---
It looks like daz doesn't update anything while it's running. Changing a setting on a character for instance should update the file that characters data is kept in. It's on my computer not on the net, changing the skin on a character should just change the old "default skin for susan" to "skin suzzy ref number (xxx). If the program can read a new surface the instant you click on it and apply it it should be able to update the character file for Susan in the same instant..
An online game can crash and logyou back in with yoiur character in the place in died with the same outfit and the same loot etc they manage to track that in real time via the net. I can hit 50 treasure chests in 5 minutes and update 200 to 300 items in inventory and they're there even after a crash.
I work really quickly. there are times when I have to wait for the interface to let me select something, it's a pain, but it's obviously better than letting me do something it's not prepared to have me do.
---
The last one occurped after I render the image in the previous post and was moving the characters into a line to render the image here which I had to do after restarting and reupdating the characters again.
If daz crashes everytime I move suzy then I know there's a problem with the file but if after crashing it lets me do exactly what it crashed on before then it wasn't the file inself but something in the processing
---
image below same characters, outfits, just moved to a different location.
Having chnages propagate to saved files would not be desirable for most users, too easy to make an accidental change and not realise until the undo stack had many additional steps. Autosave is available, which is what PS and the office applications use, but of course it can be slow to complete.
Does the Daz save the entire file or could it be modified to just update the previous one with the changes in the scene. Or does it just do that?
Autosaves can be good, although slow, but it's trying to work around the randomness.
===
trying to save often enough to offset such a random thing like it crashed when you select something in the scene menu would be absurd.
Do any of the current auto saves have an option to start with a save, then do an incremental one and then for the next one go back and overwrite the first one, and progress like that.
It saves the full current scene - suspect that doing otherwise would add to the overhead.