Search Issue Tracker
Not Reproducible
Votes
1
Found in
6000.0.46f1
Issue ID
UUM-102876
Regression
No
[OculusXR][OpenGLES] GL_INVALID_OPERATION errors on Quest Development Builds when Multiview is selected
Steps to reproduce:
1. Open the attached user's project "OpenGLESURPRendereringIssue.zip"
2. Go to Project Settings > XR Plugin Management > Oculus and confirm that the Stereo Rendering Mode is set to Multiview.
3. Go to Project Settings > Player > Other Settings and check that OpenGLES 3 is the target API
4. Open the Build Profiles window and enable Development Build for Android
5. Build and run for Quest 2/3
Expected results: no errors are spammed
Actual results: GL_INVALID_OPERATION errors are spammed on Quest Development Builds when Multiview is selected with OpenGLES Graphics API
Reproducible: OculusXR 4.4.0 (6000.0.33f1)
Could not test on 2021.3.47f1 and 2022.3.55f1 due to "java.lang.RuntimeException: Unable to instantiate activity ComponentInfo" Exception
Could not test on 6000.1.0b1 due to an exception being spammed every frame preventing from building a APK "FormatException: Input string was not in a correct format. System.Number.ThrowOverflowOrFormatException" > {color:#00875a}Fixed, project provided in comments {color}([~animesh.jha] )
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 23H2
Not reproducible on: no other environment tested
Notes:
-Issue only reproduces with OculusXR Plugin
-That error usually happens on VR when a shader doesn’t support Multiview. However, this is happening with the default shaders, which already have Multiview support
-Issue only reproduces on OpenGLES
-Issue only happens in Development Builds
-This error "Error Unity OPENGL NATIVE PLUG-IN ERROR: GL_INVALID_OPERATION: Operation illegal in current state" causes FPS drops, and it makes debugging and profiling more challenging
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
No longer able to repro on 6.0, 6.2 and 6.3