Search Issue Tracker
Won't Fix
Votes
12
Found in
6000.0.46f1
Issue ID
UUM-102878
Regression
No
[OculusXR][GLES][BiRP] Android external OES texture does not render when Oculus Low Overhead Mode (GLES) is enabled in non-development builds
Steps to reproduce:
1. Open the attached user's project "ExternalImageLowOverheadMode.zip"
2. Make sure that Graphics API is set to OpenGLES3
3. Make sure that Low Overhead Mode is enabled in OculusXR Plugin settings
4. Build to Quest 2/3
5. Observe the black quad texture
Expected results: OES texture renders when Oculus Low Overhead Mode (GLES) is enabled in release builds
Actual results: OES texture does not render when Oculus Low Overhead Mode (GLES) is enabled in release builds
Reproducible with: OculusXR 4.3.0 (2021.3.44f1, 2022.3.49f1, 6000.0.22f1)
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
Notes:
-Issue reproduces with MultiView and Multi-pass
-Issue only reproduces with OpenGLES3
-Issue only reproduces when Low Overhead Mode is enabled and Development build disabled
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
- Shader Graph template titles blink and render incorrectly in “Create New Shader Graph Asset” window
- Profiler Captures List foldouts do not open when clicked on the foldout title
- Profiler Captures List date title is not centered vertically
- ShaderGraph template titles intermittently disappear after hover interaction
- Text is pushed outside of the text box when creating a new Colors library in the Color Picker and entering the long string
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. The documentation states that if you hit graphical issues in Low Overhead Mode, please turn it off. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.