I hate Studio
lorraineopua
Posts: 643
I'm thinking of burning the program to a disc, then driving a stake through it, then burning it in a bonfire, and finally, burying its ashes with garlic so the bloody thing doesn't reanimate. Why oh why does Studio go unresponsive, to the point it can't even be killed, and when I shut down Windows, even that can't kill it and I have to hard shut down. Only 1.5gb being used out of 20 and a fraction of the cpu. So over it. W7, DS 4.12.0.86
Post edited by lorraineopua on
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
That's not really enough information to diagnose the problem. I haven't had that kind of problem with Daz, though I have suffered through it being quite slow under certain circumstances (like all packages - try deleting non-deformer history on a smoothed, rigged, character with blend shapes in Maya).
So under what circumstances is it freezing up?
(Oh, and that feeling you're getting, that kind of frustration is normal, usually in packages you're not all that familiar with - I get it all the time though no longer with Daz as I've been playing with it for several years now on and off and kind-of know how to use it without taking it out and shooting it).
Hmm that would make a great series of images
(Sorry for not being helpful, still on 4.9)
W7??? Hasn't been supported for quite some time now. The Nvidia studio drivers require a certain level for a NVidia card both of which came out during the days of W10.
I'm still on W7 pro and it works just fine; I'm staying on it until either Studio itself no longer runs on it or Nvidia quits providing W7 drivers.
To the OP - does it just sit in memory like a lump, or does it use some cpu from time to time? Is it marked as 'not responding' in task manager? Is there anything in the way of errors showing near the bottom of the log? (Help -> Troubleshooting -> View log file)
I have 14 Years using DazStudio and you are right to hate it, and yes, your issues are my issues too, specially with Gen8 released version all is more slow to load, never works the Cancel button neither the X window button, sometimes the content panel slides to the left with no reason, forcing me to reinitiate the software, and the list goes and goes on.
good for you not even trying Hexagon or Carrara.
dunno, both Carrara and Hexagon if they crash close pretty quickly
There are no problems in using W7 with DS. The scaremongering Microsoft and associates are promoting, is just to scare people to jump on the W10 wagon.
I actually had to for the 1st time ever reboot my PC because even the task manager in Windows 10 would not stop DAZ Studio 4.12.2.6 public beta.
Not completely.
The typical user is unlikely to do what's needed to keep a W7 machine at least reasonably safe; for them W10 is the safest option.
windows 10 is free if you want it to be. just man up and download it.
Because you are using the 32-bit version.
Wow , that is your reply , because the 32 bit version is used?? You have to be kidding .
What? You complain about the memory limit of the program. Actually switch to the 64-bit version to make use of the RAM you're having installed. Furthermore, Windows 7 32 bit allows a maximum allocation of 2 GB per application by default.
What fraction of the CPU? I guess it's 1/number of cores, as DS has a single thread running full pelt to clear up as it shuts down (if that is what it is doing). As others have said, without more details of your system hardware or what you are doing when it "freezes" it's really hard to say anything useful.
Well that would be a very good reason for DS not using all your RAM, since 32 bits programs are limited to 2GB.
I don't see 32bit even mentioned anywhere, where did the assumption come from?
none of the last few derails were anything from the original poster
From the limit on used memory the OP posted, which is very typical for 32-bit programs.
Sorry I was so long in replying, and I'll try to clarify. I'm using DS 64bit, I have an i7 and 20GB of ram and I render with 3dl. DS was using 1.5GB of ram and the cpu was barely ticking over. All of a sudden the program stopped responding. I left it alone and went and played on my phone for half an hour or so, figuring I'd let it sort itself out. It didn't. So I tried to kill the program and it wouldn't close so I shut the computer down and it sat there for ages with the shutting down screen, till I got fed up and hard shut it down. When I started it up again, there was a problem with my library hard drive which I had to close and start again. All that's never happened before and I'm now paranoidly saving every minute in case I lose a bunch of work again. There was only props in my scene, no figures and it's a scene I've been working on for a while, adding to it and modifying. Puzzled I am.
Which graphics adapter are you using and which driver version?
Well, it's possible that the drive problem caused the DS problem rather than vice versa, or that some other system-level issue triggered both - is this something that just happened the once, or does it keep happening?
Related to hard drives, how are the Power Options configured, is windows allowed to save power by shutting them down after a certain time of inactivity?