The online racing simulator
Searching in All forums
(53 results)
Knu
S2 licensed
Quote from Victor :i'm confused

1) 0C is that the length of the IS_NLP packet? Shouldn't that be 84 (hex)?
2) there is no position indication in a nodelap packet (see your post title)
3) what is the problem you are aiming at? Just the bold 00 doesn't tell me much tbh

InSim.txt:
struct NodeLap // Car info in 6 bytes - there is an array of these in the NLP (below)
{
word Node; // current path node
word Lap; // current lap
byte PLID; // player's unique id
byte Position; // current race position : 0 = unknown, 1 = leader, etc...
};

struct IS_NLP // Node and Lap Packet - variable size
{
byte Size; // 4 + NumP * 6 (PLUS 2 if needed to make it a multiple of 4)
byte Type; // ISP_NLP
byte ReqI; // 0 unless this is a reply to an TINY_NLP request
byte NumP; // number of players in race

NodeLap Info[32]; // node and lap of each player, 1 to 32 of these (NumP)
};

Thanks for your reply!

1) x0C is 12 and is perfectly fine as (4 + 6*1 + 2).. or am i missing something?
2) well, the InSim.txt says otherwise this might be one of the new features.
3) the problem is that byte 'position' is always zero.

Sorry for any confusion
Insim problem: "position" in IS_MCI/IS_NLP is always zero
Knu
S2 licensed
This is very confusing. First I thought the problem was my app, but I checked, and the packet analyzer shows, that the rest of the packet is perfectly ok. For example an IS_NLP: ( 0C 25 00 01 24 00 03 00 04 00 00 00 ).

Tested on W43 and W47, with 1-6 players - same thing.
Knu
S2 licensed
Hi, this library is absolutely helpful, thanks!

I noticed tho, that the IS_MCI's Position bytes are always 0, maybe that's not exactly news for you, but I hope you fix this in your next release.
FGED GREDG RDFGDR GSFDG