I think this will be my final update on this issue until Microsoft/Asobo provides a fix, but I have done some controlled testing which may be useful.
I use a native T.Flight HOTAS 4 on PS5. Before SU6 this setup worked without these random inputs. The problem only appeared after SU6, which is why I still believe the SU6 changes — possibly including the Thrustmaster SDK update mentioned in the release notes — triggered the problem.
I’ve completed 10 tests and I’ve now been able to identify something that appears to make the issue reproducible on my system: the Logitech Logi Bolt receiver I use for my wireless mouse.
With HOTAS 4 + DualSense and the Logi Bolt receiver disconnected, I completed a 35-minute Hawk flight with no issues using the default profiles. I then repeated the test using my custom bindings, again with no Logi Bolt receiver, and had no issues.
With the Logi Bolt receiver connected directly to the PS5, I had an uncommanded switch to external view after 5 minutes and another 3 minutes later.
I then removed the Logi Bolt receiver and substituted a wired USB mouse, which the PS5 correctly recognises as a mouse. That flight was also trouble-free.
Finally, I deliberately repeated the Logi Bolt test. After 6 minutes I had another uncommanded switch to external view, this time accompanied by the airbrake extending without command. Five minutes later exactly the same thing happened again, so I ended the flight.
Interestingly, my PS5 appears to recognise the Logi Bolt receiver as a keyboard, rather than as a mouse.
So, on my system at least, there is a very strong correlation between having the Logi Bolt receiver connected and the HOTAS 4 random-input problem appearing. Removing it has so far eliminated the problem, while deliberately reconnecting it has reproduced the fault twice within a few minutes.
I’m not suggesting that Logi Bolt itself is the underlying bug, or that everyone experiencing this problem is using one. Given that the same hardware configuration worked normally before SU6, and that so many reports involve either HOTAS 4 or HOTAS 5 operating in HOTAS 4 compatibility mode, I still strongly suspect that something changed in the SU6/Thrustmaster input handling which has made the HOTAS 4 path vulnerable to these phantom inputs. Other USB/HID devices may simply affect whether or how frequently the problem manifests.
For now my workaround is simple: I have removed the Logi Bolt receiver from the PS5 and gone back to a wired mouse. If that remains stable in normal flying, I’ll stick with it.
Hopefully the detailed test results are useful to the developers in reproducing or diagnosing the issue. I don’t intend to do any more troubleshooting now — I’ll wait for a proper fix.