View Issue Details

IDProjectCategoryView StatusLast Update
0028219RunnerFunctionsPublic2018-09-11 16:51
ReporterStewart BishopAssigned ToMike Rennie 
PriorityLowSeverityB - MajorReproducibility<25%
Status ResolvedResolutionFixed 
Product Version 
Target VersionFixed in Version 
Summary0028219: Functions: [GMS2] FPS not being set correctly when using 'game_set_speed' and 'draw_enable_drawevent'
DescriptionThe 'game_set_speed' function does not work properly when using 'draw_enable_drawevent' to implement frame skipping, setting the fps to a very high number like '20,000'. To me it seems like it is setting the fps to as high as it can possibly go. I've tested 3 different fps settings with game_set_speed (60, 24, and 500 fps), out of those 3, only setting it to 60 causes the fps to go out of control. This happens when using the 'gamespeed_microseconds' parameter as well. This bug affects both the YYC and VM.

This doesn't seem intentional, and it never happened in previous runtime versions of GMS2. I'm aware that changes have been made to VSync functionality in GMS2, maybe its related to that?
Steps To ReproduceTo reproduce the bug, follow the steps below:
    
1) Start the game. Note that fps of the game starts at 60 by using game_set_speed in the create event, but seems to work correctly there.
EDIT: Actually with some more testing, the fps can sometimes be slightly higher than 60.
    
2) Now use the arrow keys to change the fps with game_set_speed (left (60), down (24), right (500) by default). Start by setting the fps to something other than 60.

3) Now set the fps back to 60, notice how large the fps number is, surely this is not working correctly. Changing back to the other fps settings doesn't show this bug.
TagsNo tags attached.
1.4 Found In
2.x Runtime Found In2.1.2.172
2.x Runtime Verified In

Activities

Stewart Bishop

2017-11-06 10:17

Adminstrator  

Room_Speed_FPS_Bug.yyz (16,423 bytes)