*/OUT*
OUT context version to export RS Proxy ROP submissions, this one is used on OBJ scenes workflows.
The path of the Redshift ROP node that will be used on the submission process, by default has the expression opinputpath('.', 0) which means that can be removed and use the submitter on a “wireless” mode.
Take that will be used during the submission.
Start the submission process by starting the cooking of the internal TOP network.
<aside>
☝ You can’t submit multiple submitter nodes at the same time by selecting them and pressing Submit. If you want to submit various dy RS Proxy Submitter nodes it has to be with a TOP setup, you can do this very easily with the RS Proxy Submitter Batch Render and RS Proxy Submitter Batch Render START script tools.
</aside>
Cancel the cooking process of the TOP network.
A very IMPORTANT parameter. Together with the Frame Range, this will define how many background instances of Houdini will be opened to export the .rs, as the note at the beginning of the RS Proxy Submitter page said, depending on your scene, the export process can be very performance and RAM hungry, especially because the CPU setting of the internal scheduler will use all the CPU cores less one.
The default parameter uses a Python function with custom logic to define a recommended value based on the frame range and the core count of the system.
If you have a sequence of 240 frames and a system with 32 cores, it won’t be recommended to open one Houdini instance per core, it will be very unstable (this will happen if you set the Frames per Batch on 1).
For 240 frames and 32 cores, if the scene is not too heavy, probably a value of 24 on the Frames per Batch parameter will be a good number, it will create 10 instances of Houdini for the export/submission process.
If by any chance your export is still unstable due to RAM, you will want to increase the Frames per Batch value, this will reduce the amount of Houdini background instances, and the export will be slower but more stable.
On the opposite side, if your scene is pretty light and 10 instances of Houdini don’t consume too much of your RAM, you can try to reduce the number of Frames per Batch to force the creation of more Houdini background instances and have a faster export.
Just to summarize, the value of the Frames per Batch will depend on the system that will perform the export, the scene, and the frame range, most of the time the default Python value should suggest a good value 🤞.
Scheduler parameters from the internal TOP network.