We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
When binding both GamepadAxis and MouseAxis to the same action, unexpected behavior occurs:
MouseAxis Movement: The MouseAxis movement events trigger correctly.
GamepadAxis Movement: However, the GamepadAxis movement events do not trigger correctly and end up too early.
Both mouse and gamepad axis events should work as expected when bound to the same action.
If the action names for GamepadAxis and MouseAxis are changed, both mouse and gamepad axis events work as expected.
To test by yourself, run the example binding_with_code.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem:
When binding both GamepadAxis and MouseAxis to the same action, unexpected behavior occurs:
MouseAxis Movement: The MouseAxis movement events trigger correctly.
GamepadAxis Movement: However, the GamepadAxis movement events do not trigger correctly and end up too early.
Expected Behavior:
Both mouse and gamepad axis events should work as expected when bound to the same action.
Reproducible Steps:
Additional Information:
If the action names for GamepadAxis and MouseAxis are changed, both mouse and gamepad axis events work as expected.
To test by yourself, run the example binding_with_code.
The text was updated successfully, but these errors were encountered: