Search Issue Tracker
By Design
Votes
0
Found in [Package]
13.1.0
Issue ID
1376333
Regression
No
Huge performance spike when switching Camera from Physical Sky to HDRI Sky and back to same Physical Sky
How to reproduce:
1. Open the user's "TerrainBeach" project
2. Select "File -> Build and Run"
3. Observe the performance graph on the right in the built project
Expected result: No noticeable performance spike when HDRP Cameras switches
Actual result: Huge performance spike occurs when HDRP Cameras switches
Reproducible with: 7.7.1 (2019.4.32f1), 10.7.0 (2020.3.22f1), 11.0.0 (2021.1.28f1), 12.1.0 (2021.2.1f1), 13.1.0 (2022.1.0a13)
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
- Compiled Shader code has self-assignments and redundant code in the Shaders that use "enable_d3d11_debug_symbols"
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
Resolution Note:
The performance spike comes from PBR Sky needing a few frame to warmup after switching to it from HDRI sky.
A few suggestion were made to help with the issue:
- Reduce the number of bounces to avoid too much precomputation
- Have the camera be persistent (using hasPersistentHistory on the HDAdditionalCameraData) so that it retains precomputation for the PBR sky
However, it was found in this particular case that only one camera was used with different settings so making it persistent would not help with that kind of setup so reducing the number of bounce is the only solution here (apart from using 2 different persistent cameras)