Renders stop as a solid black screen
ArgleSW
Posts: 144
There have been countless threads about this issue over the years, but I cannot find a single solution that works. I have numerous scenes that used to render on the same hardware with 0 problems in the past, but Daz Studio often can enter a state where rendering any scene will lead to a solid black screen (just the render window). Once the render window goes black, the rendering process appears to have completely stopped and I have the option to close it. I have found threads that date back over 5 years about this issue and it seems to be a problem that comes and goes for some people. Hoping someone out there knows the exact issue. My assumption is the scene is running out of memory and failing to render, but don't understand why the same scenes worked fine in the past.
What I have tried:
- Delete temporary files
- Enabling/disabling CPU fallback
- All render settings set to default (Iray / Photoreal mode)
- Deleting objects in the scene.
- Different Daz versions (4.12 and 4.15)
- Latest NVIDIA driver.
My system specs:
i7 5820k / 64GB RAM / NVIDIA 1080 Ti 11GB
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
I'm pretty sure that you will have tried a variety of scenes so this is probably hardly worth a mention but, just in the remote chance ... are you sure that you don't have a spotlight or something in front of the camera? Does it render with an alternative camera (or the Perspective view)?
What does your log say? (Help->Troubleshooting->View log file)
Based on the logs, looks like the GPU is running out of memory. The first log has cpu fallback disabled where it just stops the render. The second log has cpu fallback enabled and Daz studio just crashes to desktop once it switches to CPU mode.
I do not have any spotlights in the scene. The strange thing is this render had 0 issues in the past using the exact same scene and Daz rendering setup. Why is it running out of memory now? I have also tried deleting objects in the scene unti its essentially a single G8 character and a camera (no headlamp). Nothing else and same issue occurs. An 11GB GPU should handle this no problem and I have had no issues for the past few years with signifigantly more heavy scenes.
LOG #1 (CPU Fallback Disabled):
2021-07-07 08:48:49.608 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 1307 textures, 8 lambdas (1 unique)
2021-07-07 08:48:49.629 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2021-07-07 08:48:49.652 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2021-07-07 08:48:49.654 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2021-07-07 08:48:49.654 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2021-07-07 08:48:49.654 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2021-07-07 08:48:49.655 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2021-07-07 08:48:49.655 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2021-07-07 08:48:49.671 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using iray core convergence estimate.
2021-07-07 08:48:49.671 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2021-07-07 08:48:49.691 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2021-07-07 08:48:49.691 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2021-07-07 08:48:49.691 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Available GPU memory has increased since out-of-memory failure. Re-enabling CUDA device 0 (NVIDIA GeForce GTX 1080 Ti)
2021-07-07 08:48:49.699 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2021-07-07 08:48:49.704 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2021-07-07 08:48:49.704 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080 Ti)
2021-07-07 08:48:49.704 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2021-07-07 08:48:49.704 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend progr: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Processing scene...
2021-07-07 08:48:51.598 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Geometry memory consumption: 8.242 GiB (device 0), 0.000 B (host)
2021-07-07 08:48:51.607 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.9 IRAY rend error: OptiX Prime maximum geometry/hierarchy size exceeded
2021-07-07 08:50:02.883 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.9 IRAY rend error: Unable to allocate 5.000 MiB from 0.000 B of available device memory
2021-07-07 08:50:02.883 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.10 IRAY rend error: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Scene setup failed
2021-07-07 08:50:02.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.10 IRAY rend error: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Device failed while rendering
2021-07-07 08:50:02.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER :: 1.10 IRAY rend warn : CUDA device 0 (NVIDIA GeForce GTX 1080 Ti) ran out of memory and is temporarily unavailable for rendering.
2021-07-07 08:50:02.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER :: 1.10 IRAY rend warn : All available GPUs failed.
2021-07-07 08:50:02.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.10 IRAY rend error: Fallback to CPU not allowed.
2021-07-07 08:50:02.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.10 IRAY rend error: All workers failed: aborting render
2021-07-07 08:50:02.884 Iray Render error: Internal rendering error.
2021-07-07 08:50:03.274 Saved image: D:\Temp\render\r.png
2021-07-07 08:50:03.295 Finished Rendering --> RENDER WINDOW IS A SOLID BLACK SCREEN AND RENDER IS COMPLETED
LOG #2 (CPU Fallback Enabled):
2021-07-07 09:11:53.898 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 1307 textures, 8 lambdas (1 unique)
2021-07-07 09:11:53.919 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2021-07-07 09:11:53.927 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2021-07-07 09:11:53.929 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2021-07-07 09:11:53.929 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2021-07-07 09:11:53.929 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2021-07-07 09:11:53.929 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2021-07-07 09:11:53.930 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2021-07-07 09:11:53.946 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using iray core convergence estimate.
2021-07-07 09:11:53.946 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2021-07-07 09:11:53.966 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2021-07-07 09:11:53.966 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2021-07-07 09:11:53.986 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using OptiX Prime version 5.0.1
2021-07-07 09:11:53.986 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2021-07-07 09:11:54.027 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2021-07-07 09:11:54.028 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080 Ti)
2021-07-07 09:11:54.028 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2021-07-07 09:11:54.028 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend progr: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Processing scene...
2021-07-07 09:11:56.730 Iray [VERBOSE] - IRAY:RENDER :: 1.13 IRAY rend stat : Geometry memory consumption: 8.242 GiB (device 0), 0.000 B (host)
2021-07-07 09:11:56.733 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.13 IRAY rend error: OptiX Prime maximum geometry/hierarchy size exceeded
2021-07-07 09:12:36.861 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.13 IRAY rend error: Unable to allocate 16.000 MiB from 0.000 B of available device memory
2021-07-07 09:12:36.884 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Scene setup failed
2021-07-07 09:12:36.912 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce GTX 1080 Ti): Device failed while rendering
2021-07-07 09:12:36.912 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : CUDA device 0 (NVIDIA GeForce GTX 1080 Ti) ran out of memory and is temporarily unavailable for rendering.
2021-07-07 09:12:36.912 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : All available GPUs failed.
2021-07-07 09:12:36.913 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : No devices activated. Enabling CPU fallback.
2021-07-07 09:12:36.914 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: All workers failed: aborting render
2021-07-07 09:12:36.934 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 12 cores for rendering
2021-07-07 09:12:36.934 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2021-07-07 09:12:36.934 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2021-07-07 09:12:36.934 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering... --> DAZ STUDIO CRASHES HERE
Your GPU has certain memory overhead, so you can only rely on having 2/3rds to 3/4ths of the available VRAM. I presume in the past you had less overhead, and now that it's increased you can't fit it all. You can try and find some way to profile your GPU, but I personally would find a way to slim down on geometry and/or textures.
Can't even render a basic scene with a single G8 character and a camera (no other props/lights). I just wish there was a clear solution for this. Seems like I am not the only one who's had this issue as I have read many forum discussions about it, but none have a clear solution. Going to try completely uninstalling everything and start from scratch. Because the hardware that was working fine for several years hasnt changed, so something most likely is wrong on the software end.
Yeah, try scrubbing all your graphics drivers and then installing the latest drivers. There's a special program to do it, but I can't remember the name.
DDU
https://www.wagnardsoft.com/forums/viewtopic.php?f=5&t=3517
When your geometry already takes over 8GiB's, there is no space left for the textures and the work space (1.75GiB), also windows, DS and the base load of the scene require VRAM.
If you are using high SubD's, take them down, otherwise you must find the culprit for such high geometry usage.
Edit; the attached chart shows how much VRAM and RAM was used on my test and what was the total VRAM consumption according to the LOG (geometry+textures+work space)
1st scene was just one G8 figure with clothing and hair, the other three had four G8 figures with clothing and hair plus the scene with architecture. On scenes 3 and 4 I increased SubD on the characters to see at which point rendering would drop to CPU - Using W7 Ultimate and 8GB RTX 2070 Super.
Edit 2; If the same scene did render in the past, the increased VRAM load is due to the RTX functions that are now emulated in software for the GTX cards.
Thanks everyone for all the help. I ended up reinstalling windows from scratch and reinstalled daz studio on a clean setup. Now I can render my large scenes again. Either it cleaned up my drivers or some other corrupt data, but it all works now. Thanks again.
I've had this issue before, sometimes it occurs with only a single G8 character in the scene and limited lighting, so not sure why my 8gb card would be running out of memory. I either get the black screen after pressing render and before iteration 1, or sometimes it happens a few iterations in. When this happens I know the GPU has crapped out so I can't use it without at least a Daz restart. However, one solution I've found when the black screen occurs is simply to run scene optimizer but not actually reduce or remove any textures. Running the script alone seems to fix it most of the time, not sure why this would fix it without changing anything texture related but it does. Sometimes a full Daz restart is required, which I also don't understand, because presumably if my GPU is crapping out on a certain scene because it ran out of memory, it would also run out of memory after a Daz restart and loading the same scene and attempting to render again, but that doesn't seem to be the case. Annoying issue but so far those two solutions have worked for me.
Sorry for bringing up an old post, but after weeks of frustration dealing with this issue I stumbled across this thread and sure enough, opening Scene Optimizer fixes the issue on every scene I have had an issue with. You have my thanks :)
Hi, sorry to drag up an older post again but I have run into the black render problem. As a test I created a very basic scene. A plan primitive with the diffuse set to blue, a sphere with a red diffuse and a single spot light. Environment setting are dome and scene with draw dome on.
If I untick CPU in the advanced render setting I get a nice black render in a few seconds.
I am running DS 4.15 and a 4gb Nvidia Quadro K4200, (yes I know its old but cant afford newer), with latest divers. By rights this should render off the card's GPU but the only way I get a render is if a switch to using CPU.
Any one got any ideas?
In Iray there is an invisible ground plane. When I tried to position a camera looking up a high rise at a steep angle the camera position was below that plane.
The render went black. Reposition the camera above the ground solved the problem. (Soultion 1).
There is (unfortunatley hidden) the possibility to declare somewhere in the parameter tab that the groundplane, which is used to fetch the object shadows during rendering,, can be made invisible.(Solution 2).
Maybe your black render is such a problem with an transparent, but not invisible (shadow)plane.
Nice days and Nice renders
atoxic
There may or may not be a setting hidden in parameters, but there is a non-hidden option in Render Settings called Draw Ground. Set that to off, and your problem is solved.
The Quadro K4200 uses a Kepler GPU. But Kepler GPUs are no longer supported by Iray, AFAIK already some time before Studio 4.15...
I've been having to deal with this of late when doing large complex renders. I've noticed when it happens Studio doesn't want to open back up for several minutes, and if I'm reloading a scene with a saved .duf, it won't open at all. Which to me means that duf file is still in memory. I think there is a memory leak that's causing the buffer to overflow, and then it doesn't flush the cashe out when you close, or when a particular scene finishes rendering. Most of the time opening Studio up from the .exe, and then loading the .duf works, other times a log off, and log on is required. Be sure to save your scene before trying. Hard to tell if it is a Studio issue or Microsoft.
DAZ Studio does not require/need logging in, and if one is having problems with adequate resources, not-logging in would be one of the first things to do together with closing all the other programs, especially any and all web browsers.
Its a bug, old bug. Need just reestart Daz.
This is still a very annoying bug in Daz for Win 11, and the only way I've found to work around it, is by saving, closing, killing the idle process of Daz that still runs and then restarting Daz.
What bug? This thread is nearly two years old, and covers a number of potential snags (most of which, such as running out of memory, are not bugs).
I've run into this too. Looks like Daz Studio was reading the available resources on my GPU incorrectly. It was failing to "allocate 2.448 GiB from 491.582 MiB of available device memory". There was close to 11GB VRAM available on my GPU each time I troubleshot it. Doesn't have to be a Daz Sutdio bug, but that's not correct system behaviour.
The open the Scene Optimizer script and close it without doing anything trick sorted it for me. Maybe Scene Optimizer triggers a call to to get the available memory through the Daz Studio API and causes an update somewhere? *shrug* Who truly knows? And I don't think it's related to the GPU crapping out, as someone eloquently put it. The issue persisted for me after a hard restart of the system and I was quite happily able to run resource intensive games between Daz Studio failing to allocate memory.
I would suggest that the message just means that there was only 491.582 MiB left at that particular point - not that it only found that much available in total. There are lots of things that need to fit in the VRAM for a render to progress. If you already have Scene Optimiser then you can run that and actually downsample some textures so that your scene fits in your card's memory.