Thrustmaster ferrari 458 spider racing wheel, can use it to navigate xbox menu, but not in-game

The wheel working in the Xbox system UI but not in a specific game usually means the game does not recognize or support that wheel as a gameplay controller, even though the console can use it as a UI navigation device.

On Xbox and Windows, racing wheels are exposed through the Windows.Gaming.Input.RacingWheel API and also act as UI navigation controllers. As a UI navigation controller, the wheel’s D‑pad, View, Menu, A, and B buttons are mapped to standard navigation commands (Up/Down/Left/Right, Accept, Cancel, etc.), which is why the wheel can navigate the Xbox dashboard and menus.

However, games must explicitly support racing wheels as gameplay input devices. They need to:

• Detect the wheel via Windows.Gaming.Input.RacingWheel.
• Read its analog controls (wheel, pedals, etc.).
• Optionally use force feedback via Windows.Gaming.Input.ForceFeedback.

If a game has no built‑in support for that wheel (or for racing wheels at all), the wheel will still work for UI navigation but will not control the car or in‑game menus.

For this scenario, the practical options are:

1. Check the game’s documentation or settings to confirm whether it supports racing wheels on Xbox and whether the Thrustmaster Ferrari 458 Spider is listed as supported.
2. If the game only supports standard gamepads, use an Xbox controller for gameplay.
3. If the game claims to support that wheel but it still does not work, contact the game’s support so they can confirm compatibility or provide a patch.

The behavior described (works in Xbox menu, not in‑game) matches a title that is only using the wheel as a UI navigation controller, not as a racing wheel input device.

References:

• Racing wheel and force feedback
• UI navigation controller
• RacingWheel Class