Arnold volume does not recognize grids

Arnold volume does not recognize grids

honorsforgod
Enthusiast Enthusiast
1,251 Views
15 Replies
Message 1 of 16

Arnold volume does not recognize grids

honorsforgod
Enthusiast
Enthusiast

Arnold volume does not recognize grids but c4d native VDB volume works fine

0 Likes
1,252 Views
15 Replies
Replies (15)
Message 2 of 16

peter.horvath6V6K3
Advisor
Advisor

Maybe it's an OpenVDB version issue. Can you send us a VDB file to check?

0 Likes
Message 3 of 16

honorsforgod
Enthusiast
Enthusiast
0 Likes
Message 4 of 16

honorsforgod
Enthusiast
Enthusiast

[c4dtoa] 00:00:01 5532MB WARNING | /Fire/Arnold_Volume.grids: use type ARRAY, not POINTER

[c4dtoa] 00:00:01 5532MB WARNING | /Fire/Arnold_Volume: could not set POINTER parameter "grids"

0 Likes
Message 5 of 16

honorsforgod
Enthusiast
Enthusiast

it's even caused the crash [GPU], when i delete the volume from my scene everything works fine

0 Likes
Message 6 of 16

madsd
Advisor
Advisor
So, this works fine in MaxToA.

I can call the 3 channels, flames, temperature, density which are visible in the VDB.

I can call them through OSL 3dtexture(); call and by just injecting the string names to the Arnold volume material.

0 Likes
Message 7 of 16

lee_griggs
Autodesk
Autodesk

This is what I get.1646288279587.png

1646288375274.png

Lee Griggs
Arnold rendering specialist
AUTODESK
0 Likes
Message 8 of 16

honorsforgod
Enthusiast
Enthusiast
yeah correct that's it, so odd


now I am able to load it


0 Likes
Message 9 of 16

honorsforgod
Enthusiast
Enthusiast

when i use Gpu i crash

minidump.zipscreenshot-2022-03-03-103440.png

0 Likes
Message 10 of 16

honorsforgod
Enthusiast
Enthusiast

cpu works finescreenshot-2022-03-03-104623.png

0 Likes
Message 11 of 16

honorsforgod
Enthusiast
Enthusiast

[c4dtoa] 00:00:53 3454MB WARNING | [imagers] forcing box filter due to usage of OptiX/OIDN imager

[c4dtoa] 00:02:26 7430MB ERROR | [gpu] an error happened during rendering. OptiX error is: Unknown error (Details: Function "_rtContextLaunch2D" caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: <internal>, line: 0)

GPU 0 had 10136MB free before rendering started and 4620MB free when crash occurred


0 Likes
Message 12 of 16

honorsforgod
Enthusiast
Enthusiast

my scene: atmospher_Volume and VDB volume[fire] and mesh light for rear lights of the car


when I delete the fire ---> GPU OK

when I delete the car and keep the fire only ---> GPU OK

everything in the scene ---> GPU Crash

0 Likes
Message 13 of 16

peter.horvath6V6K3
Advisor
Advisor

I can not reproduce the crash. The vdb and the grids are loaded and rendered fine on CPU and GPU. Make sure you are using the latest C4DtoA 4.0.3.2. From the log it seems the Optix denoiser is enabled. What if you try without that?

0 Likes
Message 14 of 16

honorsforgod
Enthusiast
Enthusiast

I disabled denoiser still keep crashing, yeah I using the latest one C4DtoA 4.0.3.2

0 Likes
Message 15 of 16

peter.horvath6V6K3
Advisor
Advisor
Any chance you can send us the scene? You can send it to support(at)arnoldrenderer(dot)com
0 Likes
Message 16 of 16

honorsforgod
Enthusiast
Enthusiast
it's not a simple scene to compact and send. it has a lot of material with external texture and large VDB files and Alembic involved too
0 Likes