Xbox One Elite controller issue (hair trigger locks)

[Llethander]

Edit: It seems like it has to do with the absolutely massive dead zones that FFXIV has for the gamepad triggers. The hair trigger locks make it so that the triggers stop at the earliest actuation point for the triggers thus reducing travel time on the pull and the reset and this actuation point appears to be roughly half of the total travel distance of the trigger. FFXIV's trigger dead zones seem to be roughly 2/3 of a trigger pull meaning that unless the trigger travels at least 2/3 of the total travel distance the game will not register the input. Since 2/3 > 1/2 it means that FFXIV fails to register the inputs of the Xbox One Elite controller when the hair trigger locks are enabled. Talk about frustrating...

I seem to be having an issue with FFXIV recognizing the LT and RT presses when using the hair trigger locks enabled. With the locks disabled (ie. normal Xbox Controller trigger functions) the game registers inputs just fine. With the locks enabled (all these do is cause the trigger travel to stop at the earliest actuation point for the switch), however, the game only recognizes the inputs if the triggers are pulled and subsequently pressed towards the center of the controller. If the trigger is pulled normally no input is recognized.


The only other person I could find having vocalized such an issue received no response (http://forum.square-enix.com/ffxiv/t...-Please-Assist) but the described issue is identical to that which I am experiencing.


Has anyone else had this problem? Anyone know of a solution other than disabling the hair trigger locks? I'd rather use them since it's not only easier on the wrists (tendonitis sucks) but it also reduces the time, or it would were it working properly, it takes to activate the cross hotbar skills.


Thanks in advance!

[Llethander]

Still hoping for a possible solution for this. Is there perhaps a way to edit the LT and RT dead zones to make the triggers both more responsive and allow the hair triggers to work?

[Dynratygus]

Good afternoon and thank you for posting on the Final Fantasy XIV Technical Support Forums.

How long have been experiencing this issue? Do you have the same problem when using a different controller?


Thank you for visiting the Final Fantasy XIV Technical Support Forums.

[Llethander]

I only recently picked up the Xbox One Elite controller and it has been this way since I first tried using it. Roughly 2 weeks or so. I thought it was defective so I exchanged it for another but it does the same thing.

I can easily replicate the issue with a normal Xbox One controller by pulling the trigger until it registers the input (ie. the cross hotbar lights up showing it has become active) but this only truly becomes noticeable on the Elite controller since it has the hair trigger locks. It can be noted by how far in the trigger has to be pulled before the game registers the input as the setting for the triggers' dead zone settings. I don't believe there's any option to change this dead zone in game, which is the crux of the problem.

[Llethander]

https://youtu.be/a4hWfdbIZgk

Here's a video example and explanation of the issue.

[Tewl]

I found your video and posted a reply but I am experiencing issue with a wired xbox one controller. Having to hold the trigger down very hard for it to respond.

[Llethander]

I found your video and posted a reply but I am experiencing issue with a wired xbox one controller. Having to hold the trigger down very hard for it to respond.

That's odd. I was using a regular Xbox One controller connected by USB to my PC prior to the switch to the Elite Controller and I didn't run into that issue. First recommendation I would make is to download the Xbox Accessories app - it's a mostly-useless app, for the most part, but it's good for troubleshooting keypress issues if nothing else - and seeing if your system is registering the inputs prior to the point where you have to apply excessive force to the trigger to get it to register. It's possible that the switch the trigger uses is dying and knowing if your system is registering the input normally will confirm whether or not that is the case.

If the app registers the input normally then it points toward a potential issue with the game.

[Llethander]

Bumping the thread back up to the top.

[Einmimiria]

Thank you for the reply Llethander.

I tested a standard Xbox One controller and was able to replicate this. The Xbox One controller needed the trigger to be pulled about 50% to register. A PS4 controller didn't. I'm assuming this has to with the Xbox controller being native to Windows, so the game will register it as a trigger, while the PS4 is registered as a button. Unfortunately, there's no option in-game to adjust that sensitivity.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

[Llethander]

Darn, I was hoping there might be a way to work around it. I definitely see what you're saying and it completely makes sense since Windows recognizes the LT and RT on the Xbox controllers as Axis inputs instead of buttons.

Ah well, thank you for taking the time to investigate and respond.

Edit: I found a solution, hallelujah~! It's not a free solution, mind you, but I'm using a program called reWASD to remap the paddles on the back of the gamepad to keyboard inputs. This program also allows manual editing of the dead zones on the triggers AND pushing those edits to affect the actual hardware. This ultimately ends up with the trigger firing immediately as soon as it is pulled instead of at 50%