On Thu, 08 Nov 2001 12:53:19 +0100, Spadge Fromley
>>Occasionally the framerate dips a bit, but nothing that affects car
>>control, so it's a fair trade off against everything that's going on.
>Correct me if I'm wrong, but isn't that basically unforgiveable in a
>console-only game? It's not like they have the excuse: "your PS2 is
>under-powered, get a better gfx card". That's supposed to be the
>advantage consoles have over PCs isn't it? Everyone has the same
>hardware, and that makes it a lot easier for coders to make a game
>that runs perfectly out of the box.
Well, that's put a bit harsh. Given a 3D game, it's not controllable
anymore whether a certain viewpoint or certain collision situation
fits into a 50 or 60Hz timeframe. Making absolutely sure that it is
always reached means having to half your reachable performance, and
even then...
I wouldn't say a PS2 game that occasionaly skips a frame (it's
probably vsynced) is not perfect. If you've ever seen what a collision
matrix equation looks like, you certainly know that if you are a
developer, you'll never be able to guarantee framerates anymore.
The 60+ was pulled back a post later. But 60, yes. NTSC does 10 more
than we do (but oh oh, you have to give in on the color side hehe).
Ruud van Gaal
Free car sim : http://www.marketgraph.nl/gallery/racer/
Pencil art : http://www.marketgraph.nl/gallery/