Search Issue Tracker
Fixed in 5.2.2
Votes
46
Found in
5.2.0f3
Issue ID
726017
Regression
Yes
[OSX] Input.inputString, GetKey etc. does not work on Mac OSX
Steps to reproduce:
1. Open the attached project
2. Open 'InputStringTest' scene
3. Play the scene
4. Click any of the keyboard buttons
5. Watch the console, notice no input is logged despite the Debug.Log(Input.inputString) being called each frame.
Note: Works as expected on Windows.
Other users report also Input.GetKey, Input.GetKeyDown,
Input.GetKeyUp and Input.GetButton as broken
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
- Text field max length is -1 by default
- Field Max Length is set to the first digit typed instead of entire number typed
- D3D12 MainLight Shadowmap clear incorrectly when using UWP
- Crash on ShaderPropertySheet::SetTexture when changing color space on a specific project
- "ENABLE_INPUT_SYSTEM" flag is true even when the "InputSystem" package isn't installed
_Acid_
Sep 21, 2015 18:14
Suddenly, after working fine for 4 days, Unity 5.2 Input stopped working completely. All the above mentioned + Input.GetAxis() gives no response.
edwin_mindcandy
Sep 09, 2015 14:35
It also seems that using Input.GetButton and setting up a button in the Input settings is also broken.
edwin_mindcandy
Sep 09, 2015 14:30
It also appears that GetKey and GetKeyDown are broken which makes working around this quite tricky!
edwin_mindcandy
Sep 09, 2015 14:15
I've reproduced this. It's not great - it breaks my plugin (TouchConsole Pro).