Different rendering scenarios that can result in your resulting render being a black/ blank screen. Learn why and how to fix it.
Last updated
In certain scenarios, your resulting render using Boost for Daz might turn out to be a black screen. We've documented the different scenarios and possible solutions below.
Black Screen Renders can occur during:
Review all...because one or more of the following scenarios might apply to your specific situation. If none, reach out to us on Discord and let us know, so we can help you figure it out.
| Potential Cause | Proposed Solution |
|---|---|
Review all...because one or more of the following scenarios might apply to your specific situation. If none, reach out to us on Discord and let us know, so we can help you figure it out.
| Potential Cause | Proposed Solution |
|---|---|
Render Package too large for selected GPU If the render package (created once you hit the render button) for your project is too big to fit into the VRAM of the GPU that you selected, Iray Server is unable to render using the GPU, and as a protective measure, falls back to using the CPU on Boost for Daz. (This is a default Iray Server behavior). However, rendering via CPU is not supported in Streaming mode. As a result, the render is unable to complete and results in a black screen.
Pick a GPU that is sized properly for your specific project Use our handy GPU guide to select the GPU with the appropriate amount of VRAM to accommodate your complete render package. Doing this correctly will avoid the Iray Server having to fallback to CPU rendering and black screens.
GPU is turned off in Iray Server Admin (rare) Prior to hitting the Render button, if the GPU is turned off through the Iray Server Admin, this will effectively signal the Iray Server attempt to render your project using the CPU as a fallback. And since CPU rendering is not supported via Streaming, this results in a black screen render result.
Iray (in Daz Studio) mismatch with Iray Server (on Boost for Daz) Notice rendering progress resetting/looping after a specific iteration Though we do our best to keep in sync with all Iray updates within Daz Studio, there have been some instances when the Iray version in the Daz Studio version you are using does not exactly match the Iray Server version supported at that moment on Boost for Daz. In these instances, we sometimes see that the render gets stuck and keep iterating on a specific frame. (You can check this by reviewing your local DS logs). Over time this might time out and result in a black screen.
Sync up your Daz Studio Iray version to that which is supported on Boost for Daz Check out our current Iray Version compatibility chart, and upgrade your Daz Studio accordingly. There might also be possibility of the render not having enough time to save its progress for large format scenes (typically > 2000 x 2000). Check out this article to resolve that.
Catch all condition: If none of the above don't apply In that event, its possible that there is a glitch in the actual Daz Studio file, or a glitch in Iray Server. This can happen even if the Iray server versions match!
Reach out to us on our Boost for Daz Discord server Opening a private ticket on our Discord server will allow us to review and assist your specific case. We'll need to know (a) your Boost for Daz registered email (b) your session number (from your Dashboard). We want this to work for you!
Ensure that no special character are used in the DS queue Job Name Use only letters, numbers, underscore and - (dash) in the Job Name. Do not use any special characters such as * & ^ % $ # @ ! or ~.
GPU falling to CPU and exceeding the Time parameter
Pick a GPU that is sized properly for your specific project Use our handy GPU guide to select the GPU with the appropriate amount of VRAM to accommodate your complete render package. Doing this correctly will avoid the Iray Server having to fallback to CPU rendering and black screens.
Iray (in Daz Studio) mismatch with Iray Server (on Boost for Daz) Notice rendering progress resetting/looping after a specific iteration Though we do our best to keep in sync with all Iray updates within Daz Studio, there have been some instances when the Iray version in the Daz Studio version you are using does not exactly match the Iray Server version supported at that moment on Boost for Daz. In these instances, we sometimes see that the render gets stuck and keep iterating on a specific frame. (You can check this by reviewing your local DS logs). Over time this might time out and result in a black screen.
Sync up your Daz Studio Iray version to that which is supported on Boost for Daz Check out our current Iray Version compatibility chart, and upgrade your Daz Studio accordingly. There might also be possibility of the render not having enough time to save its progress for large format scenes (typically > 2000 x 2000). Check out this article to resolve that.
Nitro mode is ON You'll find this option under Advanced Tab > Bridge Tab
Turn Nitro to OFF prior to clicking on the Render button
Daz Studio Max Time parameter is NOT 0 (zero) You'll find this under Editor tab > Progressive Rendering (parameter) > Completion The default value is typically 7200 seconds (2 hours), so if your render takes longer - it times out and delivers a blank screen.
Set Max Time to 0 (zero). Setting Max Time parameter to 0 (zero) effectively sets the render time to infinity. So however long the render takes, Daz Studio does not time out.
Make sure GPU is turned on Login into Iray Admin, select Resources from the left nav bar and check under the Hosts section. Make sure your GPU toggle is enabled(green).
Check to see if the Max Time parameter is set to -1 (negative 1) A Max Time parameter of -1 sometimes creates problems and can result in black screen render results.
Set Max Time to 0 (zero). Setting Max Time parameter to 0 (zero) effectively sets the render time to infinity. So however long the render takes, Daz Studio does not time out.
Special characters used in Job Name When adding a project to Iray Server queue, Daz Studio dialog requires you to enter a Job Name. Unfortunately, Daz Studio will NOT give you any errors or warning. You need to make sure to use only letters, numbers, underscore and - (dash) in the queue Job Name. Do not use any special characters such as * & ^ % $ # @ ! or ~. When special characters are used in the Job Name, the render results in a blank render.
Similar to the situation noted in the Streaming scenarios above, if the size of your render package exceeds the VRAM available in the GPU you selected on Boost for Daz, then when using Queue mode, this will fallback to using CPU. Understandably, this will slow your rendering process down significantly - and its possible that it might take longer that your the time set in your Max Time parameter in Daz Studio. You'll find this under the Editor tab > Progressive Rendering (parameter) > Completion (parameter). If your render exceeds this Max Time parameter, your rendering will complete with a black screen.
Queue Job is rejected (as soon as you enter valid Job Name) If you find the the queue job is rejected - typically experienced when you are entering the Job name and hit OK - and nothing happens, or you see an error.
Check to see if the Max Time parameter is set to -1 (negative 1) A Max Time parameter of -1 prevents the queue job from being created.
Set Max Time to 0 (zero). Setting Max Time parameter to 0 (zero) effectively sets the render time to infinity. So however long the render takes, Daz Studio does not time out. Once Max Time parameter has been changed, then try to Add to Queue with a valid Job Name.
