Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.6.X
Votes
0
Found in
2022.3.41f1
6000.0.68f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
6000.6.0a1
Issue ID
UUM-77946
Regression
No
[Quest] Player with Graphics.RenderMeshIndirect() renders with worse GPU performance when built with Vulkan compared to the OpenGLES3
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/IndirectScene.unity” Scene
3. Switch to Android Platform
4. Build and Run on Quest
5. Open Meta Quest Developer Hub
6. Open the Performance Analyzer tab
7. Enable Performance Analyzer
8. Observe that the Frame Rate is at 72
9. In Editor, add Vulkan Graphics API and remove OpenGLES3 (Edit > Project Settings > Player > Other Settings > Graphics API)
10. Repeat the 4 - 7 steps
Expected result: Frame Rate is constantly at 72
Actual result: Frame Rate gets below 60
Reproducible with: 2022.3.41f1
Could not test with: 2021.3.42f1, 6000.0.14f1 (Assets\Scripts\Indirect\LSRIndirectRenderer.cs(194,5): error CS0242: The operation in question is undefined on void pointers)
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Player crashes with 6000.0.14f1
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
The project is not compatible with Unity versions after 2022.3, so we cannot reproduce the performance problem.
We also think it's unlikely that the performance issue is caused by the engine.
Resolution Note (6000.6.X):
The project is not compatible with Unity versions after 2022.3, so we cannot reproduce the performance problem.
We also think it's unlikely that the performance issue is caused by the engine.