@johnsorger6 How did you create the 7z archive ?
Can you run with verbose logging enabled and post the contents of the log file /dev/shm/runcommand.log on pastebin.com so we can take a look at what errors appear ?

If your ROMs are on the sdcard and your RetroPie installation is functional, just copy them over to your PC via File Shares or other transfer methods.

@dudleydes Thanks, I've already made the two new systems by making custom collections. but I need to remove the old ones. It looks like Emulation Station doesn't allow you to remove a system from the carousel. If I remove them in the es_systems.cfg, the roms they are attached to also disappear from the collection.

It used to be that you could do this - https://retropie.org.uk/forum/topic/10849/create-a-custom-es-system-able-to-launch-games-for-many-systems -
but collections are the new hotness.

you edit the config.txt file with some of these settings:

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

@StarshipKnight That's a generic error message when the compilation (and the follow-up installation) fails. You'll find the detailed error message in the ~/RetroPie-Setup/logs folder, in the most recent log file.

@mitu Ah, that would explain why it worked during my last install, but not now. Updating all the core packages at once seemed to ignore the fact that there was a newer version of ES and left me on 2.7.5, so I updated that individually, which put me on 2.7.6, and everything works like it used to now. Thanks for your help there! You've saved me tearing my hair out looking for something I would never would have found by myself! :)

@tubewayarmy and use a topic that summarises the issue - not "Noobie".

@boomspar Generally BIOS and ROMs are not provided by RetroPie unless there's free/open source. That's why the BIOS requirements are always mentioned on the emulator's page. Just like for ROMs, you're responsible for copying the necessary BIOS files in place - they don't come with the package installed from the RetroPie-Setup.

@Earthboundfan15 Please add more info about your system as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

It depends how many roms you have and how many of them are part of the current mame set 0.201+202 if Progetto or scraping will be better. But a good option nonetheless.

@schmiddyman said in 2 joystick cabinet configuration issues:

gpio=13,11,15,19,10,8,-1,16,18,-1,-1 gpio2=31,29,33,35,24,-1,-1,26,-1,32,36,-1,-1

From a cursory view.
Unless you used the hotkey-btn branch your provided list for gpio2 is too long.
In your gpio parameters you provide 16 Pins/Buttons but initially you mention 15 buttons?!

However, good to see you found a different solution.

@MosaicDragon The ps3driver - if installed - will disable the native OS Bluetooth stack, so you'll not be able to pair additional (non-PS3) controllers. This is the behavior you're seeing. I advise you to remove the ps3driver and install the sibling customhidsonly driver and try to pair any Bluetooth controllers you have (including the PS3 controller).

@MrRalphMan said in Unable to get Trackball working with Mame2003.:

*** Can I mark this as solved or something? ***

Modify the topic subject and add a Solved at the beginning.

@myname You don't need to use any config file or modify any file whatsoever. Just follow the documentation and map your controller from Emulationstation, skip the Hotkey button assignment and then choose yes to use Select as the Hotkey button. That's it.

That teaches one to tidy up behind oneself after compiling, lest you'll find the remains later when you don't remember putting them there. 😊

(Alas, data remains don't tend to decompose by themselves like other remains do.)

That's great to hear, since I didn't have any ideas left anymore myself.

Yeah, bluetooth pairing is one of the most annoying things about wireless controllers in computer tech that I know.

Thanks for posting your solution, albeit not exact instructions. :)

Got it.. thanks for the input.

@mitu Thanks for replying. My gamepads mirror each other, and have the same number of buttons installed and mapped to the same keys. I'm aware that the gamepads won't work correctly if there are any differences at all. In fact, I had to add two extra buttons to the player 2 USB encoder in order to make it mirror the player 1 USB encoder precisely. Initially, we had installed two extra joypad 1 buttons to serve as a hotkey/escape and as a pause button, but they wouldn't work without identical buttons set up in joypad 2. The joypad 2 buttons are actually inside of the cabinet, because there are no holes for them on the control panel. I've already used jstest many times, too. So, I can promise that the two joypads are configured identically, and I haven't set up any player 1 buttons in the 800/5200 emulator that map differently from player 2. I know better.

I really do think the problem is that the Atari 5200 emulator isn't yet set up to recognize multiple fire buttons for player 2. I found a discussion on this forum from May 2016 entitled "Atari 5200: New version of Atari800 (Beta): two triggers (Moon Patrol), hat start and exit buttons" where user jfroco discussed a new port of Atari800 that added trigger1, trigger2, asterisk and hash support for joystick buttons, but only for player 1. A later post from user Veramacor (April 2017) detailing atari800.cfg settings also reflected trigger1 and trigger2 support on Joystick 0, but not Joystick 1. Then, in May 2017 user Used2BeRX asked user future.child if they would be able to properly code the player 2 controller to allow two-player games. It's not clear from the subsequent conversation that this ever got done in the way I'm discussing here.

I'm guessing from this discussion and my experiences this weekend that the Atari800 emulator must still be in that same developmental place, because when I tested the 5200 Moon Patrol ROM (I do own an original cartridge), sure enough, player 1 could use the second trigger (button X on my arcade cabinet config), but not player 2. The X button did nothing for player 2. Again, I'm not having this problem in any of the other emulators I'm using with Retroarch (MAME2003, MAME 2003-Plus, Final Burn Alpha, MAME2010, Stella, CoolCV, or the NES and SNES emulators). On those emulators, all buttons work the same for both gamepads. There are no discrepancies.

However, if someone can verify that they are able to use both fire buttons for both player 1 and player 2 in Atari 5200 Moon Patrol (one to fire, one to jump), RealSports Football, etc., I will be more than happy to try to get it working for Player 2 in Retropie. I just haven't seen anyone confirm that there is trigger1, trigger2, * and # support for Player 2 in the 5200 emulator. The only evidence I've found is that there isn't such support, and I don't want to spend days futilely trying to set up something that isn't actually supported. In fact, a post from three months ago said that the controller upgrades future.child made from 2016-18 aren't part of the current libretro version of atari800. (That thread also suggested that RealSports Football is viewed as a lost cause because of its need for keypad input.) Maybe the best way to ask this question is, does Moon Patrol work properly for player 2 on the 5200? Can you jump and fire?

@melbmatt50 Again, the package has not been removed from RetroPie, it's still in the optional packages section.

This actually helped:

1 year ago
OK I figured it out. I had to set the hotkeys manually rather than rely on the autoconfig.
For anyone else out there with this issue, what you need to do is open the RetroPie menu. Open RetroArch.
Go to Settings>Input>Input Hotkey Binds.
Go down to Quit RetroArch, and set that to your Start button.
Next go down to Enable hotkeys, and set that to your Select button.
Go back up to the Main Menu within RetroArch.
Open Configurations.
Save Current Config.
Back out and exit RetroArch.
You're good to go now for most emulators.

https://www.reddit.com/r/RetroPie/comments/5t44qq/unable_to_exit_emulators_help/