Trouble-Shooting Render Crashes in DAZ Studio 4.x

Render crashes can be very annoying after a lot of work has been done.  They can also be difficult for our software testers to to duplicate.  For this reason, you may need to trouble-shoot a render crash.  This may not resolve the issue, but it can give you a work-around or insight into what is causing or associated with the crash. As always, it is recommended that you save the scene before you render it, even when renders are working happily.  You may want to use progressive names, like 'Victoria Garden 01,' 'Victoria Garden 02,' etc.  This also lets you to access earlier revisions of your scene.

In general, most render crashes can be prevented by using the 64-bit version of DAZ Studio.  Render crashes are much more likely in the 32-bit version of the software.

Do NOT Overclock
We strongly recommend that users do not overclock with DAZ Studio especially with rendering.  Overclocking may an effective choice for some applications such as games where not all CPU cores are used.  However, this can be disastrous with rendering in DAZ Studio where all CPU cores are used.  In this circumstance, there is no wiggle room and DAZ Studio will probably crash.  Your computer may suffer other consequences common to overclocking.

Improve Hardware
Rendering is very hardware intensive.  While this is not an option for all users, improving hardware can greatly improve render stability.  Increasing the processor power and increasing RAM (especially on a 64-bit system) can greatly improve both speed and stability for rendering. 

Update Studio to the Latest Build
Installing the latest build accomplishes two things.  First, it gives you the latest available version with all the most up-to-date bug fixes.  Second, if you do find a bug and report it, our software testers can attempt to duplicate the bug.  If you are using an earlier version of DAZ Studio and report a bug, our software testers will usually not attempt to duplicate the issue.

Update the Content
In addition to updating the DAZ Studio application, you should update the content products in your scene.  It's less likely, but possible that an updated content product will help render stability.

Reset the Render Settings
You may have a combination of render settings that isn't compatible with the content of the scene.  Reset to the default settings and try to render again.  To do this, go to Render --> Render Settings --> Advanced --> Restore Default Settings. Make sure you don't tweak any of the render settings before you do the render as that defeats the purpose of resetting them to the default.  By default, DAZ Studio uses the 3Delight render engine, not the hardware-assisted OpenGL of your graphics card.

It's possible to change the render settings to support a much higher detail in the final render.  This is a useful power of the renderer in DAZ Studio.   These settings increase memory usage on your computer and can significantly increase render time. However, they are not always necessary. More detailed renders are good for pictures that will be printed at a high resolution such as posters.  These settings may be overkill for pictures meant only for web or computer.  The extra work placed on your computer's hardwork may not really make a noticeable difference in a render intended for display on a computer monitor.

Progressive Trouble-Shooting
Use the process of elimination to see if one or two components of the scene is causing or associated with the render crash.  To do this, you should re-save the scene under a new name for testing purposes.  Give the scene a name that you won't confuse with the regular scene.  You could call it 'Victoria Garden Testing 01,' for example.  Now, eliminate half of the content items in the scene.  For example, if you have Genesis, a skirt, a hair product, a blouse, shoes, and couch in the scene, remove the couch, the shoes, and one of the clothing models and then try the render again.  If it doesn't crash, then it's possible the crash is associated with one of those items.  If it still crashes, continue to remove more components.  You can save each change in a scene with a new name and then go back to the previous saved scene to narrow down your search further.

In addition to removing models from the scene, you can remove textures from a model in the Surfaces (Color) Pane.  This of course is for trouble-shooting purposes, since you normally wouldn't want to render a scene without textures.  

Check the Log File
DAZ Studio creates a log file that lists what the application.  It's possible that what is causing or associated with the render crash will be shown in the log.  You can find the log in two different ways. HELP --> Trouble-Shooting --> View Log File.  You can also find it on the hard drive here:



users/[user account]/Library/Application Support/DAZ 3D/Studio4/log.txt


[User Account]/AppData/Roaming/DAZ 3D/Studio 4/log.txt


Report a Bug
You can also report the render crash as a bug in our help center here:  Please give as much relevant information as you can. Our testers will attempt to duplicate the crash. If they cannot successfully duplicate the bug, it's unlikely that your bug report will be worked on much further.

We use the bug reporter to track bugs and feature requests. Our Q.A (Quality Assurance) team and our developers use this information. The bug reporter is not tech support, but may be necessary for issues that are determined to be bugs and thus beyond the scope of tech support. Feature requests are also accepted through the help desk.

Was this article helpful?
12 out of 12 found this helpful
Have more questions? Submit a request