It’s a very minor issue but the new controller emulation feature will start enabled, causing UserInputService.GamepadEnabled to be true, but opening and closing the widget (sometimes?) fixes the issue
I figured I should report it since it confused me and I thought my input code had broken, it might get in the way of other developers and cause confusion
Expected behavior
The controller emulation feature should start disabled instead of enabled
Thank you for filing this, it’s likely caused by the new Controller Emulator (currently in beta) not starting in the correct state when there are no emulated devices. We’re going to fix this in an upcoming update.