If you're set to use 2048 res skins instead of 1024 it'll want credit to download them... but then it should skip that part with the skins in the folder, no?

Done a race restart too? (If you change a skin, it's shown as blank white on other clients until next optimise at race start, etc.

We can rebind keys with scripts - there is an example for setting up using one button to cycle through the f9-f12 info in the docs here.

If I'm understanding it correctly, Scawen is saying you need to control the lights yourself if you want to know when they're green. The actual moment the standard lights change to green is hidden from insim (I think for foiling scripted launches) when it happens. You can work out the exact start time as soon as the first car hits the first split, but not until then.

The insim-controlled lights do lag the control packet being sent a little though, so you wouldn't have an exact time doing it through insim.

You could use an insim checkpoint on the start line to get a reference, but it wouldn't quite be on green, it'd be green + reaction time + inertia.

Maybe use both methods and tune a ratio between them

Quote from SimulatorRental.com :

Hopefully in the future, LFS, will have a color pallet value allocated as a background color (clear), that can change without changing the whole graphics color.

In the meantime I could knock you up a webpage where you upload a PNG skin with transparency, play with a colour selector to get the colour you want, and click a button to download a coloured JPG version.

I've been meaning to do it for a while, but it's been one of too-many things I want to get to

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)