Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0f3
Issue ID
891980
Regression
No
Input.GetAxis does not work after loading another scene while two axes are used/held simultaneously
How to reproduce:
1. Open attached project "InputBug_2018.3.0a8.zip" and scene "SampleScene"
2. Enter Play mode
3. In Game view, use WASD to move and walk into the green collider while holding W and A
4. Observe Game view after scene changes
Expected result: both W and A keys inputs are recognized and the player moves diagonally
Actual result: only A key is recognized and the player only moves left
Reproducible with: 2017.3.1p1, 2017.4.9f1, 2018.3.0a8
(2017.1.5f1, 2017.3.1f1 after scene load none of the input axes are working)
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
We are deprecating old input system bugs as we have moved all resources to the new input system.