@Parzival youd have to code the emulators to access each core... so... good luck. Would be a cool idea

I ended up reinstalling to rebaseline for troubleshooting as when I first setup before with just the keyboard and single SNES controller I was able to play and use fine for a while without issue. I didn't mess with too many things really but trying controllers in multiple ports might have created the mess and well it's like a 5 minute process.

After reinstall I was able to setup the Logitec f710 fairly well with just a few test ROM for NES and SNES. I did the standard controller config but then went into the advanced global inputs and went through there also which cleaned up outstanding issues. Seems to be working solid so far.

Tested good and stuck when leaving games, switching between consoles and safe shutdown so looking solid so far

@meleu

Good to know, thanks!

this is (almost) awesome! I fear that something physical needs done to the cable, like wiring a positional wire, like RGB sometime needs horizontal and vertical timing, does it do it at any other similar resolutions, like 480i?

@meleu said in iPac 2 and USB SNES controllers, Player 1 issues:

@briankross Check it out:
https://github.com/meleu/RetroPie-joystick-selection

I think this will solve your problem. ;-)

Thank you!

For what I want to do, it looks like I just need to configure this once and I'm good to go. When I unplug and replug the SNES gamepads, the first one I plug in is Player 1, next is Player 2, and iPac 2 is always Player 3 which seems to be just fine for MAME and navigating Emulation Station.

Woo! Thanks again!

using "pixels" skin for emulationstation reduced lag to zero. thanks y'all.

If emulationstation has no black border (overscan settings) you cannot do anything now. Open /opt/retropie/configs/n64/mupen64plus.cfg. Find rice and GLideN64 sections. There should be antialiasing (MultiSampling) options which can be set to 0,2,4.

killer instinct does not work.

lr-fba-next: preliminary support, but not playable (AFAIK)
lr-mame2003: does not work because of a bug - https://github.com/libretro/mame2003-libretro/issues/38 - almost certainly would be too slow if it did work.
advamame: works, but about 0.5 fps.

n64 has a version you could try.

For those keeping an eye on this thread, so far so good! For about a week the Delta PMC-05V015W1AA seems to be working just fine, runs cool, the rPi runs fine, I'll test the analog audio output soon just to see if it's clean. It does have a soft high pitch harmonic tone, but inside any enclosure should be completely unheard.

You could download/setup a new RetroPie image at your friends and use SSH & SCP (under Windows Filezilla or WinSCP) to copy the roms folder over. Even easier would be to use the Samba file shares by enabling them in the config and then copy files over from \retropie\roms .

@BuZz Thanks Buzz. I just retried this at work :-) and it downloaded with the correct MD5. Thanks for the pointers.

@davej thanks for the advice and insights; I was unsure if exophase's code drove the GPU directly, it sounded like it did from descriptions, but benchmarks didn't confirm.
I do use the barrel distortion shader at times, but not often. Still soak-testing the Pi with the GPU overclock removed.

So did you just scrape your Arcade library and then add your own art? I like the way NES, SNES, and Genesis scraped with the box art, but Arcade was a cluster-F. I imagine scraping Arcade just for the data and taking screen shots to use as title art would be better.

@kaitlin4599 You must set a button to be the hotkey and then a button to be the menu toggle.
And to get the configs saved, you must to enable the "Save config on exit", but be prepared to face some confusing situations. The use of "save config on exit" is discouraged in RetroPie (my words, not an official statement).

Nevermind, I burnt it all down. On RetroPie 4.0 RC1 using NES30 Pro Firmware 1.7 Beta 5 and now the hotkeys are working. Thanks for the assist anyways...

@cromartian

If this is your only problem, it's probably a better idea to continue trying to troubleshoot it rather than move backwards. Can you past the contents of /etc/rc.local?

Hey, thanks for all the help, and thanks for the command lines, Rascas.

When I ran sudo apt-get update && sudo apt-get dist-upgrade -y I got the same "failed to fetch" errors as when I tried to install kodi. Tried 20 times or so. It would get about 3/4 way through and start doing that.

It just felt like a species of a "timeout" error to me. So, just to see, I took the pi downstairs and directly connected it to the modem. It went through both installs fine. So it's something to do with the wifi.

Anyway, got kodi up and running - fantastic. Thanks!

Now I have a weird problem where kodi cycles through launch over and over with the PS3 controller in - it goes from the black screen with the grey config box to the kodi background (the blue bubbles) and then bakc again, flashing errors at the bottom of the config screen so fast I can't read them. If I unplug the controller, Kodi starts without any issues. Once it's launched, it works with the controller fine, but won't exit, reboot, power down, or anything else unless I unplug the PS3 controller. It just cycles through the same thing as the launch over and over with errors at the bottom of the screen, like I am restarting it. The minute I unplug the controller everything works perfectly again.

Works great with the keyboard, though. So my workaround for now is launch Kodi with the controller, wait for the Kodi bubble background, then unplug the controller. Then plug the controller in and unplug the controller to exit.

Thanks,

It's working now. I uninstalled retropie and installed it again and reconfigured the controllers from RTGUI and then did the "Bind"-thing to get the controls right for the "Core" NES.

The keyboard is working as it should at this moment to, don't know what that was for weird error.

Thanks. =)