logged Braking Issue with A350 v1.0.7 in MSFS 2020

[Eric Jeppesen]

Dear Support Team,

I am writing to report an issue with the A350’s braking system following the v1.0.7 update (MSFS 2020).

Setup Details:

1. Hardware:

   • I do not use rudder pedals.
   • I own a Thrustmaster throttle quadrant with a paddle lever behind the throttle axis. In MSFS, this paddle is configured as an axis input.
   • The paddle remains at a neutral position when untouched and can be pressed left/right manually.

2. Software Configuration:

   • FSUIPC Settings:
     • The paddle’s axis input is mapped to the brake axis in FSUIPC.
     • A 50% deadzone is applied in FSUIPC to eliminate unintended inputs from the paddle’s neutral position.
   • MSFS Settings:
     • The paddle axis is not bound to any function in MSFS’s control settings.
   • Previous Functionality (v1.0.6 and earlier):
     • This configuration worked perfectly, allowing the paddle to function as a brake without unintended activation.

Issue in v1.0.7:

• The A350 recognizes the brake axis input (the brake pedals animate when the paddle is pressed).
• However, the deadzone configured in FSUIPC is ignored. The sim detects 50% brake pressure even when the paddle is untouched.
• Isolated Issue:
  • Other aircraft (Asobo, PMDG, Fenix, etc.) function correctly with the same setup.
  • The problem occurs exclusively with the A350 v1.0.7.

Request:
Please investigate this regression and restore compatibility with FSUIPC’s deadzone settings, as seen in v1.0.6. I would like to continue using my paddle lever for braking.

Thank you for your dedication to enhancing the A350 experience!

Best regards,
Eric Jeppesen

[richboy2307]

Thanks your issue is logged.

Just to be sure, can you please also confirm that this isn't an issue of a profile-specific calibration that isn't being applied to the particular A350 instance on which you tested? 

Thanks!

[Eric Jeppesen]

1 hour ago, richboy2307 said:

Thanks your issue is logged.

Just to be sure, can you please also confirm that this isn't an issue of a profile-specific calibration that isn't being applied to the particular A350 instance on which you tested? 

Thanks!

Thanks for your reply! I did not turn on this option in FSUIPC.

 

Best regards,

Eric