Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.0f3
Issue ID
912543
Regression
Yes
[OS] Standalone build, cannot configure inputs on resolution dialog
Steps to reproduce:
1. Build a new project
2. Run the game
3. Select input tab
4. Double click on any entry to change it
Expected Results:
Pressing a button/key is accepted
Actual Result:
No matter what key/button is pressed, the inputs is not recognised and the "Press the button or key for..." dialog is displayed. It never goes away, you cannot escape it or select any other option or button, leaving you to Force Quit the game.
Reproduced in: 2017.1.0b6, 5.6.1f1, 5.6.0b1
Not reproduced in: 5.6.0a6, 5.5.3p3
Regression since: 5.6.0b1
Reproduced using macOS Sierra 10.12.4
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
This is a duplicate of issue #900969