-
Search Results
-
Hi,
Apologies for being a total novice and if this is covered somewhere already again apologies.I have been playing with Retropie for a week or so and was struggling to get the PS3 controller working wirelessly with my Bluetooth dongle.
Last night I downloaded 3.4 and installed the image from scratch. Connected to the Wifi with my WiFi dongle ok, connected the Playstation 3 controlled via USB cable and setup the controller using the USB cable.
I then exited retropie and ran the retropie_setup.sh script and then attempted the install pair Playstation 3 controller – The script installed at the end it stated connect via USB cable and press PS on the controller to complete setup. (I can’t remember the full screen that appeared apologies not helpful I know)
Sadly the PS3 controller still doesn’t work wirelessly.Any ideas? I have a broadcom USB showing when I perform a lsusb command.
Have I missed something
Any help really appreciated
ChrisHi,
I have just installed 3.4 from scratch and inserted my usb stick with all my roms on. Nothing happened. I usually see the light on my usb stick flickering for ages.
Is the usb rom service working in this version?
I when into configuration and enabled it, rebooted, still no luck.
Has the folder structure changed?
Regards
I had a ps3 clone working flawless via bluetooh on 2.6 but I was unable to make it work on 3.3. I saw the changelog on 3.4 and had some hopes about it but it doesnt work either.
The controller works fine on usb, but I simply cant do the pairing. The bluetooth device works fine(at least in 2.6).
I cant get the controller scanned with hcitool scan(but it happens too with 2.6 and the controller works fine).Sixpair results:
Current Bluetooth master: 00:15:83:07:ca:04
Setting master bd_addr to 00:15:83:07:ca:04———>Notice that its the same MAC for this two lines…¿?¿?¿
sixad output:
pi@retropie:/dev/input $ sudo sixad –start
[ ok ] Starting bluetooth (via systemctl): bluetooth.service.
sixad-bin[1471]: started
sixad-bin[1471]: sixad started, press the PS button nowand thats it, it stays like that, my controller 4 lights flashes a little time and then go off….
I would stick to 2.6, but I was able to use nearly all my mame roms in 3.4 after a long time and damn, I want all things to work fine at least one time!!!!!!
Hello friends,
Need some help here. I just installed retropie on Raspberry Pi 2. I connected a PS4 controller via USB and it works on the emulation menu but it doesn’t work inside the game….the only button on the controller which works is the square button which takes you back a screen. I tried googling the issue and on the forum here but no luck. Can anyone assist?
I’m using an Afterglow XBox 360 wired USB controller connected to my Pi via a powered USB hub. My Pi is a Model B running RetroPie 3.3.1 Wheezy. When setting up the controller via EmulationStation, I am able to configure all the buttons correctly except for the Right Trigger. When it prompts me to press it, it just skips over it and says “Not defined”. I have re-installed the XBox 360 controller drivers via the RetroPie Setup Script, but that did not fix it. There is nothing wrong with the controller itself as it works just fine on my PC/Xbox.
I’ve searched around and this appears to be a fairly common issue, but all the solutions say to update the drivers, which I have done and that did not fix it.
If someone could help me out with this I would appreciate it!
So I picked up the powerblock to use to control power on my pi, and after not really liking the SNES to USB interface, I decided to use try the GPIO route. I followed this plan (https://www.petrockblock.com/2012/07/19/connecting-snes-sockets-to-the-raspberry-pi-an-assembly-guide/) to connect my snes adapters to pins but I’m not having any luck (nothing is detected)… The only pins I switched was 3.3v and gnd from the guide (because the power block is on pins 1 and 6), so I’m using pins 17 (3.3v), 22 (Data2), 20 (gnd), 15 (Data1), 16 (latch), and 18 (clock). I installed the SNESDev package from the retropie setup script, but it doesn’t seem to be working. I get absolutely nothing. The part I’m not sure about is what GPIO pins the script is looking for, and I’m afraid it wants to only look on the 1,5,6,7,19,23 config that the gamecon driver wants to use. I’ve searched for quite some time to see if I can figure out how to change or check the GPIO pins, but I don’t find that anywhere. Another issue I think I see is that the SNESDev service is not running (services –status-all shows it with a ‘-‘ which I understand to be installed but not running) and if I try to service start it, it reboots my pi (oops)… Am I missing something? I’ve searched the forums to no avail, most talk about using the GPIO adapter that is sold here, but I already have the powerblock, so couldn’t use that if I wanted to…
Topic: controller settings for VICE
Hi everyone. I am new to raspberry Pi, and started my foray into this world with a retropie project. All was going well until trying to play c64 games. I can configure the controllers (usb snes controllers) upon loading a game, but the settings refuse to save no matter what i do. I have googled for hours and found limited information. Many said to create the.vice directory, and check file permissions, but it already exists. Only owner had rw permissions, so i changed all to rwx (suggested on a post i found). When i try to save the settings in the vice menu, it states that it cannot save still. This is really driving me crazy, any help is appreciated.
I have a raspberry pi 2 B and running retropie 3.3.1 SD card image.Hi guys.
I followed HerbFargus guide on GitHum to automatically configure my wireless XBOX 360 controllers. All 4 controllers work great everywhere (emulationstation + all other emulatores) but reicast (dreamcast) emulator. I plugged in a logitech usb controller and that worked fine in Reicast. However, Reicast doesn’t seem to recognize the XBOX controllers. Do I have to do something special for Reicast for my XBOX controllers to work.
Pi Model: Raspberry Pi 2 Model B
Retropie version: 3.3Thanks for the help.
Probably you are in the same situation as I was, pulling your hair because you can’t get the Xin-mo to work properly. And it is nearly impossible to find a easy to follow guide how to get it working. So when I got my Xin-mo working with all the emulators I decided to write this guide. Enjoy!
This is the setup I got:
Pi Model: Raspberry Pi 2
RetroPie Version Used: 3.3.1 Magnet link:magnet:?xt=urn:btih:6656bf7bd104930039f4eb81399976ebd297b8fe
Built From: SD Image
USB Devices connected: Xin-Mo (http://www.xin-mo.com/?page_id=34)
Bought the Xin-mo with arcade buttons here: http://www.ultracabs.co.uk/usb-interface–standard-joystick-set-109-p.aspI have tested the Xin-mo with the following: MAME, FBA, Playstation, SNES, NES, SMS, SMD, Game boy, Game boy Advance, Doom.
If you are used to installing Retropie you can skip several steps.
Step 1: Connect the cables from the arcade buttons to the Xin-mo as shown in the attached picture. Else you will get player 1 as player 2 and vice versa. (Choose PS3 mode and not PC)
Step 2: Download and Write your RetroPie image to a SD-card.
Step 3: Insert the SD-card with RetroPie 3.x in your raspberry Pi, connect it to your network with a RJ-45 cable or wifi and boot it up.
Step 4: Go to the “RetroPie” menu and select : “raspberry Pi configuration tool raspi-config”. Then click: “Expand filesystem”. Reboot. (Not needed in newer RetroPie)
Step 5: Login to the terminal and set a root password, type:
sudo passwd root
and choose a password. For example: User: Root Password: raspberryStep 6: Download this custom kernel (It will fix the problem with the joysticks messing with each other): custom_kernel_1.20150818-1.tar.gz
(Newer kernel, use this if you install 3.6: custom_kernel_1.20160128-1.tar.gz
(Thanks to feederchain for the kernels).Step 7: Don’t unpack the file just place it somewhere on the SD-card, in /home/ for example. (I used filezilla for transferring the file from my computer to the Pi) (Do this as ROOT!)
Step 8: Run these commands from the terminal on the Raspberry Pi or using SSH:
cd /home/
(This is the place you placed your file, so here I used /home/)
tar -xf custom_kernel_1.20150818-1.tar.gz
(This command unpacks the file)
cd custom_kernel_1.20150818-1
sudo ./install.sh
(This will install the custom kernel)After this the Raspberry Pi should reboot.
Step 9: Now we are going to modify the cmdline.txt so we get two controllers showing up instead of one.
SSH or terminal again:
cd /boot/
sudo nano cmdline.txt
Add the following content after a space at the end of the first line:
usbhid.quirks=0x16c0:0x05e1:0x040
Press CTRL + X and type “Y” for yes, so it saves the file.
Step 10: Now you can register your buttons in EmulatorStation, but just register the left controller (Player 1). Now you should be able to navigate and press buttons.
Step 11: Go in to the RetroArch configuration and navigate to “input”, change the buttons you want for Player 1 and 2 for the Xin-mo. Then go to hotkeys menu and select what buttons you want for quitting a game, saving etc.
RetroPie—>Configure RetroArch/Launch RetroArch RGUI—–>Settings—->Input—->”Input Hotkey Binds” and “input User 1/2/3 etc Binds”
Step 12: Change the driver for the Xin-mo from sdl2 to udev.
Step 13: Go back to the main menu in RetroArch and save the config as a new file. (For me it didn’t work just to save the old file) Quit RetroArch setup.
Step 14: Navigate to the config file (using filezilla e.g.) in /opt/retropie/configs/all/ rename the file retroarch.cfg to retroarch.cfg.old, and rename the file you just created to retroarch.cfg. Reboot RetroPie.
Step 15: If you are using MAME you have to start a game and press TAB and edit the controls in there as well.
Step 16: DONE! Now both players should work in all the games, so you can play Street Fighter II or Tekken 3 with a friend. Enjoy!
(In Emulatorstation the right controller have some issues, but the left controllers is enough for navigating. And both is working in the games.)
Here is FileZilla
Here is Win32diskimager For Writing or create a backup of RetroPie (Windows)
Here is Pi Copier and Pi Filler if you are using Mac OSX
[attachment file=”114317″]
I’m still learning alot about linux and retropie so bear with me…
Having a problem with my PS3 controller not connecting over a bluetooth connection while in the emulator, specifically SNES. Yes, ive installed BT drivers and setup the PS3 controller using the tutorials here.
After installing the bluetooth drivers, i’m able to control emulation station using the PS3 controller via bluetooth, but when I want to play an SNES rom, i notice some yellow text on the bottom left hand corner after the game is loaded saying my controller isn’t configured. If the PS3 controller is plugged in via usb on the PI, the SNES emulator picks up on it, i get the yellow text on the bottom left hand corner saying its configured to a port, and im able to use controller.
Any ideas on what I need to do to get the BT to work in an emulator? Hope this is an easy one to fix.
Raspberry Pi 2, Retropie 3.3.1 Wheezy SD image download (no update performed).
I have a Logitech F710 wireless. It has a switch between 2 different modes: D (DInput) and X (XInput). Depending on the switch position it is seen as different devices (usb disconnects and reconnects when switching):
lsusb with DInput:
Bus 001 Device 009: ID 046d:c219 Logitech, Inc. Cordless RumblePad 2
dmesg with DInput:
[ 2555.058246] usb 1-1.5: new full-speed USB device number 12 using dwc_otg [ 2555.167361] usb 1-1.5: New USB device found, idVendor=046d, idProduct=c219 [ 2555.167435] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2555.167470] usb 1-1.5: Product: Logitech Cordless RumblePad 2 [ 2555.167488] usb 1-1.5: Manufacturer: Logitech [ 2555.178335] input: Logitech Logitech Cordless RumblePad 2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:046D:C219.0008/input/input7 [ 2555.179747] logitech 0003:046D:C219.0008: input,hidraw2: USB HID v1.11 Gamepad [Logitech Logitech Cordless RumblePad 2] on usb-3f980000.usb-1.5/input0
lsusb with XInput:
Bus 001 Device 011: ID 046d:c21f Logitech, Inc. F710 Wireless Gamepad [XInput Mode]
dmesg with XInput:
[ 2505.718035] usb 1-1.5: new full-speed USB device number 11 using dwc_otg [ 2505.828718] usb 1-1.5: New USB device found, idVendor=046d, idProduct=c21f [ 2505.828746] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2505.828764] usb 1-1.5: Product: Wireless Gamepad F710 [ 2505.828780] usb 1-1.5: Manufacturer: Logitech [ 2505.828797] usb 1-1.5: SerialNumber: 56E994A2 [ 2505.830708] input: Logitech Gamepad F710 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input6
Using DInput the joystick works perfectly in emulation station, mupen64 and scummvm but is not recognised by retroarch.
Retroarch says when starting a game (snes, gba, gbc):
Logitech F710 Gamepad (DInput) (1133/49689) not configured
Now I have no idea where retroarch gets this joystick identifier (udev, SDL?). It does not appear in dmesg or lsusb.
I did a recursive find in /opt and /home/pi grepping files for the string ‘F710’ and there is no config file mentioning an F710 controller (in DInput it should be: Logitech Logitech Cordless RumblePad 2). The configured joysticks are:pi@retropie /opt/retropie/configs/all/retroarch-joypads $ ls -lrt total 16 -rw-r--r-- 1 pi pi 868 Jan 15 22:34 ACRUXUSBGAMEPAD8116.cfg.bak -rw-r--r-- 1 pi pi 868 Jan 15 22:35 ACRUXUSBGAMEPAD8116.cfg -rw-r--r-- 1 pi pi 878 Jan 15 22:44 LogitechLogitechCordlessRumblePad2.cfg.bak -rw-r--r-- 1 pi pi 878 Jan 15 23:37 LogitechLogitechCordlessRumblePad2.cfg
There are also these same 2 joysticks in the emulation station config file.
I have tried copying the file LogitechLogitechCordlessRumblePad2.cfg to another file with the name of the joystick that appears in retroarch error message (without blank and special characters) and I also tried changing the name of the joystick inside the file. This was unsuccessful. Is there any documentation on how retroarch gets the joystick name (here: Logitech F710 Gamepad (DInput) (1133/49689)) and how I can map that name to a config file?
With XInput it is worse:
Not only do I get the very similar message:Logitech F710 Gamepad (XInput) (1133/49695) not configured
but also emulation station GUI cannot configure all buttons in XInput mode (in XInput, lower R and L buttons are actually axis and when pressing one of them it triggers the configuration of 3 consecutive buttons with (axis-,axis+,not defined). It can be circumvented by editing the config file manually if only I could find a nice description of the config file settings).
I have read somewhere in this forum that DInput does not work, but according to http://linuxhacksandfixes.blogspot.de/2013/02/the-logitech-f710-gamepad.html it seems DInput should work fine on Linux. Also DInput works perfectly in emulation station, mupen64plus, scummvm (and with jstest /dev/input/js0) and also works on my PCs (also Linux but on Intel) so it could also work for retroarch (in the worst case by using xboxdrv to expose it as xinput).
I must say also that I seem to remember a week ago using this controller succesfully in retroarch snes or gba/gbc. I cannot say for sure, but this is surprising since I have not changed/updated anything except editing these joystick configs (only after the problem arised) and configuring mupen64.
Thank you.
I have the x-arcade dual joystick. It works just fine with my old xbox retro arcade, but I am trying to get it working with retropie.
I have the raspberry 2 model B. The unit works fine and it is running the most up to date, *stable* version of retropie. I put version 3.3 of retropie on the flash card and ran the update scripts.
EmulationStation boots normally, so I have no issues there. After booting, I can configure a USB keyboard without issue. I have no other usb controllers except my x-arcade dual joystick. However, EmulationStation/Retropie does not recognize the x-arcade at all.
Jstest (jtest?) is not compatible with my version of retropie, but the input subdirectory does not see the xarcade, either. I have scoured YouTube, Reddit, these forums, and the internet for a solution. The info I have come across for configuring the sticks are either months old, use older versions of retropie, or deal with the tankstick. I have read other forum posts stating the tankstick config does not work with the dual joystick.
I’m stumped. Either I’m missing some obvious step in the installation process for the dual joystick, or it just doesn’t work. After I configure the usb keyboard, none of the inputs translate to the joysticks. I get no response from ES or any of the emulators, at all, from the dual joysticks.
Any ideas at this point would be greatly appreciated. I like the pi, I like this distro, and I like the joysticks, so bringing them all together would be awesome. I have an hdmi projector and putting this altogether would cement my outdoor, big screen, retro arcade dream.
Thanks in advance,
hbchrist
I just installed rp 3.3.1-rpi2 on a RP2B+. I connected 2 identical iBuffalo USB SNES joypads and configured the first through the emulation station startup configuration menu.
Both controllers work for the NES emulator. All buttons and the D-pad for the first joypad work – including hot keys – and control player 1. All buttons and the D-pad for the second joypad work – *excluding* hotkeys – and control player 2.
The problem is mame4all. I’ve configured the controllers through the mame UI. The mame UI correctly identifies the controller and input in that when I press a button on the second joy pad the mame UI reads and correctly assigns the button as J2 Button 0+,0-,7, or whatever. But the player 2 controller doesn’t work correctly. Mame correctly identifies and executes as assigned the input from the [select] and [start] buttons of the second joypad, but it doesn’t use the D-pad or other buttons to control player 2. The D-pad and buttons from joypad 1 control the second player.
I’ve tried hard coding the input through retroarch.cfg. I get the same behavior. Any help would be appreciated. Thanks.
Topic: game on setup issue
Hi,
I received anothe Raspberry Pi 2 for Christmas and decided to make it a NES only emulator. I have a dead NES I will eventually put ut in.
I installed the latest version of retropie and have things up and running with a usb keyboard. I then installed gamecon_gpio_rpi through the setup menu and let it set itself up for SNES.
I then wired a NES controller up to the GPIO.
Back in emulation station it told me that it detected two gamepads. I held a button on the NES controller and went through all the button mapping. It then worked great for getting around in emulation station.
I then launched an NES game and the controller didnt do anything. Keyboard still works. If I exit the game the controller works again.
Trying again I noticed that it says that SNES controllers are configured on ports 0 and 1 in the bottom left when the game starts. Thinking that this is the 0 and 1 that the raspberry pi 2 doesnt use in the read me I tried remapping as per the readme, but that didnt change anything.
Any advice?
Thanks,
KberrI decide to upgrade the audio from the on board audio to an USB Audio devices. I am able to hear audio with the USB audio device with other emulators. Except when I am tring to run any N64 games using the mupen64plus emulator. When I move the audio jack from the USB audio port to the onboard audio port I can now hear the sounds from the game. I Need help in reconfiguring the emulator so that the USB audio is the defaulted instead of the onboard audio ports.
Thank -you
Frank (KB0MMR)Hi,
Firstly, I’d like to say thanks to everyone involved in RetroPie and the community, it’s awesome and works so easily.
I have recently put together a cabinet for my son with his Christmas money as he wants to play his sister on Street Fighter 2 after a recent visit to a Computer Museum.
We have the following setup….
Pi b
2 x Zippy joysticks
15 illuminated buttons
Xin-mo encoderWe first had some issues getting system to recognise 2 controllers, but we did the fix for that we found on here (adding usbhid.quirks=0x16c0:0x05e1:0x040 in the /boot/cmdline.txt).
We now have a working system, and for most Mame games it seems to be fine. But it is impossible to perform any special moves on Street Fighter 2. We’re testing with Ken, and we know there’s a simple special move of DOWN, FORWARD, PUNCH which will send a fireball. We can do this on the keyboard consistently, so we know it’s possible and move is correct. This is one example, there’s other moves that I also now that just don’t seem to be possible with this setup.
I’m a bit lost at what to try now, does anyone have any idea what the cause may be? i.e. encoder, joysticks? Or any idea how we can fix it.
Many thanks in advance – my boy will be extremely grateful if we can get it going :)
Cheers