Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
5
Found in
2019.3.0a11
2019.3.7f1
2020.1
2020.2
Issue ID
1231678
Regression
Yes
[WebGL] Input.GetAxis("Mouse X") and Input.GetAxis("Mouse Y") return inconsistent values between positive and negative axes
Steps to reproduce:
1. Open the attached project (case_1231678.zip)
2. Switch Platform to WebGL
3. Build And Run the project
4. Download and run the compiled AHK script "mouse.exe"
5. Use W/S to smoothly move the mouse cursor in the Y-axis or A/D to move in the X-axis
Expected result: GetAxis returned value for positive and negative axes is consistent
Actual result: GetAxis returned value for positive and negative axes is inconsistent
Reproduced in: 2019.3.0a11, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Not reproducible in: 2017.4.38f1, 2018.4.20f1, 2019.3.0a10
Note:
- Included executable is a compiled AHK script that smoothly moves the mouse cursor using WASD to help illustrate the issue better.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a10
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b12
Resolution Note (fix version 2019.3):
Fixed in 2019.3.15f1