I am a developer for a DOD organization in the United States and often use Bohemia's engine to show off simulation builds before selling the hardware to customers. That said:
This just started happening shortly after the Arma 3 Apex update and related patching:
When assigning a "fire" command manually to the right trigger on the xbox one controller (Z-axis) and then assigning anything to the left trigger (Z+ axis), they will conflict when both are pressed. This never happened before.
Example: When Temporary optics are assigned to the Z+ axis (left trigger), and then when you hold the trigger view through the optic to aim, when pressing the right trigger to fire, it won't fire. Instead it simply forces a zoom-out from the optic.
Pressing the Z- trigger by itself, without pressing any other button, it will fire normally.
To make sure it wasn't a problem with the current install on current machine, I checked on 2 other machines (friends were over) and they are manifesting the same behavior now and they did not before. We have to use xpadder as a work-around and we don't like it as it conflicts with other applications.
Controllers are used because having a mouse/keyboard is not possible or feasible. A controller is something MOST people are used to, and when showing off Bohemia's engine to students, they can immediately pick up the controller and go. There have been no problems until APEX and subsequent updates.
Is there a way that we can get double-tap and hold commands available for controllers? Is there a possibility of creating our own default controller schemes instead of using the ones already made, like "generic joystick" or similar? This would help in avoiding the troubles of customizing manually.
Increasing the capability of users to have controllers in Arma 3, despite the purism many see with keyboard and mouse, allows for familiarity when exposing Bohemia's engine to new users. We have proven this time and time again, now it is hard because of this one, simple bug with the triggers.