Ideas

mos53372080's avatar
mos53372080
New Spectator
6 days ago
Status:
New

F1 25 Xbox – Steering Input Scaling Issue with Logitech RS50 Direct Drive Wheel

Hello Codemasters / EA Support Team,

I would like to report a steering input scaling issue in F1 25 on Xbox Series X when using a Logitech RS50 direct drive wheel.
Issue Description:
When playing F1 25 on Xbox Series X with the Logitech RS50 wheel, steering input is significantly over-amplified.
Even when both the wheel base and the in-game settings are set to 360 degrees rotation, very small physical steering movements result in the in-game steering reaching full lock almost instantly.
Confirmed Settings:
RS50 base rotation set to 360°
In-game Wheel Rotation set to 360°
Steering Deadzone = 0
Steering Saturation = 0
Steering Linearity = 0
No gamepad connected
Local save data cleared and control profiles rebuilt
Same hardware works perfectly in Forza Motorsport 2023 (Xbox)
Same hardware works perfectly in F1 25 on PC
Observation:
This issue appears to be specific to the Xbox version of F1 25.
It suggests that the Xbox version may still be using a legacy steering input handling method that does not correctly support modern high-resolution direct drive wheels, causing incorrect steering angle scaling.
Affected Hardware:
Logitech RS50
Logitech G Pro Wheel (reported by community)
Other Direct Drive wheels (Fanatec DD, etc.)
This issue significantly affects drivability and realism.
I hope the development team can review the steering input handling on Xbox and provide a fix in a future update.
Thank you for your time and support.


Kind regards,
Moss Cheng.

3 Comments

  • davidwarner1's avatar
    davidwarner1
    Seasoned Newcomer
    6 days ago

    I’m facing a steering input scaling issue in F1 25 on Xbox while using the Logitech RS50 Direct Drive wheel, where the steering feels too sensitive near the center and unresponsive at higher angles despite adjusting saturation and linearity settings. I’ve tried recalibration, firmware updates, and different steering lock values, but the problem still remains, making precise cornering difficult. If anyone knows a fix or can confirm whether this is a known Xbox or wheel-profile issue, please share. I’ve seen similar input-mapping discussions in WA mody related communities for other games, so I’m wondering if this could be a broader console input-scaling problem.

  • mos53372080's avatar
    mos53372080
    New Spectator
    6 days ago

    Thanks for confirming — I’m experiencing the exact same behavior.

    To add more data points:
    • This issue only occurs in F1 25 on Xbox Series X
    • The same Logitech RS50 wheel works perfectly in Forza Motorsport 2023 on Xbox with true 1:1 steering
    • The same wheel also works correctly in F1 25 on PC (360° base / 360° in-game = correct mapping)

    This strongly suggests an Xbox-specific steering input scaling issue in F1 25, likely related to legacy wheel input handling that doesn’t properly support high-resolution direct drive wheels.

    Other DD wheel users (Logitech G Pro, Fanatec DD) are reporting similar center sensitivity + high-angle compression behavior.

    At the moment, the only workaround is artificially adding positive steering linearity to counteract the scaling, which confirms this is not a user setup issue.

    Hopefully the dev team can review the Xbox wheel input pipeline and apply a fix in a future patch.

  • That actually makes sense, and I agree with you.

    Steering linearity doesn’t consistently fix the issue — it only acts as a partial workaround for some setups. The fact that different users report wildly different results (or no effect at all) strongly suggests this isn’t a tuning problem, but a steering input scaling bug.

    If linearity were the real solution, it would behave predictably across all wheels. Instead, we’re seeing center over-sensitivity combined with compressed response at higher angles, which points to incorrect input mapping on Xbox rather than user settings.

    The same wheels work 1:1 in Forza Motorsport 2023 on Xbox and in F1 25 on PC, so this appears to be an Xbox-specific F1 25 input handling issue.