I think that if it's meant to get the user up to the front of the list, then it should be removed both on this side, and on the side of the LFS.exe client / server.
I think scawen already did this lately (in his version). At least i know he's checking username characters - i'll check with him if he checks other text for < 0x20 as well. That's really the only way to fix it. Filtering it on my side might cause problems (small chance, but it's possible).
For my dashboard (lcd + leds), I use outgauge and pubstat(action=pst). Up to now I entered my consumption of essence in the hand for calculate the number of lap with reserve.
Could somebody help me with this. I never did this and i don't know anything about programming or something like that. I read the first post of Victor but i really don't know what i should do with it.
Without programming knowledge, this is quite useless for you.
Pubstats is a data interface that allows programmers to retrieve LFSW data, store it and display it on their own website.
isn't there a programme or something to do this? The only thing that i want is a pulldown menu where u can choose the track and a pulldown for the car. And when u choose those 2 u can see the PB or Hotlap of our members.
heh i thought someone would get a problem. I've removed the old test pubstats script. You'll have to check your pubstat url and make sure it's the good one. It should start with http://www.lfsworld.net/pubstat/get_stat2.php
I suppose it's possible with some additions to pubstat, but pre-Y pb's are depricated really and will disappear slowly as they get overwritten by new pb's, so that's why it's not available here.
Thanks Victor that's fine. It wasn't a request, I just wanted to work out why a Pubstat application was reporting patch X times. Now I know they must be coming from the database.
It would be nice to have.
Our TeamSite contains now empty times on many tracks.
And as far a new PB is driven I would like to have the old records and show them i.e. in a different colour.
The old data is still stored?
Yeah ... weird results here to ... calling v1.4.
Seems the given result is an multidimensional array with pos 1 being the actual timestamp (or 2-6 sequential ones to be honest) ... followed by the "normal" result as the second value ...
Edit: Everything seems to be normal again ... very weird indeed ...