Search Issue Tracker
Duplicate
Duplicate in 2019.4.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2021.2.0a13
2022.1
2022.2
Issue ID
1404328
Regression
Yes
[M1] Editor FPS drops significantly when moving Editor window to the second monitor
Reproduction steps:
1. Create a new project
2. Enter play mode and turn on "Stats" window
3. Observe FPS
4. Move the Editor window to the second monitor and observe FPS
Expected result: FPS is the same
Actual result: FPS on the second monitor is lower than on the main MBP monitor
Reproducible with: 2019.4.36f1, 2021.2.0a13, 2021.2.14f1, 2022.1.0b9, 2022.2.0a6
Not reproducible with: 2020.3.30f1
Note: Reproducible with ProMotion turned on and VSync turned off
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
This is a duplicate of issue #1383448