Dead Rising 3 PC Version Will Run Into Issues Above 30 FPS, Says Capcom

[Something Amyss]

Maybe I'm just old and don't have the newfangled eyes this generation has, but given persistence of vision (which is how we actually create the concept of motion in the brain) isn't 60 FPS more than the human eye can detect?

We can only view a few discrete images per second, but that number is actually (if I remember right) in the single digits. However, when we see images at that speed, they look choppy. Higher framerate means it looks smoother to our eyes. There's some matter of debate over where the noticeable cap is, but it's not as low as you would think based on technical numbers with the eye. You can also notice changes that happen at an even faster "framerate," based on tests of picking up an individual dot, for example.

Keep in mind, though, that while there are people who will swear they can tell the difference between 30, 60, 120 and even higher, there are also people who swear they can tell the difference between lossless and high quality lossy audio files, as well as vinyl and digital, who can't actually do it when tested. I'm not sure if any such test has actually been performed for gaming applications, but I'd be interested to know how many people could actually tell the difference (even in clinical conditions).

 

[WhiteTigerShiro]

That's what pisses me off the most about this. People will throw a fit about the 30 FPS issue, but then they'll make sure that the PC version makes Capcom millions of dollars anyway. It would be nice, for once, to see the PC community band together to stubbornly cross our arms and just sit there until the developers agree to fix the issues they brazenly said that they wouldn't fix.

Of course, there is an element of "damned if you do, damned if you don't." Because DR3 will either sell well or they'll blame piracy. Even if nobody pirated the game, they'd blame piracy.

Still, it's a little tiresome to hear the outrage over these things and people buying them anyway.

Yeah, this is true. Big businesses (and this isn't exclusive to gaming) have a bad habit of nearly-always learning the wrong lessons from their sales reports, even the good ones. If a product does well, the company (and rivals) will find the simplest and most easily reproduced part of that product and then mass product the hell out of it. Hence why Lego Movie was awesome (because it had a deep and meaningful plot with characters that had actual depth), and now a bunch of toy makers are in a big rush to greenlight their own products as movies because all they saw was "movie about toys did amazingly well". Then on the other side of the spectrum, you have a game (who's name I forgot) that was horribly made, but the developers made a big deal about piracy as the reason for low sales.

*Sigh* You'd think with all that money they could afford a few brain cells... apparently not. -_-

 

[Baron_BJ]

The part about this that I find most amusing is that not only did they tie shit to the frame rate, but DR3 has been rather notorious on the xbone for consistently dropping below 30fps. Even on the console the physics would have been sub-optimal. Delightful.

 

[Cerebrawl]

Keep in mind, though, that while there are people who will swear they can tell the difference between 30, 60, 120 and even higher

I'm one of those people. I can tell right away if it's low, moderate or very high framerate. In side by side comparison I can pick out even higher, because of its smoothness.

When it's not just video, it's even more telling. Heck I can tell the difference between 60fps at 60hz and 120fps at 60hz, because of the smoothness and responsiveness of movement when I move my mouse, in first person view games.

Sidenote: any panning camera shot in movie theaters is extremely choppy to me, in both 24fps and 48fps(LotR, etc).

 

[Rad Party God]

It's really strange coming from Capcom, who have released a steady amount of good PC ports since 2007, Resident Evil 5 & 6 both ran at buttery smooth, perfect 60 fps without a problem, heck, even DmC who ran at 30 fps on consoles, ran at perfect 60 fps on PC (without counting those pesky pre-rendered cutscenes).

Why the heck did Capcom suddendly decided to put their foot into their mouths and screw up Dead Rising 3 so freaking badly?.

 

[Something Amyss]

I'm one of those people.

I'll assume you read the rest of my post and just point out that it still applies.

 

[Rozalia1]

And you'll buy it anyway, so we have absolutely no reason to change or care.That's what pisses me off the most about this. People will throw a fit about the 30 FPS issue, but then they'll make sure that the PC version makes Capcom millions of dollars anyway. It would be nice, for once, to see the PC community band together to stubbornly cross our arms and just sit there until the developers agree to fix the issues they brazenly said that they wouldn't fix.

What you want to happen in such a movement occuring:

Capcom: Seems people aren't buying our game...seemingly because of certain issues...well lets fix them.

What will actually happen:

Capcom: Seems people aren't buying our game...damn pirates the lot of them. Hey EA, Ubisoft, and all you other cool cats...you guys having this issue too?
Group: Yup.
Capcom: Well lets not bother anymore to really stick it to those losers.
Group: That'll show them.
Microsoft + Sony: We agree.

...

Nintendo: Don't really give much of a crap.

 

[-Torchedini-]

Maybe I'm just old and don't have the newfangled eyes this generation has, but given persistence of vision (which is how we actually create the concept of motion in the brain) isn't 60 FPS more than the human eye can detect?

And its not only about perceiving motion. With movies you can do that and get away with it. But games are interactive. Responsiveness varies a lot between 30 and 60 fps. at 120fps you're fine, going higher than that doesn't have too many benefits because other factors come into play.
At 60 fps you are implementing input every 16.6ms on the monitor. Drop that to 30fps thats a free 16.6ms extra delay for free. That stacks with delays in game code and the delay you have when reacting to visuals. So basically you are making it very annoying to play fast paced games. That's why I laugh when I see somebody pronouncing that 30fps is okay. Because it is not.

For more indepth material I would suggest reading this http://www.anandtech.com/show/2803
It is quite technical though so, heck I don't understand some things being said but the overall picture is very clear.