Elapsed Time oversight?

[Terrachild]

Maybe this has been mentioned before, I didn't see anything about it.

The elapsed time counter at the bottom of the GUI doesn't update properly.

If you pause the render, and then restart it after a little while, the time jumps up to show the elapsed time since you started the render, not the elapsed time of the actual render.

I don't think it should work like that. There should be an internal timer that is started and stopped along with the render. I think the coders used the system clock for the calculation.

Shouldn't this be corrected?

[Terrachild]

Oops, I guess this has been mentioned before.
But it was awhile ago. Is this going to be fixed?

[SATtva]

I guess so, as this task is already in the bugtracker, so it won't be missed.

[IndigoTea]

Just another voice adding to this; also, is there a way to save "rendered time" to the .flm, so that if you have to close and re-open the render, the amount of time spent rendering is saved and incremented between sessions?

[jeanphi]

Hi,

That's not currently possible.

Jeanphi

[jensverwiebe]

we could add the elapsed time to flm-name automatically as workaround.

Example would be: testscene_1h_35m.flm
I normally prefer adding the spx to the name: testscene2000spx.flm

Jens

[patro]

Good idea Jens!
why not both?

[jeanphi]

Hi,

Maybe we should pay more attention to incrementing the flm version number each time we change the binary format and provide a utility that would convert previous versions to the current one?

Jeanphi

[patro]

Hi,

Maybe we should pay more attention to incrementing the flm version number each time we change the binary format and provide a utility that would convert previous versions to the current one?

Jeanphi

Oh yes!
this would be also a great innovation!

[RichardPrins]

One more voice that would like to see this feature added. After a resume the Stats line should show the total render time in the Totals section. I remember Indigo did it, when it was still free, and it was pretty useful.