Bevy input and fixed movement
Separates the moment a button is sampled from the simulation tick that consumes it. It preserves one-shot actions and smooth motion when a rendered frame contains zero or several simulation updates.
bevy-fixed-input-motion
See how it helpsWhen is it useful?
Use when varying frame rates cause missed input, repeated jumps or uneven movement in Bevy.
What does it help you do?
- Separates frame-based input sampling from commands consumed by fixed simulation ticks.
- Defines input accumulation when frames contain several simulation steps or none.
- Interpolates visual movement without modifying authoritative state during pause and catch-up.
Try asking this
Our platformer sometimes jumps twice on a slow machine. Queue the jump edge for the fixed simulation, then test frames with no tick and several ticks. One press must cause one accepted jump, and camera smoothing must not move the authoritative character during pause.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Bevy — fixed input motion
Use when implementing Bevy input sampling, fixed simulation, movement or interpolation.
Version and project gate
Inspect Cargo.toml, Cargo.lock, Rust toolchain, exact Bevy release, plugin compatibility, feature selection, schedules, state definitions, asset roots and target backend. Read the matching migration guide before using newer examples. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Separate input edges sampled per render frame from commands consumed by fixed simulation. Define accumulation/consumption when several fixed ticks occur per frame or none occurs. Use the installed time APIs and interpolate presentation without altering authoritative state.
Deliver
A frame/tick input contract and a movement system with explicit pause and catch-up behavior. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Reading a just-pressed edge in several fixed ticks may execute an action repeatedly.
Acceptance scenario
Press and release between fixed ticks, induce several ticks in one frame, pause and resume without duplicating an action. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Talon. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
- https://bevy.org/learn/quick-start/getting-started/ecs/
- https://bevy.org/learn/migration-guides/0-18-to-0-19/
- https://bevy.org/learn/migration-guides/0-17-to-0-18/
Task-specific official references
Included files 1
SKILL.md