A very strange failure of submitting 3ds Max scenes via deadlinecommand

[Tiger]

@Justin_B I’m sorry to bother you, but I still haven’t been able to solve the problem on my own.

I found a similar topic where you already answered about possible causes of the problem and ways to fix it:

@Justin_B

But since you’re not having issues submitting through the integrated submitter I’d compare the job info and plugin info files created through your process to the ones created by the submitter. As far as the Worker running the job is concerned, you could have hand-written those job and plugin info files as long as the contents are valid.

Maybe there’s a file path getting mangled in the update and Max is unhappy about it?

If that path of investigation goes nowhere, see about going through the 3ds Max troubleshooting guide to see if the issue is this scene when run in the Deadline Worker’s render sandbox.

Unfortunately, these recommendations weren’t very helpful in solving the problem. It also seemed to me that the reason might be in the file paths, but going through various parameters and substituting them (job info, plugin info) into my task didn’t lead to anything. That is, no matter how I specified the paths for the output image or render elements separately, it didn’t lead to any result. I also tried the other parameters, comparing them with a successfully rendered task using the SMTD script with my custom submission via deadlinecommand, but I didn’t see any significant differences. It’s just kind of mystical.

Also, I found another topic with the similar problem:

@christopheC

We are using it in production since then and it works very well for our still renderings and animations but we are running into a recurring error anytime a render element has a filepath in it’s parameter. If you remove the filepath it does fix the error and we can render our CXR file including all render elements.

But as in the previous case, that’s not the point. Unlike the author of the message, I didn’t have any paths to the render elements in it’s parameter.

@Justin_B Returning to the topic where you had a dialogue, I tried this option with 3dsCommand. It was successful, and everything started rendering properly. However, this doesn’t solve my problem, since 3dsCommand is not as convenient for my papiplane as deadlinecommand (besides, it is not recommended to use it in the 3dsCommand documentation, only in extreme cases - “when a particular feature does not work with our normal 3dsmax plugin”)

@Enrico_Lapponi

I tried to submit the scene with the 3dsmax command option and it renders correctly (I followed the steps in 3ds Max troubleshooting guide ).

So at this point I imagine the problem is in the pluginInfo or jobInfo files?

So I still don’t understand what could be the reason. Even if you fix it with some kind of magic switch or checkbox in 3ds Max or Deadline, it still doesn’t answer the question of why two absolutely identical empty scenes, one of which is fully rendered correctly, and the other is not.

Therefore, I ask for help with debugging or to clarify where I can contact so that I can be helped to resolve this issue. If any more details are required from me, I will be happy to provide everything that is necessary

(btw, I’m using Deadline 10.3.0.13)