I’ve been using the new Input System to good results. I find it clear and convenient.
One oddity I’ve found in my setup is that my DualShock 4 controller, only when connected via bluetooth, needs its own set of bindings. I can’t use the [Gamepad] bindings, I need separate [DUALSHOCK 4 Wireless Controller] bindings. Connected via USB I don’t need them.
Maybe it has something to do with how via bluetooth, the Input Debugger shows a layout called: HID::Unknown DUALSHOCK 4 Wireless Controller
as opposed the layout when connected via USB: DualShock4GamepadHID
macOS 11.0.1
(I’ve been told it works fine over BT on Windows)
Unity 2020.1.17f1
Input System 1.0.1
I was just curious if anyone has more experience or info on this.
Not that big of a deal, just interested as to what the hurdle could be. Whether it’s a current macOS thing that’s unavoidable, etc.
I’m experiencing this too. Which is strange, because I feel like it was working correctly last week. Did you find a solution?
It seems to be functioning fine under the Device Debug View, but it’s not working when I play my game in the editor.
When I examine the PlayerInput component, I can see as HID::Unknown DUALSHOCK 4 Wireless Controller. Seems to be conflicting with Keyboard controls too.
I had to assign separate DUALSHOCK 4 Wireless Controller bindings (in addition to the generic Gamepad bindings) to every action. That (workaround? solution?) worked for our case.