Improving load times
Envixer
Posts: 60
Does anyone have any advice for improving load times for scenes with multiple G8s?
Currently it's taking longer to load a scene than it does to render it!
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
I'm having the same problem. I thought it was just my computer/
No it is the software even on a ssd.
It's all the morphs involved and the textures. You can use https://www.daz3d.com/scene-optimizer and save the textures or try https://www.daz3d.com/resource-saver-shaders-collection-for-iray. Other users have pared down their main collection of characters or divided them among different directories so DS isn't loading all the options between characters to have standing by for mixing.
I moved all my most-used content to an SSD and, sure enough, it didn't speed things up as I had expected. It is a very fast M.2 NVMe drive which I had high hopes for.
Yeah, I did the same. It's the long wait while Daz doesn't respond between deleting everything in the scene and then actually loading something.
Are (m)any of your G8s wearing clothing for previous generations that you've autofitted?
I tend to use a lot of older content in my scenes, but each autofitted item is stored withing the scene file causing it to be bigger and slower to load. The way to fix this is to autofit the item, save it as support asset, then fit that asset to your G8. The end result is smaller files and quicker loads.
Nope... All are wearing G8 assets. The file size is about 16.5 MB, so I don't think that's too big. There are 7 G8s in there, though.
You could review the log file (Help menu) and see if there are any hold-ups or errors causing the loading delays. Also, having many morphs/characters installed tends to slow things down. A good litmus test is to create and assign a new installation of the DAZ library with ONLY the G8F starter pack and see what the load times are like.
No, most of my G8F clothing is dForce which I bought after I had G8F in my workflow. There is a big difference between load times for G8 and her clothing and G3, however. I don't have any G8 men so I use G3M a lot and scenes with just G3M are quick to load and also quick to clear from task manager when I close DAZ Studio.
Interesting. Load a G8 asset that takes a long time to load. Delete the figure, then undo. Undoing a delete takes a LOT less time. That's very odd.
Even more interesting. Instantiate a fully clothed character that takes a long time to load. Duplicate the character with "Duplicate node heirarchies." Takes the same long time. Now, Duplicate the original figure again, only this time choose "Duplicate nodes". This time, it's EXTREMELY quick, even though all the morphs are loaded as you would expect. That's very odd.
Wildly interesting. If you take a figure that has no clothes, then add clothes, the figure will "Duplicate node heirarchies" with the clothes as fast as you would expect. So, it works as you would expect from memory, but not from a file. So, it's the reading a figure with nodes from a file on disk that's not working as you would expect.
I don't think the number of morphs has anything to so with it, except exacerbating the file read bug.
The number of morphfiles does have an effect, but how big, depends on the total number of morphs installed - Do you have 1 000, 10 000 or 100 000 morphfiles installed per figure?
disable plugins you don't use
I didn't disable many but it definitely helped
There was a workaround posted on Youtube :
, ZilverGrafix3D or some such.
It boils down to moving all your G8 morphs to a new directory and "turning it off" for Daz Studio to "see" when you start up.
I can see how it works, but for me that is too much messing with folders and my Daz Library set up to be effective. I imagine if you want a morph package you'd have to go back and forth and load as needed.
To me, that seems as though it would take more time than waiting for it to load, but I haven't put it ot the test.
So where to would you relocate those morphs.
I am a bit unsure.
Daz Studio needs to be able to find them, right?
Genesis 8 Female morphs are found in;
...\Data\DAZ 3D\Genesis 8\Female\Morphs\...
Genesis 8 Male morphs are found in;
...\Data\DAZ 3D\Genesis 8\Male\Morphs\...
The same logic is followed also with the older Genesis generations.
Thank you PerttiA :)
I do know where the morphs as I always install my content manually, but, in the Video, it was said to relocate all the morphs * just live the DAZ 3D untouched*
My question was, where do I relocate them too?
Daz Studio still needs to find them when I want to use them.
Maybe I just do not explain it very well.
But thank you very much for taking the time to reply.
I have 128 GB RAM and thought perhaps the load times would come down if I created a 48 GB RAMdisk and then copy the scene file to it. Well DAZ started to load it and then it would just stop responding. I'll try it again. I have fast M.2 NVME drives and even they take a while to load a large scene.
Hi,
I found a different reason for slow loading (application not responding) of certain characters.
Although I have "monster" CPU, loading of G8F took about 10 minutes minimum. So I had a look into the log-file.
And - tah..thaah: There are some products which cause daz to obviously circle in endless loops. There are some morphs with heavy errors. In this file I saw thousands of lines stating something like:
"warning: error in x-translation of ..."
"warning: error in y-translation of ..."
"warning: error in z-translation of ..."
"warning: error in x-rotation of ..."
"warning: error in y-rotation of ..."
"warning: error in z-rotation of ..."
and than this loop repeats and repeats and ...
Based on the timestamps on the beginning of each entry I could prove those entries identifying the DAZ-freeze.
Luckily these statements identified the corresponding morph files and I was able the remove those product from my content library.
As a result G8F loaded in a very shorter time.
But what's shocking most:
Those products weren't used in the figure to have been loaded. Here I suppose the DAZ developers to change the strategy of importing the morphs to a character.
Please only load the morphs if they're really involved into the current shape setting of the individual character in the scene. Not everything what is located in the "data" folder.
This will avoid a lot of frustration of your users!
Cheers
Andy
It doesn't actually matter where you put them. What that suggests is that you put the less-used morphs into another directory, but you only add it to the Studio content directory manager when you need them. Once you're done, you uncheck the directory in the directory manager, and Studio once again doesn't know those items exist.
The tricky part is actually going to be keeping track of which scenes/characters use those morphs and which do not. Opening up such a scene without making sure that the unused morphs directory is checked will result in a lot of "this morph could not be found" messages when you open a file, and the characters will look wrong when you eventually clear the mesages. You'll then need to remember to close the file without saving, check the directories in the content directory manager, and reopen the file.
I had hoped that DAZStudio would be able to find the absolute path name. That tricky part kindof ruins the work round. Requiring per-scene CMS setups, while better for many than the current behavior, doesn't really work. The only obvious thing is to have a "used" installation directory and an "unused" version. The "unused" is not normally used, so to speak, except when setting up a new scene with new characters. In that case anything from "unused" that is actually used needs to be uninstalled from DIM and reinstalled in the "used" directory.
Uugh. This is horrible. PLEASE DAZ FIX THIS, sorry to shout. Oops, I lied.
It would be so much better if there was a load on demand system for morphs.
I mean, load the ones used in the scene and get the scene up and running, then load the others in the background or when applied.
That would be a major software change, though.