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
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