Enum tetra::time::Timestep

pub enum Timestep {
    Fixed(f64),
    Variable,
}

The different timestep modes that a game can have.

Serde

Serialization and deserialization of this type (via Serde) can be enabled via the serde_support feature.

Variants

Fixed(f64)

In fixed timestep mode, updates will happen at a consistent rate (the f64 value in the enum variant representing the number of times per second), while rendering will happen as fast as the hardware (and vsync settings) will allow.

This has the advantage of making your game’s updates deterministic, so they will act the same on hardware of different speeds. However, it can lead to some slight stutter if your rendering code does not account for the possibility for updating and rendering to be out of sync with each other.

To avoid stutter, you should interpolate your rendering using get_blend_factor. The interpolation example in the Tetra repository shows some different approaches to doing this.

This mode is currently the default.

Variable

In variable timestep mode, updates and rendering will happen in lockstep, one after the other, as fast as the hardware (and vsync settings) will allow.

This has the advantage of being simple to reason about (updates can never happen multiple times or get skipped), but is not deterministic, so your updates may not act the same on every run of the game loop.

To integrate the amount of time that has passed into your game’s calculations, use get_delta_time.

Trait Implementations

impl Clone for Timestep

fn clone(&self) -> Timestep

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Timestep

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Copy for Timestep