'?' shows total laps and total qualifying time, not remaining ones. Even if it showed the desired information, you stil could not sort the list by those items, you'd have to click server by server until you find the good one.

Last edited by Mandel, Mon 10 Nov 2008, 15:21.

It would be very useful to see in the server list:

• For races, the remaining laps for the leader, or (more difficult) remaining laps multiplied by the mean lap time of the leader.
  
• For qualifying, remaining time for the qualify session to end.
  

This would help to determine (approximately) the next race to happen and probably would give an incentive for longer races.

This is the response I received from the LFS Team, which gives some information I was not aware of:

Quote :

Parsing MPRs to the fullest is not possible because they only contain user inputs, so you need the LFS physics engine to run the mpr and get actual usable data. The only way to 'parse' an mpr is to replay it in LFS and grab the racing data via insim.

Hi all!

I've been fiddling with the Lapper code to find out why it doesn't show the nicknames of the AIs (bots) instead of the player to which they belong, or why it doesn't have any variable to sort out bots and real players. It renders the whole pit information and split information useless, because you get a bunch of messages of your AIs and of you, all with the same username-nickname.

The problem is that the code does not represent the 1..n relationship between users and players, so when I ask for information of a player, I get information of the associated user.

The correct solution (renaming infoPlayer to infoUser, creating the real infoPlayer, and storing all the information and links) is something that requires time, and I have cooked a quick'n'dirty patch to store the player information at NPL (new player) events, and then, when retrieving the (user) information by PLID, stuff that NPL data in a variable of the infoPlayer object.

With this patch, you get the correct value with $Nickname and also you get the plate with $Plate.

I am planning to implement this correctly, I'd like to know if you are already working on this issue, Gai-Luron...

Saludos from Spain! Ignacio Calvo

I've been trying to program an application that extracts RAF files from non-hotlapping MPR, to avoid the hassle of MPR->RAF conversion using LFS and allow for analysis of races, and I have not been able to find a complete MPR specification.

The header is officially specified: http://www.lfs.net/?page=MPR

Looking at the source code of some applications you programmed (LFSStat, MPREdit) I have found that some of you have apparently reverse-engineered the general format of the frame events, and the data inside some types of events, but those that specify the positions and status of the car are already unknown as far as I know.

The questions are:

Has someone completely deciphered MPR format?
Has someone asked LFS developers to publish the complete MPR format?