calus wrote:Also I'm wondering if we are not overcomplicating things because of obvious missing features in Octane:
The typical case for batch render jobs is to render several shot in a scene,
obviously each shot have a different render target(different camera) and a different frame range.
There's actually no way to render at once several shots inside Octane ... not very animation friendly
Maybe a better idea is to add start and end frame to the animation node wich could be used in batch render script and render job node ?
vijay_thirukonda wrote:We do have animation frame settings in the render job node and will add output folder option to the node as well.
calus wrote:Also please change the default filename template to something actually usable,
The frame tag %f must always be at the end of the name (before extension), not the pass tag %p,
else the image sequence is not readable by any software
(Yes I know this is the same default template as in the batch render script,
should also be changed there )
gah5118 wrote:would it be possible to do a combination of the two.
in other words, have a render node group which you can connect all, but when the box comes up, it has check boxes like in the other option. this way, you can add to it or subtract as needed at the last second. also having the total frame range isn't a bad idea... when i have render failures it's helpful to be able to start where it failed.
as far as frame range per render target.... just make separate render jobs for different render targets. it's how I'm using it and is working out great. when the master render job node is implemented, then it will be a charm.
Users browsing this forum: No registered users and 15 guests