Why they had to remove hotas 4 compatibility is beyond annoying ![]()
As this is my first Beta testing here, how often are updates usually released statistically? Just to dream about this fix..VR2 is a crazy good experience now, but with the pad, it’s like moving back to the Middle Ages
Lovely … good that a workaround was published, but … I also have a lot of sensitivity etc. settings in there, I am not to keen on recreating all that.
I wonder how such a new setup would reflect on our saved settings. In other words, once we have created a custom setup, once a real Hotas 4/5 recognition is (re)introduced, do we have to do the settings etc again? I am not sure the old pre-workaround settings are saved in our profile in such a scenario.
A good export <> import functionality of these settings would be nice.
Appreciate whoever found the work around
Hi folks,
I’ve received confirmation from the dev team that this issue will be fixed in a future beta build. I’m not sure whether or not the fix will be ready for the next beta build, but the team is aware of the issue with the Thrustmaster T.Flight on PS5 and are working to resolve it.
Thanks,
MSFS Team
Good to hear. Please realise that without an out-of-the-box working Hotas, it is very likely that not much Beta testing will be performed by PS5 users.
I for sure will not assign al bindings and sensitivities by hand again for every new build.
I would also suggest that the DEV team invests in a full PS5 - PSVR - Hotas set, so they can identify these basic issues themselves before going public with any release.
