Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
4.0.3
Issue ID
1333691
Regression
No
[XR SDK] A black screen is rendered in HMD after entering Play mode in two Editor instances
Reproduction steps:
1. Open the user's attached "FocusSwitch-A.zip" and "FocusSwitch-B.zip" projects side-by-side
2. Load the "SampleScene" in each project
3. Enter Play mode in the "FocusSwitch-A"
4. Observe the HMD view ("FocusSwitch-A" project's Game view is rendered)
5. Enter Play mode in the "FocusSwitch-B"
6. Observe the HMD view
Expected result: the "FocusSwitch-B" project's Game view is rendered
Actual result: a black screen is rendered (see the attached "repro.mp4")
Reproducible with XR SDK: 3.2.13, 4.0.3 (2019.4.26f1, 2020.3.8f1, 2021.1.6f1, 2021.2.0a16)
Could not test with 2018.4 (no XR SDK available)
Notes:
- the issue is not reproducible with Legacy XR
- sometimes the "FocusSwitch-A" project's view stays rendered instead of a black screen
- switching the focus back to the first project and waiting a few seconds (~3-5s) resolves the issue (see "fix.mp4" video)
Tested with:
- Oculus Rift
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:
Currently, we don't support two or more editor instances running cases.