Search Issue Tracker
Active
Votes
0
Found in [Package]
2.3.0
Issue ID
XRIT-63
Regression
No
[XRIT] Hovering or selecting objects in Play Mode is not working when "XRInteractionManager" is instantiated dynamically
Steps to reproduce:
1. Open the attached user's project "OpenXrInstantiateTest.zip"
2. Launch Oculus Link with Quest 2 device
3. Enter Play Mode
4. Observe that hovering or selecting Objects does not work
5. Enable the "Complete XR Origin Set Up" Object
6. Disable the "XROriginInstantiator"
7. Enter Play Mode again and observe hovering or selecting Objects works
Expected results: "XRInteractionManager" Objects are removed from prefabs so that they can be instantiated at runtime and no conflicts are caused
Actual Results: Hovering or selecting objects in Play Mode is not working when "XRInteractionManager" is instantiated dynamically
Reproducible: XRIT 2.3.0 (2020.3.46f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b8, 2023.2.0a7)
Environment: Windows 10 22H2
Notes:
-A workaround is to remove the "XRInteractionManager" from prefabs so that it's possible to instantiate it at runtime and no conflicts of multiple "XRInteractionManager" happens
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Add comment