Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.47f1
2021.3.24f1
2022.2.17f1
2023.1.0b14
2023.2.0a12
Issue ID
UUM-34329
Regression
No
[Input Manager] Input.mousePresent property always returns true when all pointing devices are disconnected
How to reproduce:
1. Open the “MousePresentBug“ project
2. Open the “SampleScene“
3. Enter Play Mode, and observe the Game View
4. Exit Play Mode, and disconnect all pointing devices (mouse, trackpad, touchpad)
5. Enter Play Mode (Ctrl + P), and observe the Game View
Expected result: “Input.mousePresent: False” is displayed
Actual result: “Input.mousePresent: True” is displayed
Reproduced with: 0.2.10-preview (2020.3.47f1), 1.5.1 (2020.3.47f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a12)
Reproduced on: Windows 10 (by reporter), Windows 11
Notes:
1. Also reproducible in Player
2. If using Windows and a laptop disable the trackpad/touchpad in Windows settings (Settings > Bluetooth & devices > Touchpad)
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.