@Justin_B I agree with you, I don’t want to reinvent the wheel, so I want to use the simplest possible way of submitting without having to write a custom submitter from scratch.
I’m just trying to figure out where I can get the lines of code I need (or use the whole code) so that the whole submission process is automated.
For example, you recommend this:
But there are a lot of maxscript scripts in the folder that are somehow related to each other. I’ve studied some of them, but basically all they do is communicate with the 3ds Max interface. While I need to understand (do I need to?) how their backend works, what it calls and how to get it to initiate the whole process without having to click through the checkboxes and buttons everywhere on their own.
By the way, I studied this file too:
It also describes almost all the functionality of the 3ds Max plugin, but again about communication with the 3ds Max interface only.
Therefore, I still don’t understand how I can implement what I want.
It seems that there is a full-fledged SMTD script that satisfies me in its functionality. However, it requires the presence of a human, since this script is integrated in the 3ds Max interface. Accordingly, to submit a job through it you need to manually click on the SUBMIT button in its interface.
Therefore, the most obvious thing is to try to copy the entire SMTD script code and make it function automatically for my needs. But the problem is that I absolutely don’t understand how and what SMTD maxscript calls to during job submission.
I will explain in the simplest language with a clear example. In my understanding, when I click on the SUBMIT button in the SMTD interface, then some kind of process takes place to record all the data (settings, parameters, variables, etc.) from mine .max scene, at the same time, this data is sent to the Deadline’s API, and then the Deadline’s API recognizes this data and initiates rendering. Like this:
So what happens in the end in the 2nd process?
You have repeatedly recommended me to check the SMTD maxscript files themselves, but all maxscripts are essentially working with pressing buttons or checkboxes in the 3ds Max interface. There is no information about the backend of these scripts and what they call for.
For example, here’s what you can find there:
SMTDFunctions.storeSettingsWithScene - is one of the functions that should explain the process of submission, right?
Okay, I fond the functionality of this function in the SubmitMaxToDeadline_Functions.ms script:
But again, a dead end, since it is unclear where this function leads further and what in fact it does or what it calls to.
In my understanding, there must be something that describes the process that occurs at the moment of submitting via SMTD. Some log files, debug functions, or something where it is described. Otherwise, I cannot track this chain of actions by copying and adapting them to my needs. After all, this maxscript (SMTD) should write all the settings and parameters somewhere in a document or something else, and then feed them automatically to the Deadline API? It’s basically doing that. That’s why I want to understand where and how it does it to repeat the whole process to automate it.
That stuff makes my brain hurt ![:melting_face: :melting_face:](https://forums.thinkboxsoftware.com/images/emoji/twitter/melting_face.png?v=12)