Fossilize seems to be inaccuratly estimating current progress #251
Description
Recently I had fully compiled the shaders for Deadlock and the first 80% was kind of fast. Taking exactly an hour. An hour later it was at 91%. An hour after that 95%. With the remaining 5% taking an additional hour and a half. The problem seems to be that the replay doesn't calculate total frames correctly. At 0% there the log states it was on frame 0 out of 162,056. However, by the time 100% rolled around this number grew nearly to be 1,101,139.
I know my computer isn't great, so I understand it takes a long time, it's just hard to estimate how long it'll be taking with the percent not even closely aligning with total time.
Specs:
Manjaro Linux 6.10.6 kernel at time of processing
555.x GPU driver at time of processing
I5-4440 cpu
24 gb ddr3 ram
GTX 1070
shader_log.txt