Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
4.3.0
Issue ID
OXPB-167
Regression
No
[QuestPro][OculusXR] Right eye flickers with Vulkan and ETFR enabled on a Quest Pro device
Steps to reproduce:
1. Open the attached user's project "TestScenesXRSDK_2022_48f1.zip"
2. Switch to Android Platform
3. Make sure OculusXR is the selected XR Plugin and Eye Tracking Foveated Rendering is selected in OculusXR settings
4. Build "Assets/Test/Underlay/UnderlayQuad.unity" to a Quest Pro device
5. Observe the right eye flicker between the scene and splash/loading screen
Expected results: no flickering on the right Eye
Actual results: right eye flickers with Vulkan and ETFR enabled on a Quest Pro device
Reproducible according to the user: OculusXR 4.3.0 (2022.3.49f1)
Not reproducible according to the user: OculusXR 4.3.0 (2022.3.48f)
Could not test on 2021.3.45f1, 2022.3.52f1, 6000.0.26f1, 6000.1.0a3 due to the issue only reproducing on a Quest Pro
Testing Environment: Windows 11 23H2
Not reproducible on: no other environment tested
Not reproducible on these devices:
VLNQA00463 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Notes:
-According to the user, issue only reproduces with Vulkan
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
Resolution Note:
This issue was resolved by a firmware update on Quest Pro devices. Please update your devices to the latest firmware if you encounter this issue