Search Issue Tracker
Duplicate
Votes
5
Found in [Package]
1.0.1
2.0.1
Issue ID
MOXRB-84
Regression
No
[Quest] Visual freeze when Passthrough is enabled in Player
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scene.unity” Scene
3. Build and Run on Quest
4. Observe the Player
Expected result: 9 Cubes are present
Actual result: The Player is black and VR has to be restarted
Reproducible with: 1.0.1 (2021.3.44f1, 2022.3.47f1), 2.0.1 (6000.0.21f1)
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Quest 3 (user reported)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- With Quest 3 it’s required to press A or X to enable Passthrough (Might be required to press 2 times)
- Reproducible with OpenGLES3 and Vulkan
-
Resolution Note:
We will add a validation rule to prevent this configuration
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/OXPB-48
Comments (1)
-
CiaranWills
Nov 04, 2024 23:32
A workaround is to go to Project Settings > Player > Resolution and Presentation and make sure that all the options under Allowed Orientations for AutoRotation are checked.
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
This is a duplicate of issue #-48