Search Issue Tracker
By Design
Votes
1
Found in
2019.1.0a9
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1151652
Regression
Yes
Frame rate locks to 30 fps if Windows multiple displays option is set to "Duplicate these displays"
Steps to repro:
1. Open original project "FPS_test.zip"
2. Build and Run and open it in Fullscreen
3. Observe the Frame rate
4. Close the Build, change the Windows multiple displays option to "Duplicate these displays"
5. Open the built game again in Fullscreen mode
Expected result: Frame rate should be similar to step 3.
Actual result: Frame rate locks at 30fps.
Reproduced in: 2019.1.2f1, 2019.2.0a14, 2019.3.0a2
Not reproduced in: 2018.4.0f1, 2019.1.0a8
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.3.X):
as of 2019.1 Unity moved to use Flip Model SwapChain as default, the issue is due to this model forcing GPU to wait. There is a player settings option under resolution "Use DXGI Flip Model Swapchain for D3D11". if it is unchecked Unity would use the Windows 7 style Blt Model Swapchain where the issue does not happen. .