Quote:
Originally Posted by trixster
but the frame rate is pretty terrible as soon as there’s more than just a few cars of trees on screen.
|
One of the hard decisions while coding racing game is to artificially limit it to 20 fps, even though most sections could run at 60 fps.
But because some sections drop the framerate to 20 fps, the end result is perceived as 'terrible', even though nobody would complain about framerate if it was rock-solid 20 fps, 100% of the time.
For example almost nobody knows OutRun is 30 fps, it is a universal understanding it runs at 60 fps, even if it's not true - just because it doesn't suffer frequent framedrops. Well, technically it does, internally (no way around that - each frame is different number of cycles), it's just not visible to the player.
I'm pretty sure that if its driving speed was slightly lowered (to accommodate lower fps), and the game ran at rock-solid 20 fps, nobody would complain either, because - well - that would be the OutRun that everybody grew up with and played...