FIX: Fix for generic DualShock4 InputDeviceMatcher claiming DualSense devices too #1998
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A previous PR (#1990) improved the performance on DualShockSupport initialization by no longer requiring a RegEx match for DualShock3 and DualShock4 devices.
Unfortunately this had the unintended consequence of causing a DualSense device to be recognized as DualShock4.
This PR addresses that defect.
Changes made
Removing the extra .WithManufacturerContains() line reduces the score returned by these generic matchers ensuring the PID/VID matcher wins when matching DualSense devices.
Testing
Local testing, automated tests.
Risk
No risk - just restores the previous behaviour.
Checklist
Changed
,Fixed
,Added
sections.Area_CanDoX
,Area_CanDoX_EvenIfYIsTheCase
,Area_WhenIDoX_AndYHappens_ThisIsTheResult
.During merge:
NEW: ___
.FIX: ___
.DOCS: ___
.CHANGE: ___
.RELEASE: 1.1.0-preview.3
.After merge: