Wireless Receiver
- Raspberry Pi Xbox 360 Controller Driver Free
- Raspberry Pi Xbox 360 Controller Driver Download
- Xbox 360 Controller Driver Windows 7
- Xbox Controller For Raspberry Pi
To use wireless Xbox 360 controllers, you will also need a USB wireless receiver plugged into your Raspberry Pi. The Official Microsoft Xbox 360 receiver or a generic brand like zettaguard, VicTsing will work. You can pair multiple controllers to a single wireless receiver. Play and charging cables will not work.
To pair your controller(s) with the wireless receiver:
The setup is much the same as the PS3 with the right drivers being installed. Wireless Xbox 360 Controller. A Xbox 360 controller will also work with any Pi version, but require a wireless receiver. The receiver basically plugs into a USB port on the Pi and transmits to the controller. Jul 13, 2014 How to use an Xbox 360 wired controller with a Raspberry PI (and/or how to compile a kernel module) Background So I asked the question, 'How can I get my Raspberry PI to recognize an Xbox 360 wired controller?' The answer is. (or normal xpad driver). RetroPie allows you to turn your Raspberry Pi or PC into a retro-gaming machine. It builds upon Raspbian, EmulationStation, RetroArch and many other projects to enable you to play your favourite Arcade, home-console, and classic PC games with the minimum set-up. How to use an Xbox or PS4 controller with a Raspberry Pi. By Mayank Sharma How To. Insert it into the Raspberry Pi, connect the controller, the Wi-Fi adaptor, the speakers. RetroGame.Club or Raspberry-Pi Based Consoles Video: Configuring a PS3 controller to connect via Bluetooth Before booting your Raspberry Pi, make sure that a supported Bluetooth adapter is connected (If you are using a RetroGame.Club console or a Raspberry Pi 3, the built-in Bluetooth works for this).
- turn on your wireless Xbox 360 controller (hold down the Guide button)
- press the connect button on the receiver (green light will start flash)
- then press the tiny connect button on the top of the controller
- you will need to repeat these steps to pair each additional controller
Automatic Configuration (Easiest)
Xpad Driver
Starting with the RetroPie 4.1 SD image, the Xpad driver is enabled by default and the following steps are unnecessary.
With the recent kernel issues of xboxdrv rendering images unusable, there is an updated xpad driver which will work just as well for Xbox controllers, it's possible it may also support Xbox One controllers.
You access the driver through Manage Packages >> Manage Driver Packages >> Xpad Driver and you'll install it from source. Reboot for good measure, reconfigure your controllers and the lights should work properly.
A complete working config (that was generated from the EmulationStation configuration) is listed below at
/opt/retropie/configs/all/retroarch-joypads/Xbox360WirelessReceiver(XBOX).cfg
Xboxdrv Driver
Note! There are known incompatibilities with this driver when used in it's default configuration with the latest kernel. As such, the xpad drive is currently the best option to simply make an Xbox 360 controller operational in RetroPie.
However, these incompatibilities are not an issue when using xboxdrv as a calibration and key-mapping tool for almost any gamepad, including the Xbox 360 controller. When used this way, it's even possible for both xpad and xboxdrv to coexist together.
Access the RetroPie Setup Script and navigate to Manage Packages >> Manage Driver Packages >> xboxdrv
- Enable xboxdrv: This will install the driver and add a start-up configuration in /etc/rc.local
- Disable xboxdrv: This will disable the driver and remove the start-up configuration in /etc/rc.local
- Set Number of Controllers To Enable: Default number of controllers is 2 (If you have more than two controllers, set this first before you enable xboxdrv)
- Set Analog Stick Deadzone: Smaller number = more responsive, Larger number = less responsive.
- Set dwc_otg.speed=1 in /boot/config.txt: May help if controller is being glitchy.
- Remove dwc_otg.speed=1 from /boot/config.txt: Removes the config.
After you have enabled the driver and rebooted you'll need to reconfigure your controller(s) in EmulationStation as described on the first installation page
Alternatively if you prefer you can manually install it..
Manual Configuration
RetroPie 3.3 contains a newer xboxdrv at /opt/retropie/supplementary/xboxdrv/bin/xboxdrv - which is preferable over the older Debian package. On older RetroPie images you can install the Debian package.
install it by running
Then you must choose one of the 3 methods below
1 - Multiples instances of xboxdrv
You have to launch multiple instances of xboxdrv (one for each controller)
For example we can edit the file /etc/rc.local to start instances of xboxdrv during boot
Here is an example of what to insert in /etc/rc.local for 4 wireless pads (put this just before exit 0):
(replace the
--wid
by --id
if you use wired controllers)You must swich-on your pads before booting the raspberry.Notice the
sleep 1
between each instance: this prevents the RPi from setting random controllers with random led status; adjust timing if necessary.2 - Single command line
Another way is to specify this single command :
3 - init script
The third possibility, you can use an init.d script with the daemon -D Option. Save the following content to /etc/init.d/xboxdrv:
sudo chmod +x /etc/init.d/xboxdrv
sudo update-rc.d xboxdrv start 90 2 3 4 5 stop 90 0 1 6
You will also need a default configuration file. Save the following content to /etc/default/xboxdrv:
To specifiy the amount of controller, edit the variable CONTROLLER_NUM. If you have a wired controller, replace all '-w' occurences with '-i'.
It is generally advisable to use the daemon mode, 'cause it uses less CPU and RAM instead of several xboxdrv processes for each controller.
Additional Configuration Information
Xbox 360 controller glitchy?
According to this post it might help to add the line
dwc_otg.speed=1
to the file /boot/cmdline.txt
.Outdated optional manual configs
Xbox 360 Controller button configuration for retroarch and final burn alpha
/home/pi/RetroPie/configs/all/retroarch.cfg
input exit emulator to exit the emulator and return to emulationstation. input menu toggle to show the retroarch menu (e.g. to set the aspect ratio, save/load the game, etc.)
/home/pi/RetroPie/emulators/pifba/fba2x.cfg
(or /opt/retropie/emulators/pifba/fba2x.cfg
in some versions)Up until now, I didn't figure out how to change the configuration from the analog sticks to the digipad. To exit the emulator, press START and SELECT together.
Alternate Controller Configurations
This is what makes the Xbox 360 controller the best for this project.
Raspberry Pi Xbox 360 Controller Driver Free
- Copy necessary files: First, copy the files above to your pi. (Remove the .txt extension first of course.) I placed them in /usr/local/ but they could go anywhere.
- Edit rc.local: Next, you need to edit rc.local so that xboxdrv uses the config files. There a few different possibilities depending on how you are instantiating xboxdrv, so be careful.2a. If you have this line:change it to this:2b. If you have this line (generated by the xboxdrv install from retropie_setup.sh):change it to this:2c. Or, if you are using separate lines like this:Edit them so that they look like this:
- File Permissions: The very last step is to make the .cfg files executable. So run these commands, changing them to reflect the location you placed the .cfg files.
Now, whenever you press the Xbox (guide) button on either controller 1 or 2, it will change the control scheme. For player 1, the controller starts up in normal mode. Hitting the Xbox button will change to player1.cfg. Hitting it again will enable mouse emulation. One more time will bring back normal operation. Controller 2 cycles between normal operation and player2.cfg. Controllers 3 and 4 are unaffected.
Here's a little explanation of xboxdrv_player1.cfg (player2 is similar):
Whether you’re playing retro games through an emulator on Windows, Mac, or a custom-built Raspberry Pi console, you need a controller. We tested some of the most popular options, from simple Xbox controllers to retro replicas and expensive Bluetooth-enabled gamepads, to figure out which are worth your money.
The Contenders
Advertisement
There’s no replacing the feel of an original controller on an original game console, but if you’re building your own retro gaming rig, you still need something better than a keyboard to play those old games. After searching through forums, blog posts, and Amazon reviews, I narrowed down my search to a mixture of controller types, from new and modern to old school replicas. Here’s what I tested:
- Buffalo Classic USB Gamepad ($20)
- Retrolink Nintendo 64 Classic USB Enabled Wired Controller ($14.99)
- 8BitDo NES30 Pro Bluetooth Gamepad ($45)
- Logitech Gamepad F310 ($20)
- Xbox One Wireless Controller ($50)
- PS4 DualShock 4 Controller ($50)
- Tomee SNES Replica ($9)
- Hyperkin Genesis USB Controller ($18)
Hundreds of other generic options are available, most serving as replicas for SNES, NES, or Genesis, but the reviews are so poor for the bulk of them that I decided to skip them. Most complaints about cheaper controllers come down to build quality and button actuation, both of which I’ve also found problematic on the generic controllers I’ve used over the years. You get what you pay for, and most sub-$10 options aren’t worth your money. I also decided to skip NES-replicas since the two button layout limits what you can play.
Advertisement
How We Tested
For testing, I played a bunch of different games for several hours using each controller. I spent the bulk of those hours for 2D games with Ninja Gaiden III and Super Street Fighter II. I chose Ninja Gaiden because it requires fast response time from the buttons and the directional pad, while Super Street Fighter II is one of the rare games that uses all six buttons on a controller and requires dexterity with the d-pad. As for 3D games, I spend the most time with Super Mario 64for Nintendo 64, Crazy Taxifor Dreamcast, and Quake II on PlayStation 1.
For software, I tested all the controllers with RetroArch on Windows, OpenEmu on Mac, and RetroPie on the Raspberry Pi. Every controller I tested worked with every operating system I tested it on, though I had some setup quirks with some of the Bluetooth controllers.
Advertisement
In the end, after considerable testing, I decided there was no such thing as the perfect do-all controller, so I’ve split my picks into two categories: a controller for just 2D gaming, and an all-purpose controller for both 2D and 3D games.
Our Pick for 2D Games: Buffalo Classic USB Gamepad
Advertisement
If you’re just looking to play 2D games from console generations like the NES, SNES, Genesis, or Turbografx-16, I found that less is more, and the smaller controllers built for retro games felt much better than modern dual-analog options.
Through all my tests, there was one controller that not only felt the best for me, but also comes recommended from a variety of sources: the Buffalo Classic USB Gamepad. The Buffalo Classic controller has stellar reviews on Amazon and comes recommended from both How-To Geek and Shovel Knight developer Yacht Club Games. It also often tops out lists from the likes of NeoGAF, Reddit, and Racketboy.
$19GMG may get a commission
Raspberry Pi Xbox 360 Controller Driver Download
Advertisement
![Raspberry Pi Xbox 360 Controller Driver Raspberry Pi Xbox 360 Controller Driver](/uploads/1/2/6/6/126605575/631625540.jpg)
The Buffalo Classic is a near exact size replica of the original SNES controller, though it opts for the Super Famicom style face button design. The buttons have been resilient and continue to work just as they did when I first opened the box. The feedback is also just as good as the original SNES controller, which means the d-pad has a pleasing “click” with each movement and the buttons bounce back immediately after pressing them. Since it’s USB, it’s easy to set up. Just plug it in and you’re ready to go.
That’s a huge step up from the Tomee SNES controller we’ve recommended in the past. The Tomee controller feels poorly made and after a couple hours of use the buttons started to squeak and feel mushy. The d-pad feels like it’s held onto the controller with bubblegum and only responds when you press with a lot of force.
Advertisement
Of course, the Super Nintendo inspired design isn’t your only option. I also tested the Hyperkin Genesis controller. This was the only Genesis-inspired controller I could find with decent reviews. The six face buttons feel good, but the d-pad is stiffer than the original Genesis controller. It also doesn’t have the nice rolling action that set the Genesis controller apart from the SNES and made it perfect for games like Street Fighter II. If you’re only playing Genesis games, the Hyperkin controller does the job, but I found the SNES style works a little better for general use, especially when you consider how few Genesis games actually used all six face buttons.
If you want or need to go wireless, then the 8BitDo line of Bluetooth gamepads are well constructed, albeit luxury options. While the SNES30 Pro was the gamepad I tested the most here, I also got my hands on a couple other 8BitDo models, including the NES30 ($35) and SNES30 ($35), and they’re all similarly built. Despite their appearance, the controllers aren’t exactly replicas of the original Nintendo controllers. The buttons and d-pad are much more clicky than the originals and they all feel more like a modern controller. 8BitDo’s entire line of controllers are customizable, include firmware updates, and even support key remapping. It’s overkill for the majority of us, but if a ton of advanced options is what you want, then 8BitDo’s extensive line of controllers will suit your needs. From my experience the quality of controller extends to all their options.
However, the SNES30 Pro and NES30 are both tiny, measuring at about the same size as an original NES controller (which is not as big as you remember it being). If you have large hands, these are uncomfortable to hold. The Bluetooth also adds quite a bit to the cost, especially with the SNES30 Pro. If you don’t need wireless, this is totally overkill, but 8BitDo makes a quality, stylish controller provided you have smaller hands and you don’t mind paying extra.
Advertisement
I also gave the Nintendo 64 inspired Retrolink controller a shot for regular old NES, SNES, and Genesis games, and it’s truly awful. The controller itself is well made, but the bizarre button layout of the Nintendo 64 means it’s next to impossible to use this controller for anything but Nintendo 64 games. That includes the awkwardly placed and weirdly sized analog joystick, which bounces back into place with a satisfying, but odd, rubber band effect, just like on the original controller. The same can’t be said about the d-pad, which feels mushy at best. The slow response time on the d-pad makes it hard to get through a single level in a game like Ninja Gaiden.
I’ll get into this much more in the section below, but after hours of testing, I found modern controllers, like the Logitech F310, Xbox One, and DualShock, far too cumbersome to use for 2D gaming exclusively. That’s not to say they don’t work, but they’re heavy and the additional analog inputs are unnecessary if you don’t plan on playing anything beyond the SNES generation. For that, the $20 Buffalo Classic USB gamepad is all you need.
Our Pick for 2D and 3D Games: Sony DualShock 4 Wireless Controller
Advertisement
If you’re looking for a catch-all controller to work with both 2D and 3D games, the Sony DualShock 4 is what you want. The directional pad is well suited for 2D games, while the analog sticks are perfect to 3D games as well. It’s far too bulky and expensive to recommend for just 2D games, but if you’re looking to play everything from the NES to the PlayStation One, the DualShock has you covered.
GMG may get a commission
The DualShock 4 wins for me for a variety of reasons, but the main one is the d-pad. The buttons are responsive and the spongy click of each individual pad feels more like a classic controller than the other options I tested. The face button placement, size, and style also feels natural when you’re playing older games. If you already have a DualShock 4, you’ll likely be happy with it for retro games. It’s also a favorite among the likes of The Wirecutter and PC Gamer. You will need some additional software to pair the DualShock 4 with a PC, though it’s not terribly hard to use. On the flipside, it pairs with RetroPie on the Raspberry Pi and with OpenEmu on the Mac out of the box. If you’d prefer a cheaper option, the PS3’s DualShock 3 is just as good as the DualShock 4, but sadly doesn’t just work out of the box and requires, extra set up compared to the DualShock 4.
Advertisement
The squishier d-pad of the PS4 controller is in direct contrast to the XBox One controller’s clicky d-pad, which felt horrible for most retro games. Where the DualShock’s d-pad softens its click like a classic NES controller would, the Xbox One feels and sounds more like you’re pressing a key on a keyboard. While the d-pad style is a matter of preference, if you’re looking for the same feel as older controllers, the Xbox One doesn’t fit the bill. Aside from that, the d-pad placement in the center of the controller is also awkward and doesn’t work well for long bouts of play. The same goes for the cheaper Xbox 360 Controller, though the d-pad on that controller is basically unusable for most retro games because it’s so unresponsive.
The aforementioned SNES30 Pro also fits into this section just as much as the previous, but falls short with 3D games. It’s too small for most people to use for any game that requires dual-analog sticks because they’re tiny and jammed too close together. Likewise, the four buttons on the top of the controller are horribly placed, so it’s difficult to use them. Even despite all that, if you’re looking for a gamepad primarily for 2D games that can also handle the occasional 3D game, then the SNES30 Pro is fine, just don’t expect it to be comfortable for long.
Advertisement
If you only plan on playing Nintendo 64 games, the RetroLink controller does an admirable job of replicating the feel of the weird Nintendo 64 controller, though the single analog stick makes it completely useless for games on any other console. It’s impossible to recommend this controller for anything but Nintendo 64 games.
If you’re looking for a cheap option, the Logitech F310 (and its wireless counterpart, the F710) are big sellers, but even at the $20 price point of the F310, it’s hard to recommend. The analog thumbsticks feel tight, the face buttons are a little too big, and the input drop is too deep. This means it requires a little too much force to press a button in, which causes problems with any game that requires precise timing. The controller itself is also oddly shaped, feeling something like a mashup of both the Xbox controller and the DualShock. Most reviewers, including Polygon and The Wirecutter have pointed out the F310 feels weird to hold and I’m inclined to agree. The d-pad on the F310 has a satisfying clickiness about it, but that doesn’t translate to responsiveness on the game’s end.
![Xbox on raspberry pi Xbox on raspberry pi](/uploads/1/2/6/6/126605575/668916453.jpg)
Xbox 360 Controller Driver Windows 7
A game controller is a personal thing, and which best suits you depends a lot on the size of your hands and what you’ve used in the past. If you’re happy with what you have right now, there’s no reason to change anything up, but if not, there’s an option out there that’ll suit your needs.
Xbox Controller For Raspberry Pi
Advertisement
Illustration by Sam Woolley.