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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Double-check your setting, go to the Cog Wheel in upper Rt>Advanced Settings>Download Tab and be sure Public Build is the only selected. If it is set correctly, you can Rt click on it and select Hide Package. Did you look at your DS log to see what caused the crash?
You are speaking about the DIM, correct?
See the attached.
Yes, sorry.
Still crashes. Should I reboot?
Forgot to look at the log. Will do.
Sorry missed the attached image. Uncheck Publishing Build. That is the PA version.
My DS log is showing multiple collisions. I don't what this means or how to fi it.
Try checking Custom Size, and enter two values there, like the screenshot. Restart your PC. Try launching DS again. Good luck !
If you look at memory usage, how does that look?
In DS or Windows?
After the virtual memory change and restart I have managed to get into DS. It crashed when I attempted to add a new content library on my D drive. It just will not accept my D library. Don't know why.
After it crashed trying to add the library I reopened it and it has not crashed as yet. But I cannot see my D drive library in the list of content libraies.
I might add that I did not restart after I did what Frank recommended because I did not get a reply as to if I should. So, I don't know if it is the virtual memory change that helped or if it was the changing the setting to Public Build.
See the attached.
Do my DIM Installation tab settings look right?
Did anyone see the log I posted earlier with all the collision warnings?
I don't think the crash has anything to do with Public Build or DIM.... Your physical RAM usage also seems OK. So let's further do something.
- In the virtual memory dialogue, increase Initial size to 160,000, Maximum size to 240,000. Restart PC.
- Launch DS. After you see DS Viewport, instantly press F2, and wait for a while. If there's no crash. Go to Content tab, click CDM button, expand Daz Studio Format. Show a Screenshot.
I checked... Remote Name Collision warnings shouldn't be a real issue. You can just leave them alone. If DS crash issue is finally solved, you can try a fixing in DIM, as per the below screenshot.
DS crashes before I can open the settings window.
I don't know if it is coincidence or not but I changed a setting in the NVIDIA console and can now get into DS. I change item 2 in the attached to High Performance NVIDIA Processor.
I got a snapshot of the DS CMS Settings. See attached.
I noticed that when I manage to get DS to open, it no longer shows that progressive yellow line at the bottom where it is searching for something.
Ahhhhh... you've changed it before? I thought of driver settings but didn't think of that ~ ho.
No, in Content tab. Check the above screenshot. You can access Daz library now?
Somehow I missed this before. I just did as instructed.
I am unsure what you are telling me.
Interesting. I turned off both windows defender and Trendmicro antivirus and DS opened and seemed normal for a few minutes AND I got that yellow line showing DS was doing that search it normally does..A few minutes later when I was looking for that heat plugin, it crashed again.
Anyway, now, DS runs stably or not ?
It was not. BUT, I finally noticed that the D drive library I linked to was wrong and I corrected it and since then DS has not crashed. I am even able to download content via the connect feature and it still hasn't crashed. I will keep you posted on this thread to let you know for sure.
Fingers crossed.
Oh... very odd indeed ~~ I've never experienced the case that wrongly-configured library path results in DS crash.
But anyway, wish you a good luck to have a DS running stably !!!