Apex AIOLe Mans UltimaterFactor 2
LMU Overlays for OBS & in-game
Twenty Le Mans Ultimate overlays in one Windows app: standings, relative, radar, a 3D track map, fuel, tyres, track limits and a working MFD. Send each one to OBS as a Browser Source for your LMU streaming overlay, draw it over the sim as an in-game HUD, or both. They run in the browser OBS already has, need no plugin for LMU, and work with rFactor 2.
- Widgets
- 20
- Track maps bundled
- 32
- Destinations each
- 2
- Hz, your choice
- 1–120
- One price, every widget
- No plugin needed for LMU
- Runs in OBS's own browser
| POS | ± | DRIVER | GAP | AVG | BEST | VE | |
|---|---|---|---|---|---|---|---|
| HYPERCAR6 CARS | |||||||
| 1 | ▲2 | T#7 Conway | — | 3:25.4 | 3:24.892 | 84% | |
| 2 | • | F#51 Pier Guidi | +4.812 | 3:25.9 | 3:25.107 | 81% | |
| 3 | ▼1 | T#8 Buemi | +9.204 | 3:26.2 | 3:25.288 | 79% | |
| LMP29 CARS | |||||||
| 1 | ▲3 | O#22 Albuquerque | — | 3:32.8 | 3:32.114 | 66% | |
| 2 | • | O#34 Smiechowski | +3.551 | 3:33.4 | 3:32.640 | 62% | |
| LMGT312 CARS | |||||||
| 1 | • | B#46 Rossi | — | 3:48.0 | 3:47.552 | ||
| 2 | ▲1 | P#92 Christensen | +2.140 | 3:48.6 | 3:47.998 | ||
| 3 | ▲2 | M#63 Pereira | +12.408 | 3:49.1 | 3:48.201 | P | |
Every LMU overlay in the box
Twenty widgets. Each has its own switch, its own two destinations (an OBS Browser Source and the in-game layer) and its own background-opacity override. All twenty are in the one price.
Standings
The full field with gaps, pit status, driver-rating badges and a last-5-lap pace column.
Relative / timing
Nearest cars on track with live delta, each tagged with its class in that class's colour.
Delta
Live gap to your own best lap, updating as you drive it.
Pace delta
Time and speed delta against session, all-time or last lap.
Reference pace
Your lap as a percentage of alien pace, on Ohne Speed's reference times.
Track map
The circuit as a lit 2.5-D ribbon with every car on it. 32 circuits bundled.
Proximity radar
A spotter's-eye strip drawn to true scale, plus the pit-release light.
Race control
Start lights, flags, sector yellows and pit confirmations — without the stock HUD.
Track limits
Points left, what each cut cost, and penalties named — drive-through, stop-go, DQ.
Speedo cluster
Speed, gear, revs, hybrid battery and aid chips — the panel lights up as revs rise.
Tyre temps
Four-corner temperatures with five view modes, from core temp to a full tyre map.
Pedal inputs
Throttle, brake and clutch trace that makes trail-braking style visible.
Pedals (vertical)
The same channels a quarter-turn round, with steering as a swept needle.
Motion
G-force, rotation and attitude in three independently switchable modes.
Damage & repair
Component damage, repair seconds, and the live stop countdown.
MFD control
The in-game pit menu and driving aids — readable and fully controllable.
Fuel calculator
Per-lap use, laps remaining, fuel-to-finish and your pit window.
Fuel planner
Pre-race fuel and energy plan, live stint timer, fuel-ratio control.
Weather
Current conditions plus the short forecast that decides your tyre call.
Stream chat
YouTube and Twitch chat merged into one scrolling column, Super Chats included.
Relative, radar, fuel and tyre overlays
The widgets below are rebuilt from the app's own drawing code. The data is a representative LMU session, not live telemetry.
| 2 | HY#7 M. Conway | −4.1 |
| 3 | P2#22 F. Albuquerque | −2.9 |
| 9 | GT3#46 V. Rossi | −1.2 |
| 12 | GT3#63 T. Pereira | — |
| 11 | GT3#92 M. Christensen | +1.8 |
| 14 | GT3👻#88 D. Serra | +6.3 |
| 5 | HY#8 S. Buemi | +11.7 |
Speedo · Apex design — LMP2 crews get the Cosworth CDU design instead
Reference times by Ohne Speed
OBS overlays and in-game HUD, one switch each
Every widget has two independent destinations. Streamers use OBS, drivers who never stream use the in-game layer, and plenty run both: a full standings tower for the viewers, a slim relative and fuel readout for themselves.
OBS Browser Source
In-game HUD layer
- Made for
- OBSStreaming
- In-gameDriving
- Drawn by
- OBSThe Chromium instance OBS already runs for Browser Sources. Nothing new starts on your PC.
- In-gameThe app, directly over the sim.
- Placement
- OBSOne URL per widget, copied from its card, so each one sits exactly where your scene wants it.
- In-gameA layout editor: drag and resize each widget over the cockpit, including onto the side screens of a triple-monitor rig.
- Background
- Its own opacity override on every widget.
- Specific to it
- OBSStream chat merges YouTube and Twitch into one column, Super Chats included.
- In-gameRace control brings start lights, flags and sector yellows into your layout, so the stock HUD can go.
The LMU MFD, driven from your wheel
A working copy of LMU's MFD menu, driven from four buttons: race control at the top, LMU's own pit strategy in the middle, your driving aids underneath.
- 1Race controlServing a penalty strips the stop back to no service, and leaves your wing, ducts, pressures and fuel ratio alone.
- 2Colour groupsTyres, pressures, ducts, aero, fuel and brakes each carry a colour, so the menu reads as blocks.
- 3Driving aidsBrake bias, TC, ABS and motor map, on the same four buttons.
- 4Read backEvery value is read back from the game before it's shown. If LMU refuses a change, you see what LMU kept.
- 5Tyre rowOnly offers compounds this car has at this event, and clamps at both ends so one blind press can't cancel the tyres you just booked.
- 6Four bindsUp, down, plus, minus. Put them on a wheel, a Stream Deck or a hotkey and every adjustable row is in reach.
Over LMU's REST API
Pit changes travel over LMU's own REST API. The in-game MFD never has to be on screen, and the game doesn't need to be the focused window.
Key-binding helper
The overlay presses LMU's own key bindings, and a wheel-only binding can't be pressed from outside the game. So the app finds what's unbound and binds it in one click, using scancodes no keyboard produces. Your existing binds aren't touched, a timestamped backup is taken first, and there's an undo.
32 circuits bundled · the rest learned from your first lap
3D track map overlay
The radar tells you who is beside you. The track map shows where everyone is: traffic two corners ahead, the real gap to the car you're chasing, and whether a yellow is on your part of the circuit.
- 0132 circuits in the boxLe Mans, Spa, Monza, Sebring, Fuji, Imola and the rest of the LMU and WEC calendar.
- 02Everywhere else, learnedBuilt from your first lap, cached locally, drawn instantly after that.
- 03True world coordinatesA car running wide is drawn running wide.
- 04Your car carries the gradientEveryone else is in class colour. Pit lane is faded.
The circuit is a raised 2.5-D ribbon with a dot for every car in the session, lit as one material by one light. Each segment is shaded from the direction the road runs, so a straight and the corner it feeds read as two faces of one solid. Elevation is exaggerated and the road is extruded down to a ground plane, so a climb reads as the track pulling away from its base. Two styles ship: the classic red shown here, and a brand style that runs cyan at the start line to pink at the end of the lap.
LMU packs its circuits into encrypted archives, and no API exposes the shape of the road. The sim does publish where your car is thirty times a second. So the first time you drive an unknown track, the widget builds the map from your own lap, caches it locally and draws it instantly every session after. There's no per-track setup, at any LMU or rF2 circuit.
Track limits and pit-stop overlays
One tells you how many more careless kerbs you can afford. The other tells you what the next stop will cost.
LMU track limits overlay
- A wheel over the line
- 0.25
- A cut that gained time
- 1.00
Three 0.25s in a row is one kerb you clip every lap.
A single 1.00 is a mistake already made.
LMU charges each cut on the time it gained and issues a drive-through when your running total reaches the session's allowance. The headline number counts down, because that's the one you act on: “1.75” means a couple more careless kerbs and you're in the pit lane.
Penalties are named when they land (DRIVE THROUGH, STOP-GO 10S, even “serve within 3 laps”) and confirmed with PENALTY SERVED once paid. A rival's penalty online never touches your count.
Pit-stop predictor
Shown side by side — never summed
- Repair
- The sim's own live estimate, rounded up to the nearest 5 s so it matches the message on your screen.
- Tyres
- Priced separately and shown beside the repair time. Never summed.
- In the box
- The slot becomes a countdown to release, with a progress bar.
- Past zero
- It keeps counting and says so. The booked time is a floor: LMU adds a random delay at the stop and publishes only the cap.
“Absolutely every LMU Apex & Chill member really should try this app. You will not be disappointed.”
The lightest LMU overlays you can run
How it compares
Most overlay tools launch a second browser and draw your telemetry in it. That is a whole extra renderer competing with the sim for GPU frames.
Apex AIO's overlays are plain HTML and JavaScript, rendered by the Chromium instance OBS already runs for Browser Sources. On stream, nothing new starts. The setup workshop, StreamBot and the voice race engineer live in the control panel, not in your stream.
Spec sheet
- Second browser
- None. Nothing launches beside the game to draw the overlays.
- Runtime downloads
- None. Native fonts, no CDN.
- Blur and backdrop filters
- None. They are the expensive part of a glassy overlay.
- Audio cues
- Synthesised from an oscillator, not played from files.
- Track map
- ~40 KB per circuit, drawn once then blitted each frame.
- Telemetry rate
- 30 Hz default, 1–120 Hz on one slider.
- Frame size
- ~1–2 KB of JSON over loopback, serialised once for every source.
rFactor 2 overlays, and where the data isn't there
The standings, relative, radar, track map, speedo, motion, pedals and fuel widgets work on rFactor 2 as well as LMU. The MFD, race control, track-limit, damage and setup features depend on data rFactor 2 doesn't publish, so on rF2 they read “no data” rather than showing a plausible zero.
Track-limit charges can arrive up to ~25 seconds late because of how LMU flushes its log. The total is right, sometimes late. Repair and tyre times are shown side by side rather than added, because whether they overlap hasn't been verified against a real stop.
Set up in OBS in minutes
Nothing to configure by hand. Open the app, tick what you want, paste a URL.
- 01
Install and sign in
One signed Windows installer, no SmartScreen warning. Create an account and start the 7-day trial. The server starts itself when the app opens.
- 02
Tick the overlays
Each widget is a card with a switch for OBS and a switch for in-game. One can be on and the other off.
- 03
Paste a URL into OBS
Copy the widget's Browser Source URL from its card into your scene. Or skip OBS and drag widgets over the sim instead.
- 04
Updates wait for you
The telemetry plugin installs itself. New versions are announced in the app and never installed for you, so an update can't interrupt a live stream.
LMU overlay questions
Why is Apex AIO lighter than other LMU overlays?
The overlays are plain HTML and JavaScript, rendered by the Chromium instance OBS already starts for Browser Sources, so nothing extra is shipped or launched. An overlay tool built on its own Electron app keeps a second full Chromium and Node process running for your whole stream. The widgets also skip web fonts, CDNs, and blur or backdrop filters. Telemetry is 1–2 KB per frame over a loopback WebSocket, at a rate you set.
Can I change my pit strategy from the overlay?
Yes. The MFD widget mirrors the sim's own pit menu and driving aids, and every adjustable row can be driven with four bindable buttons (up, down, plus, minus) on a wheel, a Stream Deck or a hotkey. No other LMU overlay does this. Pit changes go over LMU's REST API, so the in-game MFD never has to be on screen and the game doesn't need to be the focused window.
Are the track-limit points accurate?
Yes. They're the sim's own numbers. LMU writes its stewarding to its trace log, and the overlay reads that log. The reader was validated against a real session-end results file and reproduced every charge from that race, in order. Penalties use the stewards' wording (DRIVE THROUGH, STOP-GO 10S) with a PENALTY SERVED confirmation, and a rival's penalty online never touches your own count. One caveat: LMU flushes the log in blocks, so a charge can show up to ~25 seconds after the cut. The final total is always correct.
How do I add an LMU overlay to OBS?
Install Apex AIO, sign in and start the trial. The overlay server starts itself when the app opens. Tick the widgets you want, copy each one's Browser Source URL from its card, and paste it into a Browser Source in your OBS scene. There is nothing to set up in a terminal, config file or game directory; Le Mans Ultimate works out of the box over its own REST API.
Are all the LMU overlays included in the subscription?
Yes. There is one plan: 7 days free, then £4.99 a month. It includes all twenty widgets in both destinations (OBS and in-game), the race engineer, setup tools, pit wall and every update. There is no cut-down tier and no widget held back as an upsell.
Can I use the overlays without streaming?
Yes. Every widget has two independent destinations: an OBS Browser Source, and an in-game layer drawn over the sim itself. If you don't stream, use the in-game layer and the layout editor to drag and resize each widget where you want it over the cockpit, including onto the side screens of a triple-monitor rig. Streamers use OBS. Plenty of people run both at once.
How do the 3D track maps work?
32 LMU and WEC circuits ship bundled and draw as soon as you load in. For any other track, the widget builds the map from your first lap. LMU packs its circuits into encrypted archives and no API exposes the shape of the road, but the sim does publish your car's position 30 times a second. The map is then cached locally and drawn instantly in every later session. There's no per-track setup.
What are the best LMU overlays?
It depends what you race with, but a good Le Mans Ultimate set covers timing, traffic, the car and strategy. Apex AIO ships twenty widgets for that: standings, relative, delta, proximity radar, fuel calculator, tyre temps, pedals and a speedo cluster. It also has a fully working MFD you can drive from your wheel, track limits in the stewards' own points, a pit-stop predictor built from the sim's repair estimate, a 3D track map with 32 circuits bundled, and your pace against Ohne Speed's reference times. Every one runs in OBS's own browser or over the game, and all of them are in the one price.
Can I change how often the overlays update?
Yes. Telemetry is sent at 30 Hz by default, and one slider takes it anywhere from 1 to 120 Hz. Each frame is compact JSON of around 1–2 KB over a loopback WebSocket, so it never leaves your machine, and it is serialised once and shared by every source rather than re-encoded per widget.
One app, one price
- 01Apex AIO SystemLMU overlays, a voice race engineer, community setups, a team pit wall and lap telemetry in one Windows app for Le Mans Ultimate. Free for 7 days.
- 03LMU Race EngineerA voice race engineer for Le Mans Ultimate. Press a wheel button, ask for gaps, fuel or pit windows, and get the answer from live telemetry, offline.
- 04LMU SetupsLe Mans Ultimate community setups ranked by verified lap times, plus a live setup editor and optimiser. Send any setup straight into LMU.
- 05LMU Pit WallA live Le Mans Ultimate pit wall for endurance teams: timing, fuel strategy, tyres, weather and the track map, in the app or any browser.
- 06LMU TelemetryLe Mans Ultimate telemetry on your own PC: every lap you've driven, your optimal lap, and two laps compared corner by corner.
Try it free for 7 days
Every LMU overlay, in OBS, over the sim or both, plus the race engineer, setups, pit wall and Review in the same app. Install it before your next session.
- Platform
- Windows
- Trial
- 7 days
- Then
- £4.99/mo
Everything included. One plan.