Dualsense joystick "snaps" to dpad directions #1915

Closed

opened 2026-11-10 20:18:38 +00:00 by Endvent · 5 comments

Endvent commented

2026-11-10 20:18:38 +00:00

(Migrated from github.com)

Hookshot version

v2.0.14

What kind of problem

Sound, controls or saves

What happened

Duplicate of #1480 which was closed despite not being fixed in latest version.

"Trying to play with a dualsense controller plugged in, joystick inputs "snap", almost like they're behaving as a dpad. But not quite as there's still some analog-ness to it but it really wants to snap to dpad directions."

Where in the game

Kokiri Forest

How often

Every time

Graphics card and driver version

RTX 4080 Super

CPU, RAM and operating system

Ryzen 9 7900x

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

Screenshots or video

https://private-user-images.githubusercontent.com/157522286/700493087-9caf36e3-0904-4847-861f-7562d0e53e62.mp4?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3OTQzNDIxMzgsIm5iZiI6MTc5NDM0MTgzOCwicGF0aCI6Ii8xNTc1MjIyODYvNzAwNDkzMDg3LTljYWYzNmUzLTA5MDQtNDg0Ny04NjFmLTc1NjJkMGU1M2U2Mi5tcDQ_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MTExMFQyMDE3MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hYzc1MzZkMjBmODkyNGJjOTEwN2Y5YTU5NjBkODZlMzUzMTY4NjlhMzZjOWZiZDUyYzI5MzMyM2ZlNTQzZjIxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9dmlkZW8lMkZtcDQifQ.GCxbzEsEv2BF49EiqSIOgcXMfTtpe-L7hZ0qVHTE2RU

Before you send it

I'm on the newest release, or the problem is still there on it.
I searched the open issues for this problem.
I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

### Hookshot version v2.0.14 ### What kind of problem Sound, controls or saves ### What happened Duplicate of https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/1480 which was closed despite not being fixed in latest version. "Trying to play with a dualsense controller plugged in, joystick inputs "snap", almost like they're behaving as a dpad. But not quite as there's still some analog-ness to it but it really wants to snap to dpad directions." ### Where in the game Kokiri Forest ### How often Every time ### Graphics card and driver version RTX 4080 Super ### CPU, RAM and operating system Ryzen 9 7900x ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34649641/hookshot_log.txt) ### Screenshots or video https://private-user-images.githubusercontent.com/157522286/700493087-9caf36e3-0904-4847-861f-7562d0e53e62.mp4?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3OTQzNDIxMzgsIm5iZiI6MTc5NDM0MTgzOCwicGF0aCI6Ii8xNTc1MjIyODYvNzAwNDkzMDg3LTljYWYzNmUzLTA5MDQtNDg0Ny04NjFmLTc1NjJkMGU1M2U2Mi5tcDQ_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYxMTEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MTExMFQyMDE3MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hYzc1MzZkMjBmODkyNGJjOTEwN2Y5YTU5NjBkODZlMzUzMTY4NjlhMzZjOWZiZDUyYzI5MzMyM2ZlNTQzZjIxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9dmlkZW8lMkZtcDQifQ.GCxbzEsEv2BF49EiqSIOgcXMfTtpe-L7hZ0qVHTE2RU ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

Endvent commented

2026-11-10 20:25:58 +00:00

(Migrated from github.com)

This is unlikely to have anything to do with input duplication as I don't have anything converting my dualsense inputs to xinput, and I also don't see why input duplication would bias my joystick input towards any angle in particular.

NotRexed commented

2026-11-10 20:46:32 +00:00

(Migrated from github.com)

Thanks for re-reporting; if it still snaps on v2.0.14, this needs a fresh look. Could you try the Insert menu's Stick dead zone at its lowest value, say whether it changes anything, and attach your hookshot_log.txt (its hid: lines name the controller and mapping)? Also: wired or Bluetooth, and is Steam Input on?

Thanks for re-reporting; if it still snaps on v2.0.14, this needs a fresh look. Could you try the Insert menu's Stick dead zone at its lowest value, say whether it changes anything, and attach your hookshot_log.txt (its `hid:` lines name the controller and mapping)? Also: wired or Bluetooth, and is Steam Input on?

Endvent commented

2026-11-10 20:53:54 +00:00

(Migrated from github.com)

[hos host] hid: controller "DualSense Wireless Controller" connected (SDL), with a gyroscope
[hos host] hid: motion controls from "DualSense Wireless Controller"
hookshot_log.txt

Steam input is not enabled, did try seeing if that would change anything back in v2.0.11 but it behaved the same. Connection is wired. Decreasing deadzone to 5% does seem to drastically increase analog granularity however it does not completely eliminate the issue. [hos host] hid: controller "DualSense Wireless Controller" connected (SDL), with a gyroscope [hos host] hid: motion controls from "DualSense Wireless Controller" [hookshot_log.txt](https://github.com/user-attachments/files/34650785/hookshot_log.txt)

NotRexed commented

2026-11-10 21:46:22 +00:00

(Migrated from github.com)

Possibly related (#1949): the Stick dead zone in v2.0.14 seems to be applied per axis rather than as a circle, and its lowest value is 5%. A per-axis dead zone pulls the stick toward the four directions near the axes, which can feel like snapping to d-pad directions.

NotRexed commented

2026-11-11 21:24:26 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2504, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2504 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened. Pull request #1600 works on this.