Looks like you've enabled 'Save Configuration on Exit' in RetroArch and the last ROM configuration is automatically saved.

I remember a topic a month ago with a similar problem - the pairing of Xbox controllers worked, but they acted as a single controller. The solution was to install an alternate driver for the controller - xpadneo (https://github.com/atar-axis/xpadneo). If you want to give it a try, the installation is quite easy: Remove any Bluetooth controller from the RetroPie script Bluetooth configuration. Remove the xpad driver from the RetroPie setup script, from the drivers package section. Install xpadneo (run this from the SSH session): git clone https://github.com/atar-axis/xpadneo.git cd xpadneo sudo ./install Reboot and then redo the Bluetooth pairing for the controllers. See if you get 3 devices (/dev/input/event[0-2]) and Emulationstation detects all your controllers after the installation.

Well i could hack code into mame2003-plus to read it thats not a good global solution though so ill add it to my todo list which isint too long atm!

Glad you got it working. You can mark the topic solved by editing your first post in the topic.

@mitu Very true! Perhaps he's missed his nap and has gotten a little fussy.

@RetroJoe This is not a ROM sharing site, the rules are there so people understand that. You seem to have not read them - https://retropie.org.uk/forum/topic/2/forum-rules. Freeware and demo image That doesn't give re-distribution rights automatically. There's a topic dedicated to how to legally obtain games/ROMs, you may post there - respecting the forum rules - links to games you think are freeware/demo: https://retropie.org.uk/forum/topic/10918/

Do you have an arcade panel configured or are you just testing out with a controller ? The X button is mapped to the input_menu_toggle_btn action, so you can remove the line containing the mapping from the controller configuration file. The file is generated by Emulationstation in /opt/retropie/configs/all/retroarch-joypads, named after your controller. To be honest, I'd be more concerned about the Hotkey + B (reset content) combo, since it will reset the game, while Hotkey + X merely pauses it. If you're using a keyboard, I think F1 toggles the menu.

@krullbeast said in can udev read i2c and hardwired GPIO buttons simultaneously?: do you think it is possible to read the i2c data and also the A and B buttons inside of retroarch? Not an expert on this, but I think RetroArch doesn't read directly from GPIO (I2C or otherwise), instead it uses an established input driver (udev/sdl/etc.) - https://github.com/libretro/RetroArch/tree/master/input/drivers.

@Brutilus Did you install any driver for your controllers ? Update your RetroPie installation (if you haven't done already) and reset your controller configuration, then try to install the ps3driver and pair your PS3 controllers. Make sure they work, then report back if they haven't. You can debug your input configuratio/detection by looking at the Emulationstation's log file - in ~/.emulationstation/es_log.txt.

@Charlie-Scheib Is there no way within the drive settings itself to keep it spinning on the RetroPie/Pi settings? I haven't tested this but this might work! You'll need to do most of this from the command line (difficulty: medium) There are a couple hard drive power management programs that can be used on the Raspberry Pi to control how long before the hard drive spins down to save power and the life of the hard drive. I wonder if the program hdparm will work for you. You could set the 'spindown_time =' to something like an hour (720) or 2 hours (1440). You basically find out how long you want measured in seconds and take that number and divide it by 5. So 2 hours is 7200 seconds (7200sec / 5 = 1440). https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

@pengu1n said in Does Retropie 4.4 Run on the CM3+ Lite?: I ran into a login prompt at the console on reboot though...which was strange That happens when systemd is updated - a known Raspbian behavior - https://retropie.org.uk/docs/FAQ/#why-emulationstation-doesnt-start-automatically-after-an-update.

Here is how I did it in OSMC (it is related to retropie because i have used retrosmc scripts, based on retropie, as a part of the solution): Install OSMC and SSH into it. Then... UDPAGRE OSMC TO KODI LEIA sudo nano /etc/apt/sources.list (add the following line in the very first line of the file) deb http://download.osmc.tv/dev/gmc-18 gmc-18 main (to save the file, press CTRL+O, ENTER, CTRL+X) wget -qO - http://download.osmc.tv/dev/gmc-18/pubkey.asc | sudo apt-key add - sudo apt-get update sudo apt-get dist-upgrade dpkg -l | grep mediacenter-osmc | awk '{ print $3 }' (the last command should show OSMC version 17, which has KODI version 18) INSTALL RETROSMC AND PS3 DRIVERS cd /home/osmc wget https://raw.githubusercontent.com/mcobit/retrosmc/master/install-retrosmc.sh . chmod +x install-retrosmc.sh ./install-retrosmc.sh Go to "manage packages" > drivers > ps3controller > install from source (wait) > configuration/options > install ps3 controller (clone support gasia) > pair ps3 controller (clone support gasia) (follow instructions) > Then "connect controller through usb", then disconnect usb, and pair via bluetooth… It may not pair yet. UNBLOCK BLUETOOTH apt-get install rfkill rfkill unblock all hciconfig hci0 up MAKE JOYSTICK RECONNECT AUTOMATICALLY IN THE FUTURE sudo su echo 'SUBSYSTEM=="input",ACTION=="remove",RUN+="/bin/systemctl restart sixad"' >> /etc/udev/rules.d/999-sixad.rules sudo udevadm control --reload-rules && udevadm trigger sed -i 's/exit 0//bin/systemctl restart sixad\nexit 0/g' /etc/rc.local INSTALL EMULATOR ADDONS From the Kodi 18 (Leia) main menu, click on the Add-ons icon (open box icon). Select Install From Repository, Click on the Kodi Add-on, Repository, Click on Game Add-ons, Select Emulators, From the giant list of emulators you now see, you have to install the ones you wish to use. If you can't find the "Emulators" section, some distros don't compile them. The script install-retrosmc.sh (above) may have some hidden menus to download and install all cores (emulators) in one shot. Give it a try. Also, check under kodi settings "my addons" to see if you don't already have all the emulators installed. Now, install some other game addon (research about your options!) which uses "Kodi retroplayer" to launch games. It will require some emulators addons (also called libreto cores) to have been downloaded and installed already on kodi.

Thanx!

It depends on how you're trying to set up the bezels. You can, in theory, put the .cfg anywhere and then point to it for each game. Or create an individual .cfg for each game. So it really depends on what you're trying to accomplish and how you are going to accomplish it. I started messing around with individual bezels for arcade (and other) games, but then I stumbled across the Bezel Project. They have a preconfigured set of bezels for literally thousands of games (I count over 7000 games). You can also install bezels for individual systems. The only annoyance is that the roms need to be named according to the No-Intro naming convention, however this only affects console roms. Arcade roms are supported by their standard rom names. You can see a video on The Bezel Project here: You can get The Bezel Project script here: https://github.com/thebezelproject/BezelProject Once you're installed reboot and you can install bezels for individual systems through the Retropie Configurations in the standard menu.

@FormulaFox Good deal. The documentation for that thing was quite an interesting read.

@aatheronb pay attention in class instead of trolling the forum

@BuZz Fantasic. thanks.