In game: F1 focuses the app, Esc pins it, H hides it while focused.
Optional FiveM binds are registered as ba_save, ba_toggle, ba_waypoint.
Built-in Square / Circle / Triangle triggers also work.
Event log
Speed is derived from consecutive position samples. No API key is required. Identifiers and API keys are never included in diagnostics.
Experimental: requires the local companion helper. The overlay itself cannot press keys inside FiveM. Only use this where server rules allow automation, and test at low speed first.
Live waypoint
Status
Off
Distance
ā
Watcher
Off
Companion
Disabled
Last signal
ā
Auto-brake is enabled but the companion is disabled. No key will be pressed.
Trigger settings
Local companion helper
Run companion/tt_brake_companion.py on the same PC as FiveM. Keep the game focused. The helper presses S for the configured hold time when it receives a signal.
Experimental position-based macro. Requires the companion helper. Record markers at low speed, verify the route, and keep an emergency stop bound. Only use where server rules allow automation.
Live status
Macro
Idle
Vehicle
Not a train
Next action
ā
Position feed
ā
Trigger
Not set
Train macro is enabled but the companion is disabled. No keys will be sent.
Route
0 actions
Macro settings
If the macro aborts with stale-feed, increase this slightly or check the Telemetry feed age. The macro now uses fresh position data even if speed estimation is still settling.
Auto recorder
Opt-in local macro recording. Press Start, drive normally, then Stop. The helper records supported key presses only while recording is active and, by default, only when a window containing the title filter is focused. Keep keys released before stopping.
Recorder
Idle
Key events
0
Position samples
0
Short presses become taps; longer holds become key-down/key-up position markers. For reliable event fetching, load the overlay from the companion itself: http://127.0.0.1:8765/app.
Optional FiveM binds: ba_route_yes, ba_route_no, ba_panic, ba_reset, ba_record_start, ba_record_stop. Click a route step below to edit its key, coordinates, radius, hold time, order, or delete it.
Browser simulator only. This never sends control inputs to the game.
Scenario
Demo driver follows the adviceCruise speed (km/h)
Distance
ām
Speed
ākm/h
Brake
ā%
The simulator feeds synthetic position messages through the same estimator used in game, so you can verify the braking envelope without FiveM.
Start train route?
Start this recorded route?
You can also use the bound FiveM triggers ba_route_yes / ba_route_no.