You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the axis_inputs example (cargo run --example axis_inputs)
Press right trigger 2
What you expected to happen
The program should print the value of the trigger press depth
What actually happened
The program crashes:
thread 'Compute Task Pool (18)' panicked at C:\Users\Travis\.cargo\registry\src\index.crates.io-6f17d22bba15001f\leafwing-input-manager-0.15.1\src\action_state\mod.rs:594:14:
assertion `left == right` failed
left: Button
right: Axis
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `car_game::car::control_player`!
Encountered a panic in system `bevy_app::main_schedule::FixedMain::run_fixed_main`!
Encountered a panic in system `bevy_time::fixed::run_fixed_main_schedule`!
Encountered a panic in system `bevy_app::main_schedule::Main::run_main`!
error: process didn't exit successfully: `target\debug\car-game.exe` (exit code: 101)
Additional information
It looks like this assertion was added in: 5e90a7d
I'm not sure if the example needs to be updated to some alternative method (from looking through the docs I didn't see a great way of getting the button value at a higher level), or if this assertion isn't appropriate at this location.
The text was updated successfully, but these errors were encountered:
Version
0.15.1, or current main ( 5bb37ff )
Operating system & version
Windows 11
What you did
axis_inputs
example (cargo run --example axis_inputs
)What you expected to happen
The program should print the value of the trigger press depth
What actually happened
The program crashes:
Additional information
It looks like this assertion was added in: 5e90a7d
I'm not sure if the example needs to be updated to some alternative method (from looking through the docs I didn't see a great way of getting the button value at a higher level), or if this assertion isn't appropriate at this location.
The text was updated successfully, but these errors were encountered: