After reading about, and getting involved in a post by scania regarding making a 2 way RoC course, I thought I'd try making my own autox layout with autox and InSim checkpoints.

If you complete a lap using the normal LFS start position, checkpoints and finish lines, it all works as normal.

However, I'm finding that when I start from a autox start position, cross the InSim checkpoints, then the InSim finish line, there are timing problems.

Issues that I'm having;

Firstly, spawning points from garage are different.

Secondly, there's a huge difference in time (approx 11+ secs) between the LFS timer, and the InSim timer.

Thirdly, in normal autox mode, a timed lap is from green light, to crossing finish line. In InSim timing mode, a timed lap is from green light to crossing normal finish line 2nd time.

My InSim start is half lap from normal start, so you have to do lap and a half to get a finish time.

Anyone else used the InSim checkpoints?

Did you note any discrepancies?

Is this an InSim issue, or an LFS autox issue?

I've loaded a lap on YouTube to show results.



InSim start line is half way round lap.

Used all 3 autox checkpoints and autox finish line, and all 3 InSim checkpoints and InSim finish line on the layout. For video, start position 1 in front of InSim finish line. Originally, I had start position 1 in front of autox finish line, and start postion 2 in front of InSim finish line, but as I'm testing alone, kept them in same position, but changed start position numbers round in edit mode.

I've broken down my observations, especially the timings.

LFS Route = standard checkpoints and finish line
- start position 1 in front of finish line, and start postion 2 in front of InSim finish line
- leave garage and spawn off track. Shift R to start race, spawn on start 1 position
- recorded lap time is from Green light to crossing finish line

InSim Route = InSim checkpoints and InSim finish line
- start position 1 in front of InSim finish line, and start postion 2 in front of autox finish line
- leave garage and spawn on start 1 position in front of InSim finish line
- recorded lap time is from green light at InSim start, crossing LFS start position, crossing InSim finish line, to crossing LFS finish line

Splits -

InSim lap time => 1:42.90 - 0:13.74 = 1:29.16 from standing start
LFS lap time => 2:25.32 - 0:59.01 = 1:26.31 from rolling start (at full speed)

Had a thought about the timing, so checked.

I thought maybe the InSim timer starts when you spawn onto the start position, rather than when the green light comes on. Almost right. But time taken between spawning on start position to crossing checkpoint line takes about 11 seconds.

Still 2 seconds too short

thx for your test

Could it be that timer starts when you spawn to your start position and ends when you cross a checkpoint, where the extra 2 seconds are about the time it takes before the line goes green?
If I remember well, the starting lights have slightly different timeframe in which it operates.

I really don't know what's happening.

To make sure I wasn't doing anything silly, I made new layout and set checkpoints.



Then I did a couple of laps in UF1 to see what happens with times.



The top time that refers to the Finish Line, is me crossing it as a start line. Thing is, in a UF1, it takes over 2 seconds from green light, my reflexes, overcome inertia, move and cross line.

As you can see from Run 1 and Run 2, there are differences in the time recorded to cross checkpoint/finish line, and time recorded for Racetime. By that, I mean in 1st run, difference in Checkpoint 1 time is 0.04s, but 2nd run is 0.32s.

If anyone wants to test this, I have included copy of my layout.

The only code I've changed in the standard lfslapper file, is...
I'm using very latest version of lapper, including new .exe file in previous posts.

Edit: Added video of 3rd run onto YouTube

I'm a bit tired and need a break, but I think that time that is reported is the time since the restart or race entry. I guess the same time you would see on the replay slider bar.

It is equivalent to the times reported by a SMALL_RTP packet. Also the same times are reported in ISP_CSC packets.

It's not relative to the time the lights went green. I think the idea is that the external program can take control of the lights.

I did a straight 2 lap race with a log for UCO, SPX and LAP if that's any help

Quote from Racon :

I did a straight 2 lap race with a log for UCO, SPX and LAP if that's any help

Its probably going to take a programmer to work out what all that means, but thanks anyway - much appreciated.

However, didn't stop me trying to make sense of at least some of it, and I think I have.

The first 3 ETime's appear to show the sector times, and the next is the lap time. The next again 3 ETime's are the 2nd lap sector times, followed by the full race time.

In between we have LTimes - 1st lap time (= ETime) and 2nd lap time (with ETime = to lap1 + lap2).

UCO Raw, SPX Raw and Lap Raw numbers mean nothing to me.

UCO Time - is this the LFS checkpoints rather than the InSim checkpoints?

Sorry, 'raw' is just a dump of the whole packet by byte. SPX is a split, LAP is the finsih, and UCO is an insim checkpoint. The lines directly below the raw are the timing information extracted from each packet.

I'm a bit confused as to what's supposed to happening where with that track, so I just dumped the lot in case you could figure it out just from the timings

I'll try on a simple test track later on to get my head around it

Right, so, I made a simpler layout with 3 checkpoints and a finish, with an insim split over each one. I've added the replay and the layout if it's needed. I did two laps, and the log is below.

The good news is that the gap looks consistent That was my big worry from earlier in the thread.

(The first UCO time is the time it takes from /restart to green lights + reactions + inertia)