DAZ taking "forever" to open a saved scene
Drogo Nazhur
Posts: 1,164
Lately, it is been taking DAZ an extremely long time to open up a saved scene. I'm talking 10-15 minutes or longer. Even scenes with only one character in it and no background props. Is this a known problem? Is there a work around? Is it something that I might be doing wrong?
Any suggestions would be appreciated.
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
There are several possible causes...one that has caused problems was certain AV software, after an update started scanning the entire content library on scene loads (it also caused long load time for content loaded directly from the content library).
Another is certain plugins would add a lot of plugin specific content to the scene file...sometimes, excessive amounts of it. Saving the affected scenes as scene subsets, with only the content you want in it, seems to strip out all that 'extra' data.
A third possible cause is using a lot of content that is not in native duf format. Older 'Poser Format' content in a scene files will increase load times...the more of it, the longer it will take.
There's a few more that I can't think of right now.
If you are loading a scene with V4 or M4 with their entire set of morphs & such those take a long time.
Saved scenes that use to load in a minute or two now are taking an HOUR or two. And, viewing it via Task Manager, DAZ is using 2.5 GIG of data. Over the months, I have purchased a lot of DAZ packages, could this have something to do with it? Is anyone else experiencing this?
What AV software should I be looking for and what / how should I be adjusting it to help matters?
I've never had saves bloat that much, but I did have a few older saved scenes from a friend that took agest to open. He had saved over the same file repeatedly and that had added new null objects to the file everytime he saved. He had literally hundreds of null objects saved that was bloating the load time and file size. His issue was he was using an old version of the 'reality' plugin that added new scene data. Any chance you're using an older version of Reality?
I'm running the current version of DAZ. How do I check if I have "null" objects?
I recently had an issue with both opening files and saving files, taking forever......it turned out to be a hard drive failure. I ignored the warnings and lost weeks worth of work. Is it taking just as long to save a scene file as it is to open it?
I second that...if it suddenly starts, for no apparent reason (like there wasn't an OS or AV update), then back up EVERYTHING immediately!
I am currently backing up my install, as I write this, because last night the 'Textures' folder disappeared between loading one item and the next and it took over half an hour to load a single item, when less the item before it took seconds. There doesn't have to be such drmatic evidence of impending failure to impact load times...
Opening takes much longer. Saving takes minutes. Opening takes hours and I really mean hours. I don't know if I accidently changed some setting or if a Windows auto update did something but no other programs seem to be affected. And, memory usage is way up during the opening stage -- 7.5 gig of memory is being used.
Any help / suggestions that anyone can offer will be greatly appreciated.
Like they said, openings taking several hours is often indicative of the OS / HD firmware repeatedly re-trying to read failing sector(s) on your HD. Why you don't have this problem on saves is because the OS & HD firmware won't write to such sectors if they are blank. However, if data is already written to a sector and it begins to fail or fails then the OS has not choice but to try and recover the data.
You should buy a new HD and copy everything to that HD but in the meantime you can use if you are using windows:
a) rightclick on HD icon, Properties for Drive containing your DAZ content, Tools, Error Checking -> Check
Or if you are running osX you need to
a) run fsck -y or whatever consumer utility Apple has made for users of osX.
One thing that drove me nuts was when I ran into the time of a weekly hard drive check. "Intel Rapid Story Technology" took hours to check everything, and during that time hard drive access for anything could have been measured with a sundial.
Only a sundial? I thought that atomic clocks would run out before it would finish...
I got around it by scheduling checks late at night while I was sleeping. Yes, it requires leaving the computer turned on, but it also takes the intensive, can't do much else with it parts out of the timeframe of active use.
I did this and Windows said that it did not find any errors / failures. Do you still think that the hard drive is going bad? Also, I noticed that the scenes that I have been saving have been getting bigger in size averaging about 50 mB
Also, the amoint of system memory being used during an open goes through the roof. I've seen it as high as 7.5 Gig.
That sounds like it's doing some serious heavy processing, and reminds me of an issue I ran into a while back.
Do any of the items in these scenes have LIE-based textures, by any chance?
How would I know?
What do I need to look for to find out?
I don't think it's HW I think you must have some DS studio plugin that's bugged out. As I have no ideal about what you have in your scene & as plugins I suggest you build a few simple scenes & test how they open during multiple openings.
Furthermore you can open the task manager & sort the tasks both by CPU load & memory load and then you can use a utility called 'Very Sleepy' to sort on exactly what that is in DAZ Studio that's causing the problem. Very Sleepy must be downloaded & installed first. Just search on the net for it.
Eliminating the hard drive was needed, because drive problems can cause the same symptoms.
I agree it's back to the software side of things...
I've done some more experimentations and this is what I have discovered ... a lot of my older / simplier scenes load normally but my newer ones are the ones with the problem.
I created two different scenes -- one with a G3F character with various morphs (muscles, older age, etc) and one with a G2M character with various morphs (body hair, etc.). They do not appear to have anything in common. Yet both scenes took almost two hours EACH to load.
There is something obviouly going on with the new scenes that I am creating that was not happening with the older scenes that I made. How do I begin to track down what it it? What am I looking for and how?
Again, any guidance that folks can offer will be greatly appreciated. I am at a complete loss.
How about just trying a "bare" G2 or G3 scene? Do they open really slowly?
Does Studio itself take a very long time to open?
Well that might be cause of have to load a boat load of morph & other settings, I know have many, many morphs & character seettings as part of G3F & G3M with the multple DAZ and 3DU characters I have added over the past 2 months & have noticed a longer time loaded a scene but it's more like a minute longer to load a scene, not 2 hours & more.
It still sounds to me as if you have a sector problem but if the SW diagnostics say you don't then well you don't probably.
Is your old data saved on one HD and your new G2 & G3 data saved on another HD? Look for clues like that. And try Very Sleepy to see what DAZ is doing for 2 hours!?
4.9.3.166 has a fix for overly-aggressive referencing of assets (listing assets that were available on the figure but not used on save) so it may help to load the things and resave them in the nw version, hopefully they will make fewer asset calls on reload and therefore will be loaded more quickly and perhaps with less memory used.
I'm running .70
How do I upgrade to .166
Everything is on the same drive.
What's a good / safe place to download "very Sleepy" from?
I downloaded the compiled version from here & installed:
http://www.codersnotes.com/sleepy/
but you can download the source code from github & compile it yourself if you like.
I attached a screen shot of Very Sleepy showing you what it looks like when I select DAZ Studio while I am rendering.
Since upgrading to the new version of DAZ I am having this exact same issue.
So you are pretty much dead in the water as well?
I'm running very Sleepy -- what should I be looking for?
This process has been loading for 9+ hours -- started it before I went to work, disabled the sleep mode on the PC so that it wouldn't stop processing after detecting inactivity, came back from work to find it still running.
Now here is where you get to file a ticket with DAZ Support. They should ask for one of your offending scene files I'd think.
Based on your Very Sleepy, it looks like to me DAZ Studio is waiting for something that is never going to happen.
Here is a synopsis of the function at 100% in your Very Sleepy:
void QCoreApplication::removePostedEvents(QObject *receiver, int eventType = 0)
Removes all events of the given eventType that were posted using postEvent() for receiver.
The events are not dispatched, instead they are removed from the queue. You should never need to call this function. If you do call it, be aware that killing events may cause receiver to break one or more invariants.
If receiver is null, the events of eventType are removed for all objects. If eventType is 0, all the events are removed for receiver. You should never call this function with eventType of 0. If you do call it in this way, be aware that killing events may cause receiver to break one or more invariants.
Note: This function is thread-safe
This function was introduced in Qt 4.3.
Do you have reality installed? I had this issue until I discovered my saves were being filled with reality hidden nodes... hundreds of them.