Daz saving stuck at 99%?
Darren556g
Posts: 4
I'm working on a scene right now, and everytime i try to save the file, it gets stuck at 99%. Sometimes it would say not responding and the program will just crash. Anyone have any idea how i can fix this?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
What OS are you using?
What version of DAZ Studio, and bit depth, 32 bit or 64 bit?
What does it say in the log file about any crash that happens? Help > troubleshooting > View Log File.
I am having a similar problem. I have been using Studio for a year or so, I recently upgraded to the latest version of Studio and have been using it for a few days.
Suddenly today every time I try to save a scene it gets to 100% on the lower progress bar (Writing Assets) and freezes, reporting 'Not Responding'.
Empty scenes save OK but as soon as I add something....this.
I am using Studio version 4.6.2.117
Windows 7 SP1
Any help solving this would be appreciated!!
The bottom part of my log file looks as follows - a few suspect lines in there...:
DEBUG: initDB!
DEBUG: Db is Open
Error writing author data!
Total class factories: 1318
WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
3D mouse support library could not be loaded.
Creating interface
Successfully created OpenGL viewport for Viewport1.
Successfully created OpenGL viewport for Viewport2.
Successfully created OpenGL viewport for Viewport3.
Successfully created OpenGL viewport for Viewport4.
WARNING: QFile::flush: No file engine. Is IODevice open?
Executing startup script...
Started in: C:/Program Files/DAZ 3D/DAZStudio4
DAZ Studio Started
Creating Pixel Buffer
Pixel buffer - Width: 1024 Height: 1024
Compiling OpenGL Shader...
Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Fragment info
-------------
0(29) : warning C7050: "_rgb" might be used before being initialized
Shader Program successfully linked.
That looks like it may be the only thing that is relevant.
This may sound weird...but have you tried saving to a different folder than the one you usually save to?
That does look like it may be the culprit. I have tried saving to alternate folders but still no luck.
I am noticing something odd in my file structure though - when I look at folder properties they are all tagged Read Only, which would explain things, but I am finding that I can write to them anyway using other applications. When I uncheck the box and apply - does not seem to make any difference though, it is still RO when I look again. So it may be a broader OS issue - though everything else seems to be working OK.
I also note that there is an update to Studio 4.6 in Install Manager so I am installing that too.
I will keep looking at it and will post here if I solve the problem.
That sure is sounding/looking like an OS/permissions problem...
Try right clicking on the DS shortcut and selecting Run as Admin...and then try saving a scene.
give more time to save!
Once you got 99% is the time he start to save data on disk!
My problem was system protected area
Another time it was about read many lights
As Mjc propose you, change location (not in a system place)
and wait more!
Had the same problem (Win8.1 -64) - for me it was the Octane plugin.
Disable the "non Daz plugins" and check if saving is ok...
And that would seem to be the problem. Disabled Octane and the problem seemed to go away, enabled it and the problem was back.
Thanks!!
Had the same problem (Win8.1 -64) - for me it was the Octane plugin.
Disable the "non Daz plugins" and check if saving is ok...
Ah, i was just about to reply to my first post in this topic, but after skimping through this topic this method works for me. I also use octane render and disabling it before saving works. THank you.
I have the same problems, and by turning off the octane plugins, I can save like usual, anyone know how to fix this problems? ( I mean with the octane plugins turned on?)
I never had this problem before.
Probably needs to be brought to the attention of the maker of the Octane plugin...and for them to make an update.
Looks like the latest Octane Plugin update fixes this problem, its on the list. I will confirm when I have had a chance to try it out.
[Edit] Quick test indicates that the update does solve this issue.
There you go...
This happens quite often with plugins. Things may not be changed or so it seems, on the Studio side, but very often some of the 'behind the scenes' stuff does change....usually a newer build of qt. If the plugin uses qt and is a precompiled plugin (as opposed to one that compiles when run), then depending on the version of qt it was built on the update can cause problems. The same thing would happen with a system-wide qt update, too. And sometimes it doesn't always break things...and usually the broken things don't show up on the developers' machines...but after it's been released. (and it's just as bad/worse with Poser and Python updates...)
There were SDK updates in the NEW DS4.6.2 so the plugin prob used a SDK call that changed a bit. Causing the error.
DS 4.5+ plug-ins should still work, but newer plug-ins may not work in older versions of DS.