Why Is My Controller Not Working on PC on Forza 6: The Input-Stack Deep Dive

Your controller is probably not working in Forza Motorsport 6 on PC because Forza 6 was never released for PC. It launched in September 2015 as an Xbox One exclusive, and the only PC-adjacent version is Forza Motorsport 6: Apex, a free Windows 10 beta that ran from May 2016 until it was delisted in September 2017. Every "fix" you read about input bugs was written for one of those two builds, so the fix must match the build you actually own.

That distinction matters more than any driver tip. The game's input path, its DirectInput support, and its deadzone handling all depend on which executable is running. Below is the mechanism-level explanation of why pads fail in each case, which symptoms map to which cause, and what actually resolves them.

How the Forza 6 input stack actually works

A controller press travels through five layers before your car steers. The pad firmware samples the sticks, usually every 4 to 8 milliseconds. The Windows driver packages those samples into an XInput or DirectInput report. The game's input layer polls that report once per rendered frame. A deadzone and response curve then reshape the raw value. Finally, the physics step applies steering at a fixed rate.

Forza 6 on Xbox One was built around XInput, Microsoft's pad API, which exposes four slots and a fixed report format. XInput reports are polled per frame, not pushed by interrupt, so a frame-rate drop directly delays your steering input. A 30 fps frame gives the game a fresh input sample every 33 milliseconds. That is the mechanical reason a pad can feel "disconnected" while still being detected: the device works, but the sample rate collapsed.

Apex inherited this model on Windows 10 but added a wrapper for the Universal Windows Platform. That wrapper is where most "controller not working" reports originate. The UWP container can deny raw input access, and the wrapper translates XInput pads only. A DirectInput-only wheel or an older pad is invisible to it.

Plain language: the game listens on one narrow channel, and anything shouting on a different channel is simply not heard.

Quantified context: what the numbers say

Forza 6 shipped on September 15, 2015, with a review embargo that lifted the same week. Apex arrived on Windows 10 on May 5, 2016, as a free beta, and Microsoft pulled it from the Store on September 9, 2017. Anyone running it today is running an unsupported binary that has not received a patch in roughly eight years.

The input budget is tighter than most players assume. At 60 fps the game polls the pad every 16.7 milliseconds. Human stick-to-thumb reaction adds roughly 100 to 200 milliseconds. A 33-millisecond polling delay is therefore a small fraction of total latency but a large fraction of the game's steering assist window, which is why frame-rate stutter reads as input loss.

XInput supports four controllers on one system. DirectInput supports effectively unlimited devices but with per-device axis mappings that vary by manufacturer. A pad that enumerates in slot 0 but reports a stray axis at rest can fail the game's calibration check and be ignored entirely.

The failure modes, ranked by likelihood

The single most common cause is device slot assignment. Windows assigns XInput slots in connection order, and the game reads slot 0 by default. If a second pad, a racing wheel, or a wireless receiver occupies slot 0, your primary pad works everywhere except in-game.

The second most common cause is API mismatch. Apex accepts XInput reports through the UWP wrapper and ignores DirectInput devices. A pad marketed as "PC compatible" that only ships a DirectInput driver will appear in Windows' game controllers panel and still do nothing in Apex.

The third cause is the Store container itself. The UWP sandbox can block the game from reading raw HID reports from third-party software, including virtual controller mappers and macro tools. Disabling or uninstalling those mappers is often the only fix.

Red flags to check before touching drivers: The pad shows in Windows' Devices panel but not in the game's controller menu. A second controller or wheel is plugged in and occupies slot 0. Third-party mapping software is running in the background. The pad is DirectInput-only and the build is Apex. The game window loses focus when you alt-tab, and input stops until you click back in.

Edge cases that break the standard advice

Windows 11 changed how XInput devices are enumerated on some USB hubs. A pad connected through a powered hub can enumerate in a different slot than the same pad connected directly to the motherboard. Swapping ports is not superstition; it changes the slot assignment the game reads.

Bluetooth-connected Xbox pads drop to a lower polling rate than wired ones in some Windows builds, and the game's calibration can fail if the first report arrives during the connection handshake. Connecting the pad before launching the game avoids this.

The counterintuitive caveat professionals know: a controller that works in every other game can still fail in Apex because Apex reads the pad through the UWP container, and the container caches the device list at launch. Hot-plugging a pad after launch sometimes never registers. Launch the game with the pad already connected.

Comparison: XInput versus DirectInput in Forza 6 builds

Timeline: the Forza 6 PC input story

Practical actions, in order

Work from cheapest to most invasive. Each step maps to a specific mechanism above.

Confirm which build you have. If it is Forza 6 on Xbox One, the pad issue is almost always slot assignment or a dead battery. If it is Apex, expect UWP container behavior. Unplug every other controller, wheel, and receiver. Launch the game, then connect your primary pad. This forces it into XInput slot 0. Connect the pad with a cable before launching. Avoid Bluetooth during the first launch so the initial report arrives clean. Close all third-party mapping and macro software. The UWP sandbox may block the game from reading mapped reports. Reinstall the pad driver from the manufacturer, not from a generic driver pack. DirectInput-only pads will still fail in Apex, and no driver fixes that. Test the pad in Windows' game controllers panel and in one other game. If it fails there too, the problem is upstream of Forza. If the pad works elsewhere and only Apex fails, accept that the binary is unsupported. The practical fix is an XInput-certified pad and a wired connection.

Threshold to remember: if the pad works in two other games and fails only in Apex, stop troubleshooting drivers. The build is the problem, and it has not been patched since 2017.

Limitations and what this cannot tell you

No public patch notes or support documentation confirm every Apex input change, and Microsoft has not published a compatibility matrix since delisting. The mechanism described here is consistent with XInput and UWP documentation, but the exact internal polling behavior of the Apex build is not observable from outside.

The dated measurements above are historical, not current recommendations. Prices and availability for replacement pads change constantly and are omitted here. If your setup involves a specific wheel or a niche pad, the general mechanism still applies, but the fix may require manufacturer-specific calibration.

This article is general educational information about input APIs and game builds, not a guarantee of compatibility for any specific device. For device-specific support, contact the controller manufacturer or Microsoft support.