@BobaTops For the love of god, this horrendous thing should not be automatically enabling itself! It hijacks the first gamepad slot *PERMANENTLY*, making it impossible to use an *actual* gamepad for testing things in studio because it gets thrown into the second gamepad slot and the core/player scripts ignore thumbstick input from all gamepad slots besides the first one.
Yes, I know I can just turn the beta off. Well, I know that now but it took me three hours. I had to waste three hours trying to narrow down what was causing studio to think I had an extra gamepad connected since I have beta features set to automatically enable. Three hours!
Wonderfully executed as always, y’all! Fourteen engineers worked on this and not one of them thought “hey, maybe this thing shouldn’t be permanently enabled, forever hijacking the first gamepad slot!” A true masterclass.
Not to mention, @Kitsomia seems to have reported this very same issue three months ago and a fix is yet to arrive! For those who aren’t particularly math savvy, that’s 25% of a year. What are we doing here???
Can you tell I’m annoyed that I had waste almost half my work day?
EDIT: Actually, as it turns out, it isn’t even possible to turn off the beta anymore! Thanks Roblox, you have officially bricked my ability to test my game in studio.
The beta features menu after a studio restart showing the “Gamepad Emulator” beta disabled, yet the widget is still loaded.
Time to take matters into my own hands, I guess.
