Search Issue Tracker
Fixed in 2021.1/staging
Votes
1
Found in [Package]
11.0.0
Issue ID
1312513
Regression
Yes
[OpenXR][SteamVR][URP] Performance regression when using URP 11+
Reproduction steps:
- Open the reproduction project 1312513Repro.zip (attached in a comment below)
- Open the "TestScene" scene
- Enter Play mode
- In the Game window observe FPS count.
Expected result: FPS count between URP versions remains consistent or better on average
Actual result: FPS count dropped 0.5 - 3 times (see "FLxlOCnCYX.mp4" video)
Reproducible with: URP 11.0.0, 12.0.0 (2021.1.0a10, 2021.1.0b6, 2021.2.0a4)
Not reproducible with: URP 7.5.2, 8.3.1, 10.3.1 (2019.4.20f1, 2020.2.4f1, 2021.1.0a9)
Could not test with: 2018.4.31f1 (XR SDK not available)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
GCCooper
May 09, 2022 22:06
Not sure something should be marked as "fixed" if it still hasn't made it to production in over a year.
PrateekP
Nov 24, 2021 06:59
We are still facing the issue with unity version 2019.4.26f1 and the tried URP version 7.6.0 and 7.5.2. This is with Vive Cosmos VR build.
Rib
Jun 29, 2021 18:19
For reference I got further context for this issue from here: https://forum.unity.com/threads/quest-urp-performance-degradation-form-unity-2019-4-to-unity-2020-2.1075897/
Rib
Jun 29, 2021 18:18
Hi, I think this issue is blocking a number of developers, including us, from being able to switch from Unity 2019.4 to Unity 2020.3 LTS. We first saw this bug back in in February when it was filed and decided to push back our migration to Unity 2020 and now we've found from testing that there still seems to be the same URP performance regression (at least especially noticeable on the Oculus Quest for us)
Is there any plan for the fix to be back ported to Unity 2020.3 LTS please?
I'm currently testing with 2020.3.12f and URP 10.5.0
GCCooper
May 19, 2021 22:28
I'm encountering this on 2020.3.8f1, using URP 10.5.0