Would an XInput wrapper to fix gamepad deadzone issues be considered an illegal app?

[RetroNutcase]

I figured I'd ask here, because I'd rather get an official answer before trying anything. I use a Logitech F310 gamepad, which is a nice gamepad for the most part. Unfortunately, it has deadzone issues in FF14 where unless you press the left analog stick to the very edge of its axis, you won't run. This can be problematic in raids when you need to be able to move at full speed at a moment's notice.

In other games where I've had this issue, I've been using an XInput wrapper that lets you adjust the deadzone of the gamepad and add an "anti-deadzone" to compensate for hardware deadzones. This wrapper does utilize a modified xinput.dll to function, but is purely for re-mapping an xinput device or adjusting its axis sensitivity. It provides no unfair player advantage or does anything to modify the game, it simply tweaks gamepad input. Would this be allowable under the EULA or would it be something that would be detected as an illegal 3rd party app that could get me banned?

I've no interest in cheating in a game I love, but I'm worried that one of these days, my F310's iffy deadzone in 14 is going to make me walk when I need to *run* from a Megaflare and get me killed in T13. And before someone suggests another gamepad, believe me, I've considered that, but there's very few good Xinput gamepads for the PC beyond this and the official 360 controller, which has a HORRID d-pad (which would make skill usage near impossible).

[aerolol]

I think it's ok to use this kind of gamepad with the "compensator" driver.

I've had this issue you described with the original PS4 controller a few times, I can totally understand how frustrating it must be with a gamepad like yours which is a good one but has this walk/run issue all the time.

[RetroNutcase]

Hrm, would it be better to ask a GM via the support option ingame you think? I'd rather have a definitive answer.

[Raist]

Recalibrating doesn't compensate for it? Had a similar issue with a ps2 knockoff once, but running through Microsoft's calibration straightened it out.

[RetroNutcase]

Sadly no, a recalibrate won't fix it. This is a known issue with the F310. It's not a problem in *most* games, but certain games, depending on how they are set up, have issues with the F310 series.

Dark Souls 2 is another good example, where unless you either A) Restrict the game to 30 frames per second or B) Use the prior mentioned input wrapper will find yourself unable to reliably lunge/guard break (Quickly press forward+attack) because the F310 doesn't reach a "full tilt" state fast enough to register properly.