Search Issue Tracker
Fixed in 1.4.X
Votes
0
Found in [Package]
1.3.0
Issue ID
1400456
Regression
Yes
XR head tracking lost when lost focus with action-based TrackedPoseDriver on Android
-Background: MSFT reported to XR team that with new action-based Tracked pose driver, Camera becomes head-locked when 2D overlay app is opened on Holoens2. This regression started happening since Input system 1.1.x and head tracking works fine in 1.0.2 package. This is a huge blocker for their MRTK v3 adoption.
-Discussion: from the discussion with input team, 1.1.x introduced completely reworked focus handling behavior and introduced the RunInBackground rules, which caused the regression. Slack thread: https://unity.slack.com/archives/C09Q7LYP9/p1642567199067700. Desktop/UWP platform can work around this issue by enabling Run In Background in player setting for short-team fix. But for Android platform. it is not possible to work around it since no RunInBackground option available. I also tried to force backgroundBehavior = ignoreFocus in script on Android, still not working.
-Requests:
For short term fix: Head tracking pose/input data should keep running regardless of the background state.
For long term: we need a clear way for the input system to know the differences between visibility lost on the headset or input lost, which are two discreet stats in OpenXR. With Visibility off, all input can be ceased, but if Visibility is on, the headset must keep tracking.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.4):
A workaround will be in place for this issue in Input package 1.4. Unity will be working on a longer term solution. If you need this fixed immediately, you can pull the package from the development branch of this public github: https://github.com/Unity-Technologies/InputSystem