Logitech X52 Control Bindings

[scobbTDC_tv]

I just purchased a Logitech X52 HOTAS for Microsoft Flight Simulator 2020. Does anyone have a set of control bindings for this particular peripheral, including elevator, rudder and aileron sensitivity and deadzones? Any help would be appreciated. Thanks.

[Sandhill]

Is it not natively supported (pre programmed)? MS lists it as such...
https://flightsimulator.zendesk.com/hc/en-us/articles/360015912899-Peripherals-compatibility

[scobbTDC_tv]

According to the link, it is supported. When I plug it in, it shows a picture, with the button numbers and has a basic amount of default key bindings. What I am looking for is if anyone has one, how do they have theirs set up?

[The Prophet]

Originally posted by scobbTDC_tv:

According to the link, it is supported. When I plug it in, it shows a picture, with the button numbers and has a basic amount of default key bindings. What I am looking for is if anyone has one, how do they have theirs set up?

Its already set up. If you want to rebind the keys go to the section in the options and do it. Its quite simple.

[kalnaren]

“Supported” and “already bound” are two different things.

[Neo King Arthur]

Just bind the keys yourself. My default X56 bindings end up useless, so I cleared everything and remapped every thing I can map to cater to my flying style.

[Sandhill]

Originally posted by kalnaren:

“Supported” and “already bound” are two different things.

I don't think so, in this context. When MS says "supported" I think that the mean that they provide a diagram of the device and suggested bindings already applied. Seems the OP is just looking for suggestions for how to change the already bound assignments to best advantage.

[SomeBloke]

Mine automatically bound when it was discovered.

[kalnaren]

Originally posted by Sandhill:

Originally posted by kalnaren:

“Supported” and “already bound” are two different things.

I don't think so, in this context. When MS says "supported" I think that the mean that they provide a diagram of the device and suggested bindings already applied. Seems the OP is just looking for suggestions for how to change the already bound assignments to best advantage.

As far as I can tell MS actually never used the word 'supported'.

See this:

https://flightsimulator.zendesk.com/hc/en-us/articles/360015912899-Peripherals-compatibility

Native peripheral support has always meant that a program will read and understand the peripheral correctly. It doesn't mean that all functions of that peripheral are bound or bound correctly.

[Sandhill]

Yes, my word that I grabbed out of thin air, not MS's. I did indeed mean compatible
I do, though, think that the OP was just searching for better maps than the one MS supplied. Pretty personal, although I'd expect most people would change a thing or two but not necessarily the same thing or two.