Search Issue Tracker
By Design
Votes
0
Found in [Package]
Issue ID
1233282
Regression
No
Unity 2018.4.16 & up does not correctly support HoloLens2's HolographicSpace.UserPresence = PresentPassive
1. What happened
The support to have Unity continue to render the application when HolographicSpace.UserPresence = PresentPassive and RunInBackground = 0 broke.
This was correctly working 2018.4.8 but seems to have have been broken in 2018.4.16 (I didn't test any builds in between so the regression might have been in earlier releases).
2018.4.16 did fix the issue where the app wasn't correctly getting Application.Paused events when the user explicitly exists out of the Unity applications (when RunInBackground = 0), so I suspect that's when the regression got introduced.
2. How we can reproduce it using the example you attached
Repro steps:
1. Build and deploy the attached project
2. Bring up the Start menu and tap on the 'Settings' application
[Expected]
The unity app will continue to be rendered along side the Settings application. We would receive the OnApplicationFocus = false event.
[Actual]
The unity app got paused -- we received the OnApplicationPause = true and OnApplicationFocus = false.
Note that if the above has been fixed, we also need to make sure this other scenario works:
1. Build and deploy the attached project
2. Bring up the Start menu and tap on the 'home' icon at the bottom of the Start panel
[Expected]
The unity app got paused -- we received the OnApplicationPause = true and OnApplicationFocus = false.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This behavior cannot be supported exactly as requested to fit all cases. Need to further discuss how this should be resolved with MS's team.