DAZ3d studio won't run
Drogo Nazhur
Posts: 1,111
If I exit out of DAZ3d Studio and so that my new purchases can take effect, it will not start up again. Other programs will launch without a problem but not DAZ3d. In order to get it to run again, I have to restart my PC. Has anyone else experienced this problem and is there another way to fix this ssue besides restarting my system.
Comments
For me, clicking the icon no longer works. I walked the dog and came back half an hour later and it still would not lauch. no error message or anythimg. Just wouldn't start.
I am running windows 10 and it is current. I have checked and DAZ is not running. I have not installed any third party software other than Virus stuff. I'm running Avast & Malwarebytes. Again, the first time I start DAZ, it starts up without issue but once I exist, it will not start again. No error message. Clicking on the DAZ icon acts as if the icon was not even there. I have to do a restart of the computer.
Do you have a scene that you made and recorded before? try to open it.
I seem to be having this issue on my MacBook Pro M1, with macOS Monterey v.12.3; I have the latest versions of Studio 4.20.0.2 and the 4.20.0.8. I had just done a download of new products from DIM, then tried to open 4.20.0.2 and it crashed and unfortunately I did not save the crash report. I found the firewall somehow turned back on, which had caused a previous crash of DIM. I reopened the firewall, tried to open D|S again, no luck. It goes thru all the handshaking stuff in the bottom left hand corner, and then, nothing. I tried uninstalling Daz 4.20.0.2 and its associated files, then reinstalling. No luck, still not open. Previously I ran disk utility few days ago on the drive that has my content, and just did it now.
I just shut down the computer then started it back up and made sure everything was off, then tried to open 4.20.0.2 and after going through all the handshaking, it failed and gave me a crash report I am attaching.
Does anyone have any insights into what may be the issue I am running into?
Or is this another issue with the poor QC on the latest macOS release?
Thanks,
Mary