FIX: Incorrect HID Stick values for LogicalMinimum with negative values

[jfreire-unity]

Description

This PR addresses the issues encountered when parsing data for devices that have LogicalMinimum values with negative values. Seems we weren't taking 2's complement values into account.

When parsing, we are now casting the bytes read to signed values. It also fixes an error when shifting bits to construct a 4-byte value.

Also includes fixes from user PR #2245

Testing status & QA

Tested with a Gamepad stick which has both signed short and byte for LogicalMin/Max of [-127,127] and [-32.768,32.767]

Overall Product Risks

• Complexity: 0
• Halo Effect: 1

Comments to reviewers

This is not easy to test without real devices that we don't have a layout for so I at least hope existing devices would still work.

One strategy could be to test this on macOS and comment this line:

InputSystem/Packages/com.unity.inputsystem/InputSystem/InputSystem.cs

Line 3798 in d1d72d5

XInputSupport.Initialize();

Then look if the sticks were well interpreted.

However, this only allows us to verify for devices that send Stick values as a signed short. For signed bytes I don't know of a device besides the ones users have reported in Discussions https://discussions.unity.com/t/input-system-reading-invalid-values-from-hall-effect-keyboards/1684840/3

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

[jfreire-unity]

Need to create a test with a report descriptor that fits this struct as well.

[Copilot]

Pull Request Overview

This PR fixes incorrect handling of HID stick values when LogicalMinimum contains negative values by properly implementing 2's complement parsing and sign handling.

• Corrects data parsing to handle signed byte and short values using proper casting
• Fixes a bit shift error in 32-bit integer parsing
• Updates stick control format determination to use a proper method instead of simple boolean check

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
HIDParser.cs	Fixes signed value parsing with proper casting and corrects bit shift error
HID.cs	Updates stick format determination and adds debug logging
HIDTests.cs	Adds comprehensive test for signed logical min/max values and refactors test helpers

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codecov-github-com]

Codecov Report

Attention: Patch coverage is 95.45455% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
Assets/Tests/InputSystem/Plugins/HIDTests.cs	95.12%	2 Missing ⚠️

@@             Coverage Diff             @@
##           develop    #2246      +/-   ##
===========================================
- Coverage    76.70%   76.65%   -0.06%     
===========================================
  Files          465      472       +7     
  Lines        87919    88304     +385     
===========================================
+ Hits         67442    67687     +245     
- Misses       20477    20617     +140     

Flag	Coverage Δ
inputsystem_MacOS_2021.3	5.90% <0.00%> (-0.01%)	⬇️
inputsystem_MacOS_2022.3	5.37% <0.00%> (-0.01%)	⬇️
inputsystem_MacOS_2022.3_project	74.53% <95.45%> (-0.05%)	⬇️
inputsystem_MacOS_6000.0	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_MacOS_6000.0_project	76.45% <95.45%> (-0.06%)	⬇️
inputsystem_MacOS_6000.2	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_MacOS_6000.2_project	76.44% <95.45%> (-0.06%)	⬇️
inputsystem_MacOS_6000.3_project	76.45% <95.45%> (-0.06%)	⬇️
inputsystem_MacOS_6000.4	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_MacOS_6000.4_project	76.46% <95.45%> (-0.05%)	⬇️
inputsystem_Ubuntu_2021.3	5.91% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_2022.3	5.37% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_2022.3_project	74.34% <95.45%> (-0.05%)	⬇️
inputsystem_Ubuntu_6000.0	5.19% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_6000.0_project	76.26% <95.45%> (-0.06%)	⬇️
inputsystem_Ubuntu_6000.2	5.19% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_6000.2_project	76.26% <95.45%> (-0.06%)	⬇️
inputsystem_Ubuntu_6000.3	5.19% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_6000.3_project	76.26% <95.45%> (-0.06%)	⬇️
inputsystem_Ubuntu_6000.4	5.19% <0.00%> (-0.01%)	⬇️
inputsystem_Ubuntu_6000.4_project	76.26% <95.45%> (-0.07%)	⬇️
inputsystem_Windows_2021.3	5.90% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_2022.3	5.37% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_2022.3_project	74.67% <95.45%> (-0.05%)	⬇️
inputsystem_Windows_6000.0	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_6000.0_project	76.59% <95.45%> (-0.06%)	⬇️
inputsystem_Windows_6000.2	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_6000.2_project	76.58% <95.45%> (-0.06%)	⬇️
inputsystem_Windows_6000.3	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_6000.3_project	76.58% <95.45%> (-0.06%)	⬇️
inputsystem_Windows_6000.4	5.18% <0.00%> (-0.01%)	⬇️
inputsystem_Windows_6000.4_project	76.38% <95.45%> (-0.27%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...m.unity.inputsystem/InputSystem/Plugins/HID/HID.cs	69.98% <ø> (ø)
...y.inputsystem/InputSystem/Plugins/HID/HIDParser.cs	87.95% <100.00%> (+4.71%)	⬆️
Assets/Tests/InputSystem/Plugins/HIDTests.cs	97.95% <95.12%> (-0.32%)	⬇️

... and 9 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ekcoh]

Thanks for looking into this. I am confused about our ReadData method, it is not yet clear to me how we handle sign-extended types of arbitrary bit sizes? E.g.
It's completely valid to have e.g. X with logical min -15 logical max 16, and hence Report size 5

[ekcoh]

I see CHANGELOG.md have not been updated yet, but if this PR picks up contribution work from @myss I suggest closing that PR: #2245, mentioned we re-reroute it via this PR and make sure to credit @myss in the CHANGELOG.md similar to previous user-contributions.

[ekcoh]

Generally looks very good, missing CHANGELOG.md entry it sounds like on your comment you intend to add more tests? Some minor comments.

[jfreire-unity]

Generally looks very good, missing CHANGELOG.md entry it sounds like on your comment you intend to add more tests? Some minor comments.

Thanks! Added changelog now and referenced the User PR in it. Feel free to do suggestions if it's not good enough

[Copilot]

Pull Request Overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[jfreire-unity]

/review

[u-pr-agent]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪ The PR involves low-level HID descriptor parsing which requires specific domain knowledge, but the changes are concise and supported by extensive new tests.

🏅 Score: 95 The PR provides a well-reasoned fix for signed value parsing, includes excellent and comprehensive tests, and improves code quality through refactoring and fixing an unrelated bug.

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Unmentioned Bug Fix The change from (data3 << 24) to (data3 << 16) when reading 32-bit data fixes a significant bug in the parser. This is a great catch, but it's not mentioned in the PR description. It's worth confirming this was an intended part of the fix. return (data4 << 24) | (data3 << 16) | (data2 << 8) | data1; Incomplete Context The layout builder now uses xElement.DetermineFormat() to set the control format. This is a good refactoring, but the implementation of DetermineFormat() is not in the diff. Please ensure this new method correctly handles all required formats based on element properties like bit size and signedness. .WithFormat(xElement.DetermineFormat()) .WithByteOffset((uint)(xElement.reportOffsetInBits / 8 - byteOffset)) .WithBitOffset((uint)(xElement.reportOffsetInBits % 8)) .WithSizeInBits((uint)xElement.reportSizeInBits) .WithParameters(xElementParameters) .WithDefaultState(xElement.DetermineDefaultState()) .WithProcessors(xElement.DetermineProcessors()); builder.AddControl(stickName + "/y") .WithFormat(yElement.DetermineFormat())

---

🤖 Helpful? Please react with 👍/👎 | Questions❓Please reach out in Slack #ask-u-pr-agent

[ericksson]

Cancelling all jobs running on this branch due to Android jobs being broken and stuck - see https://unity.slack.com/archives/C94RMJJ5T/p1760644095487229

Follow that thread to see when Lukas has a fix for the issue. Please refrain from rerunning the tests until the fix is available and you have it merged in this branch.