Dual Shock 4 - Can't rebind axes SOLVED

[Strozzapreti]

Just got this game and I was incredibly pleased to see full KB+M and controller binding support, as well as native DS4 support. Unfortunately, I cannot get the game to bind any of my stick axes for pitch, yaw, etc.

Has anyone else encountered this issue? At first, I couldn't bind any DS4 buttons and I realized that steam's controller rebinding might be interfering, so I disabled that. Now i'm able to rebind buttons and triggers, but not any of the thumbstick axes. The thumbstick works fine in menus and registers correctly in the calibration menu, so why is it that when I go to bind Pitch, Roll or Yaw, the menu fails to respond? Any help would be appreciated.

POSSIBLE FIX IF YOU EXPERIENCE THIS ISSUE:

Check your sensitivity setting for each axis in the calibration window. If it's below 50%, you won't be able to bind any of the thumbstick axes, so set it to 50% or above (at least while rebinding your controls).

[Marauder Interactive]

Hello,

Can you boot the game, try to change the axis, then quit and post your output_log.txt? You can find out how here: http://steamcommunity.com/app/283160/discussions/0/305510202679777602/#c133258092252958627 This will tell me what's happening with the controls on bootup and when you try to change something.

Also:

• What exactly are you trying to bind/change so I can try to reproduce it?
  
• Are you usually playing in VR? If so, which headset? What about Big Picture?

Thanks!

[Strozzapreti]

Here's the output_log.txt: https://pastebin.com/SKjaRh9z

Steps to reproduce:

1. Launch steam (non big picture) and connect DS4 controller via USB
2. Launch HODS (non VR)
3. Using controller, navigate to controller mappings menu
4. Menu recognizes DS4 controller
5. Attempt to bind pitch to RS Y axis
6. Menu appears instructing to center axis and press a button to continue
7. Press x (or wait for timeout) and a screen appears instructing to push a button or axis to bind it to pitch
8. Push RS up and down repeatedly, or hold it for the 5s duration, or flail wildly at it.
9. Window times out after 5 seconds and original binding remains.
10. Try steps 5 to 9 with LS Y axis too, just in case. Still nothing.

Note, I also tried clearing all axis bindings in case there was a conflict between binding an axis to more than one control. Even starting from no bindings, I couldn't bind pitch, yaw, or roll. Doesn't work when launching from big picture mode either. Hope this helps you figure out what's going on!

[Marauder Interactive]

Thanks for the excellent steps and log file. I'll take a look.

[Marauder Interactive]

Hello,

I just took a stab at this problem and despite your thorough steps I can't reproduce you problem binding gamepad sticks. I do have a few more questions though:

• Are you using any utility like DS4Windows that may be trying a bit too much to help? Those utilities are awesome, but aren't necessary for this game.
  
• What version of Windows are you running? 10? The log tells me many things, but that's not one of them.
  
• The binding module splits axes out for digital inputs like keyboards. I'm almost positive you're doing this right, but can you make sure you're binding the analog axis input? Here's my setup:
  
  http://i.imgur.com/pVXkpTH.png

Thanks!

[Strozzapreti]

No controller utilities. I only bought the DS4 after Steam started natively supporting it and I've just been using their config ever since. As I said, I disabled it for this game, though.

OS is indeed Windows 10. Think that could be causing a problem? I'm always on the lookout for excuses to revert, since I only really use Windows for gaming.

Thanks for the screenshot, but I'm definitely binding Pitch, rather than Pitch Up or Pitch Down. Is there any trick to making it recognize the analog input?

[Strozzapreti]

Also, here's a thought: Since you were able to successfully bind those axes, is that config stored in any kind of text file that I could copy over or edit into my game directory? Even though I can't bind LS Y, for example, I was able to pitch and yaw the ship using LS back when the default controls were configured. Maybe it would recognize RS as long as I had the file?

[Marauder Interactive]

I reproduced it after screwing around with the native Steam controller support! It was ignoring all buttons on rebind but otherwise the menus worked, just like you said.

I was able to fix it though. This is totally dumb but I had to register my account/controller for Steam to properly ignore it.

• Go to Steam->Settings->Controller
  
• At the bottom of the left column click the button underneath "Detected Controllers:" -- it *should* look like mine:
  http://i.imgur.com/gBR6d78.png
  
• Click Register, then Submit. This will tie your account to these control schemes.
  
• Make sure the rest of the menu looks like mine:
  http://i.imgur.com/hvFPlXU.png
  
• Unplug the controller, then plug it back in to power cycle it
  
• Launch the game either via Big Picture or normally
  
• Rebind your keys

Your instinct to just unregister everything would be mine too -- but it seems like Steam doesn't like that for some reason.

Let me know if this works.

[Strozzapreti]

Hmm. Although I disabled controller configuration, my DS4 was still registered to my account. Tried unregistering and re-registering it anyway, but that didn't help. I can bind buttons from the controller, but the axes still can't be bound.

Interestingly enough, I tried using one of my 360 controllers and I was able to rebind the axes with that, so the issue is soley with my DS4 controller. Unfortunately, since the bindings seem to be saved per-controller, I couldn't use the custom bindings I set up for my 360 controller with the DS4.

[Marauder Interactive]

Hmm... does launching the game via Big Picture help at all, since the PS4 controller has its setup there?

[Marauder Interactive]

Update: I might have been able to fix this. It's currently in the beta branch.

To access the beta, right-click the game in your Steam library and select "Properties." Go to the "Betas" tab and select "beta" from the dropdown box. Hit OK, and Steam should try to download the new version.

Basically, there's some unpleasantness with how the engine interacts with the new Steam native DS4 support. There was an old flag in the settings that might work around it.

Hope this helps -- let me know if it doesn't.

[Strozzapreti]

Good news! I installed the beta branch and it didn't fix it initially, so in frustration I was toying around in the calibration menu and I had a bit of a eureka moment. When I first launched the game, I noticed the sensitivity in the menus was a bit high, so I think I remember bumping it down in the calibration window before I went to bind my controls. What I noticed just now is that the white activation indicators weren't reaching all the way to the edge of the graph.

So, I bumped the sensitivity up to 50% to make sure that the activators reached the very edge of the graph, and now I can rebind everything. I dunno if this is something you can fix, but just in case (or until you do) I'll edit my response at the top for any other mystified players.

Screenshot of issue: http://imgur.com/a/Y8yrZ

There's still the issue with the steam controller profile, but it seems like as long as the controller is registered to your account and configuration is disabled, it works as expected. Thanks for all of your help! I think I'll go hunt some traitor lords now >.>

[Marauder Interactive]

Wow, that's a crazy stick calibration value. I wonder if the Steam controller calibration in Big Picture has anything to do with it. I initially thought it was there for the *actual* Steam Controller but evidently you can use it for the DS4 as well.

Regardless, thanks for following up on how you solved it.