Page MenuHomeFeedback Tracker

Using Customized Xbox one Controller (not default scheme), getting Z+ and Z- conflict on triggers.
New, NormalPublic

Description

I am a developer and I custom build arcade rigs for a simulation company 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.

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
latest, August Update applied
Category
Controls
Steps To Reproduce
  1. After ensuring the xbox one controller is available, Disable controllers with scheme.
  2. Make sure the xbox one controller is showing as customizable.
  3. Assign the right trigger (Z-) to "fire" in key assignments.
  4. Assign the left trigger (Z+) to Temporary optics or temp zoom.
  5. Enter a game, showcase or scenario, hold the left trigger (Z+) and while holding, attempt to fire the weapon using the right trigger (Z-).

Behavior: Instead of firing, the Right trigger forces a "zoom-out" or canceling of the optic...pressing ONLY Z- trigger (and nothing else) will allow firing.

Note: A xbox one Chatpad is connected to these controllers to allow quick access to key commands. I have not tried with the chatpad detached, but that should not affect the trigger issue.

This also occurs on the Steam controller intermittently...

Event Timeline

Mr.Knightman updated the task description. (Show Details)Aug 16 2016, 4:42 PM
Mr.Knightman updated the task description. (Show Details)Aug 17 2016, 5:35 PM
Mr.Knightman updated the task description. (Show Details)Aug 18 2016, 4:43 AM
Mr.Knightman updated the task description. (Show Details)
Zorkha added a subscriber: Zorkha.Aug 28 2016, 7:50 PM
This comment was removed by Zorkha.

Nope, no workarounds outside of using a 3rd-party mapping utility like Xpadder, which we don't like using. This never happened until after the APEX update. I also have not received any reply from the development team.

This comment was removed by Zorkha.
Zorkha removed a subscriber: Zorkha.Jul 19 2018, 4:53 AM