Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
10.0.0-preview.27
Issue ID
1310239
Regression
Yes
Performance drop in empty Scene when project is built with HDRP
How to reproduce:
1. Open a new HDRP project
2. Create and open a new Scene
3. Disable VSync in the Quality Settings
4. Go to File -> Build Settings
5. Add the newly created Scene in the Build Settings
6. Press "Build And Run"
7. Observe the FPS in the Build with any FPS counter software
Expected result: 550~ FPS in the Build
Actual result: 350~ FPS in the Build
Reproducible with: 2020.2.0b5 (10.0.0-preview.27), 2020.3.2f1 (10.4.0), 2021.1.2f1 (11.0.0), 2021.2.0a12 (12.0.0)
Not reproducible with: 2019.4.24f1 (7.5.3), 2020.2.0b5 (9.0.0-preview.71)
Comments (1)
-
james_work
Jun 02, 2021 05:13
Reported as a bug via the bug-reporter [1331167], reproduced with 2020.3.3f1.
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note:
This appears to be due to the over head of RenderGraph.
In 10.x.x you can still disable rendergraph in HDRP Default Settings and most of the difference you are experiencing should be mitigated. In the longer run we are already aware we need to optimize its overhead and the task is planned.