This specifically helps the fps graph. It calculates the fps like this:
(uint64_t)info->frames * 100 / (double)(now - info->last_time);
The timings when query_new_value() are called will vary, so fps values of
e.g. 59.9 fps will be truncated to 59 fps.
Rounding the value before casting to
On Sat, Jun 17, 2017 at 4:57 PM, Christoph Haag
wrote:
> This specifically helps the fps graph. It calculates the fps like this:
> (uint64_t)info->frames * 100 / (double)(now - info->last_time);
> The timings when query_new_value() are called will vary, so fps values of
> e.g. 59.9 fps wil
