The engine that feeds all the others. It reads the simulator's telemetry once and shares it out to every overlay in the suite.
It isn't an app you use: it's the one that makes the others work. Normally you won't even notice it's there.
Free. Comes inside the suite.
You don't. It starts itself.
When you open RACE, COACH, ADVANCE or LITTLE from the suite bar, the engine starts behind them without you doing anything. When you close everything, it stops.
If you open it by hand you'll see a small window with the status and little else. There is nothing to configure in there.
WHY IT EXISTS Overlays used to read the simulator on their own. Four overlays open meant four programs fighting over the same thing. Now one reads and shares out: that's why you can have several views open without noticing.
IT WORKS LOCALLY The engine only listens inside your own PC. It opens nothing towards the internet: no other computer can connect to it.
IT SURVIVES WINDOWS BEING KILLED If you close an overlay abruptly (or kill the browser), the engine drops that client and carries on. A badly behaved overlay cannot take the others down. This was fixed on purpose, after watching it fall over twice in testing.
THE REFERENCE LAP The engine is what holds the reference lap the other apps compare against. It can:
· serve the reference to the overlays that need it
· RECORD your lap while you drive and turn it into the reference on
the fly, without leaving the trackNone. It is the only app in the house with no settings: it starts, shares out and stops.
The web overlays are blank or say there's no data → the engine isn't
up. Close everything and open the app again from the suite bar: the engine starts with it.
I open an overlay and it can't see iRacing → start the simulator first
and get into a session. The engine doesn't invent data: with no sim, it says so.
I change something in an overlay and don't see it → the overlays are
packed INSIDE the engine. If you are testing a development build, it has to be recompiled to carry the changes. With the normal version this doesn't affect you.
My antivirus complains → the engine opens a local connection to share
the data, and some antivirus software looks hard at that. It only listens inside your PC, never outwards.
It stayed open and I can't see it → it appears in the Windows Task
Manager as PLMOTOR. You can close it from there without any problem; the overlays will restart it when they need it.
Nothing. It's included with the suite and has no licence of its own.
All telemetry stays on your PC. The engine sends nothing to any server: it only reads the simulator and passes it to the windows you have open.