Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in [Package]
1.1.1
Issue ID
1364574
Regression
No
InputSystem rumble speed takes longer to start when connected via Bluetooth
How to reproduce:
1. Create a new empty Project
2. Go into Window -> Package Manager
3. Download the Input System package from the Unity Registry
4. Put the user attached "ControllerRumble.cs" script into the Assets folder
5. Create a new Empty Object in the scene
6. Attach the "ControllerRumble.cs" script on the Empty Object
7. Press Play
Expected result: Rumble speed is consistent regardless of the way of connection
Actual result: USB connection rumble is faster than Bluetooth
Reproducible with: 1.1.1 (2019.4.31f1, 2020.3.191, 2021.1.24f1, 2021.2.0b14, 2022.1.0a11)
Note:
* macOS requires 3rd party drivers to allow Xbox controller usage
* It would seem that when connected via Bluetooth and upgrading Streams, the rumble starts to take longer and longer
-
nikescar
Oct 08, 2021 17:36
I'd just like to be clear that everyframe that you set the Rumble with a Xbox controller connected via Bluetooth, it uses 10x the frame time as when connected via USB
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
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.