Roblox’s Controller Emulator plugin forcibly takes up the slot of Gamepad1, even when closed and an actual gamepad connected. This means any code that specifically listens for input from the first gamepad slot will be completely ignored unless done with the Controller Emulator. This includes roblox’s own character controller.
As I’m sure you can imagine this is quite frustrating to deal with, as it means my character is completely locked in place anytime I playtest with a controller. The only workaround I’ve found so far is to
- Enable the Controller Emulator
- Perform any input with the emulated controller
- Close the Controller Emulator
This can also be seen happening in this post
Expected behavior
I expect the controller emulator to not exist (or at least as much as possible) while the widget is closed.
A private message is associated with this bug report