Crates.io | fixedstep |
lib.rs | fixedstep |
version | 0.3.0 |
source | src |
created_at | 2015-07-15 04:31:15.724236 |
updated_at | 2017-10-02 07:29:51.279824 |
description | Simple macro to create a fixed timestep loop for a game |
homepage | https://github.com/HeroesGrave/fixedstep-rs |
repository | https://github.com/HeroesGrave/fixedstep-rs |
max_upload_size | |
id | 2606 |
size | 22,555 |
A simple library to create a fixed timestep loop in your game (or whatever).
A basic loop running at 60Hz:
fn main()
{
let mut fixedstep = fixedstep::FixedStep::start(60.0); // 60.0Hz
while isRunning() {
while fixedstep.update() {
// Do updating things
}
let _delta = fixedstep.render_delta();
// Do rendering things
}
}
The rate of updates is 'fixed' using the update frequency specified. Be sure to note that the outer loop above runs as fast as possible, which means the rendering framerate is uncapped. You are responsible for implementing the behaviour to cap the framerate (for example: using VSync). Or you could choose not to.
By default, update()
will only return true up to 3 times between calls to render_delta()
. If you want to disable this, you can use the unlimit()
method:
let mut fixedstep = fixedstep::FixedStep::start(60.0).unlimit();
However, this is not recommended. If your update functionality takes longer than the update interval, you may get stuck in a loop and be unable to render (of course, if this occurs it means the machine running the program is unable to run at the requested update rate in the first place. In practice, skipping frames prevents small lag spikes from causing multiple frames of lag as the program tries to catch up).
If you want to change the update limit (for example, if you're updating at a higher frequency than you intend on rendering at), you can call the limit()
method:
let mut fixedstep = fixedstep::FixedStep::start(60.0).limit(5);
Note that the following two lines are equivalent (because the limit defaults to 3):
let mut fixedstep = fixedstep::FixedStep::start(60.0);
let mut fixedstep = fixedstep::FixedStep::start(60.0).limit(3);
Sometimes you may find that you need to create the FixedStep object some time before you begin using it. Time is recorded from the creation of the object, so if you wait 5 seconds before starting the loop, the first update loop will try and run for 5 seconds' worth of updates. To prevent this, you can reset the loop just before you begin using it:
let mut fixedstep = fixedstep::FixedStep::start(60.0);
// Initialise some other stuff, possibly taking a long time.
// ...
fixedstep.reset();
while isRunning() {
// ...
}
In practice you should never need to do this (because you can move the initialisation right before the loop starts), but if there's some niche case that needs it, the functionality is there.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.