Search Issue Tracker
Fixed
Fixed in 2022.3.11f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a2
Votes
186
Found in
2020.3.47f1
2021.3.22f1
2022.2.15f1
2022.3.7f1
2023.1.0b12
2023.2.0a10
Issue ID
UUM-33025
Regression
No
[URP][XR] Performance degradation when comparing Android Quest 2 builds across 2020.3 and 2023.x
Steps to reproduce:
1. Open the attached user's project "PerfTest2020.zip"
2. Build the project to Quest 2 in 2020.3.47f1
3. Observe performance via OVRMetrics (GPU usage and stalled frames)
4. Build the project in 2023.1.0b12
5. Observe performance via OVRMetrics (GPU usage and stalled frames)
Expected results: performance is mostly the same across Unity versions on a Quest 2 with the same Scenes
Actual Results: performance degrades when building to Quest 2 in 2022.2 and above
Reproducible with: URP 10.10.1 - 16.0.1 (2020.3.47f1, 2021.3.22f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a10)
Reproducible with these devices:
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
User devices:
Pico 4
Environment: Windows 10 22H2
Notes:
-Testing results are attached "IN-31610 performance results"
-Tested with OpenXR and OculusXR XR plugins, using different Render Modes, OpenGLES3 and Vulkan
Comments (31)
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] ArcCone Direction computation is wrong in Base Mode
- [Android] [Galaxy Tab] A singular Pen touch logs a Pen touch event and a singular finger touch event when logged using "VisualElement.RegisterCallback" with "Pointer(Up/Down)Event"
- Crash on D3D12DescriptorCache::Deallocate or vkGetInstanceProcAddr when loading RenderDoc in a specific Scene
- [HDRP] Lit material preview is rendered incorrectly with a mask map
- The "LerpWhiteTo" missing function displays an error when the Shadows.hlsl shader is included in a Shader file
HECer
Apr 18, 2024 16:37
is this fixed?
Did someone check the result in the newer versions?
DevDunk
Jan 19, 2024 15:00
Gotta keep saying this, if you have a project with regressions in performance after checking URP/project settings, make a bug report!
Conor_Envision
Oct 25, 2023 21:31
I agree it is not fixed
Thomas_VRML
Oct 21, 2023 14:27
I need to double-down on what 'AvatarJoe' just commented. When building and running our project on Quest 2 using Unity 2021.3.17f1 & 2021.3.28f1 with Oculus legacy backend, the performance is way better than with OpenXR and latest Unity 2022.3.11f1. We already tested Unity 2022.3.8f1, 2022.3.9f1, 2022.3.10f1 and now 2022.3.11f1 and cannot feel any improvement with 2022.3.11f1 when it comes to CPU load.
AvatarJoe
Oct 19, 2023 05:24
After migrating the project from Unity 2021.3.14f1, I can confirm that it is not "Fixed" in Unity 2022.3.11f1. Although the OVRMetrics are giving me the same average fps and stale frame rates, it seems to be exhibiting worse performance in regards to the CPU. Disappointed in these results after the initial excitement. Just had to order the Quest 3.
unity_pro_playkot_12
Sep 22, 2023 16:42
This bug is not fixed in 2023
please, Unity, fix
DevDunk
Sep 14, 2023 06:33
According to my (I am the one submitting this issue) most recent tests, performance between 2020 and 2023 is within a few %. You do need to tweak the URP settings if you upgrade, but this is good news.
This means that if you have a performance issue, file a bug report!
GamerTobbe
Sep 10, 2023 11:39
have this issue been fixed? Unity is really bad on fixed-release notes atm.
DevDunk
Sep 03, 2023 09:51
Got new tests in, the situation seems to have massively improved: https://forum.unity.com/threads/2020-3-2023-3-urp-standalone-vr-performance.1487736/
DevDunk
Aug 08, 2023 08:46
If your project has performance regressions make bug reports!
I never tested in 2019, and you might use different features, so make reports so the issues can be fixed!
Just commenting here does not help that much