DualShock 4, DS4Windows, and Input Mapper

[Trigger]

Not sure why, but the latest patch has completely prevented me from playing 20XX using a DualShock 4 via DS4Windows. The "improved" version, Input Mapper (which in my opinion is a larger, clunkier, less efficient mess of a GUI with inferior functions and terrible light bar colors -- and contains ads unless you pay!), still works, but DS4Windows does not. I'd vastly prefer to continue using DS4Windows.

[Tetsuo9999]

The game should see the DS4 as a DirectInput controller. I haven't had to use DS4Windows with this game in over a year. It should show up as "Wireless Controller" in the button config menu.

[Trigger]

Goodbye to using the light bar to indicate wireless controller latency, I suppose.

Also, the mappings for DirectInput fail so incredibly hard. Square is registered as the A button instead of the X button. The right trigger is registered as the START button. I had none of these problems via DS4Windows.

Here's a screenshot of how DirectInput thinks my controller has to be set up in order to function like an Xbox 360 controller:

http://puu.sh/qWRYC.jpg

In English:

• Cross = A
  
• Square = B
  
• Options = "?" ain't a button I'm aware of
  
• Circle = X
  
• Right Trigger = START

...and those are just the ones I actually use. Who knows what the rest might be?

[HeroMystic]

Trigger, did you try running DS4Windows and 20XX as admin?

[Trigger]

I'm always logged in as an administrative user, and I have UAC completely disabled. Everything I run is "as admin".

[Zero]

I have the same experiene. I use a Wii Classic Controller Pro with an adapter and it sees it that way. Doesn't really interfere with play.

[Trigger]

Aye, but that doesn't mean it should be visually confusing.

[batterystaplegames]

Agree that it sucks - hopefully we have time for better non-360 controller support before launch.

Does the controller work properly, albeit super confusingly?

[Zero]

Originally posted by Mega Man Trigger:

Aye, but that doesn't mean it should be visually confusing.

If our button layouts are treated as an Xbox 360 controller, it's already visually confusing.

[Trigger]

Originally posted by Zero:

Originally posted by Mega Man Trigger:

Aye, but that doesn't mean it should be visually confusing.

If our button layouts are treated as an Xbox 360 controller, it's already visually confusing.

Indeed, and reordering the buttons such that I can't visually jump between controllers for reference makes it much harder to live with that.

Originally posted by batterystaplegames:

Agree that it sucks - hopefully we have time for better non-360 controller support before launch.

Does the controller work properly, albeit super confusingly?

Yes. Its function is proper, once configured; it's just tedious to set up and sometimes confusing during play (since the Xbox 360 buttons being referenced don't line up with the buttons on the DualShock 4).

[Prof_Ghal]

I've been using my DualShock 4 with DS4Windows for the past 3 months. The only time I've ever had issues with it is when I accidentally launch 20XX before launching DS4Updater. In that case I have button remap confusion issues similar to those described above, and to fix it I just close the game, launch DS4Updater and relaunch 20XX, and it works fine.

Not sure how the latest patch could have killed DS4Windows for some but not others.

RE: DS4Updater/DS4Windows, Some troubleshooting things off the top of my head:

Make sure 'Hide DS4 Controller' is checked under settings

Check Devices and Printers, sometimes I had issues with my PC's bluetooth picking up the controller wirelessly, and this would interfere with other instances of the same game controller, like it being considered an XBOX360 controller from DS4Updater.

If you're not using any bluetooth and have the controller wired via USB, check to make sure there is an "XBOX 360 Controller for Windows". There might also be a "Wireless Controller" as well. I think this is because the DualShock4 being connected shows up as "Wireless Controller" and then running DS4Updater adds an emulated "Xbox 360 Controller for Windows", but it's essentially 2 controller devices from 1 physical controller.

Right click the "Xbox 360 Controller for Windows" and go to "Game Controller Settings" and make sure that 'Controller (XBOX 360 For Windows)' is selected with Status 'OK'. Check 'Advanced' and make sure that 'Preferred device:' is "Controller (XBOX 360 For Windows)". Go to properties to test out the buttons.

http://imgur.com/a/QP40a

This is the profile I'm using currently.

I can provide some more images of the profile or other troubleshooting tips above if requested.

[Samer Sultan]

I'm currently using DS4 with DS4Windows (Jays2Kings build) with no issues at all.

You can rebind everything right in the program its self also.

[Trigger]

It appears that DS4Windows was not actually mapping to Xbox 360 (the 360 controller was failing to show up in my device list). Given that it worked perfectly for so long, I'm at a loss to ascertain what caused the failure. After far too much finagling, including reinstalling all relevant drivers and using the Windows 10 method on Windows 7, I finally managed to restore DS4Windows to working order. Hell if I know what happened or what ultimately fixed the problem.

DirectInput could still stand better support. =P

[SILVERAMMO]

Originally posted by ∆V:

I've been using my DualShock 4 with DS4Windows for the past 3 months. The only time I've ever had issues with it is when I accidentally launch 20XX before launching DS4Updater. In that case I have button remap confusion issues similar to those described above, and to fix it I just close the game, launch DS4Updater and relaunch 20XX, and it works fine.

Not sure how the latest patch could have killed DS4Windows for some but not others.

RE: DS4Updater/DS4Windows, Some troubleshooting things off the top of my head:

Make sure 'Hide DS4 Controller' is checked under settings

Check Devices and Printers, sometimes I had issues with my PC's bluetooth picking up the controller wirelessly, and this would interfere with other instances of the same game controller, like it being considered an XBOX360 controller from DS4Updater.

If you're not using any bluetooth and have the controller wired via USB, check to make sure there is an "XBOX 360 Controller for Windows". There might also be a "Wireless Controller" as well. I think this is because the DualShock4 being connected shows up as "Wireless Controller" and then running DS4Updater adds an emulated "Xbox 360 Controller for Windows", but it's essentially 2 controller devices from 1 physical controller.

Right click the "Xbox 360 Controller for Windows" and go to "Game Controller Settings" and make sure that 'Controller (XBOX 360 For Windows)' is selected with Status 'OK'. Check 'Advanced' and make sure that 'Preferred device:' is "Controller (XBOX 360 For Windows)". Go to properties to test out the buttons.

http://imgur.com/a/QP40a

This is the profile I'm using currently.

I can provide some more images of the profile or other troubleshooting tips above if requested.

your tip to hide DS4 in the settings helped a lot thanks.

[A Tater]

Another solution is to go big picture mode in steam and select ps4 configuration, works perfectly and no need to run ds4windows/directinput/etc.