Two extra face buttons plus squared-off shoulder buttons mean that technically this is a Super NES configuration, but the aesthetics are more or less perfect, and a few more control options never hurt anyone.
This model cheats a bit with “extra” control buttons, but it keeps the Japanese Famicom shape and color scheme with a more dependable build than the more “retro” USB options.įor wireless fans, the relatively new 8BitDo (get it?) NES30 controller is one of the best Bluetooth pads around. Another well-regarded alternative is the iBuffalo USB 8-Button Game Pad. And before you cry foul on the Super NES-style bone shape, here’s a bit of video game history for you: years into its original production, Nintendo released a redesigned controller affectionately known as the “dog bone.” This updated two-button layout seems to have informed the design for the next console. However, my favorite wired option is this Retro-Link USB model. If you want the most nostalgic, square, corners-jutting-into-your-palms NES controller, this is the best one we’ve used. Unfortunately, the NES gamepad is so simple that the market seems to be flooded with cheap, low-quality replicas, most of which have poor production and serious control issues. The original Nintendo Entertainment System (or Famicom, if you’re a stickler for the Japanese version) doesn’t have the most ergonomic controller design, but the little rectangle has a lasting appeal all its own. If you leave those settings and decide to use the SNES controller for NES games it uses the y and b buttons of the controller rather than a and b and feels natural just like Super Mario World controls.Nintendo Entertainment System (NES) Controllers
Any ideas?ītw… if you want to get both buttons working correctly for the NES controllers, you should use b=3 and a =1 in the retroarch.cfg file located in the NES directory (rather than ‘all’). I can swap adapter cables and it makes no difference so I have high confidence there is no wiring issue. However, when I switch to NES it works perfectly on js0 and not on js1. When I do this I find that I can see all buttons using the jstest /dev/input/js0 (or js1) while the SNES controllers are plugged in. So then I decided to make adapter cables to allow either SNES or original NES controllers to be hot swapped into the same connector ports.
Tried both v1.5 and v1.6 I find that running 2 SNES controllers works great using the gamecon driver and with SNES dev running the poll button mode. I’ve been running the RetroPie project straight from the image download. Here’s a strange little thing that’s been happening. So far, the driver is working without any problems for me. Once the kernel is built, the module can be rebuilt separately (kernel compile is needed just for creation of Module.symvers).” Then you’ll need to rebuild the kernel after selecting the module in menuconfig (see ). Marqs puts it like this: “Basically you have to download kernel sources and copy the driver and configs to the kernel tree. This involves compiling the kernel sources on your own and takes some time. Note that root privileges are needed to follow these steps:įor future firmware version the module needs to be re-compiled (at least as long as it is not part of the official Raspbian kernel tree). The README that is contained in the download explains the necessary steps for that. You can either use the RetroPie setup script for installing the driver automatically or manually put everything in place.
He generously allows to provide a zipped archive for download at the Github site of the RetroPie Setup.
Besides the source code Marqs provides a pre-compiled module for firmware 3.1.9+.