HOF2Lap Limitations and Future Plans

First off, let me say that I'm not a fan of Geoff Crammond; the phrase I normally use to describe people like him who write superficially good code is "a triumph of ingenuity over intelligence", that is, his basic designs are poorly thought out but his clearly very creative mind somehow manages to code around this and the result is something almost but not quite brilliant. The reason I'm telling you this is so that you understand the perverse file format which is a GP2 hot lap has made life very difficult for me whilst writing HOF2Lap and is the central cause of the program's limitations.

Technical explanations for these problems appear in Gizmo's GP2 FAQ as part of the HOF2Lap Home Page. Please read that document before sending a bug report.

Okay, on to the actual problems (for which there is a solution now).

Solution

The solution is to improve the hotlap file structure. GP2Lap does exactly this by adding vital data to the file from within GP2. Since it has access to all of GP2's real-time internal data, the whole problem of not having all the needed data in the hotlap is solved. Of course, original hotlaps will still have the same problems mentioned above. To make use of the new hotlap structure, it's necessary to use GP2Lap with GP2 while driving and saving your laps. See the GP2Lap home page for more details.

Things to do

The current version of HOF2Lap has a few limitations which can and will be corrected in future versions:

HOF2Lap is untested during linked play. It may work fine; let me know if you can confirm or refute this.

I also have yet to publicly release any code for interpreting the authentication codes produced by HOF2Lap. My recommendation to those running hot lap and race competitions is to ask competitors to send in actual hot laps, and for HOF2Lap to be used to check each lap. If this is not possible, please contact me to see if we can make arrangements to use the codes directly.