Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2020.3.X, 2021.3.X
Votes
1
Found in
2019.4
2020.3
2021.2
2021.2.7f1
2022.1
Issue ID
1402940
Regression
No
Control keys are inverted in the Editor after switching to open app or window and back to the Editor
Reproduction steps:
1. Open the attached 'InputSystemTest1' project
2. Open the 'SampleScene'
3. Enter Play mode
4. Note that the 'option' ('alt') key is not pressed and 'Key pressed: false' is logged in the Console
5. Switch to any other active window, press and hold the 'option' ('alt') key
6. Switch back to the Game View of the Editor window without releasing the 'option' ('alt') key
7. Observe the Console
Expected result: 'Key pressed: true' is logged in the Console
Actual result: 'Key pressed: false' is logged in the Console and the 'option' key is inverted
Reproducible with: 2019.4.35f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b2, 2022.1.0b9
Not reproducible with: 2022.2.0a1, 2022.2.0a5
Note: Reproducible also with 'Shift' and 'Ctrl' keys
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
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a1