-
If I upgrade to 1.2 on 2021.1.23 or .28 I get mouselook drift. It never resets back to resting at (0,0). Once you move on an axis you’re going to drift some amount forever. Pretty straightforward code built on top of StarterAssetsInputs first person controller. Action: Value, Control: Vector2, Binding: Delta [pointer]. Just reading out the Vector2. Works fine on package version 1.0.2. Move and look with sticks, which are controls under the same action(s), work fine (360 controller, wired)
-
Any attempts to track down this DualShock bug ? I get this on every combination of unity version and input system package version. Tried 2021.1.23, .1.28, and .2.3. If you use Bluetooth instead of wired mode it goes absolutely haywire (No, I’m not using the specific dongle that is called out in the docs as unsupported. Just built in laptop Bluetooth). I’m just on a Windows 10 laptop with a standard, official, came-with-the-PS4 DualShock 4 controller.
(Nothing to do with the Steam speculation in that there. Did a clean restart where Steam was never active)
You say you “”““support””" DualSense but I fear it’s the same kind of “”“”“support”“”" this other extraordinarily common controller is receiving. Even if it’s a 0.5% edge case that’s a non-starter; publish a commercial game like this and you appear to your users as unprofessional. If 20% of players own this controller and 1-in-200 get this bug that’s 1-in-1000 paying customers you’re telling “uh, yeah, you have to do some crazy thing to get my game working [e.g. DS4Windows] because I built this game in Unity”.
Going on 1.5 years now. Might we see progress by the 2 or 3 year mark?