round get_fps()

[brettchalupa]

Before the decimal was just being dropped, causing the values of get_fps() to always oscillate between 59 and 60, for example. This isn't very helpful when debugging, and it's due to the decimal being cut off even if it's, let's say, 59.9 due to floating point arithmetic.

Now the value is rounded, which is more helpful when monitoring for massive frame drops.

Alternatively, if desired, we could change this to be a float that includes some number of decimal places and can be rounded/cast as desired by the developer calling the function. We could also keep track of many frames of data and average it out. But at least this is a bit more usable for now.

Before

macroquad.fps.old.mov

notice it rapidly changing

after

macroquad.fps.new.mov

notice it'll occasionally drop a frame (unsure why)

Code

use macroquad::prelude::*;

#[macroquad::main("MyGame")]
async fn main() {
    loop {
        clear_background(DARKGRAY);
        draw_text(
            format!("FPS: {}", get_fps_new()).as_str(),
            20.0,
            40.0,
            30.0,
            WHITE,
        );

        next_frame().await
    }
}