Search Issue Tracker
Fixed
Fixed in 1.5.1
Votes
0
Found in [Package]
1.5.0
Issue ID
ISXB-407
Regression
Yes
[Input System] PS4 Controller causes large CPU lag spikes when connected under certain settings
How to reproduce:
1. Open the attached project “IN-20593.zip“
2. Open the (Project Settings > Input System Package)
3. Ensure the “Background Behaviour” is set to “Ignore Focus”
4. Ensure the “Play Mode Input Behaviour” is set to “All Device Input Always Goes To Game View”
5. Open the Profiler window (Window > Analysis > Profiler) and set it to watch the Edit Mode
6. Connect a PS4 “DualShock” controller
7. Wait approximately 20 minutes
Expected results: No CPU spikes are present
Actual results: Regular CPU spikes between 100ms - 800ms are present in “Input.PreUpdate”
Reproducible with: 1.4.3, 1.4.4 (2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b15, 2023.1.0a18)
Not reproducible with: 1.4.2 (2020.3.41f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b12, 2023.1.0a16)
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
- CPU frame times spike at regular intervals in the Profiler when in Play mode with VSync enabled and using DX12 API
- UI Builder “Create Template” Fails with Invalid UXML and Missing Root Element Errors
- Decal not projected on top of a Lit Material when MSAA is disabled, and Rendering Path is Forward or Forward+ in a Standalone Build
- Separation lines between minimized fields become invisible when scrolling in the Profiler
- Drag & drop and object picker assignment fail when ExposedReference variables are used in a Timeline clip
Resolution Note (fix version 1.5.1):
Fixed in: Input System 1.5.1