GPL Replay Analyser v3.5 released

Hi everyone! We've put together a new version (3.5) of GPL Replay Analyser for all of you GPL fans to download. We didn't plan to release a new version until Anderstorp was released (will happen soon), but the engine swap patch changed our plans... We plan on refining the engine detection even more, check back for updates. The engine detection works best for offline hotlaps and worst for online replays saved by a client. It's not a 100% detection, it's a good hint on what engine is used. Version 3.5 hasn't been tested as thouroughly as we would have liked, please report any bugs you might find. The new stuff in 3.5 is: *Added Add and Remove buttons in Track Organizer. This gives you the possibility to add and remove single tracks from 67season.ini. *Added new load option in the File Menu called "Open most recently added replay file". *Added new tool: Replay CD Database Creator. More info on this in the program itself. *If you use many databases Export Records is somewhat slower than before, therefore we added progress bar in Export Records. *Added Filedate column to LapFinder. *Added sort options for Session, Filedate and File in LapFinder. Although date is sorted alphabetically, for the moment at least. *GPLRank calculator now shows how many laptimes are missing to be able to complete the rank calculation for each car. *Changed Coventry to Cooper and Murasama to Honda *Added engine detection report (for finding swapped engines) *Now all reports can be run without having to load a lap from that replay file. *Fixed these bugs: -LapFinder didn't work well with NT4, fixed. -All reports used GMT-time, now the time is presented in local time. Thanks to all helping out test this! :) Download and more info at: http://www.bigfoot.com/~GPL_Replay_Analyser/ Cheers, /Martin and Jonas

On Tue, 12 Dec 2000 18:40:14 GMT, [email hidden] (Martin Granberg) wrote: >Hi everyone! > >We've put together a new version (3.5) of GPL Replay Analyser for all >of you GPL fans to download.<snip> And here's my usual big thank you :) Downloading right now! Andre

>And here's my usual big thank you :) Hehe, thanks. It's first when I see your reply I can be sure the post made it through! :) Cheers, /Martin

Thanks much Martin and Jonas! You guys have done a great job keeping RA up to date with all the new features. Now for my question: would you care to elaborate on what your three methods of engine detection are? The main reason I ask is unrelated to the engine swapper -- I have recently had a problem with lap times getting worse over the course of practicing a track instead of getting better. I eventually tracked it down to a throttle calibration issue, but now, every time I can't seem to get my times down where I think they should be I can't help but wonder if is me or my throttle pot. After the engine swapper came out I started thinking of ways that you could implement engine detection in RA (I knew you'd come through ;-)). Anyway, there are two ways that I could think of, the second of which could help me with me controller problem: The first is to watch max revs. I figure that this probably wouldn't work too well with online replays and would be fussy even with offline replay unless you were very careful to just watch after the end of a run through a gear (as opposed to a downshift). You could probably get it to work with enough constraints and rules but it would take a lot of tweaking. The second method would be to try to measure horsepower. You could use Newtonian physics along various lengths of semi-straight portions of the track (as defined minimal and consistent slip angle) by considering chassis weight and acceleration. Assuming the client wasn't re-syncing, it would probably be pretty accurate even with a partially warp client especially on tracks with long straights. Of course uphills, downhills and drafts could cause slight errors, but, it would still be interesting and probably enlightening data. Anyway... if you could explain how you're doing your engine detection and possibly display some of your raw values instead of just assumed engine type, I think there may be a lot more uses of the engine detector than originally planned. If you are somehow calculating HP then I think it would be good if you could display your values instead of just chassis since we could then recognize the people that have managed to grant any HP they want to their favorite chassis, identify out of calibration controllers, etc. Thanks again Guys, Randy On Tue, 12 Dec 2000 18:40:14 GMT, [email hidden] (Martin Granberg) wrote:

Quoted text (7 lines)

>Hi everyone! > >We've put together a new version (3.5) of GPL Replay Analyser for all >of you GPL fans to download. > >We didn't plan to release a new version until Anderstorp was released >(will happen soon), but the engine swap patch changed our plans...

<snip>

On Tue, 12 Dec 2000 21:13:42 GMT, [email hidden] (Randy Riggs) wrote: >Thanks much Martin and Jonas! You guys have done a great job keeping >RA up to date with all the new features. Thanks :) >Now for my question: would you care to elaborate on what your three >methods of engine detection are? Not really. It isn't rocket science, but there less info available about it probably the better. >The main reason I ask is unrelated to the engine swapper -- I have >recently had a problem with lap times getting worse over the course of >practicing a track instead of getting better. I eventually tracked it >down to a throttle calibration issue, but now, every time I can't seem >to get my times down where I think they should be I can't help but >wonder if is me or my throttle pot. The calibration window should show these things I believe? But I know how you feel. When I am slow I recalibrate immediately - must be bad throttle calibration! :) >After the engine swapper came out I started thinking of ways that you >could implement engine detection in RA (I knew you'd come through >;-)). I must make it clear that the detection isn't a 100% detection, it should be used as a hint of what engine is used. There is no way anyone can base any conclusions on that detection alone. If the engine is stated to be "wrong", I suggest studying the replay further in GPL or GPLRA. (not a reply to your post, just want to make this clear) Cheers, /Martin

Many thanks for your RAv3.5! I am new to the program, tested it just a moment ago. A couple of questions - perhaps just RA rookie's problems: 1) I have saved some of my best laps just from the start, when the nose of the car is on the line, to the end, when just the nose of the car comes again there, and those laps seem not to be analysed... :-( How much should I save of a lap for it become usable? 2) One of the few I could check was a practice session at IMS. I was driving a Lotus (F1) in last September, 24 - much before the engine swapping patch. Anyhow the "Engine detection" tells me that I've been using a Brabham (A), No data (B), and Lotus (C)!? Did I understood something wrong? Arto

Arto, save the replay from a few second before the line to a few seconds after. It'll work great then :O) As for (2) it isn't perfect. Possibly it was online, or you might be able to use a bit more throttle :O) Thanx Martin and Jonas. The Engine detection isn't the only thing in the upgrade. The smaller details are what stands this program out from anything else! I especially like adding the laps needed to complete a handicap for that car, and not needing a full lap of a replay to view reports! It seems U have ESP!!! Thanx again guys :O) Geordie -50.06 "Arto Wikla" <[email hidden]> wrote in message news:wikla.976660482@kanasaari...

Quoted text (20 lines)

> Many thanks for your RAv3.5! > > I am new to the program, tested it just a moment ago. > > A couple of questions - perhaps just RA rookie's problems: > > 1) I have saved some of my best laps just from the start, when the > nose of the car is on the line, to the end, when just the nose > of the car comes again there, and those laps seem not to be > analysed... :-( How much should I save of a lap for it become > usable? > > 2) One of the few I could check was a practice session at IMS. I was > driving a Lotus (F1) in last September, 24 - much before the engine > swapping patch. Anyhow the "Engine detection" tells me that I've > been using a Brabham (A), No data (B), and Lotus (C)!? > > Did I understood something wrong? > > Arto

In article <3a36ea20$0$19410$[email hidden]>, "Geordie Pugh" <[email hidden]> wrote: > Thanx Martin and Jonas. The Engine detection isn't the only thing inthe > upgrade. The smaller details are what stands this program out fromanything > else! I especially like adding the laps needed to complete ahandicap for > that car, and not needing a full lap of a replay to view reports! Itseems > U have ESP!!! Glad you like it! :) No, the engine "detection" is the reason v3.5 was released now, but not the main new feature in the program. Personally I have much use for the database creator, but that might be cause I have 7GB GPL-replays... Cheers, /Martin Sent via Deja.com http://www.deja.com/