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 was having this problem with heavy scenes. If I wanted to get rid of a character, I had to delete each attachment (clothing, hair, etc.) seperately before deleting the figure. If I made the mistake of trying to delete the character with all the clothes still attached, it would take two of three times as long as it would have deleting the items seperately. I don't seem to have this problem anymore. Not exactly sure when it stopped, so I can't pinpoint the specific reason, but I recently bought a more powerful laptop. It could be your system can't handle deleting multiple items at once from a heavy scene.
The 4.12 upgrade also came recently. That could be it too, but someone above reported still having the problem after they upgraded.
Well I've noticed that grouping/ungrouping complex things can take a long time, so maybe it's related. When deleting an object in a group it probably needs to be ungrouped first which may be what is taking a long time.
I had problems before 4.11, but that release fixed them, at least for me. I think the issue was related to changing the parent. For complex figures like Genesis 8 up until 4.11 changing its parent took ages. For deleting it probably was unparenting an item before deleting, and this is what took ages.
If anyone is still suffering this in 4.11 or 4.12 then raise a ticket giving as much detail as possible, as there maybe cases where the bug was not fixed
So I realized there is a difference between the Pro and Public (beta) builds. I primarily use the Public build right now. When I load heavy scenes, I can select a character and delete it quickly, clothes, hair, and all. If I want to get rid of half the scene, I can a massive grouping and Poof!
The other day I imported a similarly heavy set into one that was bare bones. All I wanted was a few light props and their placement. When I took out the part I want, I cliked on the second scene's set and hit delete. Then waited for more than an hour before giving up and reloading. Like I used to before I jumped on the beta-bandwagon, I had to delete everything piece-by-piece with the annoying lag.
Currently, the Public build is technically an older version than the Pro build, so I don't know why it took a few steps backwards from the public build when it was released.
I know this is an old post.. But its something that has plagued me since version 4.9 days.
I tested this again after opening and old save of about 5/6 months. Now I have two pc's that are pretty much identical hardware setup both AMD CPU. The one is my work pc and the other my render pc. I opened the old save file and tried to delete just two characters, one Gen8 and one Gen3 model. It's not a heavy scene in the sense of lots of assets, models etc...
On my work pc which as i said is identical to my render pc except it has a single 2070RTX GPU takes minutes / hours and nothing happens.
I open the exact same file on my Render pc as i say similar to the work pc except here i have 1 x 2070S and 1 x 2060S GPU's and it deletes teh character(s) almost immediately.
The mind boggles. Both pc's have same version of Daz v.12 installed.
Funny, I just made a thread about how my problems parenting or unparenting figures to groups taking forever seems to have been solved in current version. More to the point, I think sometimes this stuff has a lot to do with your own configuration; hardware, software, and setup. I say that because while I had problems parenting figures to or away from groups, and I had problems saving wearables, I can't ever recall more than one person ever sharing those problems. So I had to at least suspect that few others shared my issues. Which suggests you might want to make a point of reporting your bugs through official channels, which I never did...
I haven't used New to clear the scene in years. I just quit DS and restart. Much faster, or at least, it was when I started doing it...
I haven't used New to clear the scene in years. I just quit DS and restart. Much faster, or at least it was when I picked up the habit.
See? That's what I mean - it's down to some software/config/godknowswhat on your work PC.
Edit: and I didn't know it was an old post. I could've sworn it said "May" next to everyone's comments a second ago...now it says October.
Wonder if it can have something to do with AV programs scanning files that are being processed, that can slow down things considerably. If you have an AV program on one machine and none on another, or the same AV program with different real time protection settings it can make a huge difference. Defragmentation can also slow things down, I've seen files fragmented into many thousand parts.
Here https://www.daz3d.com/forums/discussion/comment/5373486/#Comment_5373486 i wrote my theory about it:
From my testing, deleting objects takes Daz Studio about as long as loading objects, and that again can take quite a long time depending on how many morphs you have installed. So if loading a scene takes a minute, you can expect clearing the scene (and thus shutting down Daz Studio) to take equally long.
Depending on how many morphs you have installed, you will probably find that loading a single G8F is a lot slower than loading an old V4, for example. And if you are loading a scene with multiple such figures, loading and deleting the figures will take proportionally longer. On my system I took out an afternoon and zapped all my G8F morphs under /data/Daz3D/Genesis (sory, not at my computer right now) ... and selectively reinstalled those that I actually use. I was able to bring down the G8F loading (and deletion) time to five seconds. (Please back up any files before you delete them.)
Agreed
I have to disagree as i have just now disproved your theory. Again loading a scene that was the old one i told you guys about but i saved it and then deleted the chars on my Render pc and it deleted it so fast. I then worked with this saved version on my Work pc and now i am trying to delete just the clothes for the one character but its taking frustrating long, As seen in the image. Ungroupign makes not difference. Restarting the pc or daz no effect as i just openened this file after i just switched on my pc as it was off the whole night. In task manager it shows Daz Not responding when you try to delete.
So now i copied the same file to my Render pc and deleted the two characters each taking 1.2s to delete(It takes around 2min to laod the scene). Basically sorry to say disproving your theory.
As i say my PC's are almost identical in hardware and identical in DAZ/DIMS setup. No this is something else that daz is doing on one pc and not on the other. Nothing to do with the actual DAZ file i am working with. Image "clothes remove2"you can see the deleted characters i did so on my Render pc. Its the same file as shown in image "clothes remove".
I have this issue too, but it is intermittent, though it happens more often than not. Also, editing after stopping a render leads to several white viewports before Studio stabilises. Not to mention posing with a fully accessorised character.
It's annoying and it doesnt appear to happen with many of my files. Seems more older one's or files that have an asset that just battles to delete. I know some assets also render very slowly compared to others. But as iv'e just proven doesnt seem to be file related as much as I can delete on one pc quickly but not the other.
You have the same products installed in the libraries on both?
Yes... Both my assets/libraries are on xtra drives installed (not on OS drive as DAZ application is installed). I copied one set to the other drive. Then in dims i made sure points to correct drives. I did not hower copy or use the "settings" over. (forgot the name now. I think it resides on C:\Users\Roaming ?)
When i aquired new assets from DAZ or Renderocity i install via DIMS on mostly my Work pc then i make sure to copy the downloaded file in Downloads folder to the other pc so both are up to date with same installed assets. If i dont do this then obviously when i work on a file it will load incomplete on the pc that i did not copy the assets over to. Also as i said keeps things equal both sides.
Correction: of course this would only be a problem when loading stuff unless perhaps if the AV program is scanning memory or something when DS is deleting stuff.
Agree... I run NOD32 paid for version on both pc's so if my AV was going to be a problem would do for both pc's. No this whole thing is strange. Why only the one pc, why only some files? It's random for sure. I'll probably find in future a file that maybe battles to delete an asset or character on my Render pc but deletes fine on my Work pc.
I use the public beta 4.12 and I saw a comment earlier about how it's quicker to exit the program and relaunch, well gone are those days I think. What I've noticed is that Daz Studio will remain running in the background, clearing the scene or whatever it's doing, for close to 20 minutes sometimes. And it will not let you relaunch Daz Studio until it's finished, it's as if it's saying "I'm going to take my time and you will wait until I'm good and ready. Do you understand me, human." I have a SSD and 32 gb of memory with two GTX 1070's, and it still goes slow on just one figure.
Do you have the Octane plug-in installed? What about other third-party plug-ins? You can use http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start to disable them, restart DS, and then see if it will now shut down more quickly. If it does try one-by-one enabling the plug-ins in Help>About Installed Plug-ins, restart DS, and see if it will then shut down quickly.
I've yet to see any negative consequences from ending the process in Task Manager on Windows. I mean, Daz crashes often enough on its own, and that doesn't seem to cause permanent damage in my experience, so I don't know how much worse us pulling the plug by choice could be, as long as we save our work first.
I also exit, task manager and restart rather than use 'new'.
Are you sure the crashing isn't in part a consequence of the force quitting? It is a drastic option and should not be used by default, only when thee application has truly hung (no activity in task manager or the equivalent) - if that happens often then the important thing is to figure out the cause.
hi I have this issue sometimes so I'm experimenting with a little tool that frees unused RAm and it really seems to speed things up a lot. It's a little software by Sordum software house (well software house it's too much maybe: as long as I know it's just a guy making useful freewares) and you can find it here: https://www.sordum.org/9197/reduce-memory-v1-3/
I'm testing it since two days and I can say it works great in my situation.. when Daz seems to be stuck I hit the Optimize button and in two seconds I'm ready to add a new figure. There are of course many way to free unused RAM (even by command line) but if you use the tool I would disable the automatic optimization (even if enabled no harm should be done because the OS is able to tell which portions of the RAM are not claimed by activities and executables)
It baffles the mind why this question has not been answered yet. I can open daz and try to load a base G8F character and it will spend five minutes deleting objects before loading the figure. I'm using a 1tb ssd to hold my content library and I have a 1tb M.2 for my OS and Daz. I'm also using a Ryzen 7 1700x and I have two GTX 1070's. I highly doubt this is a hardware issue.
It has been answered, at least beyond the obvious caveat that your security software may be a factor if it has to scan each of the many files that get loaded. There is a lot of processing to do with linking morphs, as morphs are added it will presumably slow exponentially.
I can understand that loading things may take a while, but clearing a scene? I presume that data are stored in variables and arrays in memory (not on disk) and these can be cleared in a split second. Even if they are stored on disk the amount of data can't be so large that it takes minutes to clear it. There's no need to process any data, it's just about clearing. With smaller scenes I often just delete the objects (or any I don't need for the next scene) instead of clearing the scene, it usually takes less than a second. Undo data will be cleared automatically as you build the new scene because of the 20 undoes limitation.
Another thing is why it takes so long (up to 30 seconds) to save a finished render. It's already present as a png when the render is finished, and copying and creating thumbnail takes less than a second.
What's always struck me as odd is that it's faster to shutdown DS and restart it, as slow as that it, than to wait for everything to get deleted when creating a new scene after saving the old one.
It's a function of the software design and the paradigms in use, as is the slow loading. Creation and destruction of thousands of small objects is no sweat for a modern OS. The problem is if those objects fire off events to a bunch of other objects (exponentially increasing the amount of code that gets run) when they die. There's an additional burden of creating command objects for undo/redo, which in Daz seems to work sometimes but not quite always (e.g. undo a delete and in some cases materials are messed up). Impossible to say without seeing the code of course, but I suspect something like that is going on.