pub const MISS_FACTOR: f32 = 1.25;Expand description
How far past the display budget a single frame must run to count as a miss.
Not 1.0. A frame landing a hair over the budget is the ordinary condition of a vsynced renderer — the measured interval is the refresh interval, plus scheduling noise — so a bare comparison would read a perfectly healthy 60 fps run as missing on half its frames. 1.25 is “missing the budget by a quarter”, which at 60 Hz is 20.8 ms: past it the run is visibly not holding the rate.