Search Issue Tracker
Won't Fix
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
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.