What you need
A 64-bit Windows PC, Assetto Corsa Competizione, a Discord account and an internet connection for community, upload and update features.
DeepCoach is a self-contained Windows client. It reads ACC telemetry, shows live inputs and sends eligible recordings into the ROI coaching chain.
Understand the system
- ACC produces the live car, track, lap and input telemetry.
- DeepCoach Client reads, records, displays and uploads eligible telemetry.
- DeepCoach Server accepts and stores recordings and serves client data.
- Discord Bot links your ACC driver name to Discord and shows available reports, comparisons and learned-track tools.
THE CHAIN: ACC → DeepCoach Client → DeepCoach Server → DeepCoach Discord Bot. Four links, zero magic smoke.
Your community. Your driver name.
Join and accept the rules
Open the rules channel and use the join button. Look for the ACC and EVO role choices as the channel layout is updated.
Link in Discord
Use /link acc_name and choose your exact ACC driver name. A DeepCoach client link code is no longer required for community linking.
Need another name or a correction?
Use the available link commands or ask Race Control to check the account mapping before unlinking or changing another profile.
EVO chill driving and Discord votes do not require the DeepCoach client. Install it only for the ACC features you want to use.
Download, extract and start
Download the official ZIP
Use only the DeepCoach download button on this site. The current package is supplied as a ZIP containing ROI.DeepCoach.Client.exe.
Extract the entire ZIP
Fully unpack the ZIP into its own folder and keep every extracted file together. Do not run only the EXE from inside the archive, because the client needs the full extracted package.
Run the client and set your ACC name
Start ROI.DeepCoach.Client.exe. On first launch, enter your exact Assetto Corsa Competizione driver name. This name connects your laps to your DeepCoach profile.
Link your ACC name in Discord
Use /link acc_name in Discord. Community linking no longer requires a one-time code from the client.
Let updates finish
Automatic update checks and automatic installation are enabled by default. Before driving, make sure no required update or configuration message is still open.
LOCAL DATA: The standard client data folder is C:\ROI_DeepCoach_Client\data. Do not delete it while troubleshooting recordings or pending uploads.
WINDOWS WARNING: Early development builds may trigger a Windows reputation or security warning. Continue only when the ZIP came from the official RacenOnderInvloedTHC download. If the source or package name looks wrong, stop and ask in Discord.
Connect the car to the coach
Start ACC and DeepCoach
The application start order does not matter. What matters is that DeepCoach is running and connected before you begin the lap you want recorded.
Find the ROI server
In ACC, open Multiplayer, go to the online Server List and search for the exact server name RacenOnderInvloedTHC | Chill Practice | Personal & Weekly & All-Time Records in Discord | discord.gg/m3bNHDgRuh| Nurburgring 24h | ROI #1.
Enter the server
Once ACC is LIVE with a recognized track and car, DeepCoach should connect automatically and begin reading telemetry. The current client records from ACC's LIVE, track and car state; it does not rely on a verified hard-coded server-name gate.
Verify live inputs
Move the car and confirm that live throttle, brake and steering values change in the client and overlay. A green-looking status with frozen inputs is not proof of a working telemetry feed.
START BEFORE DRIVING: If DeepCoach comes online after your lap has already started, the first physical finish may only synchronize the lap boundary. Start a fresh lap after the client is active, or your hero lap may be fast, smoky and useless to the coach.
Create data the bot can use
Drive the Nürburgring 24h layout
Run the community's N24 environment with DeepCoach active before the lap begins.
Complete a clean lap
A complete valid Nürburgring 24h lap is required for records, rankings, pace roles and pace-based nicknames. Partial or invalid laps may still contain telemetry, but they do not satisfy those valid-lap features.
Let the session finish and process
If you expect new session statistics in Discord, let the session end naturally—by the timer expiring or everyone leaving—and allow upload and processing time before checking the bot.
IMPORTANT: A valid lap is not required to link your Discord account. Valid laps are only needed for records, rankings and pace roles.
Know what is live, BETA or planned
Pedal Trace and the Records Overlay are implemented normal features. Live throttle, brake, steering input and current records can be viewed in the client and overlay.
Baked Braking, richer trackmap options, zoom and supported layers are BETA features where available. Enable BETA Mode deliberately to see them.
The learned track path and your own line exist, with reference and layer support still depending on available telemetry and client build.
SteamVR overlay support is not a finished public feature yet. Normal desktop overlays remain the supported route for now.
- Enable only the overlays that help you drive.
- Position them away from essential ACC information.
- Test layout changes in practice before using them in traffic.
- If the cockpit gets too crowded, turn some overlays off.
Let DeepCoach move the data
Automatic telemetry uploads are enabled by default. When the server is reachable, the client packages eligible recordings and uploads them for storage and later use by DeepCoach tools.
- Keep DeepCoach open long enough for pending work to complete.
- The client upload package limit is 25 MB.
- A local or queued recording is not the same as a processed Discord result.
- Do not repeatedly import the same session unless support asks you to.
- Do not delete
C:\ROI_DeepCoach_Client\datawhile troubleshooting.
ADVANCED DIAGNOSTICS: Full raw ACC shared-memory recording is off by default. Enable it only when support asks for detailed telemetry diagnostics, as it creates much larger recording files.
Turn laps into community tools
The Discord bot links your Discord account to your DeepCoach driver profile and exposes the functions available to your role. Start with Discord's slash-command autocomplete; some commands are restricted by role or development status.
Use /link with the one-time code from the DeepCoach Client. Use /me to check your linked identity and current driver information.
Available /deepcoach tools include latest data, facts, your line, recordings, learning status and track-map information.
Role-gated tools can include driver comparisons, corner comparisons, corner learning and self-learning commands.
/deepzoom can request a high-resolution zoom of the learned track map. Map and reference features still depend on available learned data.
WHAT /LINK DOES: /link connects Discord to the same DeepCoach profile used for records, nickname time, pace roles, teams, garage sharing and race registrations.
Read the evidence correctly
Inputs, lap and sector timing, detected car state and other values supplied directly by ACC.
Comparisons, learned references and recommendations calculated from available data. These require enough reliable laps and may carry uncertainty.
A practical review loop
- Choose one section, such as Karussell or Pflanzgarten.
- Compare one behavior at a time: braking, release, steering, throttle or minimum speed.
- Change one thing in the next stint.
- Record another representative lap.
- Compare the result before drawing a conclusion.
BETA means optional and buggy
Baked Braking is the current BETA-only coaching feature. BETA Mode, Baked Braking and voice are off by default. Only enable them when you deliberately want to test experimental behaviour.
DO NOT TREAT A BETA PROMPT AS FACT. Baked Braking can have bugs. If distance confidence is missing, the track is incomplete or telemetry becomes unreliable, disable BETA Mode and rely on direct inputs, timing and track knowledge. A baked coach is funny; confidently wrong braking advice is not.
Quick checks before asking the pit wall
| Problem | What to check |
|---|---|
| Client does not see ACC | Enter an ACC LIVE session with a recognized track and car. DeepCoach may start before or after ACC, but it must be active before the lap you want recorded. Confirm that throttle, brake and steering values actually change. |
| Overlay is missing | Set ACC to borderless fullscreen and press F11 twice to reapply the display mode. Then confirm the overlay is enabled, on-screen, inside the current display and receiving live telemetry. |
| First lap is not valid in DeepCoach | If the lap began before DeepCoach connected, the first finish may only synchronize the lap boundary. Begin a fresh lap after the client is active. |
| Lap is not uploaded | Keep DeepCoach open, check connectivity and leave the local data folder intact. Automatic uploads are on by default, but a recording still needs time to package and upload. |
| Discord pace role or best lap is missing | Confirm Discord is linked through the one-time code from the DeepCoach Client, then complete a valid Nürburgring 24h lap. Let the session end and allow processing time. |
/link code expired | Create a fresh code in the DeepCoach Client under Settings → General → Link Discord, then run /link again in Discord. |
| Windows warns about the EXE | Verify that the ZIP came from the official link on this site. Do not bypass warnings for a copy received from an unknown source. |
| Data or coaching looks wrong | Stop relying on the affected output. Record the client build, track, session, exact symptom and whether direct live inputs were correct. |
| Client is outdated | Let the built-in update check complete or download the current official ZIP. Preserve the local data folder unless support explicitly tells you otherwise. |
When you need help
Open the Discord text channel #tickets and create a support ticket with the ticket system there. Include the DeepCoach build, Windows version, ACC track and session, what you expected, what happened and the exact steps that reproduce it. Add screenshots and relevant logs when possible. Never post credentials, upload tokens or private configuration.
BEST BUG REPORT: exact build + exact session + exact steps + screenshot. Clear evidence beats guesswork every time.