• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

17-22FPS acceptable for ordinary gamers?

Anything lower than 30 and your game is turd. Oh and I don't mean average either. If it's under 30 at any point, scrap your game. Especially in the next generation.
 
So, how would you in a non-confusing manner separate the people that play a few hours a week / month that know nothing of the technical jargon and care even less about it to the people that play 30+ hours a week and know all the fancy technical terms.
You just did.

Casuals is bad, ordinary is bad, how do we go about this?
Relax, not everything has to be reduced to an epithet.
 
Was just a matter of time before the PC crowd joined in.

So, how would you in a non-confusing manner separate the people that play a few hours a week / month that know nothing of the technical jargon and care even less about it to the people that play 30+ hours a week and know all the fancy technical terms. As one of these group of gamers see and enjoy games differently.

Casuals is bad, ordinary is bad, how do we go about this?
I usually refer to people like gaffers as ethusiasts or hobbyists.
 
I imagine playing at a constant 17-22 fps frame rate would be like controlling a game through a remote desktop connection. Probably doable in certain games but a pretty horrible experience.
 
I realize I'm not in the majority, but I don't actually mind 20fps. Most of the time I can't notice it's below what it's supposed to be, if I have no point of comparison.

When I saw this
15 fps with motionblur
ibpGMtLrHFjvYF.gif

30 fps with motionblur
iwr4Lzh9P9kHu.gif

60 fps with motionblur
izchDTW1pljCC.gif
I initially hadn't scrolled far enough to see the last 2 gifs, and I thought the post was meant to say 'see, 15fps is fine'.

EDIT and I also actually think 30 fps looks better than 60, which reminds me of the weird PixelHD mode (or whatever it's called) on Philips TVs which makes everything look like documentaries.
 
17-22fps? Hell no,i notice when dropping from 60 to 40fps or lower on pc it is horrible lagging left and right everything becomes a slideshow..just horrible.
 
Okay, this is just a quick topic to check a general view. Currently having a discussion with and individual on another simulation related forum. He's saying 17-22ish FPS is acceptable for a majority of games, no one is able to see the difference between that and higher framerates etc.

My mind is obviously full of fuck and the tearing / unstable framerate alone would make me contemplate suicide.

So I just need to know, would anyone here be okay with that for general gaming? Would you, to the best of your knowledge, say that the every man playing a game couldn't feel an FPS that low, see that tearing and feel the unstable FPS?
Your counter part in the argument is talking BS.

Now:

I do play single player games at 24 fps. It is not a problem once you get used to it. I even went to the extent of fooling a person very sensitive to frame rate, Played myself for a couple of minutes, then passed the control as far as concerned the gaming was happening at 30 fps. Pressed a key to get the fps to 30, he tough for the first few seconds it was 60 XD

Point is, you get used to it rather quickly. Of course there are benefits for higher frame rates depending of the genre and other applications like 3D, etc.
 
Pretty sure Blight Town in Dark Souls went even lower than this on PS3, haha. Anything below 30 is unacceptable for me.
 
Sorry, but no.
Anything lower that 25 is bad performance. In PC you can try to arrange it with options, but in console... Developers should aim for 60 and set a lower standard at 30.
Especially if the framerate is unstable. That makes it much more noticeable.
I remember playing Jedi Knight II and Jedi Academy on my very old G4 mac (350Mhz processor...) Framerate was so low that after a couple of hours playing my own mind was running at 15 FPS. It was horrible! A strange experience though. Our brain can do amazing things but i don't recommend that one...
 
It is very easy for the trained eye to tell the difference between 30FPS and 60FPS.

30FPS is the minimum acceptable for most games, which is why a lot of games aim for that as their target when 60FPS in unreachable.
 
didnt Zelda OoT run sub 20 fps back in the day?

When i played it on N64 i had no issues with it.

edit: of course, I wasnt as picky back then.
 
17 to 22 FPS is playable but unpleasant, and really only acceptable when you're trying to play on a laptop that's not designed for gaming — in which case, you're just happy the game in question runs at all.

It's definitely noticeable compared to 30 FPS or any higher framerate. Even 30 FPS is disappointing when you're on a dedicated gaming rig. 60 FPS or higher or bust.
 
I have a really hard time playing at anything less than 60

i'll do it on a console, but it'll bother me throughout
 
It's all about what framerate the game was designed around, Quake 3 feels laggy at 60fps, it was designed for 85. Star Fox on the SNES is still great fun at ~10fps, although I think very few developers could make an action game work at such a low framerate. 20fps is good enough for many kinds of experiences with a talented developer, but usually games developed to be fun at 30 or 60fps will not feel very fun at 20.
 
In the Voodoo2 days I used to think 20-30 fps was acceptable. But these days I demand 60 fps. I will even drop the resolution to 900p (on my 1080p screen) to maintain that framerate. Smoothness is addictive, you can't go back.
 
It's all about what framerate the game was designed around, Quake 3 feels laggy at 60fps, it was designed for 85. Star Fox on the SNES is still great fun at ~10fps, although I think very few developers could make an action game work at such a low framerate. 20fps is good enough for many kinds of experiences with a talented developer, but usually games developed to be fun at 30 or 60fps will not feel very fun at 20.

StarFox SNES is not really playable, it is really hard to hit anything at such a crap framerate.
 
Depends on the demands of the game. Ocarina of Time was playable-ish at 21-24FPS, but there wasn't a lot in the game that demanded fast reactions, and the framerate was at least consistent.

In a game where you have full control of the camera, as opposed to it being mostly automated in the case of OoT, I would say that 30 is the absolute minimum lest you be overwhelmed by judder.
 
Hell no. The lowest I could ever go is 25 fps and that's ONLY if it's for a very short period of time. Anything consistently below 30 is sickening
 
Sub 30 is fine by me in some cases but when it goes below 20 its really bad on most games but if it never goes below 17-19 i would call "playable".When i had a bad rig with geforce 6200 and latter a 3650 i played many games with that framerate (probably more to the 25fps side but with frequently dips),all where playable,not maximum pleasure but definitely playable.

I played crysis 1 with 20-24fps and felt smooth,if i play it now probably i would say its unplayable but when i played years ago felt not only ok but i could lower the graphics and get 30+ but i was convinced that 20-24 was good for me on this game.
I played company of heroes 1 and felt smooth and when i run fraps it said 17 frames,i was speechless.
I played league of legends with 15-24 frames too with sub 10 on big battles,yeah that was not very playable ;p
But i raided in wow on 12fps (25man raids) and i managed to be top damage on many raid bosses.Depends on the game

Now that i ahve better hardware i try to run games with as much framerate as possible and its hard for me to accept sub 30,its just how you have trained your eyes to see and what are your quality standards.I guess if i start playing on 120hz i would say that 30fps is unplayable or something ;p
 
StarFox SNES is not really playable, it is really hard to hit anything at such a crap framerate.

It can be hard to go back to it now but if you take it on its own terms without bringing in any skills you mastered in other games (like the n64 sequel) the gameplay can still click because they designed the game around the framerate. It's certainly more difficult, but it CAN still be appreciated in a way that a game that was designed for 30fps but suffered development issues and shipped at 10 cannot.
 
Serious Sam 3 on 360 is the only console game I've played with a framerate counter. Which is unfortunate because in splitscreen it has probably the worst framerate I've ever seen. A very quick test of the demo showed the framerate to vary wildly from a high of 25 to a low of 11 with an average of 18. This was done with player 2 stood idle at the start point far away from the action.

But Rainbow Six Vegas 2 on 360 has one section also in splitscreen where the framerate is about 5fps for a few minutes. During the very last level with the helicopter after you. It was literally like a slideshow. I tried it several times both with and without the patch.
 
Depends op the game, but for the most part it isn't acceptable. I confess I did play Tomb Raider on my 8800GT at 1080p on Ultra... and i tried not to dial back the settings because the game just looked so great at that setting... IT RAN LIKE SHIT!, but I couldn't stomach going back to 720p lol. So I played it like that until I couldn't take it anymore and upgraded my graphics card.

So with that said, tolerance for playing anything under 30fps depends on the person. I was willing to tolerated it because I wanted better image quality and I couldn't afford to upgrade. I think many gamers are like that as well.

If your friend is happy playing at 17-22 fps... plop in a better graphics card into their pc and have them play at 40-60fps. Then have them go back to what they were happy with. They probably won't be so happy with 17-22fps anymore.
 
Low framerates doesn't always mean screen tearing but let me go ahead and drop my opinion and get mocked for it.

Of course when you compare framerate gifs side by side it becomes a no brainer by default but imo, I can tolerate low frame rates and a bit of screen tear as long as it is not painfully obvious.

The other element to this is input lag. If it is a consistant framerate with barely noticeable input lag then it is acceptable. Anything else is simply game breaking for me. Everyone has their own personal limit to what the can stand, I am simply not one of those gamers who can look at a video and instantly guess it's average framerate without a tool.
 
I've never been one of those gamers who are picky about 30 vs 60 FPS. It really doesn't matter to me. But 17 FPS? That would make me want to pull my hair out in frustration.
 
If the game was locked to 22fps and I could play it on a 44Hz monitor, it would look fine. Not particularly responsive, but solid enough. It would need to be a fairly slow-paced game too.

But fluctuating between 17 and 22fps on a 60Hz monitor? Do not want.
 
I'd like to see some framerate tests for OOT. It never looks like it is running as poorly as it supposedly does. It seems like 30 with slight dips. Maybe a few 15fps moments but very rare. Constantly sub 20 though?
 
Locked FPS is pretty important to me. I can't stand dips. I'd prefer a 25 locked over 30 that dips into the 20s/teens and back when there is action going on.
 
Whomever you're talking to has likely never seen a game run at 17fps. Even the average person would say the game was broken shit.
 
The majority of mainstream gamers are generally fine with ~25fps, and start to notice choppyness ~20fps, find it has a detrimental affect by ~15fps.
 
Top Bottom