For gamepad controllers, the mapping is roughly the same for Xbox One/360 vs PS4/PS3. So it doesn’t really make sense to let the developer know which kind of controller it is.
As a developer, I can only recognize that someone is using VR, but not which VR device they’re currently using. Because of this, I can only offer suitable controls for either the Vive OR the Rift. Not both.
The property seems to be in a placeholder state.
I checked its value with my Vive activated, and its always just an empty string.
Regardless, it should probably be an Enum instead of a string.
Since (regular) scripts can’t use it, and corescripts (probably) don’t use it (as it’s just a placeholder), might as well get rid of it and move it to VRService
It’s meant to replicate to the server for analytics purposes.
I agree with the original post. It’d be nice to be able to access this because the controllers really aren’t interchangeable. It’s something to think about; there might be a more abstract and futureproof way.
Start making the distinction between the controller and the headset if you’re aiming for futureproof. It’s only a matter of time before we start seeing third-party VR controllers.
Putting this under the UIS seems logical.
Hiding the controller type is counterproductive. I don’t want to tell a Dualshock user to press Y during a tutorial.
Would be much appreciated, and developers should definitely be able to support multiple controller types. Before I got an XBox controller, I always had to fumble around looking for equivalent keys on my PS3 controller when prompted to press xyz button.
Almost CERTAIN that if Roblox really is coming to PS4, they will be forced to have this, considering the Sony-Microsoft feud.
I doubt Sony wants to see xbox-controls on their platform.
