Atmospheric environment effects create failed DBR render on deadline

[graham_macfarlane]

Hi,
Using 3dsMax2021.3.16 with Vray5 (update 1.2) and Deadline 10.4.0.12 I have the following issue:
When submitting a distributed render (DBR) job to deadline with any atmospheric effect added (VrayToon / EnvironmentFog etc…) the job always fails if RAW and Separate channel output are used.

With an atmospheric effect added + RAW or Separate channels output ON:
* If I render locally on workstation (no DBR) it renders fine.
* If I delete the atmospheric effect, then DBR job renders fine over deadline.
* If I re-add any atmospheric effect, the DBR job fails over deadline again.
* If I disable the atmospheric effect, the DBR job still fails over deadline.
* With an atmospheric effect still present, if I switch off DBR the job renders fine over deadline.
* If I turn off RAW and Separate channels (just leaving standard Max render output) the DBR job renders fine over deadline.

So, it appears any atmospheric effect interferes with RAW and Separate channel output paths, but only for DBR renders running on Deadline!


The Deadline Error log:

Error: RenderTask: Unexpected exception (26/03/2025 15:15:07; [V-Ray] Cannot send asset \\StorageDrive\Projects\Test\2025-03-26\CAM001_Toon_.exr
Error opening file: [PFileStream::Open] 2: (2) The system cannot find the file specified.)
at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)

Type
RenderPluginException

Stack Trace
at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgt, CancellationToken bgu)
at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajx, CancellationToken ajy)


Thanks for any help diagnosing!
It’s a really strange issue!

Graham

[hermit.crab]

FYi, we do not officially support V-Ray 5 anymore.

Otherwise, I tested this with V-Ray 7 and 3ds Max 2025 and did not have any issues. That error says that there's a problem finding the file specified. Is that the output location or a texture? Try testing with a different (f.e. mapped) network location.

[graham_macfarlane]

Thank you for the reply, Aleksandar.
Yes it is the render output location.
It is all UNC (more robust this way) and its all pathed correctly as when I turn off DBR or delete the atmospheric effect, it renders and saves image fine.
My test scene is blank scene with 1 camera, 1 light, 1 box, 1 sphere and no materials/textures/proxies or other assets at all.


I'm trying to upgrade to Vray7 under Max2024, however, there the DBR doesn't work at all:
Its a different issue concerning Deadline not recognising the new spawner path: C:\ProgramData\Autodesk\ApplicationPlugins\VRay3ds Max20xx\bin\vrayspawner20xx.exe
I've been waiting for over a month on a reply to this issue here:
https://forums.thinkboxsoftware.com/...2024-exe/33383

[hermit.crab]

I'm trying to upgrade to Vray7 under Max2024, however, there the DBR doesn't work at all:
Its a different issue concerning Deadline not recognising the new spawner path: C:\ProgramData\Autodesk\ApplicationPlugins\VRay3ds Max20xx\bin\vrayspawner20xx.exe
I've been waiting for over a month on a reply to this issue here:
https://forums.thinkboxsoftware.com/...2024-exe/33383

Regarding this, I've tried testing it, found an old thread of yours, and applied the mentioned fix. Afterward, in the Deadline Monitor, I went to Tools > Configure Plugins > VRaySpawner and added the new path (C:\ProgramData\Autodesk\ApplicationPlugins\VRay3d sMax2024\bin\vrayspawner2024\) to the 3ds Max 2020 Spawner field (I haven't updated it). Doing so plus submitting a V-Ray Spawner job, it successfully started the 3ds Max 2024 VRaySpawners. Check this thread about it.

Yes it is the render output location.
It is all UNC (more robust this way) and its all pathed correctly as when I turn off DBR or delete the atmospheric effect, it renders and saves image fine.
My test scene is blank scene with 1 camera, 1 light, 1 box, 1 sphere and no materials/textures/proxies or other assets at all.

I tried it on a UNC path and had no issues, too. I'm testing sending the job to my own workstation, although I've tested like this multiple times and have managed to reproduce other issues. Have you tried testing with Backburner?

[graham_macfarlane]

I just made a brand new Deadline 10.4.0.12 repository install on a different computer, and I can't reproduce the issue with DBR + Atmospheric effect!!
Bizarrely, there must be some problem with the original machine and/or its Deadline install which is able to interfere with Vray's internal operations.


Regarding Max2024+Vray7 DBR over Deadline, I re-applied the fix as you did (on the new repository) but still I get same error:

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 will update the VraySpawner.param file with all the Max versions and correct pathing and update here with findings.

Thank you for looking into this Aleksandar!

[graham_macfarlane]

I've tried everything I can think of with the
DeadlineRepository10\plugins\VraySpawner\VraySpawn er.param
And
DeadlineRepository10\custom\plugins\VraySpawner\Vr aySpawner.param

Nothing makes deadline find the the vrayspawner2024.exe


When you say

it successfully started the 3ds Max 2024 VRaySpawners

Was this from the
1) "Submit Vray DBR to Deadline" script, where you need to reserve specific nodes on farm before starting the render
Or
2) "Submit Max to Deadline (3dsCmd)" where you must tick the "Vray/Mental Ray DBR (Off-load)" tickbox. Here, Deadline manages which nodes take part in the DBR job.

For me, 1 works fine in Max2024/Vray7
It's 2 that has the problem!

Thanks again
Graham

[hermit.crab]

Was this from the
1) "Submit Vray DBR to Deadline" script, where you need to reserve specific nodes on farm before starting the render
Or
2) "Submit Max to Deadline (3dsCmd)" where you must tick the "Vray/Mental Ray DBR (Off-load)" tickbox. Here, Deadline manages which nodes take part in the DBR job.

For me, 1 works fine in Max2024/Vray7
It's 2 that has the problem!

I was talking about number 1. As for number 2, I managed to force it to start the VRaySpawner2024 from the folder by editing the .py file (3dsMax.py and 3dsCmd.py)::

In 3dsMax.py (GUI), I edited line 3676:

vraySpawnerExecutable = "C:\\ProgramData\\Autodesk\\ApplicationPlugins\\VRay3dsMax2024\\bin\\vrayspawner2024.exe"

In 3dsCmd.py, I edited line 1500:

vraySpawnerExecutable = "C:\\ProgramData\\Autodesk\\ApplicationPlugins\\VRay3dsMax2024\\bin\\vrayspawner2024.exe"

Make sure you use double slashes.

I'm getting a different error now, which I am not sure if its related to it. Mind if you try it out?

[graham_macfarlane]

Thank you, Aleksandar!
Yes I have just been looking at the 3dsCmd.py too (instead of the 3dsMax.py, which appears to be completely ignored)
I set the vraySpawnerExecutable var within an if statement, testing if Max version is above 2021. If yes then build the path to spawner using the ProgramData path, else build as before.
I haven't fully tested yet, but so far I'm not getting any errors.

Strangely it seems the param file, (listing all the Max versions and associated spawner paths), is completely ignored. Perhaps it's a legacy junk file?

What is the "different error" you see?

[hermit.crab]

Thank you, Aleksandar!
Yes I have just been looking at the 3dsCmd.py too (instead of the 3dsMax.py, which appears to be completely ignored)

3dsMax.py is for workstation mode (not cmd rendering). There's a checkbox to control it in the "V-Ray/mental ray/Corona DBR" settings in the SMTD submitter called er "Use 3dsCmd Plugin".

I set the vraySpawnerExecutable var within an if statement, testing if Max version is above 2021. If yes then build the path to spawner using the ProgramData path, else build as before.
I haven't fully tested yet, but so far I'm not getting any errors. Strangely it seems the param file, (listing all the Max versions and associated spawner paths), is completely ignored. Perhaps it's a legacy junk file?[/QUOTE]

That's for the Deadline support to answer.

What is the "different error" you see?

"Error: Renderer returned non-zero error code, -1073741819"
I'm going to investigate it later.

I haven't fully tested yet, but so far I'm not getting any errors.

So, you have managed to make it work with 2024?

[graham_macfarlane]

Yes, it's consistently rendering in Max2024 with Vray7!
I'd like to do more tests before I formally post on this, but I'd say the 3dsCmd/3dsMax python files are the issue!