In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.
I've read that the new models were found in Oculus/VR/Meshes/OculusTouchForQuestAndRiftS in the Oculus Integration v1.36. Now that it's been updated to v1.37, I don't find them any more. If someone knows where to find v1.36, it would be appreciated.
...Sorry, found the problem. Unity was for some reason saying "1.37" on the asset store, but on clicking the big "Import" button it was using a cached older version. I fixed it by removing C:\Users\accountName\AppData\Roaming\Unity\Asset Store-5.x\Oculus.
Just a quick update here. The new Oculus Touch controllers were being correctly detected and assigned for Oculus Quest, but not Rift S. We've fixed this bug and it should roll out in SDK1.39. Apologies for the inconvenience.
@Ross_Beef any timeline projected for the 1.39 release? I've got a demo app going to a trade show next week and I'd love to have the right controllers showing. Is the change simple enough that you could maybe point me to a line or two in the 1.38 integration that I can modify to get me by?
@Ross_Beef still having the issue with the SDK 1.40 (Unity v2019.2.2f1, Oculus Utilities v1.35.0, OVRPlugin v1.35.0, SDK v1.40.0.) The controllers are still the old controller for the rift even when I use the rift S. Is there a workaround to force the rift S controller ?
Comments
Apologies for the inconvenience.
will there also be animated controller like the old Touch controllers? Or if they already exist, where can I find them?
Thank you!
Best,
Boris
(Unity v2019.2.2f1, Oculus Utilities v1.35.0, OVRPlugin v1.35.0, SDK v1.40.0.)
The controllers are still the old controller for the rift even when I use the rift S.
Is there a workaround to force the rift S controller ?
Thank you
Your Oculus Utiities is outdated. You need to update the Oculus Utilities via the Unity Asset Store.