Search Issue Tracker
Fixed in 1.2.0
Votes
0
Found in [Package]
1.1.0-preview.5
Issue ID
1337797
Regression
No
Unity crashes when changing Frame Size to 1 KB in Input Debugger for Bluetooth DS4 controller
Steps to reproduce:
1. Download and open the project "Lunarity.zip"
2. Connect a DS4 controller through Bluetooth
3. Open Input Debugger (Windows > Analysis > Input Debugger)
4. Double click on your Controller's name under Devices
5. Change the Frame Size to "1 KB" instead of "10 KB"
6. Confirm the change by pressing the Enter key
Expected result: The Frame Size changes to 1 KB on confirming the change
Actual result: The Editor crashes on confirming the change
Reproducible with: 1.0.2, 1.1.0-preview.5 (2019.4.28f1, 2020.3.12f1, 2021.1.11f1, 2021.2.0a20)
Could not test with: 2018.4.36f1 (No Input System 1.0.0)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment