Search Issue Tracker
Fixed in 2022.3.62f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.X, future release
Votes
0
Found in
2022.3.6f1
2023.1.7f1
2023.2.0b3
2023.3.0a1
6000.0.0b11
6000.1.0a7
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Add comment