Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
6
Found in
5.0.1f1
Issue ID
686929
Regression
Yes
Game controllers no longer work in Unity on one of my Macs
The behavior regressed in two steps.
4.3.4f1: Input from Xbox controller works at all time.
4.5.2f1: Input from Xbox controller doesn't work while Wacom tablet is plugged in, but starts working as soon as tablet is unplugged.
5.2.1f1 (also 5.0.1f1 it seems): Input from Xbox controller doesn't work if Unity launched while Wacom tablet was plugged in. Unplugging tablet doesn't work; only if also restarting Unity player.
Comments (4)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
DnosHubz
Feb 29, 2016 17:12
Confirmed still an issue in 5.3.3p1. Using either x360 wired controller or DS4 (wired or USB) - all applications see the controller, but Unity Editor does not. If I make a standalone build, I can get controller working by plugging it in WHILE the build is running (if it's plugged in beforehand it doesn't work). I've tried all variations of having controller plugged in/paired before starting unity, after starting unity, reboots etc to no avail. Searching this problem online pointed me to MANY people with the same issue, and no solutions.
NCarter
Oct 03, 2015 22:04
Oops, just realised that this is in fact my own report that I'm commenting on!
NCarter
Oct 03, 2015 22:02
I also have this problem, except for me it only occurs if I have my Wacom tablet plugged in. Unplugging the Wacom tablet before launching Unity allows it to work as normal. This is specifically on OSX - I haven't tried any other OS.
I've run some cursory tests on older versions and found that it used to work properly in Unity 4.3.4f1, but broke somewhere between that version and 4.5.2f1. I have my own bug report in with more detail on this issue (686929).
samanabo
Jun 08, 2015 15:02
I am seeing this behavior on 5.0.2.
I've tested an xbox 360 controller with tattieboggle drivers over USB, a ps3 dual shock over bluetooth, and a logitech f310 in both X and D modes over USB.
None of these appear to be registering with unity on any OSX machine, in the editor or in a build. Calling Input.getJoystickNames() always returns empty, and no input from the joysticks is recognized.
The same project does work however, on windows.