Search Issue Tracker
Fixed
Fixed in 4.3.0-pre.1
Votes
0
Found in [Package]
4.3.0-pre.1
Issue ID
OXPB-157
Regression
Yes
[Vulkan][OculusXR] Only 1/4 of the Screen is rendered on Left/Right eye when building to Quest 2/3 device using OculusXR 4.3.0-pre.1 with Vulkan
Steps to reproduce:
1. Open the attached user's project "OculusFfrPp.zip"
2. Switch to Android
3. Make sure OculusXR plugin is using version 4.3.0-pre.1
4. Make sure Graphics API is Vulkan
5. Build to Quest 2/3
6. Observe that the Left/Right Eye renders 1/4 of the Screen
Expected results: Both eyes fully render the screen regardless of Graphics API and OculuXR version
Actual results: Only 1/4 of the Screen is rendered on Left/Right eye when building to Quest 2/3 device using OculusXR 4.3.0-pre.1 with Vulkan
Reproducible with: OculusXR 4.3.0-pre.1 (2021.3.43f1, 2022.3.45f1, 6000.0.18f1)
Not reproducible with: OculusXR 4.2.0 (2021.3.43f1, 2022.3.45f1, 6000.0.18f1)
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 12
Testing Environment: Windows 11
Not reproducible on: no other environment tested
Notes:
-Issue reproduces with Multi-Pass and Multiview Rendering Modes
-Issue only reproduces with Vulkan Graphics API
-See attached "Results.png"
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note (fix version 4.3.0-pre.1):
This issue is resolved in Unity 6000.0.20f1.