Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.4.2f1
Issue ID
842835
Regression
No
[macOS] Input from USB mouse disables further touchpad input in Input.GetAxis on MacBooks
If the cursor is moved with a USB mouse, Input.GetAxis("Mouse X") and Input.GetAxis("Mouse Y") return 0 if the cursor is moved with the built-in touchpad afterwards. If mouse isn't moved, using the touchpad returns expected values.
Steps to reproduce:
- Make sure you have a USB mouse connected to the MacBook (wired, not Bluetooth).
1) Open the latest attached project.
2) Press play.
3) Without moving the mouse, swipe across the touchpad.
- Notice the Input.GetAxis values changing on the screen.
4) Move the mouse around a bit.
5) Swipe on the touchpad again.
The input values do not change - if the USB mouse is moved, no further input from the touchpad is registered with Input.GetAxis. This does not occur on Windows laptops. Happens in the Editor and on standalone builds.
Reproduced on:
5.6.0a2, 5.4.2p4, 5.2.4f1
Tested on:
MacBook Pro Early 2013 and MacBook Pro Mid 2015 + Gigabyte GM-M6800
Comments (1)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
watsson7278
May 21, 2019 10:54
I have also faced the same error with my Epson printer and it cannot be connected after I had changed the Network Adaptor on my system. I have also searched https://errorcode0x.com/how-to-resolve-epson-printer-error-code-0xf3/, but I found no such benefit from it.