Search Issue Tracker
Fixed
Fixed in 1.4.1
Votes
0
Found in [Package]
1.4.1
Issue ID
ISXB-268
Regression
Yes
Key input state is reverted to the opposite when Editor gets focused with the Key pressed down
How to reproduce:
1. Open project “InputTest.zip“
2. Enter Play Mode, press the Control key a few times and observe the result
3. Focus on your desktop to lose focus and hold the Control key
4. Focus Unity game window and release the Control key
5. Press the Control key a few times and observe the result
Expected result: Cube is visible
Actual result: Cube is not visible
Reproducible with: 1.4.1 (2021.1.0b10, 2021.3.4f1)
Not reproducible with: 1.4.1 (2020.3.37f1, 2021.3.5f1, 2021.3.6f1, 2022.1.10f1, 2022.2.0b1, 2023.1.0a3)
Could not test with: 2021.1.0a1, 2021.1.0b9 (Errors after project downgrade)
Reproduced on: macOS 12.4 (Intel)
Not reproduced on: Windows
Note: Not reproducible with the Old Input System
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
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
Resolution Note (fix version 1.4.1):
Fixed in: 1.4.1 (2021.3.5f1)