League Night Stability Checklist for Assetto Corsa Players
admin
AC Supply Team
League racing turns small software issues into DNFs for your whole division when you disconnect or CTD mid-pack. Private lobbies often require exact car packs, track builds, and sometimes CSP expectations. This checklist is the boring ritual that keeps you on track—literally.
Seven days out: confirm the content manifest
Read the steward post twice. Download the exact car and track versions they list. If your team shares a Google Drive or checksum tool, use it—do not “close enough” a BoP update.
Bookmark browse entries you installed so you can re-verify filenames if admins push a hotfix.
Write down three numbers somewhere sticky: server IP, session start time in your local timezone, and the Discord channel where stewards post hotfixes. Panic searches cost grid slots.
Two days out: dry run the combo
Launch offline with the same car, same track, and similar weather settings. Note FPS and stutters. If you spike thermals on GPU or CPU, clean dust filters and close background stream software before race day.
Include AI traffic density similar to race night if your league starts with formation laps or pit exits—some stutters appear only with twenty cars on screen, not solo.
Day of: controller and power
Charge wheels with built-in batteries, replace AA packs in wireless kits, and tug USB cables to confirm seating. A disconnect under braking is not a story anyone wants to tell.
Day of: CSP and video profile
Load your league profile: often a conservative CSP page for stable frame times rather than cinematic rain. Screenshot the page so you can restore it if someone “helps” you tweak settings an hour before grid.
Day of: disk space and AV
Ensure 10+ GB free on the drive holding content—logs, replays, and temp extracts add up. Pause aggressive real-time AV scanning only if you already use narrow exclusions; see antivirus notes.
Thirty minutes before: reboot once
A fresh boot clears memory leaks from browsers and clears Windows Update nag states that steal focus. Close RGB suites that love overlays.
Open Task Manager and sort by GPU and CPU—nail obvious hogs before you join voice chat. Update VoIP clients the day before, not five minutes to green light.
If something breaks during warmup
Do not panic-install new mods between sessions. Revert to known-good folders from your backup and join the next round clean.
FAQ
Should I update CSP race week?
Only if the league mandates it—otherwise stability beats novelty.
What if ping spikes?
That is network path, not car mods—wired Ethernet first.
Can I stream?
Test encoder load beforehand; NVENC/AMD variants differ.
Leagues reward preparation, not heroics in the pits menu. Run the checklist once; it becomes muscle memory.
Screenshot your final CM car list the night before—if something updates automatically, you can spot the drift before join fails.
Keep a paper notepad for incident notes during the race: lap, symptom, what you changed. Stewards love specifics when protests involve netcode versus hardware.