Hi,
The default controller mapping on my T.Flight Hotas X Joystick is just stupid.. In MSFT 2020 it was ok as default, so didn’t need to change much.
Is it possible to share mapping for this joystick, like from a file or similar, or do I need to manually go in settings and change every button myself? Any other profiles I can choose from would be nice!
Have you tried thoroughly searching the forum? There have been a large number of discussions about control mapping in 24 and whether it can be carried over from 2020, like this:
There are also some general guides and FAQ’s available, like this:
https://flightsimulator.zendesk.com/hc/en-us/articles/16459737949980-Controller-Settings-FAQ
It may be that if you check a few of these threads, you’ll find the answer you’re looking for more quickly than waiting for someone with the same controller and question to respond.
Having said that, the hotas X doesn’t have a huge number of buttons, so the majority of them will be suitable for your default profile that can be used for all aircraft. I’d suggest mapping them all in manually just the once, then save the profile and forget it.
Yes, I have. Thanks for your answer, so delete everything and manually add them then.. Very cleaver MSFT..
Anyone have an overview of the most used buttons for this setup on this Hotas?
So anyone know if it works to export MSFT 2020 to 2024? I see someone tried it, but never anyone confirmed it works.
The default bindings are really stupid on 2024… what happened there??
I think that would be easiest for setting it up in 24 - delete all the existing profiles and set up one new one that can be the default for all aircraft. I know it isn’t ideal, but you’ll save yourself some headaches in the future.
Obviously you have the pitch, roll, yaw & throttle axes first. then you’ll want something easily to hand for elevator trim up & trim down - either two of the thumb buttons or the rocker on the back of the throttle are good for this, as it needs frequent fine control.
The hat switch I would configure for look up / down / left / right - this works in the cockpit or the external view.
I’d set one of the buttons on the base as “Toggle Landing Gear.” You only need it a couple of times each trip, so it doesn’t have to be immediately under your fingers, and using the “Toggle” function means you only need take up one button with it, rather than two for gear up & gear down.
You’ll need two buttons for flaps - use one for “Retract Flaps” and another one for “Extend Flaps One Notch.” This gives you all the control you need, without needing multiple buttons or a notched slider for flaps 5, 10, 15, 20, etc.
I use the trigger for “Next Smartcam Target” - if you squeeze and hold it, it moves your view to the next point on the flightplan - particularly useful if you’re looking for a runway! Letting go reverts you back to the previous cockpit or external view.
If there are any buttons left over, just map whatever functions you use the most, with the aim of getting frequently used controls away from the mouse & keyboard and under your fingers on the hotas. Much better for immersion.
I saw the suggestion that you can export bindings from 2020 to 2024, but I haven’t personally been able to make it work successfully. I have a VKB Gunfighter based joystick, their s-tecs throttle & three other VKB button / control panels, plus their rudder pedals, so quite alot of buttons to map. After trying the default / automatic setup options, I decided to just delete all the profiles and map them all in manually, to ensure everything works as I want.
