Search Issue Tracker
Fixed in 14.0.2
Votes
0
Found in [Package]
10.1.0
Issue ID
1381103
Regression
Yes
[HDRP] Framerate drops when two Game views are rendered and "Allow Dynamic Resolution" is disabled for one of the Cameras
How to reproduce:
1. Open the attached project "resRepro"
2. Open the scene "reproScene" and enter Play mode (Assets/reproScene.unity)
3. Add a second Game view window (Right-click on the Game tab > Add Tab > Game)
4. In the second Game view's Control Bar, set the Display to "Display 2"
5. Drag out the second Game view window as a standalone window and minimize it
6. In the first Game view, inspect the FPS being displayed
7. In the Hierarchy window, select the GameObject "Camera 1"
8. In the Inspector window, disable the Camera component's "Allow Dynamic Resolution" Rendering property
9. In the first Game view, inspect the FPS being displayed
Expected result: Framerate doesn't change
Actual result: Framerate drops by 40%
Reproducible with: 10.1.0 (2020.2.0b8), 10.7.0 (2020.3.23f1), 12.1.1 (2021.2.4f1), 13.1.1 (2022.1.0a16)
Not reproducible with: 7.7.1 (2019.4.33f1), 10.0.0-preview.27 (2020.2.0b8)
Note: The issue is not reproducible when setting the Dynamic Resolution type to "Software" in the HD Render Pipeline Asset
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
- Crash on SerializedProperty:CopyInternalImpl when clicking on a specific Asset
- Crash on BurstCompilerService::CompileAsync when opening a specific project
- [Android] Particles aren't rendered when the shader "Particle/Standard Unlit" or "Particles/Standard Surface" is used on a Material
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
Resolution Note (fix version 14.0.2):
Fixed in: 14.0.2 (2022.2.0a9)