Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.3.0
1.4.3
1.4.4
1.5.0
Issue ID
ISXB-358
Regression
No
Keyboard input is not working in Play mode when using wildcard
Reproduction steps:
# Open the attached project “WildCardRepro“
# Open the “Assets/Samples/SimpleDemo/SimpleDemo_UsingPlayerInput.unity“ scene
# Choose “Player“ GameObject in the Hierarchy window
# Change the “Mask“ value of the “Mask Test“ Script component to “<Keyboard>/*“ or another “<Keyboard>/[wildcard]“ option
# Enter the Play mode
# Check the “Run” checkbox in the “Mask Test“ Script component
# Try to move using the “WASD“ buttons
Expected result: The GameObject can only move using buttons on keyboard
Actual result: There is no wildcard available for the keyboard
Reproducible with: 1.4.2 (2020.3.42f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b12, 2023.1.0a16), 1.4.3 (2020.3.42f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a18), 1.4.4 (2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.1f1, 2023.1.0a19)
Reproducible on: Intel MacOS Ventura 13.0
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
Wildcards are not supported on the mask currently. We have no plans to fix at this time. Using control schemes to filter out keyboard input is an alternative approach for handling this.