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
In an attempt to track down why this and a few other files crash Daz when they try to open, I dropped the .duf file into content gatherer, and only three jpg files were not 'found', though they are on my system. How do I get Daz to "see" them?
Also ... is there a way to export all of the lower window info? I can "file List" the reference list into a text file, but nothing else copies. I'd like a copy of the path list, too.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll" at 0033:00000000FCAA1893, DzObject::modifierIterator()+35 byte(s)
I've tried installing with DIM and manually, though manually doesn't complete the process.
Rename the Content folder for a minute.
Uninstall via DIM the Daz Studio that was installed with DIM. Uninstall manually the Daz Studio that was installed manually. Same for the Postgre thing.
With all of Daz Studio uninstalled, then pick a method, install Daz Studio. Then rename the Content folder back as it was, letting the 2 merge together. And if it didn't, also install the Postgre thing.
I have never had a manual install of Daz Studio fail. So I don't know why it would be for you.
If after all this you can't get Daz Studio working, I would recommend contacting CS.
....................................
But please try to understand, if the scene file is corrupt, no program is going to open it. We cannot fix a corrupted file.
Other scenes I know were working before are crashing during loading processes, too, though, with entirely different elements. I can open my default scene and load new figures. But then when I go to reopen the file I just made, it crashes with that error. So I really don't think they are all corrupt, especially when the content gatherer finds almost every file just fine. Most times if a file is corrupt, it doesn't even start to open. I will try your renamed content folder idea.
Obviously D/S shouldn't be still creating corrupt scenes, no.
Edit > Preferences, ... you have the temp folder set to default? {I know of one plugin that won't work right if it isn't}
I use the renamed content folder idea myself "just in case" -- because I really don't want to mess up that collection. I know "normally" reinstalling D/S shouldn't cause problems but I like to make sure. [once upon a time a long time ago, there was one update for D/S3 which actually cleared the content. People were not happy about that.]
For the new scenes you are saving, all products are "finished" [i.e. not trying to save half made morphs, etc.], all texture images are in the proper Runtime > Textures > some subfolder arrangement ? [i.e. not from a temp folder], oh yes NO .tiffs. - try with no hairs ... if you try a scene with "one" element, save. Check if it opens, add "one" element, save. See if it opens ... repeat ad nauseam, maybe you can track down the cause of the error messages. Any new scripts [even 3rd party ones]?
...........
eta: probably won't help with the crashes but "just in case" ... empty out this data folder every now and then. D/S will fill it again as products are used.
C:\Users\ ... \AppData\Roaming\DAZ 3D\dson\cache\data
I recently found that something in the OS had become corrupted and needed fixing. Can't find that page now though. Microsoft's instructions to get the W10 to search for and fix its own errors. After it did that, then whatever wasn't working in another program, worked.
But I digress, okay ... for those new to the program, this is how to get to the log file and how to make it a managable size to post in the forum.
Willowraven, if you are not successful in getting D/S to work, then my next brilliant [not maybe, but I try] idea would be to clear the existing log info. Close D/S. Open D/S and try to open one of those naughty scenes again. Then check the log file, copy/paste the entire thing to a text file so hopefully some expert passing by can read it and provide more/better help.
Then close D/S and reopen it. Try the scene again. Get the log file which will now have all the information for the program and just this scene and hopefully why it's not working.
The last line in the log file was "Creating property aliases..." and the next line should have been "Creating sum stage formulas...". But the program crashed before this line. We can't determine the cause of what happened during the operation "Creating property aliases...". Perhaps the scene was saved with some wrong parameters and now it cannot be opened. I think you can unpack the scene file with Winrar (or 7-Zip) archiver and then open the unpacked file with text editor (wordpad) and see what figures and props are used in the scene. Then you need to load half of all these objects into a new empty scene and save the scene. Then try to open it. If successful, the remaining objects can be loaded into the scene. And save it again... Or does your program no longer open any files at all? What if you save an empty scene? Daz Studio won't open it too?
I did unzip the scene file for WillowRaven. There is something amiss with the scene file, crashes my D/S pretty fast too.
Overall reminder to anybody reading these posts: when making content, Save the individual props, etc. BEFORE saving scene files. If one does not, then the geometry gets written into the scene file and boy can it make a mess.
Best practice is to save each character or segment of a scene to a subset scene preset. Then one can load the required subsets for the scene to be rendered. Then in the event [and it does happen] of a scene file becoming corrupt [for any number of possible reasons], all your work is not lost.
At least WillowRaven can now read the scene file to figure out some of what was in it. However the geometry it was writing is, to the best of my knowledge, a write-off. I do not know why, just that it went nuts writing numbers ... pages and pages and pages of them.
I fully agree with you. It looks like we are in a dense forest inside this file. With the WordPad, I was only able to understand that there are certain sections. For example "node_library", "image_library", "modifiers"... But what links them together? We need another tool. If you wish, you can follow these steps:
Visit the site notepad-plus-plus.org Download and install their amazing (free!) Notepad++ software. Open the unpacked scene file in this editor. The content of the file looks much better now, doesn't it? Especially if you disable the display of some special symbols in the menu: View -> Show Symbol -> Show End of Line (checkbox must be cleared). And it's not over yet. Now let's tell the editor that our file belongs to the JSON file family: Language -> J -> JSON. After suffering with the WordPad, I want to look at this view for hours. But we still don't see the whole structure of the file. Let's do this: View -> Fold All. Everything collapsed into one small square. Click on it. And also on the square near the line "scene". Now we have revealed the main essence of the .duf file. And we can experiment with it.
I think we should take a simpler file, with one character in it. Apply some morph to our character, apply some third-party shape offered by the Daz Studio from the content library, save the scene and then remove that third-party shape from the library. What happens when we try to open this scene? Will the program crash with the last entry "Creating property aliases..." in the log file or not? Unfortunately, I can only do this tomorrow.
Recently I had a scene I'd saved in 4.16 (I think) that wouldn't open again (crashed DS). I opened fine in an older version of DS however. AFAIR (not 100% sure) after saving it in the older version (possibly as a Scene Subset) it would open again in the newer version.