I currently working on updating jinsim for patch X. It is not finished by now, but you can find a first test release here: http://liveforspeed.at/download/jinsim-0.4.91.zip
In this release all jinsim response and request packets are updated and should now work with lfs patch w24, but only UDP connections are supported right now. I will add the TCP support soon.
JInSim now requieres Java 5.0.
You should also look into the Changes file and also exam the examples, because I also have done some refactorings.
I don't know if it is a new feature in W21 or a bug. When I press reset during an online race, or a qualifying, the car is repaired and all tires are new. (I was alone online when I tested this)
I did not find any description of this (new) behavior in the changes list.
Thanks, now with W22 it works.
You don't slow my development down, because I'm updating the Java insim libraray JInSim, and there are lots of other things to update and test.
I'm currently working on updating my insim tools, and I encountered a problem. I'm trying to get a IS_CPP from LFS by sending a tiny packet as discribed in the InSim.txt with the following values: type = 3, request info = 1, subtype = 6, but I don't get a response package.
If I send a version request tiny packet (values: type: 3, request info = 1, subtype = 1), than I get the IS_VER packet as answer.
I'm using the W21 patch and all packets are transmitted via UDP. In LFS I have started a single player race with 3 laps and the car is standing on the start finish line.
I try to find an error in my code for some time, but I have no clue.
Has anybody a hint, or is it maybe a LFS bug?
I have a similar problem, because I have to update my tools to manage the austrian championship. This time I'm lucky, because the last race is before patch X is released, when the schedule is right.
A nice feature would be that we can tell LFS which InSim version we want, so that with Patch X also old tools can work.
One other solution could be that multible LFS versions are supported. e.g. in the LFS directory a LFS_W.exe and a LFS_X.exe is located, and when the user connects to a server that runs the W version the LFS_W.exe is started, and vice versa.
But this would only make sense if the InSim changes constantly.
The idea with the buttons is great. I'm was also playing around lately to add a simple interface via insim to send race control messages for admins.
For this it would be create to have a textfield.
I think it would be enough if the chat input window is shown after a button is pressed, and the entered text is also transmitted with the button infos.
I use Wine 0.9.20 on Debian to run the lfs dedi and all works fine out of the box. I have read that newer versions of Wine needs a X-Server, but I cannot confirm it.
What useless data? We do not put a penalty tag into the lap tag when no penalty event happen. Only when a penalty, takeover, flag occurs, than a tag is added to the proper lap when the event occurs.
As I suggested earlier in the thread, we should put mendatory info in the format, but the speed should be optional. But we should only put infos in the file that are useful. I only think that the top speed is one useful information. As I remember there were more things in filurs example is not available anymore, so I cannot give an example whats useless.
Hmm, first I also thought that is should be analog to insim, but now I don't know if it is the right direction. The goal of the common stats format is that different tools can use the same input format. Why not different racing sims. I mean that the naming or values like penalty should not be lfs specific. e.g.:
Namespaces only make sense if other kind of data is also included in the XML file, and that is not the cause with the stats file format. If you want a valid XML file so that the parser has no problems, than a XML-Schema is the right way.
So we need no namespaces here, it only make things complicated.
As I wrote earlier in this thread I don't like abbreviations. You sometimes use full names in your example, and sometimes use abbreviations.
So always use full names like username instead of uname, or position instead of p.
Also the time should not be formated. XML is mostly read by programs so a unnecessary parsing could be avoided.
If the flag tags have lap numbers, than put them directly into the lap tag. Also the split times. e.g.:
I have a driver detail page where every lap of a the race is display and I want to add a flags column that shows when a racer has received a blue or caused a yellow flag.
Here is an example of the current version of a drivers detail page: http://liveforspeed.at/?q=league/driver/detail/310
If the pit and penalty infos are childs of the lap element, it is also very easy with XPATH to get only a list of all pits of penalty tags.
Yes you can have more entries, and you can get the correct tags with XPATH.
Make it sense to put the yellow and blue flag also into the laps tag? I know that Insim does not send the lap number, but in my stats tool I put the flags into the current lap when the IS_FLG event is received.
I also suggest that we make mendatory infos and optional infos. For example the result or lap time is mendatory, but the speed should be optional.