Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

2

Found in [Package]

0.0.9-preview

Issue ID

1091915

Regression

No

[Windows][Gamepad] DualShock added twice if DS4Windows/DS4Tools is installed and XInput support enabled

Package: Input System

-

Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/188

If DS4Windows or DS4Tools is installed and XInput support is enabled, then a DualShock gamepad plugged into the machine will be visible both as a HID and as an XInput controller. This leads to the input system adding both a DualShockGamepadHID and an XInputControllerWindows gamepad for what underneath is the same device.

This is likely going to be hard to detect on our side. We filter out XInput HIDs added by Microsoft's driver to solve the same situation there. However, doing the same the DS4Windows/DS4Tools case is likely not going to be as straightforward.

The XInput API makes it impossible to tell which device sits behind an XInput controller index. So to handle this case, it seems we'll have to determine whether a given HID is a DualShock controller and then detect whether DS4Windows/DS4Tools is present and running with XInput enabled for the app.

Hopefully there's a simpler solution.

  1. Resolution Note:

    This is currently due to the design of the DS4Windows/Tools. Use the "Hide" option in DS4Windows before starting your project/game.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.