Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1138688
Regression
No
Standalone player does not load previous Inputs when "Display Resolution Dialog" is set to "Hidden By Default"
How to reproduce:
1. Open attached project "OldInputSettings.zip" and scene "Example"
2. Make sure that "Edit" -> "Project Settings" -> "Player" -> "Resolution and Presentation" -> "Display Resolution Debug" is set to Hidden By Default
3. Build and Run the game and hold "Alt" key immediately, a "Player Pref Bug Configuration" window will appear
4. Go to "Input" tab and change the "Red" Control to button "q"
5. Press "Play!", when the game loads press button "q", the Cube is going to be colored red
6. Exit the game
7. Open the build again
8. When the game loads, press button "q"
Expected result: the Cube is colored red
Actual result: the Cube is not colored red, only the default Input button is coloring the Cube (button "r" which is in "Edit" -> "Project Settings" -> "Input" -> "Axes" -> "Red")
Reproducible with: 2017.4.24f1, 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
With the move to the new input system package found here https://github.com/Unity-Technologies/InputSystem and in the Unity Package Manager, the old input system is being detracted.