Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InputCommon: Don't treat two analog inputs as a spurious trigger combo #11897

Merged
merged 1 commit into from
Jun 8, 2023

Conversation

JosJuice
Copy link
Member

@JosJuice JosJuice commented Jun 6, 2023

I've received a report from an Android user with a gamepad (a "BSP-D3") where one physical trigger is controlling two analog axes at the same time. This was causing RemoveSpuriousTriggerCombinations to delete both axes, which is clearly not a desireable outcome.

With this change, now the axis with the greatest smoothness is kept, or both in case they have the same smoothness.

I've received a report from an Android user with a gamepad (a "BSP-D3")
where one physical trigger is controlling two analog axes at the same
time. This was causing RemoveSpuriousTriggerCombinations to delete both
axes, which is clearly not a desireable outcome.

With this change, now the axis with the greatest smoothness is kept,
or both in case they have the same smoothness.
@AdmiralCurtiss
Copy link
Contributor

Seems fine, and the stated use case of the PS4 triggers still works correctly.

@AdmiralCurtiss AdmiralCurtiss merged commit 6513519 into dolphin-emu:master Jun 8, 2023
14 checks passed
@JosJuice JosJuice deleted the spurious-two-analog branch June 8, 2023 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants