Recommended Free Tools
For a dependable public drift server, begin with EnableAi: false, tyre blankets enabled, Old or Green track grip at 95–97%, Factory ABS and traction-control policies, 100% fuel, damage and tyre-wear rates, and one identical CSP requirement for every player. Then validate the rules with a second driver before opening the server. This combination gives predictable temperatures, enough slip to initiate a drift, and a fair baseline that works for mixed-skill events.
The recommended baseline at a glance
Use the following preset when you need a neutral starting point rather than an arcade lobby or a punishment-focused competition. It is intentionally conservative: change one variable at a time after a representative stint so you can identify what actually improved the session.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Assetto Corsa Ultimate Edition (PS4) | $24.75 | Buy on Amazon |
| 2 |
|
Assetto Corsa Competizione - PlayStation 5 | $28.00 | Buy on Amazon |
| 3 |
|
Assetto Corsa Competizione | $22.99 | Buy on Amazon |
| 4 |
![Assetto Corsa Competizione Racing Simulator, Standard Edition, PlayStation 5 [video game]](https://m.media-amazon.com/images/I/51LNe6u91RL._SL160_.jpg)
|
Assetto Corsa Competizione Racing Simulator, Standard Edition, PlayStation 5 [video game] | $24.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Category | Starting value | Why it belongs in the baseline |
|---|---|---|
| AI traffic | EnableAi: false |
Removes unexpected traffic and wrong-way interactions from a pure drift session. |
| Tyre blankets | Enabled | Cars leave the pits with a consistent temperature and grip reference. |
| Track surface | Old or Green, 95–97% | AssettoHosting’s 2026 drift guide says this reduces mechanical grip and makes initiating a slide easier. |
| ABS and traction control | Factory for a mixed public event | Assetto Servers identifies Factory as the sensible default when cars and driver ability vary. |
| Stability control | Off for competition; optional for beginners | Preserves realistic car behavior without preventing new drivers from learning. |
| Fuel, damage and tyre wear | 100% each | Assetto Servers’ normal starting point; tune rates only after a representative stint. |
| CSP policy | Declare a minimum and keep every client on the same build | Prevents feature, physics and scoring differences between players. |
These are server rules, not a guarantee that every car, track and controller will feel identical. Mod tyres, weather scripts and track surfaces can still alter the result, which is why the validation procedure later in this guide matters.
Why drift settings need a controlled baseline
Drifting is unusually sensitive to small changes in grip and temperature. A car that leaves the pits cold can feel reluctant to rotate, while the same car after several laps may gain enough rear grip to change its entry speed and steering angle. If one player has warm tyres and another does not, a leaderboard measures preparation and timing rather than driving.
#1 Best Overall
- Assetto Corsa Base Game
- Prestige Pack
- 3x Porsche Packs
- Red Pack
- ReadyToRace Pack
Traffic creates a separate problem. AI cars can appear on a line, trigger contact penalties or produce wrong-way situations while a driver is deliberately transitioning across the track. Disabling AI is therefore a performance and fairness choice, not merely a way to reduce processor load. If your event is specifically a traffic-drift or touge format, treat traffic as a separate ruleset and test it independently instead of mixing it into this pure-drift preset.
Install and configure AssettoServer
1. Put the server files in the correct folder
Install or extract AssettoServer in Assetto Corsa’s server folder and launch AssettoServer.exe. Keep a backup of the original configuration files before making changes; a clean copy makes it easier to isolate a bad rule or malformed YAML entry.
2. Edit the two configuration files
Use server_cfg.ini for the conventional server, session and assist settings, and extra_cfg.yml for AssettoServer-specific options. Set the AI switch to EnableAi: false, enable tyre blankets, and apply your chosen assists, rates and penalties. Preserve the existing key names and indentation in the YAML file; a visually minor spacing error can prevent the extra configuration from loading.
3. Restart after every rule change
Stop the process, save both files, and start AssettoServer.exe again. Do not assume a live edit has been accepted. Apply the rules, wait for the server to confirm them, and restart before asking drivers to join. A restart also clears stale session state that can make a corrected setting appear ineffective.
4. Confirm the public join path
Join once with a normal driver account rather than an administrator account. The ordinary account should see the same assists, voting permissions, pit behavior and penalties as the people who will actually compete.
Track grip, tyre temperature and weather
Choose the surface state
AssettoHosting, in a guide published in 2026 by Sergi Garzón, recommends the Old or Green surface state at 95–97% for drifting. The lower mechanical grip makes initiation easier and gives drivers room to hold angle without requiring an extreme setup. Pick one value for the whole event; do not let individual sessions silently switch between 95%, 96% and 97% if you intend to compare scores.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use blankets to remove a needless variable
Tyre blankets should be enabled for this baseline. They do not make every compound equal, but they remove the cold-out-lap lottery. Without them, a driver who starts a judged run immediately after leaving the pits can be penalized for temperature rather than technique.
Keep weather and track state fixed during scoring
Lock weather, track condition and time-of-day for a ranked session. Night-lighting, weather and track features supplied through Custom Shaders Patch (CSP) can change visibility and, depending on the car or track implementation, the available physics features. If you want changing weather for a casual lobby, publish separate runs and never combine their points with a fixed-condition leaderboard.
Rank #2
- Assetto Corsa Competizione allows you to feel the real atmosphere of the GT3 championship
- Compete against official drivers,teams, cars circuits reproduced in game with the highest level of accuracy ever achieved on console
- Sprint, Endurance, and Spa 24 Hours races come to life with an incredible level of realism, in both single and multiplayer modes
Assists: accessibility versus competition
| Policy | Best use | Trade-off |
|---|---|---|
| Factory ABS and traction control | Mixed-car public events and beginner-friendly sessions | Cars retain their homologated or configured behavior, so driver aids can differ by model. |
| Off | Realism-focused competition where every entrant accepts the same restrictions | More demanding braking and throttle control; unsuitable for an unannounced public change. |
| Forced | A tightly defined ruleset that requires the same aid policy for every car | Can make a car feel unlike its normal setup and may invalidate runs from drivers expecting Factory behavior. |
Assetto Servers lists Factory as the sensible default for mixed-car public events. Use Off or Forced only when the event rules require it, and state the policy in the lobby description and briefing. Stability control is best left Off for realistic competition; make it optional for beginners rather than changing it halfway through a championship.
Fuel, damage and tyre-wear rates
Set fuel consumption, damage and tyre wear to 100% for a normal baseline. This is a starting point, not a claim that 100% is the only realistic value for every mod. Assetto Servers recommends starting at 100%, completing a representative stint, and changing one rate at a time before committing to an event setup.
What a representative stint should include
- A pit exit and at least one judged run after the tyres reach their normal operating state.
- Several transitions, corrections and re-entries, rather than one clean lap.
- Enough fuel use to reveal whether the chosen tank size changes balance.
- At least one minor contact so you can see how damage and reset rules behave.
If tyre wear reaches a point where the car’s balance changes before the planned run ends, lower the wear rate for that event and document the change. If damage makes a single brush with a wall terminate an otherwise valid session, decide whether that severity is intentional before publishing the rules.
Preventing traffic, wrong-way and penalty disputes
Pure drift sessions
With EnableAi: false, the server does not inject AI traffic into the driving surface. This is the cleanest choice for tandem practice, solo scoring and judged lines. It also removes one source of wrong-way warnings when a driver uses the full width of a course during a transition.
When traffic is part of the format
If you deliberately enable traffic, define where passing, stopping and reversing are legal. Test spawn points and pit exits with two human drivers; AI behavior that looks harmless in a solo test can block a tandem pair. Record whether a contact with traffic is a driver fault, an automatic penalty or a restart condition.
Penalty checks before opening
- Run a legal direction lap and a deliberate wrong-way section to verify the warning and penalty timing.
- Cross the pit-entry and pit-exit lines at normal and excessive speed.
- Touch another car at low speed, then at drift speed, to see whether the contact system invalidates the run.
- Vote for a restart and session change with a normal account, confirming that permissions match the published rules.
CSP requirements and version control
Set a minimum version for feature-dependent servers
ACS Drift’s setup relies on CSP for many night-lighting, weather and track features. For a live drift HUD or CSP-assisted leaderboard validation, Assetto Servers documents a minimum of CSP 0.1.77 build 1937 or newer. Treat that number as the floor for that documented workflow, not as a universal requirement for every Assetto Corsa server.
Keep clients on the same build
Write the minimum version in the server description and require every competitor to use the same build during a championship. A player on a newer or older build may see different lighting, weather behavior, HUD output or validation results. If you change the required build, start a new leaderboard period rather than merging points from incompatible clients.
Track path and surface conversion
AssettoServer’s documented track-path pattern is:
Rank #3
- Realistic simulation. Performance and driving behaviour
- Graphics and effects of the latest generation
- All racetracks are reproduced using laser scan
TRACK=csp/<CSPversionID>/../<trackname>When adapting a track for CSP, change only the first SURFACE_0 entry to CSPFACE_0. Changing additional surfaces can produce checksum errors, preventing clients from joining even when they have the correct track files.
Making drift scoring fair
Publish the scoring boundaries
For a live HUD or validated leaderboard, define the minimum drift angle, maximum drift angle, minimum drift duration and validation mode before the first judged run. These are competition rules, not hidden implementation details: a driver must know what counts as a drift and what ends it.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Do not mix validation modes
Changing the validation mode can change point calculations. Keep runs made under one mode together and create a separate leaderboard when the mode changes. The same rule applies after a CSP requirement changes or the track surface is adjusted; historical points remain useful only when the underlying measurement conditions are comparable.
Use a repeatable run protocol
- Reset the car in the same place and allow the same pit-exit procedure for every driver.
- Use the fixed weather, track state, assists and CSP build announced for the event.
- Give each driver the same number of scored attempts and the same restart policy.
- Save the resulting score, validation status and any invalidation reason.
- Have a second driver reproduce one accepted and one rejected run before publishing the standings.
Client setup in Content Manager
ACS Drift recommends Content Manager with a specified CSP version. Players join through Content Manager’s Online tab, where required cars and tracks may be fetched when available. Tell drivers to install the exact car and track versions before a judged event; automatic downloads do not guarantee that a locally modified file will pass the server checksum.
Wheel baseline
The guide’s baseline wheel values are:
| Control | Value |
|---|---|
| Gain | 100% |
| Minimum force | 0% |
| Effects | 0% |
| Gyro | On |
| Soft Lock | On |
These values establish a common reference for troubleshooting; they are not a claim that every wheel benefits from identical filtering. ACS Drift also documents device-specific paths for the MOZA R5 and Simagic Alpha Mini, plus an A7 controller script. Drivers should load the path intended for their device and then verify steering range and soft-lock behavior in a practice session.
Validation checklist before going public
- Start the server with AI disabled and confirm that no AI cars spawn after a restart.
- Leave the pits twice and verify that tyre blankets produce the same initial response.
- Drive the selected surface at the published grip value and record the weather and time-of-day.
- Check ABS, traction control and stability-control policies with a normal driver account.
- Run a representative stint at the 100% fuel, damage and tyre-wear baseline.
- Test pit entry, pit exit, resets, voting, contacts and wrong-way behavior.
- Connect with the required CSP build and confirm the HUD or validation output.
- Compare one accepted and one rejected drift run against the stated angle, duration and validation rules.
- Invite a second driver to repeat the entire path before announcing the server.
Troubleshooting common failures
Players receive a checksum error
Check that clients have the same track and car files, then inspect CSP surface conversion. If more than the first SURFACE_0 was changed to CSPFACE_0, revert the extra edits and restart the server.
The car feels different on every attempt
Confirm tyre blankets, track surface percentage, weather and time-of-day. A changed CSP build or an unannounced surface state can also alter the reference conditions. Freeze those values before investigating setup or controller changes.
Scores cannot be compared
Check the validation mode, angle limits, duration threshold, CSP build and track state. If any of those changed, separate the runs into different leaderboard periods instead of recalculating points informally.
Rank #4
- Experience true next-generation gaming with increased visual fidelity through 4K graphics, and 60FPS for a faster and smoother race experience
- 2021 Liveries: Updated liveries from the 2021 season
- Fully Immersive Simulation: Race like a real GT World Challenge driver, with options to configure tyres, chassis, engine set up, and more
- New-Generation Graphics & Visual Effects: Photorealistic weather conditions and multi-channel audio sampling to create that authentic GT racing experience
- Advanced Multiplayer Functionality: Includes a new fair-play ranking system (rewarding virtuous players), solid matchmaking, regular challenges, and a real-time online leader-board
Beginners cannot keep the car sideways
Keep the 95–97% Old or Green surface baseline, offer Factory assists and make stability control optional for practice. Do not lower every server restriction at once; changing one policy preserves a useful reference for the next adjustment.
Which Assetto Corsa edition is needed?
ACS Drift states that the Ultimate Edition includes all official DLC and is the easiest choice. Availability and pricing vary by marketplace and region, so verify the current listing where you buy it. The edition does not replace the need for the correct mod cars, tracks, Content Manager setup or CSP build required by a particular server.
Suggested presets for different events
| Preset | Assists | Grip and tyres | Damage and wear | Scoring use |
|---|---|---|---|---|
| Public practice | Factory; stability optional | Old or Green at 95–97%; blankets on | 100% baseline | Practice only; no cross-session ranking |
| Mixed-car competition | Factory unless the briefing says otherwise | Fixed surface, weather and CSP build | 100% until a tested change is justified | One published validation mode |
| Strict realism event | ABS and traction control Off or Forced as announced; stability Off | Same fixed conditions for every run | Set only after a representative stint | Separate leaderboard from assisted events |
Choose one preset, publish its values, and resist mid-event changes. Consistency is more valuable than a theoretically perfect number that drivers cannot reproduce.
Frequently Asked Questions
Should I enable AI traffic on a drift server?
No for a pure drift, tandem or judged session. Set EnableAi: false to remove unexpected traffic and wrong-way interactions. Enable AI only when traffic is an explicit part of the format and you have tested its spawn, passing and penalty rules.
What CSP version should competitors use?
For the documented live HUD or CSP-assisted validation workflow, require CSP 0.1.77 build 1937 or newer and keep all competitors on the same build. A server that does not use those features may not need that exact minimum.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Why did changing the validation mode alter the leaderboard?
Validation mode is part of the scoring calculation. Changing it can change point totals, so runs made under different modes should be kept in separate leaderboard periods.
Why are players getting checksum errors after a CSP track edit?
AssettoServer’s documented conversion changes only the first SURFACE_0 entry to CSPFACE_0. Changing additional surfaces can cause checksum failures; revert those edits, confirm identical files and restart.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
