Search Issue Tracker
Fixed
Fixed in 1.5.0, 1.6.3, 1.7.0, 1.8.1
Votes
0
Found in [Package]
1.5.0
1.6.3
1.7.0
1.8.1
Issue ID
ISXB-825
Regression
Yes
Inconsistent character movement observed in Standalone Build with PS4 controllers (CUH-ZCT1H/CUH-ZCT1E models)
Reproduction steps:
1. Open the attached project "ReproProject"
2. Connect a PS4 controller model CUH-ZCT1H or CUH-ZCT1E
3. Build a Standalone app
4. Move the character using the left stick to one side (e.g., left/right)
5. While performing step 4, rapidly move the right stick in random directions
6. Observe the character's movements
Expected result: The character's movement remains consistent
Actual result: The character either stops moving or moves erratically
Reproducible with: 2022.3.10f1 (1.5.0, 1.6.3, 1.7.0, 1.8.1)
Not reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13 (1.5.0, 1.6.3, 1.7.0, 1.8.1)
Fixed in: 2022.3.11f1 (1.5.0, 1.6.3, 1.7.0, 1.8.1)
Reproducible on: Windows 11 23H2 (22631.3007) (Editor Play Mode), Windows 10 (10.0.19045) 64bit (user’s)
Not reproducible on: No other environment tested
Notes:
- Not reproducible with a PS4 CUH-ZCT2E controller
- Reproducible in the Editor
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note (fix version 1.8.1):
This issue is fixed in 2022.3.11f1 and above.
Resolution Note (fix version 1.7.0):
This issue is fixed in 2022.3.11f1 and above.
Resolution Note (fix version 1.6.3):
This issue is fixed in 2022.3.11f1 and above.
Resolution Note (fix version 1.5.0):
This issue is fixed in 2022.3.11f1 and above.