Search Issue Tracker
Duplicate
Votes
89
Found in
2021.3.8f1
2022.2.0b6
2023.1.0a6
Issue ID
UUM-13023
Regression
No
[Quest 2] 2022.2 is slower than 2021.3 when built on Quest 2
Reproduction steps:
1. Open Oculus Developer Hub, go to the Device Manager tab, and install OVR Metrics
2. Turn on Metrics Hud
3. Open the OVR Metrics tool on the Oculus device, and select “Basic” under Quick-set Enabled Stats
4. Open the user’s project
5. Build and run on the Oculus Quest device
6. Check GPU usage difference using OVR Metrics
Expected result: GPU usage difference is less than 5%
Actual result: GPU usage differs by more than 5%
Results:
version - GPU usage
2020.3.39f1 - 35%
2021.3.8f1 - 43%
2022.1.14f1 - 38%
2022.2.0b6 - 46%
2023.1.0a6 - 46%
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Reproduced on:
Windows 10 Pro 21H2
-
Resolution Note:
Thank you for reporting this issue. We are aware of it and have issued fixes which will appear in Unity 2021.3.9f1, 2022.2.0b7, and 2023.1.0a7. Public bug link is https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-9423
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-9423
-
DevDunk
Apr 12, 2023 09:14
There is a new big performance issue on the issue tracker. URP team is already made aware and reproduced it themselves (not just QA)
https://issuetracker.unity3d.com/issues/urp-xr-performance-degradation-when-comparing-android-quest-2-builds-across-2020-dot-3-and-2023-dot-xHere are some other smaller issues that are relevant to VR performance as well:
Input system optimizations performing worse in VR: https://issuetracker.unity3d.com/issues/input-system-enabling-both-optimization-options-of-input-system-reduces-performance-in-built-players
OculusXR performing worse than OpenXR: https://issuetracker.unity3d.com/issues/quest-2-oculusxr-has-worse-performance-than-openxr-when-built
Graphics Jobs not working on standalone VR: https://issuetracker.unity3d.com/issues/quest-2-build-crashes-on-quest-2-when-graphics-jobs-are-enabled -
NovakN523
Mar 28, 2023 06:36
However, it is not uncommon for software updates to have varying levels of performance depending on the device being used. Sometimes updates can result in improvements in performance, but in other cases, there may be new features or changes that may negatively impact performance on certain devices.
-
juan-jo
Jan 30, 2023 17:22
I too am still attached to the 2019.4 LTS version.
In my tests any later version has lower performance.It is not understandable or admissible that later versions of Unity have worse performance on the target platforms (Quest in this case, although they also occur in other areas) as this would be the main measure of Unity's improvement, which hurts the most developers and what makes it difficult for them to move to new versions of Unity and use the new features, and I think they are the main problem that Unity should address, above new features, and even bug fixes.
-
dclipca
Jan 18, 2023 08:47
Bump.
-
Cloudwalker_
Sep 28, 2022 18:06
-
AcidSheep
Sep 20, 2022 08:38
NOT FIXED. THE "DUPLICATE" IS ALSO NOT FIXED.
Tested this myself yesterday. The issue still persists!
Unity Editor and Builds are noticeably slower in 2022 & 2023. -
Cloudwalker_
Sep 17, 2022 18:52
not fixed...
-
Kabookie
Sep 08, 2022 15:46
Same as everyone else!
-
glenneroo
Sep 05, 2022 20:49
I thought I was going crazy the last 2 months why my perf dropped from 72+ fps to 45-50. I even went so far as to recreate my project multiple times, incrementally changing values back to the original, to no avail. Changing from OpenGL to Vulkan got me about 5-10 FPS increase, but still well under the required 72 I used to have.
I'm using 2021.3.8f1.
-
Extrys
Aug 30, 2022 13:59
I would put that this happens starting from 2020.2
where URP 10 was forced by default, introducing this performance drop
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
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
- [iOS] The safe area value changes when reopening the app in Landscape orientation
- Light flickering when using Forward+ on Mobile
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
This is a duplicate of issue #UUM-9423