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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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/