Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
1
Found in
2020.2.0a12
2020.2.0f1
2020.3
2021.1
2021.2
Issue ID
1326568
Regression
Yes
Mouse Input is not detected correctly when pressing in the Game view after pressing the mouse button in other Editor windows
How to reproduce:
1. Open the "TestInput.zip" project
2. Open the "SampleScene" Scene
3. Make sure the Console window is visible
4. Enter Play Mode
5. Click anywhere in the Hierarchy window
6. Press and hold the left mouse button in the Game view
7. Observe the Console log
Expected result: "DOWN" is printed once and "HELD" is getting printed every frame
Actual result: "DOWN", "HELD" and "UP" is printed once (Input.GetMouseButtonUp(0) is fired even though the mouse button was not released and Input.GetMouseButton(0) is not being printed every frame)
Reproducible with: 2020.2.0a12, 2020.3.2f1, 2021.1.2f1, 2021.2.0a12
Not reproducible with: 2018.4.33f1, 2019.4.23f1, 2020.2.0a11
Note:
- The issue is not reproducible if the mouse button is not pressed in other Editor windows
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
- UpdateRendererBonudingVolumes process takes more time when disabled Renderers are used
- "ArgumentNullException: Value cannot be null" error is thrown when selecting a Visual Element with a custom Render Texture set as a background
- Changes are not saved when changing Styles' orders in the UI Builder
- “InvalidOperationException: Not enough space in output buffer (need 24, has 0)” error is thrown when using NativeList.GetVertices()
- High CPU usage when Spline Evaluate functions are used
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a17
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.13f1