Search Issue Tracker
By Design
Votes
1
Found in
2020.2.0a15
2020.2.3f1
2021.1
2021.2
Issue ID
1315581
Regression
Yes
The FPS decreases by half in Play Mode when there is Scene view and Game view open in the Editor
How to reproduce:
1. Open a new project
2. Make sure there is Scene view and Game view visible in the Editor
3. Check the "Maximize On Play" in the Game view
4. Enter Play Mode and observe the FPS in the Statistics window
5. Uncheck the "Maximize On Play" in the Game view
6. Enter Play Mode and observe the FPS in the Statistics window
Expected result: FPS is the same with Both views visible
Actual result: FPS decreases by half when both Scene view and Game view are visible
Reproducible with: 2020.2.0a15, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Not reproducible with: 2018.4.35f1, 2019.4.26f1, 2020.2.0a14
Comments (1)
-
YamyStudio
Jan 12, 2022 10:56
I don't understand 2021.2.7f has still this issue and not resolved.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (2021.2.X):
The FPS decrease when multiple views are rendering is a expected behavior. It might be more noticeable now that the FPS stats have been updated but was always there and is normal (rendering needs to be done twice). See details in ticket notes.