3 Commando Brigade

X45 HOTAS and ArmA 3

I may be the only one in 3CB with a Saitek X45 HOTAS, but thought it worth sharing a massive fix I've FINALLY found (through Googling) to an on going problem.
It may also help out X52 owners.

The problem is with the throttle control that you assign to the helicopter collective. ArmA sees the X45 throttle as a centered axis controller as follows:

Throttle position	ArmA output
0	100
50	0
100	-100

Like any normal thinking person you probably set the Collective Raise (analogue) to Throttle + and the Collective Lower (analogue) to Throttle -.
The result is that the throttle does NOTHING for the first 50% of travel, then suddenly shoots up from 50 to 100% travel.
This makes altitude/speed control very very twitchy and almost impossible to fly accurately. Hovering is a nightmare. You've seen my flying, right?

The solution is simple, but counter-intuitive.

Set both Throttle - and Throttle + to the same Collective Raise (analogue) control.
It is important that they are in that order. Minus, followed by Plus.

Also un-map the throttle from the Collective Lower (analogue), leaving it blank.

Happy flying!
Flt Lt. Apollo

I use the Thrustmaster Hotas x, and i am not sure which patch it was but i had to change from analogue to non analogue as it stopped responding as it should do. I will try the config you used and see if that works.

I have don't have eny issues with my X52pro since A3alpha and I use analogue input comand.

In fact, A3 fixed the throtle issue from A2. In A2 75%  was idle threshold for collective

I have one but it's not usefull if you use default TFAR/ACRE keys + there is a mode for NOD/FZA AH64 mod.
The profile has TFAR/ ACRE commands on POV2 hatswich nothing more. There is nothing fancy on profile unless you are using NOD/FZA AH64 mod.