Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
1
Found in
2018.4
2019.4
2020.2
2021.1
2021.1.0b1
2021.2
Issue ID
1303445
Regression
No
Function Input.GetAxis("Mouse X") and Y-Axis in a Virtual Machine always returns 0
How to reproduce:
1. Create a Virtual Machine
2. Create a new Unity project
3. Create a new script
4. In the "Update()" function write "Debug.Log(Input.GetAxis("Mouse X");"
5. Attach this script to any game object in the Hierarchy
6. Enter Play mode
7. Wave your mouse around the Game View
Expected results: Input.GetAxis("Mouse X") returns various values when moving the mouse around
Actual results: Input.GetAxis("Mouse X") always returns 0
Reproducible with: 2018.4.31f1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a2
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
- Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
Resolution Note (fix version 2021.2):
Fixed Input mouse deltas when Windows is run on a virtual desktop, such as a remote desktop or a VM.
Fixed in 2022.1.0a1
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b6
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.18f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.17f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.30f1