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
- Trees painted on a Terrain are not affected by any Wind Zone when those trees are part of an LOD Group
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
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).