Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.3.1f1
Issue ID
583362
Regression
No
Input.inputString produces buggy behaviour for arrow keys
to reproduce:
1. Open attached inputtest project
2. Attach inputTest script to camera
3. Enter play mode
4. Enter some letters, followed by arrow keys. Left Arrow key seems to be especially bugged creating strange artifacts
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
hoveeagle
Apr 05, 2017 09:25
I still seem to be experiencing issues with the arrow keys and as far as i can tell, they are not even stored at all. This bug was reported ages ago so why hasn't it been fixed?