Search Issue Tracker
Active
Won't Fix in 2023.2.X
Under Consideration for 2022.3.X
Votes
0
Found in
2022.3.6f1
2023.1.7f1
2023.2.0b3
2023.3.0a1
6000.0.0b11
Issue ID
UUM-44328
Regression
Yes
F13/F14/F15 buttons are not being recognized when used with the Input function in Scripts
How to reproduce:
1. Open the attached “IN-49290.zip” project
2. Open the “SampleScene” Scene
3. Enter Play Mode
4. Open the Console Window
5. Press FN+F13/F14/F15 on the Keyboard
Expected result: “Pressed F13/F14/F15” is logged
Actual result: Nothing is logged
Reproducible with: 2022.1.0a15, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1
Not reproducible with: 2021.3.29f1, 2022.1.0a14
Reproduced on: macOS Ventura 13.4 (Intel), Windows 10 (User reported)
Notes:
- Reproducible on a new project
- Reproducible in Player
- Keyboard used: “Magic Keyboard with Numeric Keypad”
- Scripting Reference documentation shows that it is still present/supported: https://docs.unity3d.com/ScriptReference/KeyCode.html
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
- Fix for 2022.3.X: Flickering of HDRP Directional Light shadows with DirectionalMixedCachedShadows when in an Entities Graphics rendered Subscene
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.