Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.3
Issue ID
ISXB-325
Regression
Yes
Second ReadValue<Vector2> returns a zero vector when the Action Maps are the same
Reproduction steps:
1. Connect a Gamepad
2. Open the user’s attached project
3. Enter Play Mode
4. Press and hold any D-Pad button on the Gamepad
5. Observe the Console
Expected result: Both ReadValue<Vector2> results are the same
Actual result: Second ReadValue<Vector2> result is always (0.00, 0.00)
Reproducible with: 1.4.1 (2020.3.41f1, 2021.3.7f1), 1.4.3 (2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a15)
Not reproducible with: 1.3.0 (2020.3.41f1, 2021.3.7f1, 2022.1.10f1, 2022.2.0b3, 2023.1.0a3)
Reproducible on: Ubuntu 20.04.5, Windows 10 Enterprise 21H2
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254
Resolution Note (fix version 1.4.4):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254