Assetto Corsa Controller Not Working | Fixes That Work

When steering or throttle stops responding in Assetto Corsa, the cause is usually a mix of driver priority, Steam Input overrides, mis-mapped buttons, or Windows power settings that put USB devices to sleep. This guide walks you through fast checks first, then deeper fixes that restore stable inputs for gamepads and racing wheels. You’ll see what to change in Steam, Windows, and the game itself, plus a clean way to test each step so you don’t chase ghosts.

Quick Checks When Assetto Corsa Controller Not Working

Goal: confirm the device works, the game can see it, and no simple toggle is blocking input.

• Test In Windows Game Controllers — Open joy.cpl (press Win+R, type joy.cpl). Verify axes and buttons light up for your controller or wheel.
• Confirm Steam Big Picture Overrides — In Steam, go to Settings > Controller > Controller Settings. Uncheck mismatched templates (e.g., Xbox layout for a DualSense) or, if needed, enable the matching support only. Then in Manage Game > Controller set Override to Disable Steam Input for a straight DirectInput/XInput path, or to Enable Steam Input if your device needs it. Test both.
• Plug Directly To A USB Port — Use a rear motherboard port for wheels and pedals. Skip hubs until the issue is solved.
• Close Conflicting Apps — Exit apps that hook controllers (RGB suites, screen recorders with overlays, device managers, macro tools). These can steal focus.
• Verify Game Files — In Steam, right-click the game > Properties > Installed Files > Verify integrity. A damaged config can drop inputs.

Common Reasons Assetto Corsa Controller Not Working

Most control failures track to one of a few patterns. Scan these first so you pick the right branch of fixes.

Fix Controller Not Responding In Assetto Corsa: Fast Paths

Run these short steps in order. After each change, launch a quick single-player session and test steering and throttle for 30–60 seconds.

1. Set Device Priority In-Game — From the main menu, open Options > Controls. In the device list, pick the controller or wheel you actually drive with so the game polls it first.
2. Apply A Clean Preset — Choose the closest preset (Xbox, DualShock, wheel brand). Hit Reset. This wipes a broken mapping and writes sane defaults for axes and buttons.
3. Rebind Steering And Throttle — In Controls, click the function (e.g., Steer Left), then move the stick or wheel. Repeat for throttle, brake, clutch, and handbrake. If the wrong axis captures, press Esc to cancel and try again.
4. Set Deadzones And Sensitivity — Start with tiny deadzones (0–0.05) for sticks, slightly more for worn hardware. For wheels, keep linear response first; advanced filters can wait until inputs register normally.
5. Flip Steam Input Mode Once — If you disabled Steam Input, try enabling it and vice versa. Then restart the game. Many cases hinge on that single toggle.
6. Unplug Extras — Disconnect spare pads, HOTAS, and old wheels. Fewer devices mean fewer duplicate axes for the game to trip over.

If those steps bring inputs back, save the profile and back up the control files so you can recover later without repeating the process.

Deep Windows Fixes For Stable Inputs

When quick actions don’t stick, the root cause usually lives in drivers or power management. These steps lock in stability on Windows 10 and 11.

Stop USB Ports From Sleeping

• Disable Selective Suspend — Open Power Options > Change plan settings > Change advanced power settings. Under USB settings, set USB selective suspend to Disabled for both battery and plugged in.
• Turn Off Hub Power Saving — In Device Manager, expand Universal Serial Bus controllers. For each USB Root Hub, open Power Management and uncheck Allow the computer to turn off this device.

Clear Conflicting Drivers

• Remove Ghost HID Devices — In Device Manager > View > Show hidden devices. Under Human Interface Devices and Sound, video and game controllers, right-click grayed entries for old pads or wheels and uninstall them.
• Prefer A Single Input Layer — Many pads support both XInput and DirectInput. If the game sees two devices from one pad, switch the mode on the controller (hardware switch or software) so only one layer remains.
• Update Vendor Drivers/Firmware — For wheels and pedals, install the latest driver pack and firmware from the manufacturer. Firmware fixes axis jitter and pedal detection more often than you’d think.

Trim Background Hooks

• Close Overlays — Turn off extra overlays in Steam, GPU software, chat apps, and recorders. Start the game clean, then re-enable only what you need.
• Exit Macro/Remap Tools — Close tools that remap buttons or emulate keyboards. They can steal the event before the game reads it.

Use Reliable Ports And Cables

• Pick USB 2.0 Or 3.0 Based On Device — Some legacy wheels behave better on USB 2.0. If a 3.0 port glitches, test a 2.0 port on the rear I/O.
• Swap The Cable — Short, shielded cables reduce dropouts. Kinked or loose micro-USB leads are common disconnect culprits.

In-Game Settings That Restore Control

Once Windows and Steam behave, finish the job inside the game so steering feels natural and inputs stay consistent across sessions.

Pick The Right Device Profile

• Start From A Matching Template — Choose the closest pad or wheel brand profile. It sets base deadzones, rotation ranges, and default buttons that tend to work out of the box.
• Save As A New Preset — After remapping, use Save to create a named preset. If a tweak goes sideways later, load the saved one in a click.

Calibrate Steering And Pedals

• Center The Wheel — Put the wheel dead center, then bind left and right. If it pulls, re-center and bind again before touching filters.
• Bind Each Pedal Cleanly — Click throttle, press it once smoothly to the stop. Repeat for brake and clutch. If a pedal shares an axis with another device, remap after unplugging extras.

Tune Deadzones And Filters

• Set Small Stick Deadzones — Gamepads: 0.05 is a safe start for left/right. Raise slightly only if drift appears.
• Keep Wheel Response Linear First — Leave gamma and filters at defaults until inputs read correctly. Fancy curves help only after base detection is solid.
• Check Brake Sensitivity — Load-cell pedals feel different from pot brakes. Adjust sensitivity so full pressure equals full brake without tiny taps locking wheels.

Map Camera And Menu Keys

• Put Pause And Reset Near Thumb — Place Pause and Reset Car on easy buttons. You’ll test more confidently when recovery is instant.
• Bind Look Left/Right — If you drive from bumper or cockpit, quick glances reduce penalties from blind merges.

Clean Configs, Logs, And Fresh Starts

When odd behavior returns after every reboot, rebuild the control configs and keep a backup. That stops drift from creeping back.

Rebuild Control Files

• Back Up Current Files — Locate the game’s controller profiles in your Documents folder. Copy the profile you use to a safe spot.
• Let The Game Regenerate — Rename the existing controls file so the game creates a fresh one on launch. Re-apply your bindings using the steps above.

Check Logs For Clues

• Scan For Device Names — Open the game’s log file after a failed session. Look for how many input devices the game enumerates and which IDs it favors.
• Watch For Duplicate Axes — Two devices presenting an X axis can cause flips and dead steering. Unplug until only one remains, then re-introduce others.

Do A True Clean Start

• Test On A New Windows User — Create a temporary profile and run the game there. If inputs work, the issue lives in per-user configs, not hardware.
• Reinstall Only After Backups — If nothing helps, remove the game, delete leftover config folders, and install fresh. Restore your known-good preset afterward.

Prevent The Problem From Returning

The best fix is the one you never need again. Lock in a routine that keeps inputs steady across updates and new content.

• Keep A Known-Good Preset — After everything works, save a profile with a clear name and back it up. If inputs scramble later, load it and get racing.
• Update Drivers On Your Schedule — Wheel firmware and USB chipset drivers matter. Update when you have time to test, not mid-event.
• Use Stable Ports — Leave the wheel and pedals on the same rear ports. Moving them around invites re-enumeration and fresh conflicts.
• Limit Layering — Either route through Steam Input or go direct, not both. Extra layers add lag and extra points of failure.

When You Need A Clear Path Forward

If you made it here, you’ve likely trimmed conflicts and set clean mappings. Two final notes help with edge cases. First, some devices present as multiple HID entries; pick one path and disable the rest so the game does not see duplicates. Second, pedals on a separate USB bus can appear as a new device after a reboot; bind them again once and save to your preset. If issues return only with heavy apps open, launch the game alone and add those tools back one by one until you find the hook that breaks inputs.

Use this page as your baseline. If assetto corsa controller not working pops up again after an update, run the Quick Checks, flip the Steam override once, and load your saved preset. If none of that helps, rebuild the control files and retest from a clean Windows session. That sequence solves most stubborn cases. Should you hit the rare hardware fault, a different cable or port often reveals it faster than any menu tweak.

For track days that start smooth every time, keep backups of your control profiles and note the Steam Input mode that actually works on your setup. Label your USB ports, avoid hubs for mission-critical gear, and don’t stack overlay tools on top of each other. If assetto corsa controller not working shows up again, you can fix it in minutes with the steps above instead of losing a whole evening.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback