Search Issue Tracker
Fixed
Fixed in 2023.2.0a9
Votes
1
Found in
2022.3.2f1
2023.1.11f1
2023.2.0b7
Issue ID
UUM-42267
Regression
No
Play Mode's performance spikes regularly when AssetDatabase.Contains() is called on a specific HDRP project
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/Flight.unity” Scene
3. Enter the Play Mode
4. Use WASD keys on a keyboard to move the character
5. Observe the Game View and the Statistics tab
Expected result: The Play Mode runs with a smooth framerate with no spikes in the framerate
Actual result: The Play Mode stutters and there are significant spikes in the framerate
Reproducible with: 2022.3.2f1
Reproducible on: Windows 10
Looks like it is not reproducible on Mac.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2023.2.0a9):
This issue is happening because HDRP calls AssetDatabase.Contains() in it. This call has been removed in 2023.2 and future, so issue is fixed since 2023.2.
Unfortunately we can't backport that fix to 2023.1 and 2022.3, so AssetDatabase.Contains() will continue to be called on those versions. But internally we were unable to reproduce the issue that AssetDatabase.Contains() takes long, for us it was very fast on both Windows and Mac. We tend to think that it is something related to user's machine/setup.