Deadline 10 Vray Next GPU Affinity doesn't work

I’ve tried several methods to get this to work, but it simply doesn’t.

I cannot get the 1st GPU to render with deadline, when i have more than 1 GPU on the machine. I tried setting the affinity to 1 gpu per task, with 2 concurrent tasks, but it always picks the 2nd gpu, never the 1st one. Same thing happens if i create 2 slaves and manually overwrite the gpu affinity on each slave, it only renders with the 2nd GPU.

We’re using 3dsmax 2019, Vray GPU Next, Windows 10, Deadline 10 latest version…

This is really annoying and we cannot seem to use the 1st gpu to render…

Any ideas?

Well, GPU affinity isn’t a standard so each application needs to support it a little differently.

I did some digging into the 3DS Max plugin specifically and the way we’re defining GPU affinity for V-Ray is by setting “VRAY_OPENCL_PLATFORMS_x64”. It looks like that’s what’s explained here:
https://forums.chaosgroup.com/forum/v-ray-rt-forums/v-ray-rt-general/989261-gpu-farm-deadline-affinity

Does anyone know if they’re still using the same variable for 4.0/Next? I did some quick Googling but didn’t find anything specific.

Update: Also interesting would be to see what this line shows from the job report:

This Slave is overriding its GPU affinity, so the following GPUs will be used by Octane/RedShift/V-Ray RT: X

From a cursory glance, it appears they’ve moved to a different environment variable, it looks like it behaves the same as the old one:

VRAY_GPU_PLATFORMS

1 Like

So it has to be changed on deadline’s end for gpu affinity to work now, right?

When can we expect an update to fix this? Thanks

What’d I’d do if I was only using V-Ray Next is back up “[repo]/plugins/3dsmax/3dsmax.py” and replace every occurrence (I believe two) of “VRAY_OPENCL_PLATFORMS_x64” and replace it with “VRAY_GPU_PLATFORMS” and see if that works for you.

This’ll be an easy fix on our side, but different folks will be on different versions. This quick fix will get you working today regardless of which Deadline version you’re using.

A more robust fix (which would work for all versions of V-Ray would be to add the additional variable, but I’m concerned Python formatting might be tricky for some.