New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Current limitations of input mocking for `GamepadButton`s due to constraints in Bevy's input handling #516

Open

Shute052 opened this issue May 3, 2024 · 0 comments

Labels

blocked bug

Collaborator

Shute052 commented May 3, 2024 •

edited

Loading

Due to a change introduced in input: allow multiple gamepad inputs to be registered for one button in one frame bevyengine/bevy#9446, Bevy now disregards all external GamepadButtonChangedEvents that attempt to modify the state of GamepadButtons.
Caused input mocking subtly broken Input mocking is somewhat broken by Bevy 0.12 #407
Upstream issue: Sending a GamepadButtonChangedEvent but Axis<GamepadButton> is not changed bevyengine/bevy#13195

The text was updated successfully, but these errors were encountered:

Shute052 added the bug label

alice-i-cecile added the blocked label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment