Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.14f1
2020.3
2021.1
2021.2
Issue ID
1333735
Regression
No
[XR][Quest][Multiview] Errors spammed in device's log: OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_OPERATION
Repro steps:
1. Open the attached project "OESTextureBug"
2. Build and Run on Quest
3. Observe the logcat
Expected: No errors are thrown
Actual: Errors are spammed
Reproducible with: 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a17
Notes:
- Doesn't reproduce on MultiPass
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
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Resolution Note (2021.2.X):
The cause of the GL_INVALID_OPERATION is a shader that is not multiview-aware being used with a multiview framebuffer. In multiview, the vertex shader needs to be aware of which eye is rendering to as well as the number of views. Refer to unity's docummentation to find how to adapt your shaders to multiviewa and single-pass stereo: https://docs.unity3d.com/Manual/SinglePassStereoRendering.html