Canceling Batch render in v3 vs v2

[dhaskovec]

Question regarding canceling a batch render in standalone 3.02 using the built in batch rendering script.

When leaving a batch render overnight with a large amount of samples set, in v2 I could cancel the batch before it finished on the last view, close out of the batch rendering dialog, and have that view with all the render progress visible and ready to be saved manually. When I try the same process in v3.02, it dumps all the progress and deselects the view/ render target making me unable to save any batch progress. Another difference I noticed is the render viewport is sort of grayed out behind the batch dialog in v3, which I assume means it's not actually selected.

Any reason why this changed or how to save a batch render mid progress?

I liked this approach since I could control the order of views rendered, saving the least important view for last but still having something to work with the next day. Any suggestions would be appreciated.

[bepeg4d]

Hi dhaskovec,
v3.02 is quite old now, culd you try with the new 3.5 to see the difference?
Now there is a new render job node system that allows to make more complex batch rendering sessions. Basically the render job node is a special Lua scripted graph that can be personalized based on your needs.
I have to admit that I have not personally tested the situation that you describe, but it would be nice to have your opinion about the new batch node system. Here is the direct link to v3.5 topic:
viewtopic.php?f=33&t=57811
and here is a link at a discussion about render job nodes:
viewtopic.php?f=9&t=57135
ciao beppe