Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
Votes
3
Found in
2022.3.58f1
6000.0.38f1
6000.1.0b5
6000.2.0a2
6000.3.0a1
Issue ID
UUM-97174
Regression
No
SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
Reproduction steps:
1. Open the attached “IN-93020.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Click “Block WindowsKey 1” button
5. Press the Windows key on the keyboard
Expected result: The Windows key is blocked
Actual result: The Windows key still activates
Reproducible with: 2022.3.58f1, 6000.0.38f1, 6000.1.0b5, 6000.2.0a2
Reproducible on: Window 10 (User reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- Reproduces if Active Input Handling is set to “Input System Package (New)” or “Both”, but does not reproduce with “Input Manager (Old)”
- Reproduces both in the Editor and the Player
- Only reproduces when the Editor or the Player Window is in focus
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Add comment