Search Issue Tracker
Duplicate
Votes
2
Found in
2022.3.63f1
6000.0.51f1
6000.1.9f1
6000.2.0b7
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-109934
Regression
No
Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
Reproduction steps:
1. Open the attached “IN-105806.zip” project
2. Make sure a Secondary Display is connected to the PC
3. Build and Run the project for Windows Standalone (File > Build and Run)
4. Open the Player on the Main Display and observe the FPS
5. Press A or D on the keyboard to move the Cube and observe its movement
6. Move the Player to the Secondary Display and observe the FPS
7. Press A or D on the keyboard to move the Cube and observe its movement
Expected result: FPS is ~15, and Cube movement on both displays is similar
Actual result: On the Secondary Display, the FPS is at 61 (similar to display refresh rate), and the Cube movement is smoother
Reproducible with: 2022.1.0a1, 2022.3.63f1, 6000.0.51f1, 6000.1.9f1, 6000.2.0b7, 6000.3.0a1
Reproducible on: Windows 11 Pro (23H2), Windows 11 Pro (24H2)
Not reproducible on: Windows 10 Pro (22H2) + NVIDIA GeForce GTX 680 (Driver version: 475.14)
Notes:
- Alt+Enter to enter full-screen mode can fix the issue, but if you return to windowed mode, the issue reproduces again
- Reproduces on both DX11 and DX12, but not on Vulkan
- The script sets QualitySettings.vSyncCount = 1 and limits the frame rate to ~15 FPS using Thread.Sleep
- More info in the Internal Notes
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fix broken IDXGISwapChain::GetFrameStatistics with cpu-side time sampling
Duplicate of another internal issue: UUM-107892: IDXGISwapChain::GetFrameStatistics reports broken values