Skip to content
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.

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

Need to add Controller support for input #594

Open
capnkenny opened this issue Nov 7, 2023 · 0 comments
Open

Need to add Controller support for input #594

capnkenny opened this issue Nov 7, 2023 · 0 comments
Labels
engine core Tickets pertaining to the engine core codebase. proposal A proposal up for debate.

Comments

@capnkenny
Copy link
Member

What is the current behaviour?
Currently, our GLFW input support does not map to any joysticks/controllers via the Input Provider, so end-users are isolated strictly to keyboard/mouse.

What is the expected behaviour/change?
We want to allow end users to use either KBM or joystick (or both, if applicable).

What is the motivation / use case for changing the behavior?
Enhancing input support for more modern usage.

Are there any potential roadblocks or challenges facing this change?
We may need to alter the input provider to respond to all inputs instead of only "mapped actions" - we can let the default ECS system filter them out, or something similar - mainly that the end state should be both KBM + controller inputs should be provided by the low-level input provider.

Are there any downsides to implementing this change?
No

@capnkenny capnkenny added proposal A proposal up for debate. engine core Tickets pertaining to the engine core codebase. labels Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine core Tickets pertaining to the engine core codebase. proposal A proposal up for debate.
Projects
None yet
Development

No branches or pull requests

1 participant