old retropie image downloads
-
Does anyone have an older version of retropie that i could use? ideally before 3.0! Need the retroarch auto joypad configs for my project and they dont seem to be available in 3.0 or later.
-
@Loxley rather than forfeiting all of the improvements since 3.0 perhaps you should brush up on the updated settings for retroarch:
-
thanks for the response! I am having the problem he discusses were my controls arent recognized in emulators... however im also using a rasberry pi zero... not a 2, and i dont have the "edit retropie/retroarch configurations" option in the retropie settings menu... is this just because im using the rasberry pi zero version of retropie?
-
never mind... i was able to find the same settings in a different menu
-
alright, thanks to you I finally got my usb gamepad to work! thanks!
However I still cant get the @#$%ing gpio buttons to show up in emulators! any ideas? ive mapped them to keyboard buttons and they work in emulationstation but in any game they just dont do anyting! -
@Loxley if your gpio are treated as keyboard buttons they should be automatically configured when you configure a controller through emulationstation otherwise you can set the controls manually in retroarch.cfg as explained here: https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration
-
Alright... I've tried manually changing the inputs as well... still getting nothing. its like there is some disconnect between retroarch and my controller pcb. what i dont get is that if go to the terminal and hit the pcb buttons they type the keys that they are assigned, but if i go into a game i get nothing when i hit them. When i plug in a keyboard i can use the same keys that the pcb has assigned to it no problem though! I figure i need to somehow force retroarch to use keyboard controls through the gpio... is that correct?
-
@Loxley Can you explain more about your "Controller PCB"? It seems like if the keyboard is working then you're configured correctly for keyboard input. Then I would assume your PCB is not sending the correct input if it's supposed to be simulating keyboard strokes via GPIO. Here's a link that may or may not help but I did GPIO project quite a while ago but I was using Adafruit's retrogame.c and setup the GPIO inputs for MAME default keys and it worked like a champ.
https://retropie.org.uk/forum/topic/363/joystick-using-gpio-and-usb-at-the-same-time
-
Here's the controller pcb im using.
http://store.kitsch-bent.com/product/common-ground-dmg-button-pcb
What i dont understand is that all of my controller pcb buttons work fine in the emulationstation menus. I can use them no problem to navigate the menus but as soon as i launch a game they stop working. Even weirder than that is if i go to the terminal and hit my gpio buttons they even work there! And each one types out the key that i mapped it to! Its got to be something to do with retroarch... You said that you mapped your controls to the "default" mame keys... Is there any way to see what keys an emulator considers default? Specifically looking for NES. Maybe if i map my pcb buttons to the default keys that the emulator is looking for it will work!Thanks!
-
When you configure your keyboard/joystick input they become the default emulator keys (if you left NES at it's default Libretro emulator).
Look in /opt/retropie/configs/all/retroarch.cfg and look for the keys similar to this. These will be the global key configurations for all Libretro cores if you haven't configured the emulator specifically which it sounds like you haven't.
input_player1_a = "alt"
input_player1_b = "ctrl"
input_player1_y = "shift"
input_player1_x = "space"
etc.I am not sure on that PCB. I think it's entirely different from what I was doing so I probably wouldn't be much help. You'll probably have to experiment or maybe another user has experience with that board. Here's basically what I did. I used the GPIO input method and it does work well. My main focus was MAME games.
You have to keep track of each GPIO input you wire (i.e. - Up=GPIO pin 2, Down=GPIO pin 3, Left=GPIO pin 4, Right=GPIO pin 17, Button 1=GPIO pin 18, etc), then assign it to a key (i.e. - 2, KEY_UP | 3, KEY_DOWN | 4, KEY_LEFT | 17, KEY_RIGHT | 18, KEY_LEFTALT, etc. these can be any keyboard input).
Then compile the file and run a short command to make it persistent and poll the GPIO inputs on bootup. I believe GPIO pins are NO (Normal Open) when you press a button it closes the circuit and the polling engine sends the key assigned/setup from the retrogame.c file below to a queue or wherever inputs go (getting deeper than I understand here). As far as I know it can not tell the difference between a GPIO or keyboard input. At least for gaming purposes it doesn't matter.
Lastly start the game you want to play and start configuring inputs (if using a standalone emulator--Libretro cores are configured with ES Input Configuration) which basically is just pressing the button you want assigned for up, down, etc. in the emulator configuration (I didn't have to much to do here as I configured the inputs to match the MAME default inputs). You'll need a keyboard attached for this part.
It's also handy to have a Dupont header block to unplug all your wires at once (you have several when you're done, one to each button, joystick directionals and a common ground) or you need a way to label them if you plug them in directly to the Pi. It's similar to what you use on a regular motherboard to plug in power, reset, HD LED, etc. to a block before attaching to the mobo.
Here's a snip of what I mean from the file, you see how each GPIO input is assigned to a key, basically it treats it like a keyboard input. The numbers are the GPIO pins and to the right is the key assignment.
// Input Output (from /usr/include/linux/input.h) { 2, KEY_UP }, // Joystick (4 pins) { 3, KEY_DOWN }, { 4, KEY_LEFT }, { 17, KEY_RIGHT }, { 18, KEY_LEFTALT }, // B/Bomb/secondary { 23, KEY_LEFTCTRL }, // A/Fire/jump/primary { 24, KEY_Z }, { 25, KEY_LEFTSHIFT }, { 8, KEY_X }, { 7, KEY_SPACE }, { 27, KEY_5 }, { 22, KEY_ENTER }, { 10, KEY_1 }, { 9, KEY_ESC }, // For credit/start/etc., use USB keyboard or add more buttons. { -1,
-
Welp, I've done all that and at this point i have literally no idea what could be wrong. for some reason retroarch just wont recognize my gpio inputs not matter what i map them to. I've even tried configuring a controller then going into the joypad config file and changing the inputs to the ones that my pcb buttons are. Still nothing! Its really weird honestly! wish this thing would WORK XP.
Thanks for your help so far though!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.