Search Issue Tracker
By Design
Votes
0
Found in
2019.2.3f1
Issue ID
1180680
Regression
No
"Input Axis Axis 1 is not setup" errors pop up when calling Input.GetAxis(stick.X_Axis_Name)
How to reproduce:
1. Open attached Unity project
2. Play InputDeviceTester scene
3. Select Xbox under Devices dropdown
Errors appear: ArgumentException: Input Axis Axis 1 is not setup.
Reproduced with: 2019.2.7f2, 2019.3.0b5, 2020.1.0a6.
Note: Can't test on 2017.4 and 2018.4 because of errors.
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note:
the InputDeviceTester visualizes input from both the old and new Input Systems. Now, for the old input system you need to correct setup in your Input Manager settings. As is documented in the Readme file for the sample, you should copy the InputManager.asset file into your project settings: https://github.com/Unity-Technologies/InputSystem/blob/aa36bb01336a7c7f74355377f6f84c3be0a59f86/Assets/Samples/InputDeviceTester/Readme.md
So, this is expected, and "by design". However, we realize that this is a bad and confusing design, so in future releases, we will distribute this sample as a .unitypackage file, which will then automatically import the settings (like we already do for some other samples for similar reasons).