Search Issue Tracker
Fixed in 1.1.0-preview.5
Votes
0
Found in [Package]
1.0.2
Issue ID
1284958
Regression
No
Crash on UnityEngine.InputSystem.InputAction/CallbackContext when Behaviour is set to Invoke Unity Events and invoking Move()
How to reproduce:
1. Plug in a controller with "HID compliant game controller" drivers
2. Open project from "controller_crash.zip"
3. Open scene "SampleScene"
4. Enter Play Mode
5. Move a joystick or push a button on the D-pad in one direction and then move the mouse
Reproducible with: 2018.4.31f1, 2019.4.20f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4 (0.1.2-preview - 1.0.2)
First lines of stack trace:
UnityEngine.InputSystem.InputAction/CallbackContext
Notes:
1. Does not reproduce with Xbox 360 controller
2. Seems to only reproduce with HID compliant game controllers (any controller with Microsoft drivers does the job)
3. Editor.log added to Edit section
4. No real stacktrace
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
Resolution Note (fix version 1.1.0-preview.5):
Fixed in 1.1.0-preview.5 and above