Changing job frame range loses render time info

Esoteric this…

I render 1-100. Its finished, all good. Then I realise in my tiredness I should’ve rendered 1-150. Fine. In the monitor I extend the framerange, knowing that deadline will remember its already rendered the first hundred frames.

Unfortunately it loses the timing information for those rendered frames, so the estimated time to finish is all wrong. Could this be fixed?

Yes, this will be fixed in the next release.

Cheers,

  • Ryan