Search Issue Tracker
Won't Fix
Under Consideration for 2020.3.X, 2021.3.X, 2022.1.X, 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.1.0b9
2023.2.0a7
Issue ID
UUM-30414
Regression
No
CPU timing increases up to 6x times when opening the Material Inspector for a Shader with [PerRendererData] attribute
How to reproduce:
1. Open the attached “IN-35464” project
2. Enter the Play Mode in the “SampleScene” Scene
3. Toggle on the “Stats” preview in the Game view
4. Record the CPU timing for Graphics
5. Select the “GameObject → Canvas → Image” GameObject in the Hierarchy
6. Click the drop-down under the Shader field in the Inspector
7. Record the CPU timing for Graphics
8. Compare the timing records of the 4th and 7th steps
Expected result: The timing difference shouldn’t be more than 1ms
Actual result: The timing difference is ~6x times
Reproducible with: 2020.3.46f1, 2021.3.16f1, 2022.2.11f1, 2023.1.0b9, 2023.2.0a7
Reproduced on: macOS 13.0 (Intel)
Edit 03/20/2023: although the initial description says it is MacOs only, the attached screenshots are using DX11 API, therefore it should also be reproducible on Windows.
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
- Lightmap "View" button is not symmetric and has an empty space
- Unable to abort when asynchronous loading a Scene
- Errors are thrown when clicking "Refresh Virtual Offset Debug"
- 2D Renderer Breaks When Animating Material Property with MaterialPropertyBlock
- PlayModeStateChange.ExitingPlayMode is not logged when Play Mode is exited due to recompilation
Resolution Note:
Thank you for reporting this issue. As we transition focus to UI Toolkit, we are no longer making improvements to IMGUI, including performance improvements.