Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
4
Found in [Package]
1.4.1
1.8.0-pre.2
Issue ID
ISXB-783
Regression
No
Composite binding do not reset when bound to Gamepad stick instead of key or button controls
How to reproduce:
1. Open the attached project "WebGLControllerBug.zip"
2. Open File>Build Settings...
3. Switch Platform to WebGL
4. Build And Run the project
5. Move the left analog stick up on the controller
Expected results: "Left Stick (Gamepad)" returns "(0.00, 1.00)" in the Player
Actual results: "Left Stick (Gamepad)" doesn't return anything in the Player
Reproducible with: 1.3.0, 1.4.1 (2020.3.38f1), 1.4.1 (2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6)
Reproducible on: Windows 10
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
A workaround was provided for this issue.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.8.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
A workaround was provided for this issue.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.