fps_clock 2.0.0

A crate for making your game loop run at the correct FPS
Documentation
  • Coverage
  • 83.33%
    5 out of 6 items documented1 out of 5 items with examples
  • Size
  • Source code size: 15.16 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.36 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Links
  • BookOwl/fps_clock
    13 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • BookOwl

fps_clock

https://docs.rs/fps_clock/

A simple crate to control the FPS of your game loops in Rust.

Usage

This crate is on crates.io and can be used by adding fps_clock to the dependencies in your project's Cargo.toml.

[dependencies]
fps_clock = "1.1"

and this to your crate root:

extern crate fps_clock;

To use the FPS clock, just create one with the FpsClock::new(fps: u32) method. Then call the tick() method at the end of your game loop.

Examples

Running your game loop at 30 FPS:

extern crate fps_clock;
fn main() {
 // Set up your game here
 let mut fps = fps_clock::FpsClock::new(30);
 loop {
     // Complicated game loop stuff here
     fps.tick();
 }
}

License

This crate is licensed under either the MIT or the Apache 2.0 license, depending on what you want. See LICENSE.MIT and LICENSE.APACHE for details.

Changelog

v2.0.0

Made FpsClock::tick() return the time in nanoseconds since the last time it was called instead of ()

v1.0.0

First release.