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.
Comments (1)
-
TJoE70
Jun 16, 2022 01:35
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 1.5.1):
Fixed in OpenXR 1.5.1 package