Search Issue Tracker
Won't Fix
Won't Fix in 1.3.X
Votes
1
Found in [Package]
1.3.0
Issue ID
ISXB-121
Regression
Yes
Input System doesn't throw away Mouse Input before the actual Gameplay when Play Mode is active
Reproduction steps:
1. Open the attached project
2. Open the Console Window (Windows > General > Console)
3. Enter Play Mode and move your cursor away from the Play button
4. Observe the output in the Console Window
Expected result: Console Window output should be empty
Actual result: OnLook value logged in the Console Window is really high
Reproducible with: 1.2.0, 1.3.0, 1.4.0 (2020.3.22f1, 2020.3.33f1, 2021.3.0f1, 2022.1.0a10, 2022.1.0b16, 2022.2.0a11)
Not reproducible with: 1.2.0, 1.3.0 (2019.4.38f1, 2020.3.21f1, 2021.1.28f1, 2022.1.0a1, 2022.1.0a9)
Notes:
- Tested on Windows 10
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
- AdaptiveLOD sample has missing prefabs and throws missing prefab errors when the AdaptiveLOD sample is imported and the AdaptiveLOD scene is opened
- Error "transform.position assign attempt for 'x' is not valid" is logged when Moving Game Object to View while a Scene is multi selected
- [Desktop] Plastic move detection mixes up identical files
- SVG Icon has tessellation issues in "Antialiased Arc Encodings", ok with "Basic Triangulation"
- "You may not pass null objects" and "Maximized serialized file backup not found" errors are thrown when maximizing and minimizing docked Multiplayer Play Mode window after Multiplayer Play Mode package is uninstalled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.