@perryrhodan Sounds good. Glad I could help. Just remember... 'Google is your friend'.

@dankcushions This case gets more and more curious :D
Im pretty sure i reinstalled the emulator "from binary" and not from source and it still worked at the end...weird.
Anyways, thanks for the headsup !

@sselph That looks great, I had no idea it would work that way!

Disregard the rest of this message. I found the solution on the Raspberry Pi Forums. Again, surprised it doesn't have anything to do with network shares but the solution will be the same.

In case someone else stumbles on this post and wants to know the solution I'll be going with; I'll be editing the savestate and savefile directory in the retroarch.cfg file. We'll make this a local destination and worry about space issues if/when the time comes.

I have another problem. I was apparently wrong about it being able to save to the share. The save files I saw in there were all from before I set it up this way and they don't update as we make progress.

When I hold Select + Right Shoulder, it says "Failed to save to /home/pi/RetroPie/smb" or something to that effect. I'll have to play with permissions and stuff on my Windows machine tonight but any advice would be greatly appreciated.

It's weird that I'm not finding anyone else that did a setup like this. It was one of the first ideas I had before the RasPi even came in the mail. Hopefully I'll get all the kinks worked out and write an all inclusive guide for it. Would love to see it put up on the wiki someday! :)

I take that back, I see where a couple of people touched on the subject and maybe more on Reddit but I can't access it at work :(. The one I was able to read barely got as far as I have and made no mention of issues with saving. I'm guessing it wasn't a problem because he was using NFS but I've never played with NFS shares so I can't speak to that.

In my research I've found three variations:

Wifi and Bluetooth never worked - To me this seems like a defective board or image on your sd. Try retropie 4 and/or NOOBS (full image) to install rasparian. If that doesnt work its probably the hardware. From what I gather both wifi and bluetooth functions are on the same chip. For me, my bluetooth seems like its working, but I dont have any controllers worth testing. I got some fake ps3 controllers but I think its those that arent working and not the bluetooth. in rasparian the bluetooth icon was lit and said no bluetooth devices found.

wlan0 is listed in 'iwconfig' - This seems to be the best scenario of the three. If its listed it seems like people have been 50/50 in getting it fixed. Some say that apt-get update /upgrade fixed it, or various other updates. Or reflashing the sd card. This doesnt seem to transcend os installations.

wlan0 isnt listed in 'iwconfig' - This is the boat Im in. I know wifi worked at one point in time. Maybe it the chip fried, or maybe there is something wrong with the firmware or other bios/drivers stored directly on the pie. Updating the firmware didnt help, and no other command or config change works. This transcends all OS installations so in one way that limits the search and is good. But its mostly bad because the fix for the others may simply be to reflash your sd card.

Good Luck, Im still messing with mine hooked up to ethernet, but in a week when Im satisfied with everything except wifi ill be returning it for one that is working. I know one other poster took this route. Anyway, decide what group your in and narrow your searches. If your in my group let me know, I have 4 different threads out there, unfortunately none have the answer. Mine seems to be the rarest and most unresolved, but maybe I just think Im special.

@djdarlo
I think linux consider a keyboard key as a keyboard key, no matter what keyboard has its key pressed. It doesn't care about "this key comes from keyboard1, this key comes from keyboard2".

You have to set different keys for players1 and 2.

Thank you @Floob (or is it PRB?) I understand now how it works. I can use the left and right to select WHICH save state slot I want, and proceed to save OR load.

BTW, Ive watched many of your "how to" videos on youtube... Not to be a lurker, but thank you for much of the help in the past that you dont know you did.

@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.