DAZ3D - No loading for Nvidia Iray Preview and/ or Black render

[Deleted member 416612]

Hi mates,


I've created a scene, not too complex with two Genesis 8 characters, high resolution with subdivision level 1 and Render Subdlevel to 2. This applies to both of them. The assets in the scene are not many and the environment is set to scene only. The resolution is Full HD.
When I first load the scene, it shows me the Iray preview when selected and it will render the image in an hour for a max sample of 4000. If I close the render/iray preview and try again, it will not load the preview nor render it. This can be reproduced for 70% of the tries. With even more tries I do, it can be reproduced 100%. The workaround is to close Daz3d and open the program and scene. Now, I think that the specs are not the issue as it would work from the beginning and there were scenes where I could render with around 7 genesis models (with some modifications on the models).

In the daz3d log I found this:

When it rendered


2022-05-25 01:55:58.773 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (35 light sources with 14374 triangles, 1 instance) took 0.000 s
2022-05-25 01:55:58.774 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating volumes.
2022-05-25 01:55:58.774 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2022-05-25 01:55:58.774 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2022-05-25 01:55:58.776 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2022-05-25 01:55:58.776 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2022-05-25 01:55:58.777 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2022-05-25 01:55:58.779 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2022-05-25 01:55:58.779 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2022-05-25 01:55:58.784 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using no convergence estimate.
2022-05-25 01:55:58.787 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2022-05-25 01:55:58.790 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2022-05-25 01:55:58.790 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2022-05-25 01:55:58.792 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using OptiX Prime version 5.0.1
2022-05-25 01:55:58.792 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2022-05-25 01:55:58.826 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2022-05-25 01:55:58.826 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080)
2022-05-25 01:55:58.826 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-05-25 01:55:58.827 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend progr: CUDA device 0 (NVIDIA GeForce GTX 1080): Processing scene...
2022-05-25 01:56:05.921 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Importing lights for motion time 0
2022-05-25 01:56:05.924 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Initializing light hierarchy.
2022-05-25 01:56:06.041 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : Light hierarchy initialization took 0.117 s
2022-05-25 01:56:06.071 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): Scene processed in 7.244s
2022-05-25 01:56:06.073 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): Allocated 39.552 MiB for frame buffer
2022-05-25 01:56:06.081 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): Allocated 1.463 GiB of work space (1571k active samples in 0.005s)
2022-05-25 01:56:06.081 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): Optimizing for cooperative usage (performance could be sacrificed)
2022-05-25 01:56:07.144 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Allocating 1-layer frame buffer
2022-05-25 01:56:07.475 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 8.649s.
2022-05-25 01:56:08.178 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 9.352s.
2022-05-25 01:56:10.209 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 11.382s.
2022-05-25 01:56:14.410 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 15.583s.
2022-05-25 01:56:18.455 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00012 iterations after 19.628s.
2022-05-25 01:56:22.739 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00016 iterations after 23.912s.
2022-05-25 01:56:26.651 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00020 iterations after 27.825s.
2022-05-25 01:56:30.881 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00024 iterations after 32.054s.
2022-05-25 01:56:35.404 [INFO] :: Saved image: C:\Users\petre\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2022-05-25 01:56:35.406 [INFO] :: Finished Rendering
2022-05-25 01:56:35.438 [INFO] :: Total Rendering Time: 49.16 seconds
2022-05-25 01:56:36.473 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:
2022-05-25 01:56:36.473 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (NVIDIA GeForce GTX 1080): 24 iterations, 7.329s init, 28.655s render (here I canceled the render)

When it doesn't work:

2022-05-25 01:35:24.021 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2022-05-25 01:35:24.022 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: No device specified or usable
2022-05-25 01:35:24.025 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 0 device(s):
2022-05-25 01:35:24.025 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-05-25 01:35:24.025 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(367): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: No worker to render with: aborting render
2022-05-25 01:35:24.025 [ERROR] Iray :: Internal rendering error.

Specs:
Processor: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 CPUs), ~3.7GHz
Memory: 32768MB RAM
Available OS Memory: 32720MB RAM
Chip type: NVIDIA GeForce GTX 1080
Dedicated Memory: 8079 MB

Is there a fix for this? There will be more than 100 renders for this scene and closing and opening Daz3d for each of it will bring me closer to my insanity.

 

[Meaning Less]

Go to windows graphics settings and try to enable Hardware-accelerated GPU scheduling.

If it still isn't working I would try reinstalling the gpu drivers, or even resetting it into the motherboard slot.

 

[MissFortune]

If you're on Windows 11, don't turn on Hardware-Accelerated GPU scheduling. It causes crashes, among other minor annoying issues.

That being said, Iray Preview not loading and black render screens are almost certainly you running out of VRAM. Unfortunately, the only real ways out of this are using Scene Optimizer (which will lower the quality of things. Don't use this on figures, clothing, hair, or anything you plan on zooming into), getting a beefier GPU with more VRAM, or look into a Render Queuing plugin like the one from ManFriday. It'll restart Daz automatically after each render.

 

[Deleted member 416612]

If you're on Windows 11, don't turn on Hardware-Accelerated GPU scheduling. It causes crashes, among other minor annoying issues.

That being said, Iray Preview not loading and black render screens are almost certainly you running out of VRAM. Unfortunately, the only real ways out of this are using Scene Optimizer (which will lower the quality of things. Don't use this on figures, clothing, hair, or anything you plan on zooming into), getting a beefier GPU with more VRAM, or look into a Render Queuing plugin like the one from ManFriday. It'll restart Daz automatically after each render.

I mean, I thought about it but I don't understand how it works the first time if it's due to VRAM. Also, for a previous game update, I've rendered a scene with 7 Genesis 8 figures (with basic mesh, subdivision level 0 and Render Subdlevel to 0.). The new GPU is in the plan for buying but honestly, it feels like an issue either with Daz or with something related to my software.

 

[MissFortune]

I mean, I thought about it but I don't understand how it works the first time if it's due to VRAM. Also, for a previous update, I've rendered a scene with 7 Genesis 8 figures (with basic mesh, subdivision level 0 and Render Subdlevel to 0.). The new GPU is in the plan for buying but honestly, it feels like an issue either with Daz or with something related to my software.

The technical explanation escapes me, but it is Daz not your GPU. It's been a bug for a few versions now, where the memory essentially 'runs out' and basically forces a restart. The more VRAM you have, the less you have to restart. More or less, at least. Some of that could be wrong, though. Just what I've picked up from reading about it. Hopefully it's something they finally fix (doubtful) in the new major version update of it.

 

[MissFortune]

Ah, it was memory leak.

You must be registered to see the links

. See the second comment by u/dragotx (bottom)

You must be registered to see the links

. This one's actually quite similar to your own.

You must be registered to see the links

 

[Deleted member 416612]

Ah, it was memory leak.

You must be registered to see the links

. See the second comment by u/dragotx (bottom)

You must be registered to see the links

. This one's actually quite similar to your own.

You must be registered to see the links

Thank you! I am relieved that this is not mainly due to my GPU but I am also concerned that this is a known issue with Daz3d and they haven't done anything about it.

What info I extracted from the links you gave me is:

1) A script can be created and imported in Daz:

"// DAZ Studio version 3.1 filetype DAZ Script
clearUndoStack();
App.clearDelayedDeleteStack(true);
Save it as a DSA file and place it in the script menu. You can then right-click on it and create a custom action to place it on a toolbar for easy access. I have used it for years and it still works in DS 4.14.1.22
I have not experienced the slow down in my renders. Having recently done some promos of multiple options in the same scene, they each took the same amount of time to render. Whether or not the clear undo stack had anything to do with it I cannot say but its worth a shot. I use the clear undo stack script constantly. Just don't use it right after deleting a genesis figure."

2)

You must be registered to see the links

Apparently this script for bulk rendering, restarts daz3d after each render. This would the black render issue I had with

You must be registered to see the links

.