Yup same here after 6.1 update. Spoilers, flaps up a notch on short final will really test reflexes 
Me too,
With 6.1, parking brakes activated at runway, external view change + +
Why this can’t be fixed?, We are having a ghost input from Hotas!
Using: ps5 + dual sense + keyboard + TM hotas4
Anyone using mouse have same issue?
When holding right click to look around in the cockpit , other controls from Hotas get blocked, so you can use only one peripheral while looking around
Same here my hotas 4 after the update still had random inputs like internal then external view without buttons being pushed. Should have been fixed by now i would have thought. But no. Too interested in launching new scenery rather than sorting the joystick out first. How hard can it be to create a hot fix?.
Had another couple of fun ones today. Park Brake key binding won’t “stick” on shutdown. Brakes set and then release right away. But the best one that had me laughing was when I was flying the Cabri G2 and it switched to external view…and the rotor brake engaged. Yahoo!
I hate to say it but the chaos that ensues after the external view switch happens has become slightly entertaining. It switches and I’m immediately waiting for all hell to break loose. Sometimes it’s just the parking brake, sometimes it’s a rotor brake, and once it was a condition lever on the C208 to cutoff 
Haha it’s failure simulation 
in all seriousness though I don’t think the Thrustmaster SDK integration went as well as they think it did. There’s been several reports of bindings being jacked up and it looks like several planes had an invalid ID bound to a ton of actions. That, plus this ghost inputs problem, and I’m wondering what the value add was of the change.
I’m wondering if it’s future proofing for further PS5 peripherals…
Dare to dream!
Would be nice for them to at least acknowledge this. It’s frustrating that a game I’ve really enjoyed playing has been unplayable for the last 2-3 weeks simply because the hotas 4 is broken after SU6 but it’s been radio silence about it. Instead they focus on pushing world updates. I refuse to play this solely using the Dualsense after spending money on the hotas 4. I wanted the experience of using the joystick and throttle quadrant but it just straight up is broken
[Moderator edit: please do not ping the Community Managers] get the team on this. People shouldn’t need a workaround such as having to disconnect the dualsense to use the hotas 4 so you don’t get random inputs. I use a small keyboard that is plugged into the Dualsense so I can’t just turn off the controller because then my keyboard doesn’t work. We all paid for hardware that should work straight out of the box and it did prior to SU6. Every sim update is one step forward, 2 steps back and then we have to wait weeks on end for another fix even though this issue hasn’t been acknowledged at all or a timeline on when this will be rectified
“Please do not ping the community managers” Alright, we’ll just sit in silence and hear nothing about this from them and just accept a broken game
[Moderator edit: please do not ping the Community Managers]
When we get Infos, and why is it not Bug Logged?
6.1 bring a good amount of fixes, but thes annoying and gamebreaking Problem is still in the Game and make it unplayble on PS 5, it cant be, that we get no Informations.
The communication culture at MS / Asobo is absolutely appalling, and a slap in the face for all of us paying players here.
And I don’t care whether we’re allowed to ping you or not, just as MS / Asobo clearly don’t care that the game we paid a lot of money for just over a year ago is still not properly playable.
This bug is so frustrating. It’s happening in every aircraft. It makes me not want to even fly anymore. HOW is this not carrying a higher priority. The ONLY immersion adding hardware for PS5 is flat out broken.
It’s crazy isn’t it. It’s been feedback logged for the past 2 weeks and I’m still waiting for it to be bug logged. I’m not sure what criteria needs to be met for it to move to bug logged but you summed it up. We’ve literally got the hotas as the only hardware that works on PS5 and you can’t use it normally without this issue on every single flight. The radio silence from any community manager or anybody with a bit of authority with the game is astounding. We’ve all paid a lot of money for the game and the hotas and for the past 3 weeks it’s all just been sat collecting dust. When are the team going to acknowledge this issue?!
Yep, this is beyond comprehension.
I wonder if MS/Asobo team has any PS5 test team, and I really wonder that team has a TM Hotas at all? if they did, this couldn’t be happening, even just a half-hour of play would show them what is wrong. Frankly, even before playing, they would find out that the key bindings themselves are an issue.
What should we do? Send them a Hotas?
Hi folks,
Our internal test teams have been tracking this thread closely and have tested extensively with both a T.Flight Hotas 4 and T.Flight Hotas 5 on PS5 consoles using build SU6.1 (1.8.16.0). Unfortunately, they have not been able to reproduce the behavior you are reporting here with phantom control inputs.
They have requested that those of you experiencing this issue please post a photo to this thread showing all the hardware peripherals (Hotas, PS5 gamepad, any other input devices) you have connected to your PS5 consoles.
Thanks,
MSFS Team
Hello,
This issue seems to be part resolved for me with the Hotas 5.
Now that the Hotas 5 has default control binding profiles, I have copied the few customisations I had with it before in Hotas 4 mode and am using it in Hotas 5 / PS5 mode. No issues so far with the Hotas, dualsense, and keyboard connected. Using in Hotas 4 / PS4 mode still results in the dodgy random inputs.
My best guess is that to experience or reproduce this issue you have to:
-Use a Hotas 4 (or Hotas 5 running in Hotas 4 mode).
-Have the dualsense PS5 controller turned on and assigned.
-AND have a keyboard (or possibly a mouse) connected.
Hopefully this helps:
- PS5 Standard
- HOTAS 4 plugged into back USB port
- Thrustmaster rudder pedals plugged into HOTAS 4
- Logitech G305 wireless mouse, receiver dongle plugged into back USB port of PS5
- Wireless standard Dual sense PS5 control with wired headphones plugged in
No keyboards
EDIT: speedbrakes and parking brakes literally deployed on their own immediately after posting this 
EDIT 2: also want to mention that while this is happening in 3rd party aircraft like the FlightFX Citation X I’m flying here, it is also occurring with all default aircraft. Strangely though, I’ve been unable to reproduce in the FSReborn Phenom 300E.
But how long did they test the hotas 4 and hotas 5 for , as the bug may happen in 5 minutes or 45 minutes. There is no telling but it deinately happens to me.