If you can somehow press whatever would be your 'start' key, you can setup an input from there.

You can also try to ssh into the Pi and delete configuration files for the controllers, but if you're having this issue, i'd honestly just reinstall.

I was having controller issues a few weeks ago and I tried so many different things and nothing worked and then I just said F IT and reinstalled and it magically just worked.

@BuZz
I'm planned on using a SNES USB controller so i have nothing to worry about then!

Thanks for the answer!

Please see https://retropie.org.uk/forum/topic/3/read-this-first before posting, and please use the "Support" area for help, not the ideas and development section. I will move this thread.

thanks yet again herb , i getting there slowly but surely

I updated from source and everything OK. No more GUI-analog-bug Well done Kaos!

thanks. will try that out!
do you run your Pi 2 on stock clocks?

@andymck I gather you've read and configured as per the wiki? https://github.com/retropie/retropie-setup/wiki/Xin-Mo-Controller

I've not got this controller, but I'd start with this guide first if I were you.

@YoshiFan501 no prob. Glad i could help!!

Thanks @dudleydes
I updated my original post to say "PWAD" instead of "IWAD" so I didn't look like an idiot haha

I think the wiki page is out dated because it refers to /opt/retropie/configs/doom/ when mine actually has /opt/retropie/configs/ports/doom/ instead. Maybe someone should update that :-)

Here's what I did (hopefully no typos):

mkdir ~/RetroPie/roms/ports/doom/class_ep
unzip class_ep.zip -d ~/RetroPie/roms/ports/doom/class_ep
ln -s ~/RetroPie/roms/ports/doom/prboom.wad ~/RetroPie/roms/ports/doom/class_ep/prboom.wad
ln -s ~/RetroPie/roms/ports/doom/doom.wad ~/RetroPie/roms/ports/doom/class_ep/doom.wad
cp ~/RetroPie/roms/ports/doom/prboom.cfg ~/RetroPie/roms/ports/doom/class_ep/
nano ~/RetroPie/roms/ports/doom/class_ep/prboom.cfg

# Files wadfile_1 "Class_Ep.wad"

nano ~/RetroPie/roms/ports/The\ Classic\ Episode.sh

#!/bin/bash /opt/retropie/supplementary/runcommand/runcommand.sh 0 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-prboom/prboom_libretro.so --config /opt/retropie/configs/ports/doom/retroarch.cfg /home/pi/RetroPie/roms/ports/doom/class_ep/doom.wad" "lr-prboom"

chmod +x ~/RetroPie/roms/ports/The\ Classic\ Episode.sh

Then I restarted EmulationStation
Ports -> The Classic Episode -> New Game -> The Shores of Hell

For some reason, selecting "update all installed packages" installs the retroarch cores from source. The lr-fbalpha takes hours to compile.
In the meantime I tried to use the rpi2 to update the retrofit 1 image, but when I popped the card in the Zero, emulationstation wouldn't start..
Finally I was able to update on the Zero by using the "manage packages" option, and selecting to update from binaries. Although the retropie version did not change until I also selected to update the setup script.
Maybe (probably) I'm doing it all wrong.. but for now, at least the version is 4.0.4,which supports individual loading splash screens. Which is all I really wanted 😀

gotta love fridays.

@Nightfire Oh I think I know what you mean. Doesn't that automatically turn on anyhow? I used to use it all the time, but found it easier to just use WinSCP since I could view all the files and roms.

@ciroreb Any luck figuring this out? I use a 360 wireless controller and have the same problem. Tried plugging a mouse in first, but the controller still lags. Maybe we can get an install on the previous version of ScummVM as an option on a later build?

@johnes
Broadly speaking if you have a Pi3 the mame-2003 emulator is a good bet with the 0.78 romsets.
If you want to stick with the 0.375b then I'd use lr-imame4all - not least because it will allow all the Retroarch functionality as well as easier controller file config.

If you just want to enable a shader (including the one mentioned in the thread you list above), I would strongly recommend using the inbuilt configuration editor:
https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

OK, so this was helpful!

Turns out I had built by romset

Place your lr-Mame2010 ROMs in
/home/pi/RetroPie/roms/mame-libretro
Romset Used: .139

The directions said to put both lr-mame2003 and lr-mame2010 in the same mame-libretro folder. So It seems I just need to figure out how to default the emulator to lr-mame2010

I have posted a solution/ workround about this topic in another thread.

https://retropie.org.uk/forum/topic/4361/20-pin-xin-mo-wiring-diagram-set-up/7

Hope it helps

@sirus505 said in Setting up multiple controllers issues:

Just thought I could make both controllers have the same privelages in terms of saving and exiting for games.

There's an option named all_users_control_menu, but it's so new that isn't available in a fresh 4.0.2 install. If you install/update retroarch from source you'll get it.
I commented about it here
https://retropie.org.uk/forum/post/24548

@suprjami Thanks, yes this was solved. Sorry for not updating.

@GtBFilms Thanks for the info. I had a look at the ROM libraries I have for the emulator on my Mac and they don't even total 1GB, so that will give me plenty of room for other 'stuff'.

I've borrowed a keyboard from work so I have that and the memory card in my possession: the RPi was delivered today but whilst at work, so it's at our local depot.

Looking forward to getting my hands on it and getting started now: I have the Retropie installer downloaded and Retropie itself, my ROMS are all in situ and ready to go: so now it's just a case of build, install/setup and hopefully I'll be good to go!

I like the idea of having it connected to WiFi, I'm not going to install a tonne of ROMS, just my old faves and a few never-played titles, so being able to transfer one or two wirelessly now and again would be really handy. Plus it is 2016, so really WiFi setup should be a given!

Thanks for your help: no doubt I'll have more questions thrown up after installation, but fingers crossed it all goes ok!