vdb-apocalypse and Ultra scenery = crash

Pitmatic · September 20

Hi

I am trying to combine KVAP Bare fire (or anything else) from https://www.daz3d.com/vdb-apocalypse and ultrascenery (1 or 2) scene and it just crashes out and watching task manager shows no memory consumption issue. If i delete the vdb container box it works but the vdb will not show.

I am running Studio 4.24 Nvidia 561.09 on a RTX3060 12GB with I5 13thgen and 32GB and either product on its own renders fine just not together.

Last bit of the log

2025-09-20 12:19:21.748 Iray (Scene Access) : Retrieving device motion transform data

2025-09-20 12:19:21.748 Iray (Scene Access) : Retrieving lens data

2025-09-20 12:19:21.748 Iray (Scene Access) : Retrieving device lens data

2025-09-20 12:19:21.831 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : JIT-linking wavefront kernel in 78.428 ms

2025-09-20 12:19:21.838 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Initializing volume acceleration structures took 0.000 s

2025-09-20 12:19:21.838 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Scene processed in 0.655s

2025-09-20 12:19:21.844 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Allocated 13.599 MiB for frame buffer

2025-09-20 12:19:21.847 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Allocated 2.094 GiB of work space (2048k active samples in 0.003s)

2025-09-20 12:19:21.847 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Optimizing for cooperative usage (performance could be sacrificed)

2025-09-20 12:19:22.016 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Kernel [12] (FreePathVl ) failed after 0.012s

2025-09-20 12:19:22.016 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while launching CUDA renderer in <internal>:904)

2025-09-20 12:19:22.016 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Failed to launch renderer

2025-09-20 12:19:22.017 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): Device failed while rendering

2025-09-20 12:19:22.017 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : CUDA device 0 (NVIDIA GeForce RTX 3060) is no longer available for rendering.

2025-09-20 12:19:22.019 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - OPTX:RENDER :: 1.11 OPTX rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

2025-09-20 12:19:22.019 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error

2025-09-20 12:19:22.019 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - OPTX:RENDER :: 1.11 OPTX rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

2025-09-20 12:19:22.019 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - OPTX:RENDER :: 1.11 OPTX rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : All available GPUs failed.

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [WARNING] - IRAY:RENDER :: 1.11 IRAY rend warn : No devices activated. Enabling CPU fallback.

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while initializing memory buffer)

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: All workers failed: aborting render

2025-09-20 12:19:22.021 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)

2025-09-20 12:19:22.022 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.11 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)

2025-09-20 12:19:22.022 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)

2025-09-20 12:19:22.023 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 3060): an illegal memory access was encountered (while de-allocating memory)

2025-09-20 12:19:22.023 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 20 cores for rendering

2025-09-20 12:19:22.023 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):

2025-09-20 12:19:22.023 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU

2025-09-20 12:19:22.023 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...

2025-09-20 12:19:22.023 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend progr: CPU: Processing scene...

2025-09-20 12:19:22.023 Iray (Scene Access) : Retrieving geometry

2025-09-20 12:19:22.024 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Using Embree 3.13.4

2025-09-20 12:19:22.024 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Initializing Embree

2025-09-20 12:19:22.251 Iray (Scene Access) : Retrieving volumes

2025-09-20 12:19:22.251 Iray (Scene Access) : Retrieving textures

2025-09-20 12:19:22.251 Iray (Scene Access) : Retrieving flags

2025-09-20 12:19:22.251 Iray (Scene Access) : Retrieving section objects

2025-09-20 12:19:22.251 Iray (Scene Access) : Retrieving lights

2025-09-20 12:19:22.252 Iray (Scene Access) : Retrieving materials

2025-09-20 12:19:22.252 Iray (Scene Access) : Compiling custom code

2025-09-20 12:19:22.315 Iray (Scene Access) : Retrieving environment

2025-09-20 12:19:22.315 Iray (Scene Access) : Retrieving backplate

2025-09-20 12:19:22.315 Iray (Scene Access) : Retrieving decals

2025-09-20 12:19:22.315 Iray (Scene Access) : Retrieving motion transform data

2025-09-20 12:19:22.315 Iray (Scene Access) : Retrieving lens data

2025-09-20 12:19:22.465 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : CPU: Initializing volume acceleration structures took 0.150 s

Richard Haseltine · September 20

How about just the VDB in an empty (or nearly empty) scene?

Richard Haseltine · September 20

A quick test with primitives works - 64GB system memory, RTX 2080Ti with 11 GB

barbult · September 20

Richard Haseltine said:

How about just the VDB in an empty (or nearly empty) scene?

The original message says either product on its own renders fine just not together.

barbult · September 20

I am running Studio 4.24 Nvidia 580.97 on a RTX3080 10GB with I7 8thgen and 32GB (different driver, less GPU memory, much older CPU generation).
I am testing with UltraScenry2. I put just the basic terrain in the scene (no feature or ecology preset = no plants or feature props) I added two VDB props from VDB Apocalypse. GPU-Z says it is using less than 6 GB of GPU memory, and it is rendering fine. Did you try it with bare terrain in UltraScenery?

After this, I will try with an ecology.

barbult · September 20

OK, I tried UltraScenery2 and the two VDB and the Oaks 01 Ecology = CRASH
My log file looks similar to yours. illegal memory access over and over. It failed over to CPU but didn't render. It crashed. The crash report says the Exception Reason is: DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libiray.dll" at 0033:0000000032E751A7, mi_plugin_factory()+3114375 byte(s)

barbult · September 20

I tried UltraScenery with only 7 oak trees being rendered in the ecology - no grass, flowers, rocks, etc. I used only one of the VDBs. It still crashed on render.

barbult · September 21

I think the problem may be caused by the custom shader used on UltraScenery props. Even if I use UltraScenry2 with no Ecology, but manually add a single UltraScenery tree prop, it crashes on render. If I apply the Iray Uber (MDL) shader to the tree, it renders fine. For good measure, I added two UltraScenery trees and applied Iray Uber shader to them and it renders fine.

(Tone mapping was turned down because scene was so bright before.)

barbult · September 21

So, my final test is a whole UltraScenery2 Oaks 01 Ecology with Iray Uber applied to every Biome layer prop surface. It renders fine with the two Apocalyptic VDBs. It actually looks pretty nice, in spite of not having the special shaders. I imagine if I has used a Terrain presets with a river, I might have to apply Iray Uber shader to the feature props like rocks and logs, too.

I wonder if other shaders also have a conflict problem with VDBs. In the end, it seems to be a Daz Studio problem, by not handling a combination of things, each of which is supported and works fine individually.

barbult · September 21

Further testing shows that it is the emission part of the VDB that is the conflict. If you disable the Emission in the Surface parameters for the VDB, it no longer crashes, But then you get only the smoke and no fire, so that is not a good solution. It is only a clue to the problem.

Mattymanx · September 21

Have you tested with different VDBs?

I did test my VDB portals with US1 and it did not have an issue. But those are the only VDBs with lights that I have. I have not tested US2 cause I have not used it at all yet.

barbult · September 21

Mattymanx said:

Have you tested with different VDBs?

I did test my VDB portals with US1 and it did not have an issue. But those are the only VDBs with lights that I have. I have not tested US2 cause I have not used it at all yet.

No, I have not tested with other VDBs. I'll have to see which I own that have emission.

Pitmatic · September 21

Thank you @Barbult your a star I will have to try your solution, I only have two vdb proucts vdb clouds and the apocalypse one I need to channel my inner firestarter when the current project finishes rendering...

barbult · September 21

Mattymanx said:

Have you tested with different VDBs?

I did test my VDB portals with US1 and it did not have an issue. But those are the only VDBs with lights that I have. I have not tested US2 cause I have not used it at all yet.

I don't think I own any other Daz VDB products with emission, other than two KindredArts products. Both of those products cause the crash for me. So, I downloaded two OpenVDB sample VDBs with emission (fire and explosion). I created a primitive and applied the Default Resources for Daz Studio shader Simple OpenVDB MDL Volume. I loaded the OpenVDB shader into that. I tweaked the surface settings to get the fire and smoke to show up well. I put those into an UltraScenery Oaks 01 scene and it did NOT crash.
Something about the KindredArts VDBs is incompatible with the shaders used in UltraScenery, when other VDBs appear to have no problem. Thank you @Mattymanx for pointing me to trying other VDBs.

Pitmatic · September 22

Thank you for the work around @Barbult I set all the trees to the uber shander and the scene worked.

barbult · September 22

I'm going to submit a but report about this problem.

Notifications

vdb-apocalypse and Ultra scenery = crash

Comments

Adding to Cart…