Uhhhh ok (almost troll post).
GP3 is Grand Prix 3 by Geoff Crammond, probably the best racing game
developer ever (With David Kaemmer). His previous titles like Revs, Formula
1 Grand Prix and Grand Prix 2 demonstrated that he has an incredible
talent, since he works almost alone, and does everything his way, and in a
good way. He still had a game title to make with his contract with
Microprose, so he worked on it, and when Hasbro bought Microprose he
continued under his new house.
And yes, he still has his Mansion on a private Island near Hawaii :)
<r.a.s. inside joke>
And MGPRS3, who cares! Same old game engine, no big additions, little fixes
here and there. Just "another annual update" it seems so. Don't get me
wrong here, but they are going the EASports way.
--
-- Fran?ois Mnard <ymenard/Nas-Frank>
-- NROS Nascar sanctioned Guide http://www.nros.com/
-- SimRacing Online http://www.simracing.com/
-- Official mentally retarded guy of r.a.s.
-- May the Downforce be with you...
"People think it must be fun to be a super genius, but they don't realise
how hard it is to put up with all the idiots in the world."
GP3 by G. Crammond and D. Kaemmer? I don't belive it!
Borut
I can't believe (well, I can) how Nascar Rev was so villified for doing the
exact same thing and Crammond gets a pass. I'm talking this one issue, not
the other aspects of the games.
For those who don't know to what I am referring. In GP2, set the framerate to
say 20 fps. When the "PO" goes above 100%, gametime slows down, laps take
longer real-time, you have more time to react (though your timing may be
thrown off). You may find a 30% or greater slowdown. Conversely, if the
occupancy drops well below 100%, there is a slight (~5%) speedup, again
throwing off timing. Basically, you can't set it well enough to have realtime
match tracktime. A horrible design decision, IMHO.
>> GP3 is Grand Prix 3 by Geoff Crammond, probably the best racing game
>> developer ever (With David Kaemmer).
>GP3 by G. Crammond and D. Kaemmer? I don't belive it!
>Uhhhh ok (almost troll post).
>GP3 is Grand Prix 3 by Geoff Crammond, probably the best racing game
>developer ever (With David Kaemmer). He still had a game title to make
Crammond did Nascar Revolution??? I didn't know that. It certainly
makes me e***d for GP3. I suspect the Processor Occupancy thing
will make it into GP3. After all he is 2 for 2 with that feature. It make be
the only way he can comprehend doing the game :-)
--
Header address intentionally scrambled to ward off the spamming hordes.
cisko [AT] ix [DOT] netcom [DOT] com
Aaah...
Frank
On Sat, 15 May 1999 11:01:59 -0500, "Greg Cisko"
>Crammond did Nascar Revolution??? I didn't know that. It certainly
>makes me e***d for GP3. I suspect the Processor Occupancy thing
>will make it into GP3. After all he is 2 for 2 with that feature. It make be
>the only way he can comprehend doing the game :-)
Andre Ming
Anything under 100% PO is "real" realtime racing. There's no speed-up.
On some tracks it still _seems_ that there is a speed-up or slowdown,
but this is because GP2 does not display the real time on all tracks.
On some tracks the time is multipliedby a certain factor (to make CC
cars drive more "realistic" times?)
Just try this by keeping PO way under 100 and compare realworld time
(on your chrono) with the displayed time.
JoH
========================================
Jo Helsen EDP Operations BF Belgium
========================================
Not sure what you mean. I do know that I timed hot laps at PO<<100% and
compared it to the time I was awarded, and the real world time was slower.
But as I mentioned previously, only by a few %. Whereas the opposite slowdown
effect at high PO is clearly evident.
Drive a lap with around 10-20% PO, then do the same with 80% PO. Compare the
in-game lap times with the times that you get with a stopwatch. No matter
how low you go with the PO, there won't be a speedup in the game. There
sometimes is a difference between in-game and real life times, but just a
little.