Sub-1fps rates are REAL — a software-rasterized scene on a heavy volume
genuinely renders at 0.4fps — and rounding them to 0 reads as "not
rendering at all", the opposite claim, in exactly the regime where the
number matters. Below 0.1fps (one frame every ten seconds) a second
decimal keeps "0.0" off the readout too. Two decimals is where it
stops: under 0.005fps (one frame every 200 seconds) the reading does
round to "0.00", and a wider string would not fit the 38px rail
square. Nothing reaches that — the FPS window would have to hold two
frames more than three minutes apart — and at that point "0" is the
honest answer anyway.
Shared with the Performance panel's Current FPS row so the rail gauge
and the panel can never disagree about the same rate.
Format an FPS reading for a numeric readout.
Sub-1fps rates are REAL — a software-rasterized scene on a heavy volume genuinely renders at 0.4fps — and rounding them to
0reads as "not rendering at all", the opposite claim, in exactly the regime where the number matters. Below 0.1fps (one frame every ten seconds) a second decimal keeps "0.0" off the readout too. Two decimals is where it stops: under 0.005fps (one frame every 200 seconds) the reading does round to "0.00", and a wider string would not fit the 38px rail square. Nothing reaches that — the FPS window would have to hold two frames more than three minutes apart — and at that point "0" is the honest answer anyway.Shared with the Performance panel's Current FPS row so the rail gauge and the panel can never disagree about the same rate.