CSU, are you by chance pulling roms from USB?
Just when you say missing roms, I did this, moved my roms to USB and edited es_configuration.cfg but it turns out you need to edit mame.cfg for mame4all as well because one config file pulls the ES menu to list the roms but the mame.cfg is the file used to launch the roms. It was still pointed at /home/pi/ and as such ES could list the rom but on launch it was hitting an empty directory in /home/pi.
hih
Hardware Specs:
Raspberry Pi 2
RetroPie 3.0 V2
32GB Class 10 microSD
WIFI WirelessN thumb drive
24″ Sceptre HDTV monitor
Happ 2 Player arcade button kit
iPac2 usb arcade controller
Lepai 2 channel stereo amplifier (20w x 2 RMS)
Pioneer 4″ stereo speakers
Bose Acoustimass subwoofer
USB & 3.5mm audio jack connector (for easy access from control panel)
Hello,
So, I purchased a USB SNES Adapter off Amazon. And the controller is detected in emulation station (Hold down A) comes up as SFC/USB. But, when I go to configure it
I cannot configure the Down or Right on the D-Pad.
Up, Left, Start, Select, A,B,X,Y,ShoulderL,ShoulderR all configure fine. I tried with several different SNES controllers and they are all the same.
Did you ever get the down and right to work? They do not for me either.
I purchased a USB to SNES controller adapter. It detects it but does not respond to down or right.
Thanks, I’ve heard sometimes USB is a little slower at responding. Would be good to know what emulators the ControlBlock has been tested on (2 player).
I would say that the main differences are that
– the ControlBlock also contains a power switch functionality
– the ControlBlock is an extension board for the RPi and directly communicates with the RPi via some of the GPIO pins and not, like the Ipac, via USB. Whether this is beneficial or not for you depends on your preferences.
There is also a video on the ControlBlock page mentioned above that shows the use of two arcade controller sets with the ControlBlock.
Hello,
Is there are recommended guide on controller we should buy for our Raspberry Pi when used in a bartop? I read many say the ipac2 is the best, USB is slow, and possible issues with the GPIO.
What are you using and can recommend for a 2 player bartop?
Thanks
Picked an icade case up for a tenner and decided to convert it. the panels that are white are clear, the protective film is still on them. The bezel is laser cut to fit an ipad2 screen which I obtained from a broken ipad.the material used is sprayed black mdf to keep it light yet give a smooth finish. Speakers sit at the top with the works being fitted on the back behind a cut box. I’ve tried to keep the lines as clean as possible. The controls are re wired to a usb encoder. Apart from graphics and a vga driver board for the screen the project is nearly finished. The usb is an extended ribbon that fits underneath to easily update.
Last post here and I’ll call it resolved. Running through the non-libretro core fixed the resolution issues as stated.
USB controller configuration was set within the emulator itself. While a rom is running, press TAB on a keyboard to get to the in-emulator menu and you can set global properties from there. The exit emulator hotkey is labeled “UI Cancel” if anyone is wondering. All of my buttons were identified without any additional configuration.
Dear reader,
For a long time now I’m a big fan of RetroPie-project. Recently I bought a Raspberry Pi 2. Mostly because of the N64 games I wanted to play.
So far so good. SD burned and everything works like a charm. Until the moment I tried to play a N64 game in the N64 emulator (Libero I thought, not the mupen64plus).
I have installed a Logitech Rumble 2 USB controller, (it’s exactly like a ps2 controller). Almost every button works, except the moving button, the left analog stick.
I’ve watched and read, I think, almost everything there is to find about, setting up a controller for the N64. But still… Nothing.
On the mupen64plus emulator everything works fine tho. The only problem I in the mupen64plus emulator is the lack of my hotkeys.
Could somebody please help me, anything like a link or some pointing in the right direction would be appreciated.
If only I can use the Hotkey’s in the mupen64plus or analog stick in the Libero emulator.
system: Raspberry Pi 2 standard settings, not overclocked.
Retropie-project latest image
(16 GB SD
Cheers,
Michel
AnonymousInactive
Hi guys,
The obligatory “new to linux and raspberry pi, retropie” etc.
I’m trying to set up my SNES controller using the Mayflash SNES to USB converter. I followed the set up guides here (https://www.youtube.com/watch?v=ySoTQhQqZdI around the 9:30 mark), here (https://www.youtube.com/watch?v=OBloKEbBRAU) and here (https://www.youtube.com/watch?v=Z0FT4i2CQVI). The set up seems to go off without a hitch and JSTEST shows all the buttons registering as they should. However when I go to load a SNES game, none of the buttons are configured correctly, the R button is the start button for some reason and the start button closes the emulation. Then when I press f4, I can see some text at the top, after a few lines that start with “Dispmanx:”, that says;
“Could not find joystick mapping forHuiJia USB GamePad, use default
Could not find joystick mapping forHuiJia USB GamePad, use default
No ROM file header found”
This is despite the fact that when I set it up it was recognized as a HuiJia USB Gamepad and config files for it have been configured and are present. What could be going wrong?
I’m using the Raspberry Pi 2, RetroPie 2.6, installed from an SD card image.
I have even tried copying other peoples config settings, such as here: https://www.petrockblock.com/forums/topic/mayflash-usb-with-snes-controllers-second-controller-not-working/
Thanks!
Ive honestly never used the l + r buttons in gameplay for SNES but I’m pretty sure they are functioning. Its possible for your controller they may be buttons 6 and 7 rather than 4 and 5 but idk. This is my official gamepad configuration file that was created by retroarch (I didn’t know what I was doing when I created the first file above):
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/USBgamepad.cfg
AnonymousInactive
Did you get the l + r triggers working? I’m sure I have the same config as the USBgamepad.cfg_.txt but my triggers don’t seem to work on SNES games
I’m having the same issue with the Buffer Underrun errors, but getting (0), (1) and (2). The system works, buttons are mapped correctly, just no audio.
I am running audio through this USB device (http://www.adafruit.com/products/1475) using this tutorial (https://learn.adafruit.com/usb-audio-cards-with-a-raspberry-pi/updating-alsa-config) without issue on everything except for Mupen64Plus.
My guess is that the OUTPUT_PORT setting in mupen64plus.cfg is trying to send the audio through either the HDMI or the 3.5mm jack and not through the USB.
Thoughts?
Check out my post (https://www.petrockblock.com/forums/topic/usb-snes-controller-d-pad-not-working-in-games/).
If you are using Version 3 Beta 2 I am starting to think there might be a problem with the autoconfig files.
My fix was as follows:
1 – Backup all files under config
2 – Delete them all
3 – Reconfigure each joypad using RetroPie Setup script and Joystick setup
My original issue was also fixed by using Floobs retroarch config as my spacing had got changed. As long as you haven’t edited that file then I would try what I said above.
Same goes for my controller: http://www.ebay.de/itm/311040570750?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
cd RetroPie-Setup
sudo ./retropie_setup.sh
Option 3 Setup
Option 317 Configure Retroarch Controller
Followed this steps, config was saved in USBGamepad.cfg – running jstest shows that every button is working when I press them.
When I start a SNES rom, the x,y,l,r buttons are not responding.
Pi Model: 2
RetroPie Version Used: 3.0.0 Beta 2
Built From: SD Image
USB Devices connected: keyboard
Controller used: none yet
Error messages received: blank screen
Guide used: https://learn.adafruit.com/running-opengl-based-games-and-emulators-on-adafruit-pitft-displays/pitft-setup
Hello, first time post here. I’ve been following the guide to the letter, as this is my first time trying this project. I lost the ability to launch roms after installing the PiTFT due to an error(partially my fault). At the end, it mentions to edit the runcommand.sh to add a DMT-87 mode in order to prevent from switching the HDMI resolution. First off, I was using the 3.0.0 Beta2, so there is no get_mode() function in runcommand.sh. I improvised and added it anyways in the get_parameters() function. This was my error, as I should have just skipped the step and not added it anywhere. If you add the line, it results in a blank screen on the PiTFT and you can’t do anything. I experimented with a lot of settings and moving that line in a few places before realizing that I should just delete it and try it out. Just posting this so it could help someone not waste a couple hours like I did, or maybe it should be added to the guide. I haven’t tested it any further than launching a couple roms, but for now I’m just assuming that the latest beta doesn’t require us to add that line.
hi all,
so i am just about tweaking my box. i have ES loaded on a 32gb sd card with a 2TB external drive for everything else.
i would like to move everything from the 32gb sd to the usb drive and boot directly from that. i hear there are boot up speed advantages and that you minimize the risk of sd card corruption for a more stable system.
is there anyway that i can copy my sd card to the usb and keep everything that I have done the same? i would hate to start from scratch.
thanks
Update:
I decided to install 2.6 and then update via the binary method, which seems to have worked. I no longer have an issue with my usb flash drive.
Hi, thx for ure reply!
1. Yes, 3.0 beta 2
2. Both setupsscript and mupen64 testing are fixed!
3. My controller is not listed in inputAuto.cfg file. Im using a standard snes usb from retrolink. I want to add the information, but i dont know what to write. I have tried to add the controller information i got from retroarch when im did the configuration but i didnt work.
As i wrote before, i need to know exactly what information i have to add to inputAuto.cfg.
Thx
Hi, I am having trouble with the 3.0 beta 2. I was using 2.6, and I had no issues.
before I detail my problem, here is what I am using:
Pi Model: B
RetroPie Version Used: 3.0 beta 2
Built From: SD Image
USB Devices connected: Dualshock 3 controller, usb keyboard/mouse wireless combo, usb flash drive
Controller used: Dualshock 3
Error messages received: none
Guide used: TechTipsta’s guide on youtube https://www.youtube.com/watch?v=ySoTQhQqZdI
File:
Attachment of config files:
How to replicate the problem: When I plug a usb flash drive into my Pi, it never populates the folders for the roms like it did with 2.6. I installed 2.6, put my usb drive in, populated the folders, reinstalled 3.0 beta 2 using the SD image method, and tried to add games and a bios for psx using the old folders. The flash drive is recognized when I hit f4 and navigate to it, and I can see all the old folders. The contents of the folders are not being recognized and I can not see anything in them when I navigate into the individual rom subfolders. For now, I will reinstall 2.6 since it seems to work fine, but I would like to get 3.0 at some point.
Thanks.
Just recreated it, rebooting now and will let you know. Can I have you USB gamepad file to test too?
Have you tried changing
input_up_axis = "-32767"
input_down_axis = "+32767"
input_left_axis = "-32767"
input_right_axis = "+32767"
to
input_up_axis = "-1"
input_down_axis = "+1"
input_left_axis = "-0"
input_right_axis = "+0"
The only other difference on mine, is that my first line says
input_device = “USB Gamepad ”
rather than
input_device = “USB gamepad ”
but then I think thats specific to my controller so I wouldnt worry about that.
If you manually change it to the -1 etc.. above make sure the quotes are just as the other examples in the file (or just dont change them basically).
I’m assuming you havent changed anything in any of the retroarch.cfg files.
herbfargus:
I did look at the autoenable feature but I do use a multitude of controllers based on the emulator I’m playing on. Is there a way to specify specific controllers when they are plugged in based on the RetroArch.cfg file?
Floob:
I have re-run it several times, even with all the config files deleted so it recreated a fresh version. The content is listed below:
input_device = “USB gamepad ”
input_driver = “udev”
input_b_btn = “2”
input_y_btn = “3”
input_select_btn = “8”
input_start_btn = “9”
input_up_axis = “-1”
input_down_axis = “+1”
input_left_axis = “-0”
input_right_axis = “+0”
input_a_btn = “1”
input_x_btn = “0”
input_l_btn = “4”
input_r_btn = “5”
input_enable_hotkey_btn = “8”
input_exit_emulator_btn = “9”
input_menu_toggle_btn = “0”
input_load_state_btn = “4”
input_save_state_btn = “5”
input_reset_btn = “2”
input_state_slot_increase_axis = “+0”
input_state_slot_decrease_axis = “-0”
Yes, I’ve just been looking at this. There does seem to be some questionable settings in the default USB_Gamepad_.cfg
A quick way of updating this to ensure it is specific to your exact controller is to run the setup script for your retroarch controller.
So
sudo /home/pi/RetroPie-Setup/retropie_setup.sh
Option 3 – Setup
Option 320 – Configure input devices for RetroArch
Hi All,
I’m starting to pull my hair out on this one! I bought two (let’s face it, knock off) USB SNES controllers off eBay.
They plug in and play beautifully in the menu system for EmulationStation once configured as new controllers. I have run the Joystick setup and they are picked up there without issue also.
Using JStest and the joystick setup I can see the buttons are all working and register on both as the same results:
a = 1
b = 2
y = 3
x = 0
Start = 9
Select = 8
Left Sh = 4
Right Sh = 5
Up = -32767
Down = +32767
Left = -32767
Right = +32767
The confusing part is that once an Emulator loads and picks up the RetroArch configuration file of USBgamepad.cfg, the D-Pad does not work full stop. All the other buttons do, including the special configurations such as emulator quit, save state, load state etc..
I close out of the emulator and the D-pad starts working again.
I’ve tried reconfiguring the cfg file with just +1, -0, +1, -0 etc for the axis and have even added the input buttons for h0up and so on. Still no go.
I should probably tell you that this is a Pi 2 running the latest RetroPie build Version 3 Beta. I have also plugged the controllers in to a PC and they work fine there.
HELP!!!
These appears to work for me now. The aforementioned solution of completely removing all the pre-existing controller .cfg files and making it so only my USBGamepad.cfg was the only file in the directory seems to have fixed it.
I’m making a few of these for gifts (including controllers) so I don’t see an issue with removing all those pre-existing files, but it would be nice to know a solution that doesn’t involve that.
Thanks all!
Looking at the .cfg file RetroArch created, it appears to be similar to all the other USB Gamepad mappings:
input_device = “USB Gamepad ”
input_driver = “udev”
input_b_btn = “2”
input_y_btn = “3”
input_select_btn = “8”
input_start_btn = “9”
input_up_axis = “-1”
input_down_axis = “+1”
input_left_axis = “-0”
input_right_axis = “+0”
input_a_btn = “1”
input_x_btn = “0”
input_l_btn = “4”
input_r_btn = “5”
input_enable_hotkey_btn = “8”
input_exit_emulator_btn = “9”
input_menu_toggle_btn = “0”
input_load_state_btn = “4”
input_save_state_btn = “5”
input_reset_btn = “2”
input_state_slot_increase_axis = “+0”
input_state_slot_decrease_axis = “-0”
Hi all!
I just installed RetroPie v3b2 image for RPi1. Everything is working great, but for some reason after I ran the RetroArch controller setup (from the RetroPie menu in Emulation Station) only two action buttons are mapping.
I’m using SNES style USB controllers and the controller setup seems to detect every button I input, but only buttons A and B seem to map to the emulators; buttons X and Y do nothing.
Any ideas?
Thanks!
Well Ive rebuilt the bulk of the set using clrmamepro off the advmame dat. They run flawless on my computer running advmame 102 (same as retropie runs i believe). I copy them over to a usb stick ,put it in the pi and mount it. They show up in the gamelist under mame in emulationstation but when launched I get the missing files again. The files it says are missing are in the zipped rom. Just to experiment Im going to get a 64 gb cd card and put retropie and the roms on the card from the usb stick. Until then any other suggestions?
well i have tried it two different ways, first up i used midnight commander to copy all my folders from the 1tb to the 2tb disc.
second method (after a format of the 2tb drivce), i plugged both into my mac and copied all folders from the root of the 1TB to the root of the 2tb drive.
in both instances, the 2tb behaves the same. on a side note, when i first did it, the drive would mount but there would be an extra foolder in the directory tree. so instead of the mount point being /media it was /media/usb
but that screwed up my rom patths. so fixing my rom paths and a rebbot, the mount point was BACK to /media. so now my new rom paths didn;’t work. swithch them back and the mount point was back to /media/usb. weird to say the least.
so, i started with a reformat and now am at a point where the drive will not automount. i must quit ES, use sudo mount -a and restart ES, then everything is back.
i have tried adding rootdelay=5 but that did nothing.
any thoughts? and many thanks!
ok, what method did you use to move yer file system to the hdd? I take it was the same method you used on your 1tb hdd, and that worked ok?
also are you using a powered USB hub?
[quote=93598]– For N64, I also use the RetroArch emulator in order to get benefit from all the standards (UsbGamepad.cfg). The problem is that Mario Kart M3 (E) ! rom is a mess on that emulator. Even the “press start screen” is buggy. Again, are there some settings that would enhabce the emulation ? I hope so because I never read elsewhere that someone had such an issue with that rom. FYI, this rom plays nicely on other emulators and on other platforms also.[/quote]
useing the expermintal mupen64plus package fixed that for me. Also if you will just add your controler to the autoinputconfig.ini in the configs/n64 folder it will see your game pad and remap it (with out using retrorarch i understand but it worked better.)
