Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.0b10
2018.3.7f1
Issue ID
1155153
Regression
Yes
Terrain F1, F2, F3, F4 shortcuts are not set
How to reproduce:
1. Create a new project
2. In Hierarchy window, create 3D Object -> Terrain
3. Press the "F1" button ("F1" according to the documentation selects "Paint Terrain" )
Expected result: "Paint Terrain" is selected
Actual result: nothing happens, terrain F1, F2, F3, F4 shortcuts are not set
Reproducible with: 2018.3.0b10, 2018.3.14f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Not reproducible with: 2017.4.27f1, 2018.2.21f1, 2018.3.0b9
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
- TouchScreenKeyboard.hideInput set from "true" to "false" when TextField is clicked in Android builds
- [Android] ReadPixels gives different results when using Vulkan on some devices
- [URP] Exceeding the platform's supported light limit gives shadow distortion when using Deferred Rendering Path
- URP Sample Buffer Image Tile is moved when the Offset Value is changed
- Static constructor in a struct returns false when running tests with IL2CPP
Resolution Note (fix version 2019.3):
Setup default bindings to F1 - F8