Please implement a better way of disabling this. Currently, the only way to turn it off is to have the device emulator open all the time, which is not a great experience. My game disables keyboard controls when a gamepad is connected, since they control vehicles in completely different ways, so this is making testing a nightmare.
1 Like
This behaviour is still very much broken.
Currently in Studio on my mac, for GamepadEnabled to be false you need to first open the device emulator, then enable the virtual gamepad (by ticking the box), and then close the window (disabling it).
Unticking the box does not disable the virtual gamepad. The only way to do this is to press the “x” on the window.
Then, you need to keep the device emulator open, or you will need to repeat the whole process again.
The default should be off and false.
1 Like
Hi,
Thank you for your feedback, however, I’m not sure I follow the issue here: is the Controls Emulator showing when the Device Emulator is turned off?
In default Play Solo with no Device Emulator on, the GamepadEnabled is false, so you should be able to test in that mode.
You can also create custom devices if needed and set the Platform to None to work around any issues you’re having.
In the meantime, I forwarded this to our product team to see if they have any thoughts on your use case.
Thank you!
1 Like
It is not showing when Device Emulator is turned off.
On my mac, the default is that GamepadEnabled is true. The only way of making it read false is by opening the emulator, opening the window, and then pressing the X. Even unticking the toggle does not work.
1 Like
Wow sorry to hear that!
It’s super strange behavior, are you able to file a DevForum bug about this with a video attachment?
I’ve been trying to repro this, and this is what I have (which is as designed):
- Whenever I turn off the Device Emulator or switch to a non-console or VR device, I get false for
GamepadEnabled. - When in Play Solo, the
GamepadEnabledis following the state of the widget as well. - Only in Edit mode does it stay on for Console and VR devices.
1 Like
Hi, I’m sorry I missed your reply (blame exam season). I would be happy to check again and record a video if it is still needed. It does seem to be remembering the fact that the emulator is off now when I relaunch studio so this hasn’t been a major issue.
The Controller emulator only turns on automatically for console and VR devices – by design, since we would like devs to know that these virtual controllers exist. We are looking into better ways of handling this based on the above feedback, for example through new APIs or settings. For now, the workaround is to use a cloned device with non-console / non-VR Platform. Given that the Platform doesn’t play a significant role in the Emulation this should be an easy workaround.
Fingers crossed, and I’m really glad that there’s attention to the VR development team. I am really excited about the future of VR with Roblox, and equally I am really hoping that future updates won’t break VR games. If thing’s continue this “smooth sailing” path, I hope to release “Toolbox Engine” potentially in the future: