Search Issue Tracker
Feature Request
Votes
2
Found in
2021.3.37f1
2022.3.26f1
6000.0.0b16
Issue ID
UUM-70930
Regression
No
[OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Steps to reproduce:
1. Download the attached user's project "StereoZoom.zip"
2. Switch to Android platform
3. Build to Quest 2/3
4. Change your Quest's IPD value by adjusting the distance of the lenses
5. Observe the difference between having IPD set to the highest and lowest
Expected Results: Zooming in on the camera's URP opaque texture does not cause "double vision" on Quest with OpenGLES3 no matter what IPD is used
Actual Results: Zooming in on the camera's URP opaque texture causes "double vision" on Quest with OpenGLES3
Reproducible with: 2021.3.37f1, 2022.3.26f1, 6000.0.0b16
Reproducible on 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:
-Reproducible with OculusXR and OpenXR Plugins
-Reproducible only with OpenGLES3 Graphics API
-Reproducible with Multi-pass/Single Pass Instanced and Multiview
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
- Search: Inspector section icon is less sharp/more pixelated than other editor icons
- Search description string is always truncated
- [VFX] When Grouped Nodes are converted to Subgraph Operator resulting Graph Node is not included in the Group
- Search window icons are less sharp/more pixelated than other editor icons
- The Inspector can be covered when scaling the horizontal separator bar
Resolution Note:
Tested the demo project on Unity 6000.0.x.
It seems that the problem is not related to IPD but that on OpenGLES symmetric projection (find on Oculus plugin setting) is only available on Vulkan.
If you disable the feature on Vulkan API the same problem persist on bot Oculus and OpenXR plugin.
The asymmetry is by design but there are no shader nodes or global parameters that the user can query to have this information without, it's worth to request this as a new feature.
If you have any further questions, please don't hesitate to reach out!