Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.7.0
Issue ID
ISXB-716
Regression
No
StackOverflow error using input system after connecting Bluetooth controller in Editor and crashes in Build
Reproduction steps:
1. Open the attached “TestProject.zip“ project
2. Build And Run
3. Connect RadioMaster TX 12 or RadioMaster Pocket controller via Bluetooth and observe the Player
Expected result: Player doesn’t crash
Actual result: Player crashes
Reproducible with: 1.7.0 (2022.3.11f1)
Reproduced on: Windows 10 (by the reporter)
Notes:
- Not reproduced by CQA due to not having the required devices
- User noted that the issue does not occur with Xbox or DualShock controllers
- User noted that connecting RadioMaster TX 12 or RadioMaster Pocket controllers on Editor throws “Could not create a device for 'Ͽ USB (HID)' (exception: System.StackOverflowException: The requested operation caused a stack overflow. …” error
Comments (1)
-
Slava27061995
Jul 25, 2024 14:11
How did you connect RadioMaster to Unity? I have a problem in this case....... Can you help me with this? Maybe you have an example implementation?
I was considering options for event capture, also using the new input system, I managed to capture one axis, but the other axis shows a constant value of 1, and does not respond to changing the position of the manipulator.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The mentioned device is not currently supported and we were unable to test this locally. But in Input System version 1.12 we've made additional stability fixes which may prevent this crash