It would also help to give us the exact V-Ray build that you’re using - you can find it under the Houdini Top Menu → V-Ray → About V-Ray → Copy to Clipboard.
Unless you’re locked to this particular V-Ray for Houdini build version, may I suggest grabbing a recent stable builds from the nightlies section? I double-checked to make sure this works as expected there.
You can find the stable builds here: Chaos
@Gosho.Genchev I tried 6.20.23 and I’m still getting the same issue.
V-Ray for Houdini number:22761 hash:954828e from 22 Sep 2024 01:17
V-Ray Core 6.20.23 from 12 Sep 2024
I’ve attached my test file for 6.20.23.
Are there any V-Ray environment variables, V-Ray render settings or VFB settings that could cause this to happen? chaos.zip (62 KB)
I see in your scene that the Renderer ROP is set to “Export” so I assume you’re generating VRScenes and sending them to a render farm - what is the V-Ray version deployed on the render farm? Ideally, it should be the same stable build that you’re working with on your workstation.
We do export out scenes on the farm and then have a separate vray standalone render job. But the tests I was running were all local. I changed the “Export Mode” to “No Export” and that didn’t make a difference either- again running locally. Must be some other setting or environment somewhere causing this issue on our end. Either way, we’ve updated our tooling to just add “/vrayOutput” to the material path. Thanks for the help!