FPS Troubleshooting Order of Operations for Assetto Corsa and CSP

Low FPS in Assetto Corsa is a symptom, not a diagnosis. Players often jump straight to Custom Shaders Patch ultra presets or reinstall the entire game while a single overlay or a modded Nürburgring packed with objects is the real culprit. This article gives an order of operations that saves time.

Use it alongside our performance optimization guide for deeper tuning ideas.

Layer zero: measure honestly

Pick a fixed test: same track, same time of day, same camera mode, same number of AI cars. Note average FPS and 1% lows if your overlay can show them. Changing the scenario between tests invalidates comparisons.

Close RGB software, aggressive antivirus real-time scanning on the game folder, and browser video on a second monitor—each has caused “mystery” stutter reports.

Layer one: resolution and frame caps

Drop resolution one step or enable a sensible frame cap to see if GPU headroom returns. If FPS barely moves, you may be CPU-bound (physics, AI, draw calls on huge grids). If FPS jumps, you were GPU-bound—now tune graphics, not physics threads.

Layer two: in-game video basics before CSP micro-sliders

Confirm fullscreen vs borderless behavior on your setup—some systems lose performance in borderless due to compositing. Disable redundant MSAA stacks if you already lean on post-AA. Turn off motion blur if you dislike it anyway; small savings add up on weak GPUs.

Layer three: CSP categories by cost

Inside CSP, tackle shadows, reflections, and weather-heavy effects as separate passes. Do not enable rain, max mirrors, and ultra shadows simultaneously and then ask which one hurt. Revert to a known-good CSP page screenshot between attempts.

Layer four: AI count and visible opponents

Large AI grids hammer CPU and increase draw calls. Test solo, then add AI gradually. Online leagues with full grids are the worst case—tune for that scenario if that is your main use.

Layer five: modded track complexity

Some community tracks include enormous scenery counts. If FPS collapses on one venue but not others, the track is suspect. Try a Kunos baseline track with the same car and CSP profile to confirm.

Layer six: storage and streaming hitches

Stutters that feel like “hitching” rather than low average FPS can be shader compilation, drive latency, or texture streaming from slow disks. Moving the game and content library to a faster SSD is a valid fix—not every problem is a shader toggle.

When to ask for help with useful data

If you post “low FPS pls help” without GPU, CPU, resolution, CSP version, solo vs online, and track name, you will get generic answers. Add a screenshot of your CSP video page and note whether the problem started right after a single mod install. That one detail often identifies the culprit immediately.

FAQ

Should I disable CSP entirely to test?
Temporarily testing vanilla can isolate CSP, but remember features like extended lighting are gone—compare fairly.

Does reinstalling help?
Rarely, unless files are corrupted. Backups first—see backup guide.

Is DLSS or FSR always on-topic for AC?
Depends on your exact pipeline and addons; treat upscalers as another variable with their own artifacts.

Discipline beats superstition. Walk the layers in order, change one major variable per test, and your FPS story becomes understandable instead of chaotic.