Search Issue Tracker
Won't Fix
Votes
5
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b5
Issue ID
UUM-30269
Regression
No
[Quest 2] Significant performance difference between Vulkan and OpenGLES3 when built with ECS
Reproduction steps:
1. Open the attached project “ReproProject"
2. Install the OVRmetric tool from Meta Developer Hub on Quest 2 device
3. On Quest 2 go to the library and enable the OVRmetric tool
4. Go to File > Build Settings > Player Settings and change Graphics APIs to OpenGLES3
5. Build And Run the project on Oculus Quest 2 device
6. Wait for the Scene to switch in Player and observe the FPS
7. Change Graphics API to Vulkan
8. Repeat steps 5 and 6
Expected result: FPS with Vulkan is about the same as with OpenGLES3
Actual result: FPS is lower with Vulkan
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b5
Could not test with: 2023.2.0a4 (Crashes with a single line of Stacktrace “0x00007FFF5B984FD9 (KERNELBASE) RaiseException“ when building the project with Vulkan on 2023.2.0a4)
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Notes:
* Player built with 2022.2.9f1, ECS 1.0.0-pre.44 and OpenGLES3 shows 72 FPS and only 50 FPS when built with Vulkan
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
- TreeView drag and drop operation is not cancelled when a modal opens over it
- Remote Config window causes performance drop in Editor when multiple settings are added
- Property field override bar does not update transparency correctly when switching between valid and invalid GameObjects
- Project window selection is not updated when search term is changed
- Error when adding valid MonoBehaviour script to Prefab in Project window
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. 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.