Search Issue Tracker
By Design
Votes
0
Found in
2022.3.55f1
6000.0.33f1
6000.1.0b1
Issue ID
UUM-91847
Regression
Yes
Low FPS in the Game View when the Editor window loses focus
Reproduction steps:
1. Create a new 3D project
2. Enter the Play Mode
3. Enable the “Stats” Overlay in the Game View
4. Unfocus from the Editor window
5. Observe the Game View FPS
Expected result: FPS remain the same as when the Editor window is focused
Actual result: Game View averages around 5 to 10 FPS
Reproducible with: 2022.3.54f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Not reproducible with: 2021.3.45f1, 2022.3.53f1
Reproducible on: Ubuntu 24.04, Arch Linux (user)
Not reproducible on: No other environments tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After investigating, this is by design. Recently, there was a change to make the Editor throttle when the app is deactivated, even if the game is running. This is to conserve resources for other activities on the computer.
This change also was to make the behavior standard with macOS and Windows which drop frame rates even more than on Linux with this update.
There is no setting to reduce the throttling in the Editor, but if you need the game to run at full speed in the background for whatever reason, you can build a standalone player and run that way unhindered.