Forum Discussion
xbox controller and no rift no longer works with sdk 1.9
Hi
I've been working on an app for a while now which includes support for multiple devices including having no VR headset plugged in. I have the OVR Manager in my project and I've been using the OVRInput options to be able to map my controls to an xbox controller which in the past has been very useful. All this was working fine in Unity SDK 1.8 but once I've updated I've found that this way of mapping the xbox controller has broken and now only works when the Oculus headset is being used.
Is there a way round this or do I now have to write two mapping systems for the xbox controller, one for when the Oculus is plugged in and one for when it's not? The other option is to drop back the Oculus SDK support back to 1.8.
Any help with this would be gratefully received.
All the best
Phil
I've been working on an app for a while now which includes support for multiple devices including having no VR headset plugged in. I have the OVR Manager in my project and I've been using the OVRInput options to be able to map my controls to an xbox controller which in the past has been very useful. All this was working fine in Unity SDK 1.8 but once I've updated I've found that this way of mapping the xbox controller has broken and now only works when the Oculus headset is being used.
Is there a way round this or do I now have to write two mapping systems for the xbox controller, one for when the Oculus is plugged in and one for when it's not? The other option is to drop back the Oculus SDK support back to 1.8.
Any help with this would be gratefully received.
All the best
Phil
1 Reply
Replies have been turned off for this discussion
- To add to this, if I use this code in my project:
OVRInput.GetDown(OVRInput.RawButton.A, OVRInput.Controller.Gamepad)
It returns false and when I press 'a' on the gamepad it will then returns true but only when the Oculus is plugged in. If it isn't plugged in it then returns false and never returns true.
