View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0031655 | Runner | General | Public | 2020-03-04 15:55 | 2020-03-05 09:34 |
| Reporter | Patrick Roche | Assigned To | Mike Rennie | ||
| Priority | Medium | Severity | C - General | Reproducibility | Unable To Reproduce |
| Status | Assigned | Resolution | Open | ||
| Platform | Windows | OS | 10 | OS Version | |
| Product Version | 2.2.5 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0031655: Performance: Users still report using a game speed lower than their monitor's max refresh rate causes inconsistent frame times | ||||
| Description | Users still report using a game speed lower than their monitor's max refresh rate using game_set_speed(60, fps) causes inconsistent frame times and concern that their game will not run reliably on other people's systems. One user reports that on a 144Hz monitor, with game speed also set to 144 the game will run as intended, but when the game speed is capped at 60 their game will run at 50 FPS and capping the game speed to 30 will result in 25 FPS. Please see Issue 1.jpg for details, and Issue 1 Sample.yyz for a sample. Adding a string that prints fps_real() returns a smooth 1410 FPS, but still 50 FPS is displayed. One user is reporting that the move to the latest 2.2.5 runtime caused frame pacing issues. They have been able to reproduce it with a 50/50 chance, and using alt+tab to leave fullscreen mode seems to be a stop-gap cure for the issue. When unlocked, the value shown in their project shows roughly 500 FPS, but when capped at 60 FPS, frame times can become very uneven. For example: outgame | Step 2 | 0.01414700 outgame | Step 2 | 0.01887100 outgame | Step 2 | 0.01426000 outgame | Step 2 | 0.01943000 Two frame times are adding up to roughly 0.032s which should be close to 60 FPS but they are reporting that character movement seems extremely jagged. | ||||
| Steps To Reproduce | We've been unable to reproduce this internally, due to non-suitable hardware, but there've been enough issues raised for it to be a cause for further investigation by CT. | ||||
| Additional Information | Some of the behaviour mentioned in here is very similar to behaviour shown in https://bugs.yoyogames.com/view.php?id=29146#bugnotes | ||||
| Tags | No tags attached. | ||||
| 1.4 Found In | |||||
| 2.x Runtime Found In | |||||
| 2.x Runtime Verified In | |||||