The lower the stability number - more stable one's lap times are. Only racers who completed more than 2 laps are present in stability table. First lap time is excluded from calculation. I use the following deviation formula to calculate stability. Example of calculation for one player: stability = sqrt(sumN((AverageLapTime - LapTimeN)^2) / (N - 1)) where: N - number of laps; AverageLapTime - Player's average lap time; LapTimeN - Player's time of Nth lap;
but this assume that LFSLapper and LFS server are on the same computer. An other way it's to have LFS server on machine who have http access and make a little script giving IP on web.
I think the issue on 0.6E is corrected now. replace yout tcp.cs file with this attached one.
If you can, put the old incim4.cs. It's not an obligation but it's better because in the new insim4.cs i gave you there are modifications doing nothing for bug.
It's not me who said that. When i see the message the issue was not fixed. In ths message i guess that error seem to be a read error like LFSLapper.
If airio work fine, it's very good for you and all airio's user
Here a version of LFSLapper for Sjoerd 5.8.4.6 to try.
In this modified version, i bufferize stream in queue and read only if len of buffer queue is more or equal to len indicated by the first byte of the queue (len of next lfs packet). I think the reason of incomplete packet before this modified version of LFSLapper is that i'am not using block reading of tcp stream to not freeze LFSLapper loop. But before last lfs release i always receive a complete lfs packet in one shot.
LFSLapper 6 seems to work fine. The only difference is that in the 6 version the stream is received in a thread to avoid lagging issue (waiting for a complete packet in previous version of lapper block LFSLapper loop). In this case i can use block tcp receive and i think i receive in this way always a complete packet.
I hope my explanation are clear in my very poor english