Y1 in gamepad mode is permanently bound to middle mouse

[Neltulz]

Device manufacturer

• LENOVO

Device model
Legion Go 2 Z2E 32GB

Handheld Companion Version
0.28.1.6

Describe the bug
In gamepad mode, and PS4 dual shock mode, the Y1 button is permanently bound to middle mouse button. I cannot unbind it no matter how hard I try. I have all of the legion space software disabled. I have GeForce Now added as a non-steam game in Steam and I have Steam Input Enabled for this. Steam considers this a PS4 controller.

To Reproduce
Steps to reproduce the behavior:

1. Set Y1 to disabled
2. Watch as it doesn't work.

Expected behavior
Pressing Y1 should do nothing

Screenshots
N/A

Logs file
N/A

[Brodooski]

I had the same problem, my only solution was to rollback to a version before your original comment. I ended up on 28.0.0

[Valkirie]

Let me check

[Brodooski]

In my case I'm on Legion go OG Z1E 16gb
I experienced this issue with Legion Go and Legion Go 2 controllers.
In almost any shooter game I map "A" to the Y1 to be able to jump.
While playing fortnite I would place a ping Everytime I jumped.
In Cyberpunk 2077 a grenade would be thrown while jumping.

[Valkirie]

Issue reproduced, fix on the way.

[Valkirie]

Issue was fixed on forthcoming nightly build for early access members.

It was caused by a byte misalignment, which in returns caused Y1 to also send a Mouse middle click. While at it, I've also improved the touchpad experience a bit.

[Brodooski]

After updating to both 0.28.4.5 & 0.28.4.6, I'm still encountering the issue. With the Legion Go & Go 2 controllers on the original Legion Go

[Valkirie]

Well that's an issue. I can no-longer reproduce. Could it be you use a old controller firmware ?

[Brodooski]

LegionSpace says the controllers are up to date. Interesting note. When Handheld Companion and Legion Space are both open the y1 key stopped activating middle mouse click and instead was set to controller home i.e. Xbox/Sony button and would cause steam to open. I assume because they were conflicting with one another

[p3stuff]

Opened a fix here: #1384