Rendering issue - V-Ray Error [getVoxel]

[saddington_baynes]

Hello! So we are running into an issue with V-Ray mesh proxies, rendering through deadline.

Error: V-Ray error: [getVoxel] 116: Error loading voxel 27 for mesh file

A bit about our setup, AWS linux blades connected to Lucid Link, rendering Maya V-Ray from proxies. Rendering with Maya 2023, VRay 5.20.02

-If we use full res instead of proxies, the renders take twice as long but we don't get the errors.
-The errors seemed random at first, but I was able to recreate them by spinning up new workstations or rendernodes (windows and linux respectively) that connect to and access the same projects on Lucid Link, this will cause an otherwise successful render to fail, sometimes annoyingly at 95%.
-When the renders fail they all fail for atleast 10 minutes.
-My google searches led me to other folks who had the same Vray error, but it seems to be connected to using a new file server, that led me to suspect Lucid's part in all this.
-I'm unable to try UNC paths as listed here because we are using Linux render blades: https://forums.chaos.com/forum/v-ray-for-3ds-max-forums/v-ray-for-3ds-max-problems/1132965-v-ray-defmeshfile-getvoxel-59-error-loading-voxel-8-for-mesh-file
-This Thread also doesn't really help us but seems to be a similar issue: https://forums.chaos.com/forum/v-ray-for-3ds-max-forums/v-ray-for-3ds-max-problems/1173096-error-loading-voxel-0-for-mesh-file

Any help would be appreciated. Trying to avoid pointing fingers at Chaos or Lucid but if anyone can help us move forward that would be appreciated.

Thanks,
Jay

[saddington_baynes]

We discovered it was only happening when we submit 2 or more different proxy assets that are rendering at the same time. In order to avoid this we setup dependancies so that each set of renders with a different proxy asset waited until the previous one finished.

Not a full solve but a decent work around.