VRay Volume Grid Rendering: Stack Trace Fatal Error On Farm....

V-Ray V-Ray Common Public
1

This doesn’t happen all the time… But occasionally VRay volume grids (even if rendered 1 frame tasks) will result in the following VRay fatal error… and present the following stack trace output:

2018-11-06 09:12:00: 0: STDOUT: [2018/Nov/6|09:12:00] V-Ray: Rendering image…
2018-11-06 09:12:00: 0: STDOUT: [2018/Nov/6|09:12:00] V-Ray: (Estimated time remaining: 0h 0m 1.1s): 16 % completed
2018-11-06 09:12:01: 0: STDOUT: [2018/Nov/6|09:12:00] V-Ray: (Estimated time remaining: 0h 0m 0.7s): 36 % completed
2018-11-06 09:12:01: 0: STDOUT: [2018/Nov/6|09:12:01] V-Ray: (Estimated time remaining: 0h 0m 0.4s): 58 % completed
2018-11-06 09:12:01: 0: STDOUT: [2018/Nov/6|09:12:01] V-Ray: (Estimated time remaining: 0h 0m 0.4s): 73 % completed
2018-11-06 09:12:01: 0: STDOUT: Stack trace:
2018-11-06 09:12:01: 0: STDOUT: [2018/Nov/6|09:12:01] V-Ray: (Estimated time remaining: 0h 0m 0.1s): 92 % completed
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray_geometry.dll!getLibDesc
2018-11-06 09:12:01: 0: STDOUT: vray.dll!VUtils::BSDFShadeable::getPlugin
2018-11-06 09:12:01: 0: STDOUT: Qt5Core.dll!QThread::start
2018-11-06 09:12:01: 0: STDOUT: MSVCR110.dll!_beginthreadex
2018-11-06 09:12:01: 0: STDOUT: MSVCR110.dll!_endthreadex
2018-11-06 09:12:01: 0: STDOUT: KERNEL32.DLL!BaseThreadInitThunk
2018-11-06 09:12:01: 0: STDOUT: ntdll.dll!RtlUserThreadStart

As we can see it starts rendering, and then in the middle it seems like it cant resolve some library, and a plugin? I’m not really sure how to interpret this issue… It only happens in scenes with VRay volume grids, and generally happens if the vdb per frame file size is more than 100mb++

Any insights would be helpful, or if anyone else has experienced this before.

VRay 3.6.01, Maya 2017 sp5

2

Hey there,

Have you tried newer builds like 3.60.04 ?
Is this windows or linux?
And most importantly - can you get us a scene that we can use to reproduce the issue on our end?

3

Hi Yolov,
I figured this out to only occur while referencing a VRay proxy (containing an alembic) for debris, contained in the same asset as a VRay Volume Grid… I’ll do more testing later when this project ends, but I would assume this only happens with referenced VRay Proxies, and has nothing to do with the VRay volume grid…
Not sure why referencing this particular debris inside a proxy causes a fatal error, as I have definitely had success with referenced proxies before, but possibly its a combination of the vdb + alembic… i’ll try to make a simple scene later that has the same error… The same debris works just fine in the asset with the same vdb (volume grid) but as a live alembic, thats how this was resolved currently.
PS: this is windows 10
-Ross

4

A simple scene would be very helpful, yes.