I Keep Throwing Batarangs When I Release LT

[Tyler]

Whenever I hold down LT to ready any gadget, and then release it, I throw a batarang as if I was tapping it for a quick throw. It seems to mainly happen right after performing a quick throw. If I use the gadget then it stops happening till I throw another one. Any fix for this? It's gotten me killed a few times when I'm trying to be crafty in the midst of armed thugs.

I'm using a PS4 controller. I don't know if that may be a factor.

[Andrei]

This happens to me with an Xbox One controller. It triggers once when I press it and again when I release it. It happens in all Arkham games. It's very annoying, especially in Predator encounters. I found no way to fix it, other than look up before I release the button. At least now I know it's not just the X1 controller, cause I tried 2 of them and it's the same.

[Tyler]

That's unfortunate. Never happened when I played it back on PS3. Oh well.

[㊕ [̲̅f̲̅σ̲̅x̲̅] ㊕]

♥♥♥♥

[Andrei]

I actually found a solution to my problem. In Steam, I went to settings, controller, general controller settings and disabled "Xbox configuration support". And now it works fine. The problem was in every Steam game and started when Steam introduced this feature, though I didn't realize it then.

Give it a try. I'm curious if this solves it for your PS4 controller.

[Tyler]

Already have that disabled in my settings. Thanks for trying to help though. :)

[Qmzn]

I've suddenly been having these same issues with my Xbox 360 controller, and so has a friend while playing Arkham Origins. I think I've figured out the culprit, and how to fix it.

On Dec. 13th, 2017, there was a Steam client update that made a *lot* of changes to how controllers are handled in Steam. This seems to be part of Valve's push to bring all game controllers in Steam under one umbrella, called "Steam Input".

Unfortunately, as part of this initiative, I believe Steam is now intercepting *all* Steam-Input-compatible controller signals before they reach games, even outside of Big Picture Mode.

This wouldn't necessarily be a problem -- and might even be a blessing, in some cases -- except that this process seems to be built around the default "Gamepad" template in the Steam Input Configurator. This template is designed for the Steam Controller -- specifically, its dual-stage triggers. When you perform a "Full Pull" on either trigger, the template is built to send a SECOND analog trigger signal at maximum strength.

While this seems to work properly when using the actual Steam Controller, Xbox and PS4 controllers do not have dual-stage triggers, so this default "Gamepad" template causes all sorts of weird issues when you move the triggers in and out of the "Full Pull" range.

Some games just ignore this weird signaling, but *not* the Arkham games. These doubled trigger signals cause all sorts of problems -- two quick-fire Batarangs from a single trigger pull, a quick-fire Batarang when releasing a fully-held trigger, unintentional quick-fire freeze grenades when sneaking, and more.

So, how to fix it? Well, as of right now, there's two ways.

For either fix, start by entering Big Picture Mode. Head to the Settings page, via the gear icon in the upper right. Choose "Controller Settings". If you are using an Xbox 360 or Xbox One controller, enable "Xbox Configuration Support". If you are using a PS4 controller, enable "PS4 Configuration Support".

Method one, find your game under Big Picture's Library tab, and select it. Choose "Manage Game" on the left, then "Controller Options".

The setting "Use Steam Configuration for Non-Steam Controllers" should be set to "Global (Xbox)" if you have an Xbox controller, or "Global (PS4)" if using a PS4 controller. In either case, change this setting to "Forced Off".

You'd think this would be the same thing as just disabling Xbox or PS4 Configuration Support, but since the mid-December update, this no longer appears to be the case. Currently, enabling Steam Input support then setting "Forced Off' for each game seems like the only way to totally prevent Steam Input from intercepting your gamepad.

Now, if you actually *want* Steam Input to intercept your gamepad signals (perhaps to correct an old, worn analog stick that won't stay centered), then instead of choosing "Controller Options" under "Manage Game", choose "Controller Configuration".

This puts you in the Steam Input Configurator. Select "Browse Configs" at the bottom of the screen, then "Templates", then "Gamepad". Apply this template.

Next, enter the options for the Left Trigger on your gamepad. If "Full Pull Action" says "Left Trigger", choose that option and REMOVE the binding. The "Full Pull Action" box should be blank, while "Trigger Analog Output" should still be set to "Left Trigger".

Do the same thing for the Right Trigger -- remove the "Full Pull Action", but leave "Trigger Analog Output" as-is. When you are finished, the gamepad overview should just have the word "TRIGGER" over each trigger.

In my testing, this seems about the same as the "Forced Off" option, although the analog sticks probably have *slightly* different behavior.

Despite being handled in Big Picture, either of these changes should take effect when running games from Desktop mode.

[Tyler]

I tried this, but now my controller won't work, or even seem to be detected in-game. It still works in the Steam/Big Picture though.

[Qmzn]

After doing a little more research, I seems setting a Dual Shock 4 to "Forced Off" in Big Picture means it will not work with games that expect xinput (like the Batman: Arkham series, since it does not natively send xinput signals.

So if you have:

• 'PS4 Configuration Support' enabled in Big Picture's 'Controller Settings'.
  
• 'Use Steam Configuration for Non-Steam Controllers' under Arkham City's Big Picture configuration page set to 'Global (PS4)'.
  
• The 'Full Pull Action' binding disabled on both analog triggers.

-- and you're still getting Batarangs on LT release, or no input at all, then Steam's built-in Dual Shock 4 support is working incorrectly. This means your options for using a Dual Shock 4 are limited, especially in Windows 10. You might have to wait for a Steam client update to fix your issues...

If you're using a non-Dual-Shock-4 PS4 controller, then you might try enabling 'Generic Controller Configuration Support' instead of 'PS4 Configuration Support' in Big Picture settings, and see if that makes a difference.

[Tyler]

Originally posted by Qmzn:

After doing a little more research, I seems setting a Dual Shock 4 to "Forced Off" in Big Picture means it will not work with games that expect xinput (like the Batman: Arkham series, since it does not natively send xinput signals.

So if you have:

• 'PS4 Configuration Support' enabled in Big Picture's 'Controller Settings'.
  
• 'Use Steam Configuration for Non-Steam Controllers' under Arkham City's Big Picture configuration page set to 'Global (PS4)'.
  
• The 'Full Pull Action' binding disabled on both analog triggers.

-- and you're still getting Batarangs on LT release, or no input at all, then Steam's built-in Dual Shock 4 support is working incorrectly. This means your options for using a Dual Shock 4 are limited, especially in Windows 10. You might have to wait for a Steam client update to fix your issues...

If you're using a non-Dual-Shock-4 PS4 controller, then you might try enabling 'Generic Controller Configuration Support' instead of 'PS4 Configuration Support' in Big Picture settings, and see if that makes a difference.

Yeah, I'm using an actual PS4 controller with the Sony USB wireless adapter.
I just tried to get the 'rang on release to happen in both games, and it didn't.
This seems to have fixed things. Thanks :D

[berkcetınc]

.

[drmv]

Originally posted by Qmzn:

For either fix, start by entering Big Picture Mode. Head to the Settings page, via the gear icon in the upper right. Choose "Controller Settings". If you are using an Xbox 360 or Xbox One controller, enable "Xbox Configuration Support". If you are using a PS4 controller, enable "PS4 Configuration Support".

Method one, find your game under Big Picture's Library tab, and select it. Choose "Manage Game" on the left, then "Controller Options".

The setting "Use Steam Configuration for Non-Steam Controllers" should be set to "Global (Xbox)" if you have an Xbox controller, or "Global (PS4)" if using a PS4 controller. In either case, change this setting to "Forced Off".

Worked for me with the Xone controller in Arkham Knight. Thanks.

[Ghost]

Check out your mouse settings. I had an issue similar to this and found it to be a mouse setting.
Has somthing to do with 1 click instead of a double click.