Adding to Cart…

Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Well if you shut down DS normally it may still run for a good while and during that even increase RAM use considerably, until it shuts down completely. And with the later versions you can't restart it before that has happened. So for instant restart you have to kill it in Task Manager, it seems.
Well I don't know the code either so hard to tell what's going on. Considering you can manually delete everything in a scene in a second or two and then load new stuff into that scene instantly, it does seem strange though that clearing the scene using NEW takes so long.
I am facing this issue right now in the current 4.12 release version. As others have hinted, it seems to be a lot worse when you try to delete several objects at once. So I left my PC alone for about 2 hours and a half to do other things and now that I am back DS is still busy deleting those objects.
2.5 hours? Well that doesn't sound right to me. Sounds like it's dead actually. When I read slow deletion, I was thinking seconds or at most a few minutes, depending on scene complexity, not hours.
20-25 minutes has been quite normal before DS has released the resources and exited from the task manager
DS may have been busy doing something when you deleted the objects. If it's not done in two hours, it's not going to get done, and you'll need to kill it.
wow and I thought 5-10 minutes for release was taking awhile.
One reason I'm still using 4.12.0.86, that allows opening a new instance even when there is another one running (closing down)
Current versions of DS allow starting a new instance, but it has to have a different name (and of course if DS is in the process of closing you can't use it to run the script for launching instances - though if it's a frequent issue you could prepare a shortcut iin advance of the need).
I can open a second instance with the current public build.
I'll just wait for the next non-beta as there are no problems with this setup.