Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.1.0p5
Issue ID
945632
Regression
No
[Controller][Gamepad][Input][Mac] Game launcher input tab does not allow gamepad/controller input to be assigned
Reproduction steps:
1. Create new project
2. Build and Run for standalone
3. Open Input tab on game launcher
4. Double click on any of the input areas
5. Try to assign gamepad/controller input.
Notice: that nothing is happening until keyboard key is pressed.
Expected behaviour: Gamepad/Controller input is assigned to the corresponding input.
Actual result: Input assign does not react to gamepad/controller input.
Reproduced on: OSX 10.13
Works as expected on Windows.
Reproduced on versions: Unity 2017.1.2p3, 20172.0p4, 2017.3.0b11, 2018.1.0a6
Note: Unity 2017.1.2p3 crashes when input configuration window appears.
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
Add comment