Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a4
2018.3.0a7
Issue ID
1065920
Regression
Yes
Wrong instructions provided in error message when Input Button name is not setup
How to reproduce:
1. Open attached project and "SampleScene"
2. Enter playmode and open console, observe the error message thrown
Actual result - "ArgumentException: Input Button wat is not setup. To change the input settings use: Edit -> Project Settings -> Input" error is thrown, which is wrong, since Input is not in a Project Settings anymore
Expected result - Error message contains this: "ArgumentException: Input Button wat is not setup. To change the input settings use: Edit -> Settings -> Input"
Reproducible with - 2018.3.0a7, 2018.3.0a4
Not reproducible with - 2018.3.0a3
Fixed in - 2018.3.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
Add comment