next »

[gimymblert]

tearing, lag, hiccups are more terrible to game than pure fps

Stable framerates and Vsync does a lot to game too, more than framerates

however now there is Gsync, framerate is so last years

I also wait for some game to implement 2frames motion blurring to keep 30fps warmth into 60fps game lol

[Cobralad]

Yeah, you are speaking as if every last game was not a bleak frankestein of 2009 tenoutatens.
But hey, there also pixel games. Nuclear Throne stutters during explosions and Rogue legacy works at 4-9 fps on my laptop. It also requires shader support. Me neither.

[gimymblert]

[Lauchsuppe]

http://www.30vs60.com/

just about any pc monitor can run at least 60hz, doesn't it? my 100 bucks tft can't do shit but there's a massive difference between 30 and 60 fps to me. I honestly can't believe all you guys don't notice the micro lags in direct comparison

[J-Snake]

I honestly can't believe all you guys don't notice the micro lags in direct comparison

I think it is because some have never consciously cared about it, just like with movies.

[gimymblert]

http://www.30vs60.com/

just about any pc monitor can run at least 60hz, doesn't it? my 100 bucks tft can't do shit but there's a massive difference between 30 and 60 fps to me. I honestly can't believe all you guys don't notice the micro lags in direct comparison

I can see the difference, but it matter only if the situation call for it. Sonic generation is best appreciated at 60fps and higher because what the game is about.

For example I like in cinema that my FOV is full of the movie, so I go to front row sit ... 25fps don't do it to me anymore (the chug make me sick, it's distinctly perceptible) and there is no incentive to go further from the screen if the fov is the same as my TV at home (in the era of big flat led tv), even my tablet have a correct FOV since I have it close to me ...

[Sik]

60hz feels really choppy in a game like quake if you try playing in 120 for a while, I think anyone would notice really.

Same if you were looking at something at 240Hz and switch back to 120Hz. I think 240Hz is the true limit for most people but I wouldn't be surprised if I get proven wrong with 480Hz.

Then again I think the problem is relative framerates... I can play games at 15FPS without noticing it (

) but then I look at something at 30FPS and suddenly it feels extremely smooth. If I go from 60FPS to 30FPS it feels extremely choppy, instead.

Also vsync and frameskip matter. I once made a game with a 100Hz timer on a 60Hz display, without even bothering to implement vsync (I was young, hey ), so it meant tearing everywhere but you wouldn't notice it since the tear moved all over the place. The difference between the game running at 99FPS and 101FPS was huge, despite the difference between other close framerates barely being noticeable. It was like the framerate equivalent of sonic boom. I'd expect this to become a serious problem once monitors with variable refresh rate become common, since they will trigger the same issue.

[s0]

virtua racing doesnt look choppy at all to me but thats because it uses some tricks to give the illusion of smoothness maybe?

[Sik]

Nah, it doesn't at all, maybe the recorded video does though... Maybe check

, which is on an emulator?

But yeah, 15FPS doesn't really feel choppy unless your reactions are extremely quick (enough to hit the framerate wall) or you just came from seeing something at a higher framerate.

[ProgramGamer]

I remember Mario Kart Super Circuit feeling mega horrible. Was it because of the frame rate or because of purely bad programming on Nintendo's part?

[Lauchsuppe]

I didn't mean to say that 60fps are superior to 30 fps. It just makes for a different effect. The amount of fps have a huge impact on how interactions feel; I think this can be utilized creatively.

[Schoq]

for example: higher fps may be utilized to make a game feel more responsive, smooth and exciting, while lower fps can be effective at making them feel more slow and boring, as if the game is badly programmed or running on insufficient hardware, if that's what you're going for.

[MeshGearFox]

I can tell the difference, but the 60FPS stuff in that comparison site looks unnatural to me.

It's like the animations were created with 30FPS in mind, but then they're sped up to 60FPS.

Also you get some games -- shmups and fighting games in particular -- that are really particular about frame timing.

[rj]

I remember Mario Kart Super Circuit feeling mega horrible. Was it because of the frame rate or because of purely bad programming on Nintendo's part?

neither. the 2D mario kart games (snes, 64, and gba) were always really fucking weird. they have a strangely disorienting (for some) parallax effect that doesn't quite make sense

[oahda]

64 has billboard cars, but the levels are true 3D…

I do agree that it hasn't aged well tho. Double Dash is an incredible improvement and I just can't go back to 64 now. It's unplayable. I've tried.

[Lauchsuppe]

for example: higher fps may be utilized to make a game feel more responsive, smooth and exciting, while lower fps can be effective at making them feel more slow and boring, as if the game is badly programmed or running on insufficient hardware, if that's what you're going for.

but 30fps doesn't have to feel less responsive than let's say 60fps.
by your logic, making use of lower resolutions than you are technically capable of would be dumb as you can put less stuff on a screen.
or using low poly models over high poly models would be equally dumb since they are less realistic.
or yet another comparison I don't want to type out right now

[quantumpotato]

I used to play Tremulous at 120+ fps and it felt way smoother than when I clocked it down to 60 or 90. Definitely the higher FPS (and more consistent), the better.

Funny anecdote: playing Smash Bros. Melee (60fps) on a PAL television (50fps) meant that 1frame moves sometimes wouldn't appear at all but still have their effect, causing hilarious reactions.

[s0]

by your logic, making use of lower resolutions than you are technically capable of would be dumb as you can put less stuff on a screen.
or using low poly models over high poly models would be equally dumb since they are less realistic.
or yet another comparison I don't want to type out right now

it makes a difference in responsiveness for twitchy action games but is p much irrelevant for anything else

[MeshGearFox]

by your logic, making use of lower resolutions than you are technically capable of would be dumb as you can put less stuff on a screen.
or using low poly models over high poly models would be equally dumb since they are less realistic.
or yet another comparison I don't want to type out right now

it makes a difference in responsiveness for twitchy action games but is p much irrelevant for anything else

I don't feel like this universal though. Like some games I've played feel less responsive at lower framerates, but in other games it feels like the input is still processed as quickly, stuff just happens across the board.

I think what's really problematic is when you get frames being /dropped/.

[s0]

that happens when game logic is not tied to framerate i think?