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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
We are deprecating old input system bugs as we have moved all resources to the new input system.