Search Issue Tracker
Fixed in 1.1.0-preview.6
Votes
3
Found in [Package]
1.1.0-preview.1
Issue ID
1271119
Regression
No
Dualshock4 SetLightBarColor and SetMotorSpeeds cannot be called on the same frame using Input System
How to reproduce:
1. Open the attached project ("DS4LightVibration.zip")
2. Open Sample Scene
3. Press Change Color and later Reset
~ Observe it does indeed change DS4 light bar color~
4. Press Start Vibrations and later Stop Vibrations
~ Observe it does indeed change DS4 vibration ~
5. Press Vibration then Color button
~ Observe it only changes Vibration, but not color ~
Expected result: Changing Vibration and Color on the same frame changes both
Actual result: Changing Vibration and Color on the same frame changes only one of them
Reproducible with - 1.0.0, 1.1.0-preview.1 (2019.4.12f1, 2020.1.8f1, 2020.2.0b6)
Workaround: Delay one call (either light bar change or vibrations) by one frame
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note (fix version 1.1.0-preview.6):
Fixed in: 2022.1.0a7 (SetMotorSpeedsAndLightBarColor() function was added in Input System 1.1.0-preview.6)