startswithf

As I said I unplugged every usb hardware, including mouse and keyboard.

i just unplugged all of my usb hardware completely and the issue is still happening. there is physically nothing plugged into my pc that could even cause a double assignment or conflicting input right now. This proves it is 100% an issue inside the aircraft software code and not my controller setup.

As mentioned, this was just a quick test to capture the intermittent bug without wasting time on a full flight setup. the Airbus flybywire system handles basic stabilization (Normal Law) completely independently of the MCDU. Even with an empty flight plan, the aircraft is supposed to maintain its bank angle when the stick is centered. it should never violently move the control surfaces on its own. The video clearly shows the flight control computer generating an uncommanded roll signal regardless of navigation data.

I have checked my configuration once again and completely removed any other non-essential aileron, elevator, or rudder axes, but the issue still persists. It happens quite randomly when flying at a low altitude or during an approach, almost as if the flight control computer isn't holding the roll rate as it should.I have attached a video for demonstration. At around 10 seconds into the clip, I completely let go of the sidestick, and right after, the aircraft aggressively banks to the right on its own.Please note that I didn't set up a full flight plan or proper final configuration for this specific clip, as this video was made strictly to demonstrate the raw control surface behavior. However, this identical uncommanded roll happens exactly the same way when the aircraft is set up perfectly and flown properly on a stabilized approach. https://youtu.be/fSKUpbawmu0

Hello, Since updating my iniBuilds A350 for MSFS 2024 to version 1.2.6, I am experiencing a severe issue with uncommanded banking immediately after takeoff. Right after rotation, without touching my sidestick at all, the aircraft aggressively rolls to the side on its own. When checking the FCTL ECAM page, the flight control surfaces are actively moving and deflecting on their own without any physical input. I have already verified my hardware settings in MSFS: my deadzones are properly configured, there is zero axis jittering, and no conflicting double-bindings exist. This behavior only started appearing after installing the v1.2.6 update. Is this a known bug with the ground-to-flight FBW transition logic or weather compensation in the latest version? Any help or workaround would be greatly appreciated. Thank you! Hardware: Thrustmaster TCA Airbus Sidestick