You mean something like that ??

showing trajectories What is that ?? (sorry my english is not as good)
fuel level posible...but only for your own car. Or the car that is sending the data.
tyre temps not with Insim/Outsim/Outgauge
tyre wear ok
suspension frequencies not with Insim/Outsim/Outgauge

Driving line would be posible.
Or sending a command to the driver. But I think normaly you are connected with teamspeak or something else.

Decide to arrange the information on more windows.
Which Info´s should be shown .... ??

When i found someone for the graphics it will be released

Nice ....
Dammed I only have this old HP thing.

hmmm....for TomTom Navigation it´s good enough. :rally_dri

Quote from Knu :

Just in case it helps, my initial problem:

[code]
-IS_ISI
0000: 2C 01 01 00 00 00 10 00 00 00 E8 03 6E 33 31 31 ,...........n311
0010: 00 00 00 00 00 00 00 00 00 00 00 00 49 53 52 4D ............ISRM
0020: 00 00 00 00 00 00 00 00 00 00 00 00 ............

Quote from InSim.txt :

// zero : LFS sends NLP / MCI packets using your TCP connection
// non-zero : LFS sends NLP / MCI packets to the specified UDPPort

I mean that.
Knu get´s the MCI over TCP Connection. If a port is send within IS_ISI it´s sent over the UDP Port, isn't it ??

You receive MCI over TCP??
Ever tried to receive over UDP if there is the same result ??

Screenshots

Quote from Scawen :

..... I could in fact take one more step and make it variable sized packet,

No problems with that. But in MCI-Pack this would be very nice too.

Nice....now i use NLP

@ buedi

check PN

Quote from kiss me :

only works with W
it doesnt work with W39, tried it to
got it to work!!

Working on it for new InSim

At the Moment everything is shown in LFS directly. Later i will build a Form to show it in other PS´s.

Quote from T-RonX :

My code is currently a big mess, you really don't wanna have a look at it.
buedi might want to provide his code.

The post was for buedi

May you send your code and i will have a look ??

Don´t forgett to charge he Battery

Quote from buedi :

Hi T-RonX,

no problem here with the ISI Packet. IMHO I upgraded all necessary Bits to V4. When I send my ISI Packet I see the Connection in LFS and I even get the Version Packet back into my App which I can process and display on my Screen. And LFS sends all 30 Seconds a IS_TINY Package for Keep Alive to me..
So the Connection is established, InSim is initialized and I get Packets from LFS.
But LFS seems not to believe me that the following Packets I send are for the InSim Connection I previously opened. I used Wireshark to find differences in my Packets. And what I recognized so far is that my 1st UDP Package has an SRC Port of i.e. 1130, the 2nd one of 1131 and so on. Does LFS expect the same SRC Port Value in the UDP Packets it receives to know which Packets are for which InSim Connection?

You want to send with UDP ?? Wright ??
Make sure that you not allway´s set a new connection cause then every time the next Port is chosen. Establish 1 Connection and use this.

greets

Solved
I just had to cut the received stream into pieces

Do you have set a password in LFS.
Ever tried to host a game from your local PC.
If so...remove it.

If I send the following Packet

sTiny.Size = 4
sTiny.Type = E_InSim.ISP_TINY
sTiny.ReqI = 1
sTiny.SubT = E_TINY.TINY_NPL

LFS send back only the first two drivers on Server.
Even if I stop all other procedures in the Tool.

In Last InSim i had to send NPL for each driver. I think now i only have to send this one packet, wright ??

Any hint ???

Last edited by riskredruM, Fri 1 Jun 2007, 10:13.

Quote from buedi :

...... So I can just say Thank you very much

Agree

Solved nearly all Problems.

Ok....i got it

But i have big lags between action in LFS and Displaying in the Tool.
Wenn the SHIFTLIGHT is on in LFS, a button (to show this) apears 1 second later.

The lag is only with OutGauge (UDP). Here is a list of the incoming UDP Packets.

Time size Pack
..
..
41:38--228--MCI
41:49--228-- MCI
41:60--228-- MCI
41:72--228-- MCI
41:75--92--OG
41:85--228-- MCI
41:96--228-- MCI
42:72--228-- MCI
42:19--228-- MCI
42:30--228-- MCI
42:43--228-- MCI
42:54--228-- MCI
42:66--228-- MCI
42:75--92-- OG
42:77--228-- MCI
42:90--228-- MCI
43:90--228-- MCI
..
..

Both is set to 100ms

Last edited by riskredruM, Wed 30 May 2007, 12:30.

Quote from GeForz :

I'm not using .net atm .....

I know ....

Quote from GeForz :

You can find a lot of example code snippets on the net to see how tcp works in vb#

Well, i found many examples and i can connect to LFS. But the packets my tool seems to receive are some how ... hmmm .... strange

I tried so much arround and it is not getting better.

So i thought if someone have a "connect", "send" and "receive" procedures or classes and share it with me i can concentrate on the packets and what to do with them.

Quote from the_angry_angel :

As I understand it LFSLib.NET doesn't support InSim v4 yet -
http://www.lfsforum.net/showthread.php?t=24700

I know. For that i need something else for testing with new Insim.
I hope anyone who do the same with any .net language could give me a little starting help.

Hi
For my last tool I used LFSLib.NET from sdether with vb2005 and earlier vb6.
But now i want to make a bit testing with the new insim.

I understood the packets and can handle them. But i can´t get the tool connect proper to LFS with UDP and with TCP either.

What i need is a little starting help. Perhaps a piece of code for getting in contact with LFS so i can send and receive the packets.

So ... if someone have a funtion or class in vb2005(.net) to handle this it would be nice if i could get it.

Sorry for my bad english

I wrote new one but now ther is a totaly nw InSim Version.
So i will wait until InSim ist finfished and than we will see.

Quote from Soeren Scharf :

hello Scawen,

would it be possible to include the absolute time into the LAP/SPX packets? If a program wants to calculate the gap between 2 cars, it would have to add up the times of all driven laps. But this is not possible if the program is missing the start of the race (eg. if a spectator connected to the server after some laps).

regards Sören

Lap and Node of each car is sent in MCI pack. So you have the position of each driver in the race (Lap * 1000 + Node f.e.). Simply store this information with the time and you can calculate the gap when ever you want to.
No need to add up the times of all driven laps.