Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.2.0a12
2020.2.0b2
Issue ID
1280168
Regression
Yes
[2020.2] Pressing "F" while the mouse hovers over the Hierarchy causes the Game window to lose mouse tracking input
How to reproduce:
1. Open the attached project named "Case_1280168"
2. Click from main menu "Game > Open > Episode 1 > Floor 1"
3. Enter Play mode
4. Observe that the crosshair is following the mouse cursor
5. Move the cursor to the Hierarchy window and press the "F" button
6. Move the cursor back to the Game window and Left-Click to fire
7. Try moving the crosshair again
Expected result: Once Left-Click is pressed, the Game window is re-focused and the mouse cursor is tracked
Actual result: Mouse cursor is not being tracked
Reproducible with: 2020.2.0a12, 2020.2.0b5
Not reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.8f1, 2020.2.0a11
Workaround: Changing the Game window's Aspect mode re-enables the mouse tracking
Comments (1)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Peter77
Oct 02, 2020 19:13
Related forum thread:
https://forum.unity.com/threads/case-1280168-regression-pressing-f-while-mouse-hovers-over-hierarchy-causes-to-break-game-input.976212/