Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.2.0a14
Issue ID
UUM-35260
Regression
No
"leftButton" value stays 1 when clicking once to gain focus on the build
Reproduction steps:
1. Create an empty project
2. Install the “Input System” package through “Window\PackageManager”
3. Enable “File\Build Setting\Developement Build”
4. Build And Run the project
5. Open “Window\Analysis\Input Debugger”, select “OSXPlayer” and attach “Devices\Remote\OSXPlayer\Mouse1”
6. Click anywhere in the build
7. Observe the Mouse1 Input Debugger
Expected result: “leftButton” value changes to 0 after letting go of the button
Actual result: “leftButton” value stays 1 after letting go of the button
Reproducible with: 1.4.4, 1.5.1 (2020.3.48f1, 2021.3.24f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13)
Reproducible on: macOS Ventura 13.2.1 (Intel)
Not reproducible on: Ubuntu 22.10, Windows 10
Note: after clicking anywhere in the build for the second time, the value behaves as expected
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.