Search Issue Tracker
Fixed in 12.0.0
Votes
0
Found in [Package]
2020.3
2020.3.9f1
2021.2
Issue ID
1417754
Regression
No
[Universal RP] ScriptableRenderPass.Configure method takes up to 20-80% of GPU resources when being in Play Mode
How to reproduce:
1. Open the attached "case_1417754" project
2. Enter the Play Mode in the "SampleScene" Scene
3. Open the "Window -> Analysis -> Profiler" window in the menu
4. Toggle on and select the "GPU Usage" Profiler Module
5. Search for "ScriptableRenderPass.Configure" method
Expected result: Total consumed GPU resources by the method isn't more than 0.5%
Actual result: Total consumed GPU resources by the method is 10-30%. Sometimes, taking up even to 80%
Reproducible with: 10.8.1 (2020.3.34f1), 11.0.0 (2021.2.0a3)
Not reproducible with: 12.0.0 (2021.2.0a4), 12.1.6 (2021.3.2f1), 13.1.8 (2022.1.0f1), 14.0.2 (2022.2.0a12)
Couldn't test with: 2019.4.38f1 (no ScriptableRenderPass.Configure method found or alternative function)
Note: In some versions, "Inl_ScriptableRenderPass.Configure" is returned in the search that is considered to be the method with the same functionalities, but inlined
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 12.0.0):
Fixed in 12.0.0 (2021.2.0a4)