There are several buttons and hats and scrolls that can't be mapped because the game doesn't recognize them. E.g. the hat and the scroll on the throttle and the second (upper) hat on the joystick aren't recognized by the game.
They didn't work in A2 either, hopefully it can be fixed at some point. No need to hurry though ;P
Try to map the aforementioned controls in controls menu.
Ditto here. Some of the hat buttons, possibly because I noticed some of the hats are recognized as axis within Linux?
Also, the hat button on the throttle controller as well. Very likely, the hat buttons are the main issue here.
I have yet to try the mode switch, but have never used the mode switch as things just get too overly complicated. NOTE: The mode switch on the throttle controller use to be the main problem within the Linux kernel drivers or joystick calibration.
I would also guess, most other Saitek joystick hat buttons would also be tagged as having this same similar problem, as manufactures tend to use similar manufacturing procedures for all their joysticks.
Applies to the Saitek X65F as well. Problem is probably due to maximum number of buttons per controller set to some arbitrary number like 16 or 32 or something.
@EDcase I don't know if that is true for arma, but it is not true in general. The DCS series can make use of every button on a controller without the need for anything other than the drivers that come with it. The topic has been discussed extensively in their forums, and the limitations most games have is due purely to an arbitrary choice by the authors. This is an easy problem to correct.
From http://msdn.microsoft.com/en-us/library/windows/hardware/gg487464.aspx
"DirectInput does not limit the number of usages that can map to each type of axis. Applications designed for DirectInput typically request up to 128 buttons, four points of view (POVs), two sliders, and one each of X, Y, Z, Rx, Ry, and Rz."
My understanding is that the program simply has to internally provide names for as many buttons as it intends to support, so it's really a minor issue to increase that number. I may be wrong about those details, but I am confident that BI could very easily add support for all the buttons on these controllers, should they decide to.
And they should decide to.
Shrugs.
The Linux driver and applications have no problem seeing all Saitek buttons.
If the MS Windows driver can see all buttons, then the problem must lie within the application.
FYI: I can further confirm as I previously had a Saitek X45, the X52 Pro also has many unassignable keys and axis.
I don't know why the in game detection cannot detect these extra keys axis, unless it's depending on the old limited generic joystick key layouts, significantly limiting the number of detectable axis and keys to the days when joysticks were first available or engineered. I would suggest either adding the extra programming if it's not already planned, or at least resolve the game joystick axis and keys conflict with installed Saitek Profile 3rd party software, allowing the Saitek Profile software to manage all axis and keys for the game.
Albeit, I've always seen far better performance with controllers using the in game configuration versus Saitek's Profiling software, as the third party software throttle axis tends to perform worse with simulations or games!