Search Issue Tracker
Fixed
Fixed in 6000.0.78f1, 6000.3.19f1, 6000.5.1f1, 6000.6.0b1
Votes
0
Found in
6000.0.77f1
6000.3.18f1
6000.4.0a4
6000.5.0b10
6000.6.0a7
Issue ID
UUM-143528
Regression
No
[Linux] Input System does not register the backButton or forwardButton when using the Linux Editor
How to reproduce:
1. Create and open a new HDRP project
2. Open Window → Package Manager -> Package Manager → Unity Registry
3. Install the Input System package
4. Open Window → Analysis → Input Debugger
5. Double-click the mouse icon
6. Try pressing the mouse forward and back buttons
7. Observe the “Value” column in the backButton and ForwardButton rows
Expected result: backButton or forwardButton “Value“ changes to 1 when the buttons are pressed
Actual result: backButton or forwardButton “Value“ remains 0 regardless of whether the buttons are pressed or not
Reproducible with: 0.2.10-preview (2023.1.0a4, 6000.0.62f1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4), 1.15.0 (6000.0.62f1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4)
Reproducible on: Ubuntu 22.04
Not reproducible on: Windows 11
Update:
Important note. While testing we noticed inconsistent behavior with some mice. We determined that this is not OS or driver specific but rather a peculiarity of the mouse.
For example with the mice we have tested with.
A 2013 Razer DeathAdder behave as you would expect. Hold the button down and you see the value in the Input debugger goes to 1. Release and it goes to 0. Great!
The Logitech MX Anywhere 3 coalesces both the press and release events and send them upon the buttons release. So in the debugger you see a quick flip to 1 then back to 0.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Visible instance buffer returns 0 for every instance when using BatchDrawCommandIndirect on Adreno devices with Vulkan API
- [Android][Vulkan] Native crash in AndroidVulkanVideo::ProcessFrame and AndroidVulkanVideo::Context::~Context() when switching screens
- Screen brightness is not set to a default value when Screen.brightness is set to a negative value
- macOS app window title is not localized when built from generated Xcode project
- Unity Hub doesn't preserve the changed Channel when manually restarting the Hub
Resolution Note:
Fixed in 6000.6.0b1
Resolution Note (fix version 6000.6.0b1):
Fixed in 6000.6.0b1