Thread: unlimited frame rate option has been removed from the client on 5.0

This change has me pretty worried.... Not just the fact that uncapped framerate, which a large number of users use, will no longer be available, but the fact that the in-game limiter has historically been problematic for a very long time now is what concerns me the most.

For me, the in-game fps limiter causes unstable framerate AND frametimes (stuttering) which I've read is a common issue. Thus, setting FPS to unlimited is the only option which actually allows the game to run smoothly.

If square manages to fix the in-game limiter to be functional for people running on monitors higher than 60hz, then that's not so bad. Otherwise the game could very well end up being unplayable for users like myself....which sucks, alot. I really want to be able to enjoy the new expansion.

And to the few who are criticizing those of us who are concerned about this change with statements along the lines of "It doesn't affect me personally, so everyone else should stop making a big deal about it". Please don't do this. It's not cool to downplay the misfortune of others, no matter how trivial it may seem to you. For me personally, it's a matter of the game being playable or not. I don't care about having massive FPS for no reason - I care about having a stable, smooth frame-rate which this change could potentially threaten.

So are all the upset people here part of the bot cartels?

Originally Posted by RyuSaarva

So are all the upset people here part of the bot cartels?

Unlikely. More likely it's a bunch of people on a forum finding something to get riled up about 36 hours before they can just find out for themselves if this is a big deal or not.

The in game limiter is not just a limiter. I think I've read around that others believe it's also a vertical sync, potentially a triple buffer. I'm literally standing still in Rhalgr's @ 141-144 fps on my 165 hz monitor with no cap. I turn the cap to 1/1 at 165fps, what should you expect? If you thought 141-144 you're wrong. the frames immediately fall to 133-138. Let's try 1/2 @ 82 fps because I was getting over 100 fps, I should easily see 82 constantly. Nope, any where from 61 - 80 with just wild fluctuations up and down. So if they implement a 90fps max, I can just play at 60fps like the rest of you because that's what that setting will realistically do. It's broken and anyone who thinks otherwise needs a reality check. Just because it "works for you" doesn't mean it "works as intended".

While I only talked about frame rate above, there are huge stuttering issues that I didn't even touch on. Frame stutter is the REAL reason most of us are concerned, not "mah frames". Yea we're getting riled up before we can test it, but do we have any reason to believe that the engine is any different what so ever? It's likely the exact same frame rate limiter that we've had since 2.0, they're not going to magically change it now. But we'll see who's right in 2 days.

Originally Posted by KrystalRaina

The in game limiter is not just a limiter. I think I've read around that others believe it's also a vertical sync, potentially a triple buffer. I'm literally standing still in Rhalgr's @ 141-144 fps on my 165 hz monitor with no cap. I turn the cap to 1/1 at 165fps, what should you expect? If you thought 141-144 you're wrong. the frames immediately fall to 133-138. Let's try 1/2 @ 82 fps because I was getting over 100 fps, I should easily see 82 constantly. Nope, any where from 61 - 80 with just wild fluctuations up and down. So if they implement a 90fps max, I can just play at 60fps like the rest of you because that's what that setting will realistically do. It's broken and anyone who thinks otherwise needs a reality check. Just because it "works for you" doesn't mean it "works as intended".

While I only talked about frame rate above, there are huge stuttering issues that I didn't even touch on. Frame stutter is the REAL reason most of us are concerned, not "mah frames". Yea we're getting riled up before we can test it, but do we have any reason to believe that the engine is any different what so ever? It's likely the exact same frame rate limiter that we've had since 2.0, they're not going to magically change it now. But we'll see who's right in 2 days.

Out of curiosity, are you running fullscreen or fullscreen windowed, and have you checked to see if fullscreen optimization is turned on on the executable?

Originally Posted by Gula

So like every thread where the whole community likes to get holier than thou and strawman until the thread is a mismatched garment, just gonna say "this." Because doubtful if anyone wants to read through the pages of arguing for the sake of arguing and trying to look smart.

People want solutions for bots, this is one of them. Not an absolute, but it is a measure.

This is not a solution for bots in the slightest. It has absolutely nothing to do with bots. The bots you see teleporting around are not using uncapped FPS and are instead using a map hack to get around and jump to wherever they need to go.

Originally Posted by Valkyrie_Lenneth

Out of curiosity, are you running fullscreen or fullscreen windowed, and have you checked to see if fullscreen optimization is turned on on the executable?

Windowed full screen and yes I disable windows fullscreen optimization on the dx11.exe.