Slow deletes
bsett
Posts: 74
I have a fairly powerful computer and have been able to build, combine and render scenes with as many as 23 characters in them without much of a problem. But when I have a scene that has several characters in it and try to delete a couple characters it takes several minutes (and in some case hangs completely) for them to be removed.
Just curious as to why this part of the process takes so long. Using DAZ 4.8 on a 64 bit Windows 7 pro system with 64 GB ram, i7 5960x CPU and GeForce GTX 980 GPU
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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
YES! I was just about to post on this as well. I just finally switched from DS 4.7 to 4.8 over the weekend and this has been happening to me too, despite never having a problem with the 4.8 Beta. It seems to affect primarily the human figures as well. Lights, cameras and props delete with no issue, but try to delete a G2F and it locks and burns every time.
I’ve found for sets I like working with it’s faster to save a version without any characters and reload that as apposed to deleting a character. I also will make character groups and just make the whole group invisible instead of waiting for them to delete.
I believe it has to do with purging the memory. The more complex the mesh, the more it takes to recalculate everything. don't forget, it isn't just the mesh in RAM it's several other interactions as well. The same you will find when you exit D|S, It must back out of the scene and purge the memory. The more you have loaded, the longer the pause before it exits (or deletes).
Except that it doesn't have a problem exiting DS, it does the lock up with just a G2F loaded in an otherwise empty scene and, as noted above, neither 4.7 or 4.8 beta ever had a problem. There's something specifically funky going on with the current version of 4.8.
If there is a problem with DAZ being able to purge the memory then there is something wrong with the program code. As least in how it interacts with my system. On my dual monitor system I can multi in DAZ (not Iray rendering of course), PS, Maya and still browse or read emai.
It shouldn't take 20 mins (just timed) to delete a single character in a scene with only 3 characters in it.
That is some crazy time! 20 minutes is a lot. I assume you are on the 64bit version...that 20 minute delete time reminds me of using the 4.0 32bit standard....
Actually, I'm currently still on 4.7 Pro, and believe me, the slow deletion has been an issue for me ever since I moved from 4.6 up to 4.7! And no, it does not matter how complicated the mesh is, or how full (or empty) the scene is. I've seen a delete take literally OVER AN HOUR to complete. And no. I'm not exaggerating. I timed it. It took 1 hour and 32 minutes to delete a SHIRT from the scene. A single, low-poly, SHIRT.
My computer is pretty powerful, too. So it's not a lack of RAM, not a lack of memory in any way. This is something that changed (for me) between 4.6 (no matter WHAT I had loaded, a delete was practically instant!), and moving to 4.7, where the problem immediately began. I am another one who just closes the freaking program, rather than sit and twiddle my thumbs for an HOUR while DS decides whether or not it's actually going to delete the item from the blasted scene.
It's not restricted just to figures for me. It's with anything. Clothing, hair, jewelry, props, plants, basically any mesh object in the scene. Period, end of story, it takes forever and a freaking day to delete it, and if the problem still persists in 4.8, then that's really just one more reason that I'm not in a rush to jump on the Iray bandwagon. The length of time required for deleting (a single Genesis 1, or at one point even a single Michael 3 in the scene), and removing ONE piece of clothing is insane.
I stage-save at this point. I add something, I save a file. I add something else, I save a file. If I don't like the previously added thing, then I just delete that file and load the most recently saved before version. I don't have the patience - or the temperament - to let Daz Studio chew for a bloody hour just to delete a single pair of paints or a single pair of eyeglasses from the scene, and at least for me, this problem began immediately with the upgrade from 4.6 to 4.7.
Strange, haven't noticed this. Just did a test, loaded 6 different G2F characters all with different hairs and clothes. Took about 5-6 minutes I think. Saving the whole scene took a few seconds (surprised me a bit actually). Deleting all objects one by one (about 25 in all I think) took about a minute. Didn't render (would probably kill DS with only 8 GB RAM and 6 already used) or do anything else. CPU is an old 2.6 GHz quad core, RAM DDR2 so it's not particularly fast according to today's standards,
Like bsett says, could be a memory leak or something which is first triggered when working with certain features.
Window's memory management is driving me nuts sometimes. If you have a program open which is using a lot of RAM, and you don't use the program for say an hour or longer, Windows swaps the data in memory to disk which means that when you start using the program again it can take a looong time before the program responds, because Windows now have to read the data from disk back to memory.
I have from time to time noticed it takes longer than it should (10 seconds or so) to delete a scene. Nothing like 20 minutes, though.
Maybe the extremely long delays are caused by hard drive or other computer issues. For example, what's D|S doing with that log file? Is there something it does to the log when it changes scenes? It would have to close the log when exiting. Is the filesystem doing something that's preventing that? Is there a permissions/filesystem issue for the files that are being deleted from the brickyard?
I have to wonder about the purging of memory. That's all done by pointers, and fairly common Windows (or Mac) calls to unallocate memory. If that's the problem, it would likely be a programming error. D|S isn't doing (or should be doing) the purging of any memory. The actual mechanism to release the memory is done at the OS level (well, if they're not insane!).
For me anyway my scenes always closes fairly fast it's just when I'm trying to delete an item or character out of the scene. Also as stated above I can move about complex scences in DAZ while using other 3D apps such as Maya and PhotoShop at the same time without any problems. It's just when I go to delete something that I'll get the "Not Responding" delays. There is one scene in my Gallery thats has 23 characters in it so my system shouldn't have any problems when it comes to just being able to delete one.
So, as an experiment I uninstalled the beta I had installed and loaded the latest public beta of 4.8 instead (64 Win). Works like a charm. Tried the current 4.8 again - immediately locks up on delete, even thgouh the only thing in the scene was a g2f w/hair. Same exact files. llibrary, runtimes and plugins, same computer, same session.
If that doesn't say that the problem is specfically in the current version of 4.8, I don't know what does. On the other hand, since the Beta does work, I'll probably just use it until the next update for 4.8.
What the heck. I just went a step further and opened G2F with BOTH programs simultaneously. I hit delete in the one in 4.8, it started locking up and then I went to the beta and hit delete on that G2F. The one deleted instantly while the other is proably going to sit there for another 10-15 minutes. That's kind of crazy.
Lol it might be easier to open the scene.duf in notepad and delete stufff
BTW, I'm using 4.8.0.59 - 64 bit
Time to start looking at operating system, file system and version numbers...
This problem persists in DS 4.9.3.166. It takes longer to delete a scene (3-min) than it takes to restart the program (5-sec).
Rig: Win 8.1 64-Bit on SSD, ASUS P9X79WS w/ i7 3970x 3.5 GHz & 64-GB DDR3 RAM, nVIDIA TITAN OC x 4
Scene: 1.343m triangles, 6,794 nodes
Whatever DS is doing to clear the scene is grossly inefficient.
PS: The existance of any geografted, heavily modded G3-Female characters seem to worsen the problem substantially.
Same problem here.
Deleting or File/New seems makes Studio preform some memory clean up that can take a while. Shutting Studio down also makes it preform memory and temp file folder clean up that takes often just as much time or more, so immediately restarting Studio could cause issues.