Search Issue Tracker
Won't Fix
Won't Fix in 1.1.X
Votes
0
Found in [Package]
1.1.1
Issue ID
ISXB-49
Regression
No
[Windows] Crash on InputDeviceIOCTL with DS4 + Strike Pack Eliminator
Reproduction steps:
1. Create a new project
2. Install the Input System package using the Package Manager
3. Connect a PS4 Controller and the Strike Pack Eliminator
Expected result: The Editor doesn't crash
Actual result: The Editor crashes
Reproducible with Input 1.3.0: 2021.2.10f1, 2022.1b5, 22.2a5
Doesn't crash on MacOS
Stacktrace:
0x00007ff6acf58c90 (Unity) InputDeviceIOCTL
0x00007ff6abf07e2e (Unity) NativeInputSystem_CUSTOM_IOCTL
0x000001f401d33ca3 (Mono JIT Code) (wrapper managed-to-native) UnityEngineInternal.Input.NativeInputSystem:IOCTL (int,int,intptr,int)
0x000001f401d33b83 (Mono JIT Code) \[NativeInputRuntime.cs:43] UnityEngine.InputSystem.LowLevel.NativeInputRuntime:DeviceCommand (int,UnityEngine.InputSystem.LowLevel.InputDeviceCommand*)
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:
We'll have to be honest with ourselves that we won't be getting around to fixing this. Sorry.
For now this addon for the DS4 controller can be considered to be not supported.
Resolution Note (1.1.X):
We'll have to be honest with ourselves that we won't be getting around to fixing this. Sorry.
For now this addon for the DS4 controller can be considered to be not supported.