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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
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)