I bought a new computer and some toys as well as FS2020 4 days ago and since then I have been only suffering and chasing issue after issue...I have tried on several communities but nobody could really help me so this is literally my last hope otherwise I will just delete everything and leave it behind...
- ASUS TUF15, i7 11800-H, GPU 3060 6GB, 24GB RAM
- Win10, FS2020 Ultimate (Microsoft Store Version)
- Joystick is a Microsoft ForceFeedback 2
- Rudder is a Thrustmaster T. Rudder
- My FS2020 as well as my Winodws are up-to-date
- XPForce Pro for the joystick ForceFeedback
My rudders are "flickering". I can move them to a certain point and they take my inputs more or less fine.
- If I slightly guide left, the plane slightly goes left, If I slightly guide right, the plane slightly goes right,
- If I guide left/right more than just slightly, the plane also takes this turn but may interrupt until I repeat the input which is causing wider turns,
- If I go full left/right, it just ignores the input and goes straight, it may do a small movement towards the full-input side but not at all useful or controllable
- If I slightly guide left/right, the plane follows my input, if I increase my input and go full left, it stops taking the input which is again causing me unexpected movements.
- Lets just say it like this: A backtrack with A320 is doable but hard and only if I keep continuously repeating my rudder inputs.
Maybe related issue
- If I bind my rudder to the left and right brake by touching the top of the pedals, the brakes work as they should but whenever the plane comes to a stop or slows down after I tipped the brake, I am finding myself in a "invisible parking break" situation. That means: It acts like the parking brake was set, but to move on I actually need to set the parking brake and release it. The same issue happens when I go full left or right with the rudders and the plane comes to a stop situation (example: Backtrack on a runway, rudders full left on low speed, if the planes comes to stop due the nose wheel position and lacking power and I wasnt fast enough to apply some thrust, I have to set the parking brk and release it again. Pretty annoying.
- There is one exception, the FBW A320NX Developer version just takes me in a non-escapable situation and I am just stuck, the only thing helping is reloading the flight. The FBW 320NX Stable version had the same issue, although I could move on by setting and releasing the parking brk.
Let me show you a visual example how my rudders visually look and have a look at the lower ecam. It looks like it is continuously fighting against a counter input but it really is not:
Conclusion: It is kind of playable, but not really enjoyable and that only if I do not assign the brakes.
- I made sure this is not an aircraft / model related issue by selecting several planes, like the C152 or the DR400 default. I just used the Airbus because its Lower Ecam and the rudder visualization make it quite visible and understandable
- I downloaded all drivers and softwares from Thrustmaster, the latest driver and also their calibration tool.
- I do not think it is an error in the game controller itself because the flickering like you see it in the video above does not show in the calibration software. It also does not show in the MSFS sensitivity tool and axis preview.
- I unplugged the Thrustmaster rudder and assigned the rudder inputs to the unused joystick axis and had exactly the same issue, so again I think it is not a ThrustMaster Rudder failure.
- I played with the sensitivity settings of the MSFS2020 and couldnt find any improvements.
- I made sure that there is no sort of double binding by going thru every single controller in the MSFS2020 and looked at the assignments. The rudder assignments are unique and theres no binding issue, although it looks so much like theres one force fighting against another. I went thru all the bindings and even if I assign the rudders only to some keyboard keys and leave the USB controllers disconnected, it is still the same issue.'
- I also made sure that the issue is not caused by the XPForce Pro software by launching the FS2020 not thru the ForceFeedback launcher but the ordinary way by clicking on the very FlightSimulator.exe.
- I changed the USB Slots although I was pretty sure that if there was a connection problem or a input signal conflict, I could see that with the calibration raw data.
The Thrustmaster is new and although I first thought it might be the source of the problem, with all the counter-troubleshooting I did, I am not convinced it really is. Especially that the input issues are showing only in FS2020 but not the calibration tools or FS2020 sensitivity curves where the movements go linear and uninterrupted. It is like very ingame only.
I am thanking everybody in advance and I hope I can fix this problem with your help.