Vray DBR submission error with deadline 10.3.0.10

Hi everyone,

I’ve been setting up Vray7 in Max2024 and hitting same issue with the path to the vrayspawner2024.exe. (Using Deadline 10.3.0.10)

The Deadline monitor gives this error when running a DBR job on any node:

Error: Error: V-Ray DBR: V-Ray Spawner executable does not exist: C:\Program Files\Autodesk\3ds Max 2024\vrayspawner2024.exe

at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)

I realise Chaos group changed the installed path a while ago to:

C:\ProgramData\Autodesk\ApplicationPlugins\VRay3dsMax2024\bin\vrayspawner2024.exe

So, I tried adding these to my firewall exclusion, which didn’t help:

…\bin\vrayspawner2024.exe
and
…\3ds Max 2024\3dmax.exe

Also, Freiraum_FX_GmbH, I tried your suggestion. On the server machine I went to:

DeadlineRepository10\plugins\VraySpawner\VraySpawner.param

I found the last entry (for 3dsMax) was:

[VRaySpawnerExecutable_Max2020]

CategoryOrder=0
CategoryIndex=7

So, after this entry I added entries for Max2021 (current setup) and Max2024 (new setup):

[VRaySpawnerExecutable_Max2021]
Type=multilinemultifilename
Label=3ds Max 2021 Spawner Executable
Category=V-Ray Spawner Executables for 3ds Max
CategoryOrder=0
CategoryIndex=8
Default=C:\Program Files\Autodesk\3ds Max 2021\vrayspawner2021.exe
Description=The path to the V-Ray Spawner executable file for 3ds Max 2021. Enter alternative paths on separate lines.

[VRaySpawnerExecutable_Max2024]
Type=multilinemultifilename
Label=3ds Max 2024 Spawner Executable
Category=V-Ray Spawner Executables for 3ds Max
CategoryOrder=0
CategoryIndex=9
Default=C:\ProgramData\Autodesk\ApplicationPlugins\VRay3dsMax2024\bin\vrayspawner2024.exe
Description=The path to the V-Ray Spawner executable file for 3ds Max 2024. Enter alternative paths on separate lines.

Unfortunately, even after restarting the PC running the Deadline server, the problem persists!

I tried the same entries here too:
DeadlineRepository10\custom\plugins\VraySpawner\VraySpawner.param

Still nothing got fixed! :frowning:

Related thread:

Is there a fix for this or another workaround I can try?

Many Thanks
Graham