@BuZz Thanks, it worked. I was just killed by a jackel.

@gizmo98

OK, despite numerous current postings to the contrary on this subject, the udevRUN+="/path/to/executable" function has been deprecated at some point in favor of other, more reliable methods.

http://blog.fraggod.net/2012/06/16/proper-ish-way-to-start-long-running-systemd-service-on-udev-event-device-hotplug.html

http://blog.fraggod.net/2015/01/12/starting-systemd-service-instance-for-device-from-udev.html

Both techniques make use of a daemon as you mentioned, but they can still be controlled with a modified udev rule that will launch the daemon when a specified device is added or removed. They require a little more work, but hopefully at least one of them will bear fruit.

Like this right?

https://cloud.githubusercontent.com/assets/10035308/16599642/7f43e53a-42c0-11e6-9152-c33099878ccc.png

Thanks so much!

That much I know, the problem is I have very little programing experience and don't know how to edit it,

Thanks

@livingthedream

I haven't spent much time on this, so am curious to your thoughts. I use an HD HomeRun Prime right now with the official Kodi HomeRun prime addon (not sure the exact name) on my retropie setup. This works flawlessly for me for live tv and can find in Kodi video addons... I have not setup or even tried the PVR functionality yet. I assume by your post that the official HomeRun addon does not have PVR functions and that's why you want to use the unofficial? At work, so no way for me to check right now.

I think I got it.. I went in and made some settings changes and saved them on my profile. I noticed it happening only when I sign in, so I figured it was account related.

@gizmo98 said in Retropie version 4.0 - Reicast - Logic Error !:

Did you update RetroPie-Setup as well? Update to RC2 will only be complete if you update the script in first place.

yes done script & retropie setup. still no reicast-audio-omx.

A very likely culprit is a name mismatch between the bin and cue file. Open the cue file in your favorite editor and ensure the bin file name listed there matches the actual bin file name exactly, case and all. It is often the case that the two names do not match and the one in the cue file needs to be changed to match.

@BuZz
You taught me that retropie_packages.sh trick, then I tried

sudo ~/RetroPie-Setup/retropie_packages.sh retroarch configure

And it created a configs/all/retroarch.cfg.rp-dist file. I compared (diff) it with my all/retroarch.cfg and found some few differences (input_state_slot_increase, input_state_slot_decrease, input_exit_emulator, input_enable_hotkey, input_menu_toggle, and some keyboard mappings for player1), but I think these differences are because I configured some keyboard inputs in emulationstation.

And then I tried

sudo ~/RetroPie-Setup/retropie_packages.sh lr-fceumm configure

And it created that small default retroarch.cfg for NES. I think this trick very useful to get the default system specifics retroarch.cfg. Is it OK to use this command for this purpose? (I mean: "can I suggest this command to the users that ask for how to get the default retroarch.cfg?")

@Capt-Bornel select button is usually used/ defaulted for coins

Thanks @edmaul69.

I don't play the ps3 often enough to spend the money on more controllers, and if I did buy more, I would probably end up syncing them to the Pi too so I can play 4 player games.

Retroarch by default sets controller priority to USB ports. Try putting the wired controller on the top left (Port 0) and the wireless adapter on the bottom left (port 1). That should make player one on the wireless player 2 and the wired controller player one. if that doesn't work for you , go to Retropie setup and to the xbox360 driver and set number players to 1. It defaults to 2 making the first USB port players 1 and 2 and the second USB port player 3

@Floob Thanks man! I actually found the correct install location and dropped my customs in. It works beautifully.

This may have been mentioned elsewhere, but for anyone affected by this issue, it seems to have been fixed as of this posting and a work around is no longer needed. Confirmation and issue closure specific to RetoPie can be found here.

Thanks for the quick response. I will double check the version when I get home and post. I installed it about 4 months ago on a Raspberry Pi 2. I'm currently running RetroPi just fine and MAME runs so it must be a version that is supported.

When my RetroPi boot it bootstraps into emulationstation on bootup which I select MAME, then select which game I want. It all seems to run fine other then the controller mapping issues I'm having. How do I find out which version of MAME emulationstation/RetroPi is running?

Thanks again,

@bazmonkey that's excellent, thanks for the detailed insight, I really appreciate it. In many ways the Pi is the gift that keeps on giving - complex enough to do amazing things, but logical enough that it's possible to learn how that complexity is manifested.

@Ostego editing the file is not recommended. Better to symlink or mount the USB over existing from location.