Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.3.53f1
6000.0.28f1
6000.1.0a5
6000.2.0a1
Issue ID
UUM-88913
Regression
No
Editor's GPU usage is higher when testing new HDRP project with a newer version of Editor
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/OutdoorsScene.unity” Scene
3. Enter the Play Mode
4. Open Task Manager on Windows
5. Observe the GPU usage of the Editor
Expected result: GPU usage is less or equal compared to the 2023.2.20f1 version
Actual result: GPU usage is more than in 2023.2.20f1
Reproducible with: 2022.3.53f1, 6000.0.28f1, 6000.1.0a5
Reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproducible with Post-Processing and Always Refresh off
- GPU usage is the same when the Editor is not focused which is not reproducible with 2023.2.20f1
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
- Unable to bind RenderTexture to the VisualElement's StyleBackground property
- SVG fails to import when 'stroke-miterlimit' is less than 1
- Test Runner fails to create a script in the active path when selecting a file as the active path
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
Resolution Note:
Thank you very much for bringing this issue to our attention and for helping us improve our software.
After thoroughly reviewing your report and testing on multiple devices, we were unable to reproduce the problem. As a result, we will be closing this bug for now. However, if you continue to experience this issue or have any additional information—such as specific steps, screenshots, or device details—please don’t hesitate to reach out. We’re always happy to investigate further.
We appreciate your understanding and your valuable feedback.