Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
41
Found in
2019.3.0b11
2019.4
2019.4.19f1
2020.3
2021.1
2021.2
Issue ID
1327408
Regression
No
Performance in Game View is significantly impacted by Gfx.WaitForPresentOnGfxThread when a second monitor is connected
How to reproduce:
1. Create a new project using the default 3D template
2. Open the Profiler (Window->Analysis->Profiler)
3. Enter the Play Mode
4. Inspect the performance
5. Plug in a second monitor
6. Inspect the performance again
Expected result: Performance is not heavily affected when plugging in a second monitor
Actual result: Performance is heavily affected when plugging in a second monitor
Reproducible with: 2019.3.0b11, 2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a13
Not reproducible with: 2018.4.34f1, 2019.2.21f1, 2019.3.0b10
Tested on: macOS Catalina 10.15.7 with Radeon Pro 580 8 GB
-
Ijin
Oct 25, 2021 11:19
With 2020.3.19f1 update it broke editor performance on single-monitor setups. Tested on Mac mini (2018), Big Sur and iMac (Late 2014), Big Sur.
-
mellofelipe
Sep 21, 2021 10:16
Hi, I was the one that reported the bug. Is there any plan to do a fix for 2019 LTS as well?
-
JohnnyFactor
Aug 17, 2021 22:32
I found this too but only when the Unity window was maximized to fill a monitor or crossed the boundary between the two monitors.
-
justdizzy
Jun 25, 2021 02:10
[Unity 2020.3.8 & x.12] I just ran in to this, and in trying to find the issue, I stumbled upon that the FPS was matching my 2nd monitor's refresh rate, so I think that somehow the Editor is getting VSync locked regardless of settings?
-
Beatriceol
Jun 22, 2021 08:01
When I click the mouse to switch focus, there may be a frame rate drop between Unity and the desktop or other applications. I don't know if it's the same problem as this.
-
MeadowGames
May 19, 2021 02:20
I am also having this issue. On windows 10 PC. GTX 1050 16GB ram. You can easily reproduce the bug in 2018.4.26f1 and 2020.3.4f1. Major FPS drop with a second monitor. I've been driving myself crazy trying to fix this without dev support.
-
JeffG
May 07, 2021 18:07
I went from 2020.1.17 ~60fps in Editor with 2 screens. Running 2020.3.5 now getting ~28 fps in Editor. Builds seem to be fine (back up to 60+)
-
loten
Apr 17, 2021 11:00
Does this affect builds as well?
-
oliviaark765
Apr 12, 2021 11:57
The same things happened to me when I was working for cryptoexchangesoftware.net/bitcoin-exchange-software/ and Did the same thing as you mentioned above It is the best possible solution for improving the response and performance
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a7
Play Mode performance while using Metal would occasionally spike while a second monitor was attached - this was not visible before 2019.3 due to a Profiler issue. This frame present delay is fixed with the change to use CVDisplayLink with Metal on OSX to time presents, so that additional monitors do not affect performance.
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b13
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.22f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.19f1