> We talked about the problem with Gpperf when cpu-occ. is above 100%. I had a
> discussion with Jay Freels who told me about his P60. He set frame rate to
> 8, cpu-occ=20% (I don't know why, maybe he is angry to have an engine blow
> up :-)). With this configuration you get the annoying message, too.
> I guess, if frame rate is too low, you don't drive really all segments (some
> may be skipped), so gpperf can't log them.
> What we now know is that cpu-occ has to be below 100% and fram rate has to
> be high enough.
Psion and I reckon that at 200 mph you travel just under 300 feet per
second. Assuming that segments are about 16 feet apart (as listed in
the GPPerf documentation), that means that you travel in 19 of them per
second, ie. the frame rate needs to be at least 19 (and probably 20)
before GPPerf will work correctly.
This may all be fixed in GPPerf 2.0, which should be coming to the
MicroProse FTP site sometime in the next few weeks. (Of course, if
someone wants to mail it and GPAnalyser 4.0 to me it will appear on my
web site a darn sight sooner... :-)
-- Dave "Gizmo" Gymer Telephone +44 (0)1268 534228
-- General DataComm Advanced Research Centre Ltd, Basildon, UK
-- http://www.racesimcentral.net/~dgymer/ LFRS 95-96 co-director & car #3