GPPerf (was Re: Lap not continous)

[Posted to r.a.s also.]

Quoted text (8 lines)

> 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.

Ah ha! I just did some "back of the envelope" calculations on my trusty 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 -- [link lost in import: /~dgymer/] LFRS 95-96 co-director & car #3

Yeah, I've experimented with different frame rate setttings, and found that 18 fps is not good enough but 20 is. My problem was that I could only get 12.5 fps with the computer I was using ( if you're wondering what computer could be so damn slow I can report it is a 486sx/25 with perhaps the slowest vga card in existence, an Oak Tek 256Kb... And this is with _all_ detail turned off :) I tried with an old Tseng card and it gives me about 100% occupation at 25 fps so there's nothing wrong with the computer per se.), my prf looked kinda strange. I guess the only way to fix this problem is to include an option in Gpperf that makes it possible to log every 10m instead of 5m... That way the files could be comparable, you just compare every other "tick" like : 5m file 10m file 1 0:00:075 0:00:075 2 0:00:132 3 0:00:189 0:00:189 4 0:00:247 5 0:00:301 0:00:301 ...you get the point.