The online racing simulator
Searching in All forums
(7 results)
Stephane
S2 licensed
Hi,

I've coded a part of LFS Movie Maker by Peeps, that could analyse the replays to detect the "Hot moments".
This part was included in LFS Movie Maker and scan the replay. It was not done in real time.

If I find this old code, I'll try to put it in a stand-alone app that could point the camera directly to the player that in involved in hot moments.

But I think I have to add some features or thresholds, because at start of a race, all players are to neer each others so the cam will focus about 10 car in a second

I'm actually working on an InSim app for the LFSFrance leagues, so I'm a little busy. I'll try to do my best to make the 2 things in the same time
Stephane
S2 licensed
No problems
Stephane
S2 licensed
Setup data was not my question. I only wanted to know how to be sure that a HLVC replay has been made with our own setup and not driven in Test Drive Mode.
colcob has well understand my problem and oper@tor needs to understand that his sentence is not very wellcome here, in the LFS Programmers Forum.
If cheaters have their own forum, I don't thing that it's hosted by lfsforum.net
Some new InSim packets needed
Stephane
S2 licensed
Hi all, but in particular Scawen

I wonder if it is possible to get some new InSim Non-Verified tracking packets.
Those packets concern the pits opeerations. I thought to :


struct IS_PEP // Player Enter Pitlane (Player enter in the pitlane, when the 3g_enterpit ou 3g_enterfor message is dislpayed)
{
char PEP [4];
char UName [24]; // username
char PName [24]; // nickname
byte UniqueId; // player's assigned unique id
byte reason; // 0=3g_enterpit, 1=3g_enterfor, may be used sometimes
};

struct IS_PPI // Player Pit In (Player stops his car between the yellow marks, when the 3g_x_pitstp message is dislpayed)
{
char PPI [4];
char UName [24]; // username
char PName [24]; // nickname
byte UniqueId; // player's assigned unique id
};

struct IS_PPO // Player Pit Out (Player leave pitlane, when the 3g_leavepit message is displayed)
{
char PPI [4];
char UName [24]; // username
char PName [24]; // nickname
byte UniqueId; // player's assigned unique id
};

struct IS_SWP // SWap Pilote (A spectate player take place in the car instead of another, when the 3g_xtakovrx message is displayed)
{
char SWP [4];
char UName1 [24]; // username gettint out of the car and go to spectate
char UName2 [24]; // username gettint into the car, was spectate
char CName [32]; // car name (can be usefull for some cases)
byte UniqueId1; // leaving race player's assigned unique id
byte UniqueId2; // going to race player's assigned unique id
};

Some of those events can be intercepted by parsing the MSS ou MSO messages, but we are limited to one language and need that the original language file.

Thanks
Stephane
S2 licensed
Yep, Happy Birthday Busta.

20 years old today, 3 years old on LFS so a 3 years old great champion.
Stephane
S2 licensed
I need this info for one of my soft. I looks for all my PB in all the replays to send them on the the LFSFrance Hotlaps web page, but if I (or a player) done an HLVC pb in the "Test drive" mode, this replay has to be ignored (like on LFSWorld)
Replay files formats
Stephane
S2 licensed
Hi guys.

In the S1 version, "Drive Test" was used as the UserName, but in the S2, the real UserName is used and I think the their is a byte inserted in a flag.
I've tried to upload the "Drive test" SPr on LFSWorld but it has been refused, so this info is stored in the file but Scawen forgot to specify where in the SPR file format (here : http://www.liveforspeed.net/?page=SPR)

I've tested others SPR file and the "Player flags" note given in the page seems to be bad.
Does someone knows where is the "Drive Test" flag or byte in the SPR files ?

... 10 minutes after ...

The "Test Drive" and the "TEST DRV" strings are stored at offset $49D and $4B5 in one of my replays used for test... too far to be loaded with the Scawen's struct
I'll try with others files to see if those string are always at the same offset...

... to be continued
FGED GREDG RDFGDR GSFDG