Input/Accessibility – can't play with Dualshock 4

Windows 10, Steam + Dualshock 4 (Ver.2)

When used as is:

  • You can’t use controller in UI/menus.
  • Impossible to bind LT/RT axes since “button” input is registered first.
  • Sensitivity settings for steering axis are inadequate.

When used trough Steam Input/DS4Windows as an Xbox controller:

  • There are massive dead zones and input delay which can’t be removed

When used trough DS4Windows as a Dualshock 4:

  • Game somehow finds another xbox controller? I have HIDHide, and even in system control panel there is only one “game device”, which is the emulated DS4.
  • Constant flicker between keyboard and xbox prompts
  • “Controller” tab appears, which forces you to bind “pause”
  • Blanking “Controller” tab does not remove “dual input” issues (twitchy steering, camera spazzing out etc.)

This game so far is one with most amount of issues I’ve ever had, trying to play with DS4. How on earth does it manage to find “an xbox controller” on my system? And why selecting “Blank Layout” in “Controller” tab doesn’t work as expected? How people with Xbox controller + wheel are playing with no issues?

Best scenario would be using DS4Windows: it allows mapping buttons to keyboard for UI + accurate dead zone and sensitivity. However, game starts detecting weird xbox inputs this way. I’ve not seen any other game having this issue.

Possible solutions I’m seeing:

  • Stop interpreting random input devices as an xbox controller.
  • An option to ignore any/all “xbox controller” inputs outside UI/menu
  • Ignore “xbox controller” inputs for actions bound to a device in “Input” tab.

Remap Xbox One controller with powerful gamepad mapper (rewasd.com)

This tool allows for remapping from DS to an x-input device and hides the HIDs for you.

I know it’s not a solution but it might help you play in the short term - I personally paid for every feature in REWASD as I think it’s a brilliant tool but you shouldn’t need any of the fancy expensive features to get it working.

If I wanted to emulate an XInput device, I’d do that with either Steam Input or DS4Windows (free of charge, by the way), and not waste hours writing a pamphlet over here. Reason for avoiding Xinput was described above.

There are devices out there that don’t need mandatory 15% deadzone + layers of interpolation. They simply need to be picked up by the game correctly.

If FM23 wouldn’t make up an xbox controller out of nowhere (and try reading inputs from it), there wouldn’t be a problem.

Fair enough - just a thought I found it useful in the past.
I hope they fix the issues you describe.

1 Like

OK so I managed to get more or less serviceable results using info from this topic, by changing one of the default wheel presets.

It’s even usable in menus now. Not involving 3rd party programs, too.

There are some issues still however:

  • Steering is too sensitive near center, even at 0-1 Linearity setting. Some options for finer adjustment, and output visualisation (like in BeamNG) would be nice.
  • Binding left or right stick to camera rotation makes view spaz out, unless stick is perfectly centered
  • No DS4 button prompts :disappointed:
  • No vibration

I’d gladly provide preset file to dev team, so they can include it as an officially supported device.

Game theoretically supports any DirectInput controller. One would suspect that having more presets for popular devices attracts more people into the game?

If y’all at T10 ain’t bringing support for those devices (availablility/licensing issues or whatever), at least document your xml files. Let community make proper custom device templates.

Bonus issue found after playing some online races:

Most of issues above will affect any/all DirectInput controllers (and wheels!) as well, not just Dualshock.