tell you. I think it's very important.
I loved very much GP2 in 1996, but I stopped playing when I realised
that cheating was possible because of slow-motion problem.
the same slow-motion problem is still present in GP3, so hotlaps will
not be true.
try this experiment:
(my system is a PIII 550, 128 mb ram, voodoo5 5500, sb live! basic)
set graphics at maximum manually until you reach 150% of CPU occupancy
(in the game press key O to check it): for me is resolution 1280,
FSAA4x and frame rate bar at maximum (25.6 fps), all details on.
if you are not able to reach that amount of processor occupancy try
software rendering, but you have to reach solid 150%/200% processor
occupancy.
then start a hotlap at monza, you will notice that graphics runs
smootly, but very slow. don't care about that and do you hotlap. GP3
said to me I did a 1m32sxxx while driving with one hand only. very
very easy. the problem is that in real life the lap time was about
2m27sxxx
now set graphics in order to obtain about 60% of CPU occupancy: for
me was a 640x480 resolution all details on, and try to do the same
hotlap.
you will notice that now graphis runs as fluently as before, but the
simulation is very fast, as it should be. now it's normal. I tried a
hotlap, and GP3 said me it was a 1m37sxxx. my real life stopwatch said
me 1m37sxxx
it's obvious that hotlapping in slow-motions conditions is much
easier, so hotlaps with GP3 will be not reliable.
the main problem is that GP3 is exactly GP2 code + D3D support.
exactly the same game.
geps.
Driving
per gli appassionati di Grand Prix Legends
http://www.racesimcentral.net/