Search Issue Tracker
Fixed
Fixed in 1.5.1
Votes
3
Found in [Package]
1.5.0
Issue ID
OXRB-11
Regression
No
XR Plugin Management - Oculus + disabled OpenXR w/ Oculus Touch Profile causes controller tracking issues.
Repro Steps:
Open Project
Ensure Oculus headset is attached
Press Play
Observe wild controller movement
Stop, navigate to Project Settings > XR Plug-in Management
Disable Oculus, Enable OpenXR
Press Play
Observe controllers move normally
Navigate to Project Settings > XR Plug-in Management
Disable OpenXR, Enable Oculus
Navigate to > OpenXR sub-tree
Remove Oculus Touch Controller Profile
Press Play
Observe controllers move normally
The issue is that the OculusTouchController layout defined in the interaction profile, even though its in a different namespace and a nested class, has the same name as the layout from the oculus provider. This causes the last one to register to win and all sorts of weird stuff to happen.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note (fix version 1.5.1):
Fixed in OpenXR 1.5.1 package