*/OUT - /LOP - /TOP*
Multithreaded TOP export of the RS Proxy files with the possibility of being submitted to Deadline render manager as a rendering Job for the Redshift standalone tool (redshiftCommandLine tool).
<aside>
π‘ Make sure to read the Frames per Batch information inside the RS Proxy Submitter OUT or RS Proxy Submitter LOP
</aside>
<aside>
β It is very recommended to bake every simulation that your scene has before starting the submission, especially if it is a heavy simulation. Why is this? Letβs say you are going to render a job with 240 frames, those frames will split into multiple background instances of Houdini by the internal TOP network, each instance will have to run the simulation to be able to export the .rs file, which means that will be a very performance and RAM hungry, especially for the instances that will render the last frames because they will need to simulate the ending point and then start the .rs export process.
</aside>
<aside> π‘ Each context version of the submitter has its own parameters, but the Deadline parameters are the same on each version.
</aside>
Toggle to submit or not the Deadline job, useful to only export .rs proxies without submitting the Deadline job.
Specifies the range of frames to render (start frame, end frame, and increment).
Submit the job as suspended, you will need to manually enable the job in Deadline Monitor.
The name that will be used on the Job creation.