Search Issue Tracker
Third Party Issue
Third Party Issue in 4.3.X
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
- Crash on FindNearestVertex when objectsToSearch array contains a null transform
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
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
Resolution Note (4.3.X):
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