Seems I had a problem with permissions, when following the github wiki I was using the mount command with SUDO, and ofcourse the owner/group was root so the user pi couldn't read the mounted dir, the fix was to include the UID and GID for PI in the options during the mount command

sudo mount -t cifs -o domain=workgroup,username=<USERNAME>,password=<PASSWORD>,nounix,noserverino,defaults,users,uid=<LINUX_USERID>,gid=<LINUX_GROUPID> //<HOSTNAME>/ROMSSHARE /home/pi/RetroPie/roms

both LINUX_USERID and LINUX_GROUPID were 1000 in my case.

Hope this helps someone from wasting as much time as I have on this problem.

Ignore that - I misunderstood (And the PS3 controller does work ok in Ubuntu 16.04 unlike I said above - I just had to configure it by holding the playstation button it seemed).

You mean it's fine in ES and games, just no good in the retropie-setup menu ?

It works - it's just it doesn't use the same mapping. Left analog moves, and select will choose an option. This will be resolved at some point in the future, but the menus were never originally designed for navigating via joypad - it was added later via joystick to keyboard mapping. Since it;s mostly configuration and you are on a PC, it's not a big deal to use a keyboard to configure if you don't like the ps3 mapping.

I figured out the sound problem but I still don't know how to boot to ES

@Rikochet see https://github.com/RetroPie/RetroPie-Setup/issues/1798

you can add the product id / vendor id manually (assuming they both have different product ids) to the controller config in /opt/retropie/configs/all/retroarch/autoconfig (so you have two copies of it each with the difference ids).

You will however also need to manually set the controls up. Right now when controls have the same name we don't do this automatically. TBH the manufacturers should bother to give them unique names etc, but the cheap stuff often has missing device/vendor info etc.

example

# Hex vid:pid is found using "dmesg -w" or "tail -f /var/log/syslog" and converted to Decimal using http://www.binaryhexconverter.com/hex-to-decimal-converter # Hex vid:pid = 2810:0009 -> Decimal vid:pid = 10256:9 input_vendor_id = 10256 input_product_id = 9

Note when posting please also read https://retropie.org.uk/forum/topic/3/read-this-first first and provide the information as requested so I know your set-up.

@jnbui79 Any update? I am having this identical issue on my Samsung set. RetroPie works perfectly on every other TV I try it on.....

Please let me know. Thanks!

-Craig

@jpretpiuser14 you may have saved a "per system" retroarch config which overrides it (eg by settings save config on exit to on in an emulator ). There are a bunch of topics related to this and some info on the wiki (Sorry short on time to explain further).

@jworkin after scraping your names will show up proper even if the filenames are a little less readable. You never want to change the filenames with mame as that is how they are identified by the scraper among other things.

My morning shower thought for tomorrow will most certainly be "I wonder then, how did I get those initial 3 images in the first place?"

@JHNTR Then the issue is most likely your power source. If you still have trouble with a proper PSU, the next thing would be to check the image was written currently, and that the sdcard isn't faulty.

Solved!
Nvm, I figured it out after reading the wiki for the 15th time. You need to disable hotkeys in the autoconf.cfg file first and then edit the mupen64plus.cfg to enable whatever you want to exit the emulator. As stated above I use Z Trigger + Start button to exit back out. It works perfectly and you do not sacrifice any buttons.

/opt/retropie/configs/all/autoconf.cfg

mupen64plus_hotkeys enable hotkey auto configuration (0)

then go in and edit

/opt/retropie/configs/n64/mupen64plus.cfg

and set your control to the way you want it to exit out of game. I programmed mine for Z trigger and Start hit together

https://github.com/retropie/retropie-setup/wiki/retroarch-configuration
You can also swap the ok and back buttons of emulationststion in the retropie setup menu

@nwgalloway nope. Not until an on-screen keyboard is integrated

This is the only solution in the interim.

https://github.com/retropie/retropie-setup/wiki/Wifi#method-2-connecting-to-wifi-without-a-keyboard

@derebo You can enter the menu on a keyboard initially, and then under Input (general) the first item is Config Menu which can be changed to a joypad button

Note that lr-mame2003 is a better mame emulator for the rpi3 though (Supports more games) - along with lr-fbalpha

@BuZz ok, thank you

@gromgsxr should already be fixed if you update retropie-setup

I have a hunch, which I won't be able to confirm for a few days. The above behavior was observed on my brother's cab/Pi, which is identical to mine except that his IPAC is newer. I've read elsewhere that newer IPACs get recognized by retroarch as a USB gamepad and thus don't necessarily send the corresponding key.

On my machine, which has an IPAC that I bought in 2001 or 2002, everything shows up as a keypress, and the above behavior isn't an issue.

I'm going to see if I can retroarch to ignore the IPAC and just treat it as a keyboard so that we can share config without remapping. Otherwise, I might have to remap and get used to a different default layout. This is the layout I prefer, as it makes sense to me in ES, mame, and console emus:

(A/B1) (B/B2) (Y/B3)
(X/B4) (L/B5) (R/B6)

@rbaker its a file not a folder. If you load your roms with a usb it would go into the same folder the roms go into. In this case you would put the file in the snes folder. You can make a text file on your computer, add the info i posted and save it. Then rename the file. Remeber to name it exactly the same name with the file extension but then .cfg at the end removing whatever extension name it had when you created the file.

I found that thread before.. Nothing in it seemed to help so far. I've tried to change the controller configuration as mentioned and that didn't help. I supposed I could try to remove and re-install lr-pcsx-rearmed next.

EDIT: I tried re-installing lr-pcsx-rearmed - didn't help.