Microsoft Xbox 360 Common Controller For Mac
Sheron Kernan
I couldn't get the wheel to work on win7 back when I got it, either, but thrustmaster support told me to install the wheel manually through device manager as an xbox 360 controller (driver 6.1.7600.16385 [21/06/2006]) under the "Microsoft Common Controller for Windows Class" group.
As a matter of fact, I just got this up and running last night. I got Lego Indiana Jones working in Fusion on my MacBook Pro with my 360 wireless controller. One thing, I had been using a wired controller, and had the 1.0 Microsoft drivers installed (the filename for 1.0 was xbox360Eng.exe). That didn't work with the wireless controller, so I had to download the 1.1 version. Installed the new driver package, the green light came on the receiver, and then just had the hold down the buttons on both the receiver and controller to sync them up, after that, worked like a charm.
Type xbox, press the Down arrow key until you hear "Enable Xbox Game Bar," and press Enter. With Narrator, you hear: "Open Xbox Game Bar using this button on a controller, Xbox button, toggle switch, off." With NVDA, you hear: "Xbox button, toggle button, not pressed."
A standard Xbox 360 controller features eleven digital buttons, two analog triggers, two analog sticks and a digital D-pad. The right face of the controller features four digital action buttons: a green button, red button, blue button, and yellow button. The lower right houses the right analog stick, in lower left is a digital D-pad and on the left face is the left analog stick. Both analog sticks can also be clicked in to activate a digital button beneath. In the center of the controller face are digital "Start", "Back" and "Guide" buttons. The "Guide" (more commonly known as simply the "Xbox") button is labelled with the Xbox logo, and is used to turn on the console/controller and to access the guide menu. It is also surrounded by the "ring of light", which indicates the controller number, as well as flashing when connecting and to provide notifications. The left and right "shoulders" each feature a digital shoulder button, or "bumper", and an analog trigger.
tl;dr: Unity (as of at least 4.5.2) has significant problems dealing with two or more Xbox 360 controllers on Windows, where they randomly may not work at all, or have non-functioning triggers, and/or have phantom clones. This is significant because it is the most common controller on the most common platform for many desktop gamers. There is no known workaround or reliable method for returning all connected controllers to a working state, except by trial and error.
Reports covered a range of controllers, with the general flavor being controls not working, or working incorrectly, particularly triggers. Over time, the Xbox 360 controller has been the common denominator. Finally, one user responded with some specifics: two wired Xbox 360 controllers, on Windows, occasionally not working at all or the triggers not working properly.
This is a common issue with the joysticks on the controllers. Over time and from use there is a little clip in there that wears down and you start to get stick drift. I have it on 2 different ones, only both are in the left stick for me. Always upwards though.
Finally, for the most roundabout setup, you can use a DualShock 4 through a program called DS4Windows. It's free third-party software that tricks your PC into thinking the DualShock 4 is a much more common (for PCs) Xbox controller, like the Steam configuration mode and 8Bitdo USB adapter do.
If you're a fan of driving simulators or flight simulators, you might want to invest in some simulator-worthy equipment. Racing wheels are steering wheel controllers that let you drive cars in racing games by realistically turning a wheel instead of tilting a stick. Similarly, flight joysticks (not to be confused with the analog sticks on gamepads or the digital sticks on arcade sticks) let you fly planes with a realistic full-hand grip to control your pitch, roll, and yaw. These seem like very different types of controllers, and they are. Still, they share three important common factors: They're designed for very specific games and genres, they often consist of multiple, modular components, and they can be expensive.
huge help getting my usb wireless reciever (official microsoft one) working,
thanks again,
you should add a link to this utility as well allows you to shut off the controller from the PC otherwise you cannot shut them off directly.
Some games and emulators are hardcoded to work with an Xbox 360 controller, and will not work with other controllers. To get around this, you need to create a virtual Xbox 360 controller that emulates the expected interface, but is bound to your controller's inputs. This can be done with Steam Input or xboxdrv.
If you want to use one of the widely available Bluetooth gamepads, such as iPEGA-9017s designed mostly for Android and iOS devices you would need xboxdrvAUR, bluez, bluez-plugins, and bluez-utils. You should connect it in gamepad mode (if there are different modes, choose the gamepad one). Technically it is ready to be used, but in most cases games would not recognize it, and you would have to map it individually for all application. The best way to simplify it and make it work with all applications is to mimic Microsoft X360 controller with xboxdrvAUR.Once connected you can create a udev rule to give it a persistent name, that would come in handy when setting it up.
python-steamcontroller-gitAUR can also be used to make the Steam Controller work for games running under Wine. You need to find and download the application xbox360cemu.v.3.0 (e.g. from here). Then copy the files dinput8.dll, xbox360cemu.ini, xinput1_3.dll and xinput_9_1_0.dll to the directory that contains your game executable. Edit xbox360cemu.ini and only change the following values under [PAD1] to remap the Steam Controller correctly to a XBox controller.
Now start python-steamcontroller in Xbox360 mode (sc-xbox.py start). You might also want to copy XInputTest.exe from xbox360cemu.v.3.0 to the same directory and run it with Wine in order to test if the mappings work correctly. However neither mouse nor keyboard emulation work with this method.
xboxdrv supports a multitude of controllers, but they need to be set up in /etc/default/xboxdrv. For each extra controller, add an next-controller = true line. For example, when using 4 controllers, add it 3 times:
xboxdrv can be used to make any controller register as an Xbox 360 controller with the --mimic-xpad switch. This may be desirable for games that support Xbox 360 controllers out of the box, but have trouble detecting or working with other gamepads.
The above example is incomplete. It only maps one axis and 3 buttons for demonstration purposes. Use xboxdrv --help-button to see the names of the Xbox controller buttons and axes and bind them accordingly by expanding the command above. Axes mappings should go after --evdev-absmap and button mappings follow --evdev-keymap (comma separated list; no spaces).
While some Xbox console games, such as Halo Infinite, support a mouse and keyboard, this new feature is ideal for PC gaming, particularly games that lack controller support and require a mouse and keyboard. While it is common for newer games released on PC to have dual support for controller and mouse/keyboard, older games or games where controller inputs are worse or finicky to set up will now be more accessible. One example is the Steam version of Dead Rising 2, which supports mouse and keyboard in addition to the controller, but the latter only supports modern controllers with a lot of workaround or mods to get working properly.
You can download the drivers this-a-way. However, you'll also need to root out a micro USB cable too. The Xbox One controller doesn't come in a wired form, and can't connect to a PC. [Some hasty editing after a canny reader points out it uses proprietary tech, not Wi-Fi Direct as commonly believed.] Hopefully Microsoft are planning to release a dongle like the wireless Windows 360 controller uses.