so… did a quick test on my laptop.
It was successfull, with some little hiccups.
When I submit the job I get this error.
After this an empty handler opens. If I close it I get the same error as before.
However, if after I manually open the tray and the handler, the job is actually there, and things work fine. I tried to submit the job from the regular pandora submitter and I didn’t get the same error.
So after this the rendering went smoothly.
Another thing: Pandora has a neat functionality for rendering passes. When you activate some pass for cycles, to render them out you need to activate the compositor and connect them to an output node, as you would do normally. However Pandora automatically sets the render output path based on the main output you set in the submitter, and automatically names the passes based on their name, or on the label of the last node that is connected to the output node for a specific pass. When I tried to output some render passes using the shot manager, the output node behaved as in default blender, where you have to manually set the output and the pass names. This is obviously not a “show stopper”, but it would be nice to maintain the ability to automate the render passes output and naming process based on the root output path and original passes names.
Let me know if this makes sense, I guess the passes explanaition maybe it’s a bit confused
Also… do you have a donate button or something? I am proposing all this stuff, but first of all I don’t want to sound as I am pretending something. I think your plugin is great and it has the potential to be a little game changer for my and I am sure many other people workflow! I would gladly pay for this, just so you know