I am using
MAX 2024 2024.1 update 26.1.0.2270
Deadline 10.3.0.13
Corona 10 hotfix 1
I have been using custom submission scripts since max 2016 and 2019 is our current production version with deadline and corona. Everything works correctly with 2019 with no issues and has for several years.
We would like to switch to 2024 but not until it can be verified that it works with my scripts.
I submitted a simple cube to deadline with 2019 and everything works correctly. With 2024 I do get an error. It seems it will not save the image I am trying to render. The cube has an unwrap on it. If I doownload the max file and rendering script and run them locally, everything is good but not when the worker picks up the submission, there is an error. I do not see anything obvious in the logs. attached is my max log and deadline log
The file in Deadline log.zip is empty, so I can’t say what might be going wrong.
All we know from Unexpected exception (Monitored managed process "3dsmaxProcess" has exited or been terminated is that Max has quit and we didn’t tell it to. Usually that’s a crash, but not always.
Re-upload that Deadline log and we’ll get this figured out.
There’s no clues I can find in this render log, no warnings, exceptions or other typical signs of trouble.
I want to say it’s a Corona issue, just because the crash happens as Corona triggers cleanup (line 505):
2023/11/21 16:56:29 INF: [20184] [24200] CORONA : Pass 59/60
2023/11/21 16:56:29 INF: [20184] [24200] CORONA : Denoising
2023/11/21 16:56:29 INF: [20184] [24200] CORONA : Cleaning up
2023/11/21 16:56:29 ERR: [20184] [24200] An unexpected exception has occurred in the network renderer and it is terminating.
That last line is from 3dsMax, and what’s causing the crash out.
If you re-submit this scene to go through 3dscmd how does it behave? Maybe running in our batch mode is obscuring an error message that would help explain what’s going on.
@Justin_B we spoke about using the 3dscmd command quite a while ago in another thread. I believe you said that it won’t work because it’s using a script to call the render command.
I’ll have to take your word on that one, I don’t recall that and I’m not finding the thread.
Anyways, if pulling the render out to a command-line equivalent isn’t possible then there isn’t much more I can recommend as it doesn’t appear to be Deadline causing the problem.
Gotcha - and the 3dscmd submitter only has support for pre and post render maxscript scripts instead of running the render as a maxscript job so you’re correct that that’s a dead-end.
Assuming the ‘max log’ file is from your running that scene and script I compared the output between that and Deadline. I should have done this earlier!
The issue is that Corona is kicking out the following:
2023/11/21 16:56:29 ERR: [20184] [24200] An unexpected exception has occurred in the network renderer and it is terminating.
We assume that anything that outputs that line is a failed render so we fail the task, but in your testing it carries on.
That’s why your render fails on the Worker - our error handling is stepping in. If you can get Corona to stop crashing while its cleaning up Deadline will start behaving. Or you could run these jobs through the generic CommandLine plugin (Submit->Miscellaneous->CommandLine) which won’t have error handlers catching on these messages.
Not explicitly. But if it works in 3dsMax it should work. The reason being that Deadline is just telling Max to render, so we should be inheriting functionality from there.
