yes, this is not related to vsync.It could be related to v-sync, have you tried turning it on/off and seeing if it affects the FPS?
No, other people has same issue. Just try to reproduce it. It is very simple to reproduce (in case you have Windows 10 2004)Can it be related to your monitor? Like your monitor is 60Hz or something?
I have 1509 or something as I remember correct. And if a such bug happens I rather not update it to 2004 then.No, other people has same issue. Just try to reproduce it. It is very simple to reproduce (in case you have Windows 10 2004)
1909 is the current latest build available for most people, likely you're on that, same as me.I have 1509 or something as I remember correct. And if a such bug happens I rather not update it to 2004 then.
If you think you have found a bug, stating it on the forums is no use at all as this is a community run forum and YYG don't take bug reports from here. You would need to report it through the official channels.There is nothing to say more, really. Please, fix this critical bug.
Tech support is for getting help from the community with the software, not for reporting bugs. If you had come trying to simply see if others were having the same issue(trying to confirm if it is actually a bug, or just user error), then that wouldn't have been an issue. But just stating that something is a bug and asking for it to be fixed...that doesn't really belong here.Okay for some reason i thought that the Tech Support forum intended for this. Bug report is sended.
Most likely it is not a bug (at least not in GMS) and just a driver issue. There have been many complaints about 2004 and fps issues across many games.Okay for some reason i thought that the Tech Support forum intended for this. Bug report is sended.
I had not upgraded to 2004 yet, so I just did and I can confirm my fps for GM apps was stuck at 64 fps.Just try to reproduce it. It is very simple to reproduce (in case you have Windows 10 2004)
Also turning off some apps like Steam helps. It seems like YoYoGames doesn't want even recognize it as bug...I have the same issue as well after I update my Windows 10 to version 2004, and it's on GMS1.4 as well.
View attachment 34233
Room speed set to 60 but frame rate is less than 50FPS when using the Intel GPU. Only when forcing the game to use the Nvidia GPU that the game runs at 60FPS. Well, when on battery power only (I use a laptop), because the game uses the Intel GPU while charging even when the game is set to use the Nvidia GPU.
I suspect it has got to do with the newest Windows 10 version. My Nvidia GPU (GTX1050) driver version is also 451.67, and Intel GPU (HD Graphics 630) driver version is 22.20.16.4836.
It seems like YoYoGames doesn't want even recognize it as bug...
Issue raised and forgotten, this has been plaguing GM games earlier than 2018. One of the games I worked on had a terrible launch experience due to it making people return it and bombard it with low ratings... https://steamcommunity.com/app/356650/discussions/0/1743343017633405081/
Issue raised and forgotten, this has been plaguing GM games earlier than 2018. One of the games I worked on had a terrible launch experience due to it making people return it and bombard it with low ratings... https://steamcommunity.com/app/356650/discussions/0/1743343017633405081/
lmaoView attachment 34651
View attachment 34652
Not really "raised and forgotten" since 2018 if the bug report leading to this was submitted (by me) this year and the last update was barely two weeks ago. I'm just as frustrated with this bug as you are. I have several GM games I've bought on Steam that I can't play properly because they run at 50FPS instead of the 60 they should. I've been checking the bug report weekly. That said, they are actively working on fixing it. There's no need for misinformed hyperbolics.
I wasn't calling you out for being critical. That's perfectly reasonable and frankly, warranted. It's unacceptable that this has been going on for so long across several versions of GM and YYG needs to get off their butts and fix this issue.lmao
You should search around the BT yourself and maybe take your own advice before ironically being the misinformed one yourself. This isn't some issue only raised recently, hell I've given you a link from 2018 so you can stay lazy but I guess that wasn't enough. Efforts have been made to fix the issue during 2018 but apparently it never was completely fixed (hence was forgotten and here we are), before that the response was "cannot fully reproduce due to varying hardware, will keep an eye on lul". We were in the process of reporting the bug ourselves before we were pointed to the existing report and asked to be patient. I'm sure it's easy for a hobbyist to call this hyperbolic but I assure you it's a much scarier endeavor in face of a commercial release.
View attachment 34656
https://bugs.yoyogames.com/view.php?id=29146
But yeah, f*ck me for being critical
EDIT: Formatting.
If you have this issue, submit a bug report. Nothing else will help, least of all preaching to the choir.If you think you have found a bug, stating it on the forums is no use at all as this is a community run forum and YYG don't take bug reports from here. You would need to report it through the official channels.
This is simply laughable considering it's me who pointed out these issues are persisting for over 2 years now and you on the contrary keep saying it's continuously been worked on basing it on your personal report in late 2020 and fully ignoring the 2 and a half year gap in-between...nacho_chicken said:I was calling you out for spreading misinformation. You said it's been forgotten; that they're not currently working on it. They are, even if they're not treating it as an issue as serious as it is. The most recent bug in the tracker for this issue is not the one you posted, but this one. In fact, the most recent update was added to reference that original bug report you listed. They're obviously receiving enough bug reports for this specific issue to reopen it.
So which is it?...It's unacceptable that this has been going on for so long across several versions of GM and YYG needs to get off their butts and fix this issue.
Color me skeptical. Reports exist and were filed to appropriate channels.I know it's a major issue that's been going on for years, because I've dealt with it for years. None of those matter unless those people also submitted bug reports:
Rest assured we tried, as I already mentioned we were quickly told to refer to the already existing reports - as we should and gladly did.If you have this issue, submit a bug report. Nothing else will help, least of all preaching to the choir.
Please do not put words in my mouth. All I said was that it's being worked on now. BTW, that isn't just "my personal report". I apologize if I made it seem that way earlier. More than half the stuff in there isn't even from me. It's multiple peoples' reports, merged into one issue on the tracker. There's nothing else I can add to this conversation that I haven't already said.you on the contrary keep saying it's continuously been worked on basing it on your personal report in late 2020 and fully ignoring the 2 and a half year gap in-between...