Crash, crash, crash....crash. Then...crash.
acecombs_b317c01b8d
Posts: 100
I am completely exhausted by Daz 4.10 and this absurd constant crashing. I submitted a ticket about this and was able to backdate to 4.9 but that eventually started with the same crash behavior. The crux is this--I start a project and build a complete scene. I can Iray preview and render without any problem. Then I close the file and later reopen it. Crash. I go through all the menus, check the crash log and change to solid bounding box in the Drawstyles menu. Sometimes it opens and I can hide one figure and reset the draw to wireframe and work on the single, but viewing them both at the same time causes a crash. These are not huge files--385kb is my current project's size. It happens with all my files new or old, large or small, complex or simple. I can work on it while new but the minute I close the file it becomes a crash-magnet. This has only become a problem in 4.10.0.123.
At this point, I've spent hours searching for a solution and days struggling with working on projects while walking on eggshells, knowing that a crash or reopening a file will cause the program to become unstable. I've exported some files to Modo but it doesn't have the same paradign for its renderer and the shaders have to be rebuilt--only .obj files work. FBX and COLLADA do not.
For me Daz is not a free program--I have thousands of dollars tied up in assets. I need it to just work. My computer is a 2012 Mac "cheese grater" running OS 10.12 Sierra,with an Nvidia 1070 8GB on a separate power supply, 16gb Ram, 2 2.4 6-core Xeon processors and plenty of storage. I keep my CUDA and web driver up to date and I reinstalled 4.10 today for the second time. Still crashing. I've been using 3D programs for a while, Modo and Zbrush mostly and while they do crash sometimes, they are not nearly as unbelievably unstable as Daz Studio (at least on my machine). I'm stuck with a massive investment in assets from Daz and Renderosity and I'm dead in the water. I've attached a crash log from my 8th crash today.
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
If both versions are crashing constantly, it's your setup. Sadly, the root of your problem probably lies with the Mac and Sierra.
I have some bits of clothing that have caused my scene to crash probalby 2/3 to 3/4 of the time I tried to open the scene.
What happened was mesh smoothing. I had collision of the clothing set and at some point, the collision item was cleared. It seems Daz does not like to load a scene where mesh smoothing does not have a collision item or the collision item somehow ends up as self collision.
If you can get your scene loaded, check your clothing and figures and make sure smoothing isn't empty or trying to collide with itself.
From the log, it looks like it's crashing right after loading a Genesis 8 figure. Have you recently installed an update for G8? (Some people in an earlier "why is it crashing" thread suspected that might be it.)
Thanks for the suggestion. Unfortunately that does't appear to be the problem in this case, but I'll keep an eye out for it. There seem to be so many ways for DS to crash these days that I'm not sure I'll ever get to the bottom of this.
Is the problem with the G8 caused by updating or by not updating? I did recently update G8. BTW, I tend to agree with your "more like Genesis 3.5" tagline, especially when it comes to stability. Having all these bells and whistles is great, unless you can't use them.
Most of the people in that thread experiencing frequent crashes said they had updated recently, and most of us with still-stable systems had not. Correlation does not necessarily indicate causation, but....
In your render settings panel, under the "Advanced" tab for the Nvidia Iray engine, and just above "Interactive", is the "OptiS Prime Acceleration" box checked? Because that was what took me to crazy crash town a couple of months ago. Drove myself nuts looking for why I constantly crashed, finally tracked it down to that little box. Unchecking it restored functionality to normal.
Thanks, Those Things, for the suggestion--unfortunately it didn't work for me. I'm still living in Crashtown.
I feel like Daz is a category killer--they don't have to rush their software to market. This seems like something that would be caught before the update was released. It also seems like something they should patch--there's a whole infrastructure around DS that's been built by vendors who suffer when the software glitches out. If nothing else, I wish there were backdating options so that people could try their own solutions. Deprecating the software with every version is IMO a recipe for disaster.
Except that the update isn't causing crashes for everyone.
Richard, good to see you weigh in here--your expertise is appreciated. The sporadic causes of these crashes, I think, are part of the problem. Several people have suggested things that worked for them, but that haven't worked for everyone. I know the complexity of 3D software is bound to cause conflicts and each new release has some bugs--a couple of years ago Modo had a glitch that made it impossible for many users to open any file after an upgrade, but they released a patch within a week that cured the issue. As far as I can tell, DS versions are pretty static and Daz doesn't issue patches. With Modo, The Foundry keeps at least two previous versions of the software available to download--backdating to see if the software is the issue is easier. Similarly Zbrush (another category killer) offers patches on a regular basis and they haven't charged for upgrades for almost 8 years, while adding feature after feature.
Given the number of people having problems (and I think that, like fruit flies, one sighting means there a many more unreported) and what seems to be a slowing of work on 4.11, it would be nice if Daz tried to fix some of these issues now. I've started several tickets on this but haven't gotten anything useful from them yet. I'll be sure to post if I do.
Well, Daz doesn't patch - and issuing an updated DS would require that they know what is causing the crashes (and that it be something Daz can fix, not an external factor).