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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment