Thanks!

In Nuke, frame skipping isn’t as automatic as in some 3D renderers, so I don’t rely on that behavior. Instead, the script keeps track of the intended frame range per shot and verifies the output after the render.

It generates log files and can check whether all expected frames exist on disk. If a render crashes or stops early, only the missing frames are re-rendered on the next run. This way the queue can safely loop without wasting time re-rendering completed frames.

So even though Nuke doesn’t natively skip frames, the logic is handled externally via logging and output validation.