Hi everyone,
At my workplace we updated every machine with the latest version of V-Ray, client side, that is 61009.
Unfortunately it appears that the standalone latest version, which is 61008.
We ended up starting the render server using V-Ray for Maya itself. This kicks off a compatible version of the render server.
I was wondering if someone else has ad the same issue with the standalone in a distributed rendering setup?
Thanks in advance foe any help! 
Hi, thanks for posting. Latest V-Ray Standalone version is 6.10,08. Latest official V-Ray for Maya version is 6.10.00. Are you sure you are not using a nightly version on your setup?
We are using the latest available from the user downloadable contents. Never used nightly versions.
Hi, you can find the latest official version of V-Ray for Maya here - Download | My Chaos
You can find the latest official version of V-Ray Standalone here - Download | My Chaos
This is the V-Ray Standalone version we have.
However, when we tried to use this there was a version issue 61008 versus 61009 that was being used by the client that was submitting the job. So we did not use the standalone, we launched the render server using the VRay for Maya client that is also installed, So that client and render server matched.
Hi, you are correct. I tried to start a distributed rendering with latest official V-Ray build for Maya and latest official V-Ray Standalone and I got the same error. This is not normal behaviour I will log it for review.
Another way to use distributed rendering is if you start the vray.exe from the V-Ray for Maya bin folder (C:\Program Files\Chaos Group\V-Ray\Maya 2024 for x64\maya_vray\bin) Drag and drop the vray.exe from this location into command prompt and type "-server"
It should look something like this:
We are going to try that too.
Unfortunately this happened right in the middle of a job :-\
Please accept our apologies for the situation that occurred. You could also use a stable version of the V-Ray Standalone found here - Chaos
No need to apologize, really.
Is that standalone version compatible with the V-Ray version I am currently using? Have you tried it?
Thank you
So, another issue raised (we haven’t installed the latest nightly as suggested yet), which is very serious.
The render nodes/servers are now producing black/empty buckets most of the time, and V-Ray is also giving incredibly weird results, like randomly misplacing our geometries around and/or producing an empty view with a gradient as a background.
This is getting serious, and I think we need to roll back to the previous version of V-Ray, because 6 update 1 is definitely not production ready nor it is reliable at all.
If you guys have a quick solution, before we roll back, then it’ll be much appreciated.
Thank you
Hi, could you explain your latest setup in a bit more details?
Did you try this
Another way to use distributed rendering is if you start the vray.exe from the V-Ray for Maya bin folder (C:\Program Files\Chaos Group\V-Ray\Maya 2024 for x64\maya_vray\bin) Drag and drop the vray.exe from this location into command prompt and type “**-server”**
and what was the result?
What versions of Maya and V-Ray are you using with your latest tests?
Run a small simple scene trough the system to verify you have no issues with the distributed rendering and after that try a production scene.
Yes, this is exactly how our setup is working at the moment. The result is that our render nodes/servers fail to produce an output that makes sense, after few frames (usually after 20 or 80 frames, but is always different on a scene by scene scenario).
We get black/empty buckets (think of it as a render with a scattered series of black boxes all over the place)
We are using Maya 2023.3 and V-Ray 6 Update 1.
I’ll run a test with a simple scene and let you know what happens.
Thank you
servers fail to produce an output that makes sense, after few frames (usually after 20 or 80 frames, but is always different on a scene by scene scenario)
This sounds like it has nothing to do with your original issue with incompatible V-Ray versions on your servers and workstation. Let’s see what the simple scene test looks like. If it runs with no issues we will be looking into something scene related, probably something in you production scenes that is not supported or you are hitting a bug.
Just for further clarification: these production scenes are the same we previously rendered, a couple of months ago, successfully with the previous version of V-Ray 6.
All these issues happened after the update.
Among the other issues, we also hit the system memory limit on our local workstations, with scenes that previously rendered just fine.
All these issues happened after the update.
Are you having issues on local render with the latest update? It is not impossible that you have something in the scene that hits a bug in the new version and does not in the old version.
But we need to narrow down the possible scenarios.
1 - are you having issues on a local render with the latest version
2 - if you are having issues on local render, test with simple scene, if the simple scene is ok lets review the production scene
3 - if the issues are only with distributed, again - simple scene and if it is ok we have to look into the production scene
1 - Yes, we are having issues locally as well.
2 - Testing that right now, I’ll let you know.
3 - The simple scene with distributed has the issues.
Tested 49 frames with the simple scene. No issues locally with this one.
We are now about to test the nightly build of standalone that you suggested earlier.
Ok, the new nightly build of Standalone didn’t make any difference. black/empty buckets are still there, and also misplaced pieces of geometry are too.
Rolling back to V-Ray 6 at this point.
