@xxalphawolf420xx From the 2nd screenshot, I see that the WLAN Country hasn't been set. It shows as DFS-UNSET, while on a working system it should show:

root@pie4:/home/pi# iw reg get global country UK: DFS-ETSI (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A)

The other command screenshot looks like the command's been miss-typed (wlan instead of wlan0).
Check again your wpa_supplicant.conf and make sure it's correct - no extraneous characters, proper newlines, no funny quotes, un-balanced parantheses {/}. Post it here to take a look.

@G30FF I did not realize the wired version had that limitation, that's good to know

I watch this video and I done everything as shown, still same problem. I successfully connected Xbox controller but ES does NOT detect it. I still can't configure buttons and jstest is still same, nothing changes.

You should add a proper title for your topic - just saying Help in a Help and Support category is meaningless.
Take a look at https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=58151#p1485558 to diagnose boot problems. Look at the LED flashing patterns on your Pi and compare it to the diagnose info posted in that forum post to see where the boot stops.

May I suggest you unplug any wireless (game) controllers particularly using bluetooth. I had the same issue but the problem was resolved when I'd disconnect my XBOX One controller via bluetooth and used a wired keyboard,wired mouse and a wired controller/

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

Hello everyone, so all of the sudden I am getting —- in the control input slots in MAME2016 and MAME2003. These are also uneditable. I would really like to get some game controls configured, so any help would be extremely appreciated! Thank you

This is on Retroarch 1.8.5, and I did not see any error messages. I am just unable to change any of my controls suddenly. I also tried re-installing (assuming that I did something) from binary and it did not help. I did not update the system during this.

Here are my
Details:
Raspberry Pi 4B w/4GB ram, 64bit processor
Power Supply used: MODEL DCAR-RSP-3A5C, INPUT 100-240V AC, OUTPUT: 5.1V 3.5A
RetroPie version: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7l+
Built From: RetroPie-Setup version: 4.6.1 (4464b474)
USB Devices connected: SNES controller, USB keyboard
Controller used: SNES controller, USB keyboard

Please note: I did switch to a PS2 USB controller during the process of going through my arcade games & configuring the emulators. It did let me change the controls at first and I did not update anything so I cannot understand why I am suddenly getting three dashes in the input slots - - -

Also note: Mame2003 works up I cannot go up down left or right.

SOLVED, a MAME 2016.rmp file was generated in
configs/arcade/mame2016 and over wrote my controls. I deleted the .rmp file and now I have my controls working again.

It was.... the salmon mousse!

Actually, it was my USB controller adapter.

I have a Retro-bit Atari 2600 dual joystick adapter. It works fine for other emulators like 2600 and MAME, but if it is plugged in to any usb port while launching lr-atari800, the emulator crashes.

It is necessary to unplug the adapter, launch the game with the keyboard, then plug the adapter back in and wait for it to be recognized in game. I don't anticipate there is anything I can do on my end to fix this, but maybe this information may be helpful if users with other incompatible hardware experience the same crashes.

Cheers

@inolen Yeah I though it would "just work" when I plugged it up but it wasn't. If I had thought to go to Redream website to see the keyboard mapping, that would saved myself a lot of time. All other emulators just worked (minus Daphne). Once I saw that mapping, I figured it out. It should have just used the mapping from emulationstation but whatever, it works now.

@francis2019 said in Advance Mame sample sound not working:

when i go to the network folder in windows bios is not in caps

That's the file share name, not the folder name as seen by the Pi.

Did you have any ports package installed ? If you don't, that might be the reason the system doesn't appear (with your game).
Try installing one of the smaller ports - like lzdoom - this will create the folder and the necessary configuration to show up in EmulationStation.

@smilker

I mean you really don’t need a tutorial, I think your making it more difficult than it needs to be.

Plug player 1 one encoder up to port 0
The player 2 in Port 1

If the player 1 controller is working and you set it up right on initial boot, then all you need to do is hit either select or start (can’t remember which one) and go down to configure inputs.

It will say 2 controllers detected, hold a button on the player 2 controller and set that one up like you did the player 1 controller.

That’s really all there is to it.

@mitu

Hey thanks for your help, I actually have solved the problem via first installing raspbian then retropie following the video below after installing with NOObs and now I everything works as intended.

Still have no idea why the boot didn't work for me but at this point I am more interested in relaxing and playing some lovely 8bit games on my Picade. May be I can bump this later on when my curiosity kicks back in.

Have a great day.

That did the trick.....installing lr-flycast, the controls working perfectly. Thanks!

@Schonarchy Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@sexbeer It only works on lr-beetle-psxwhich only works on an overclocked pi4 and pc's right now. In the future, it might be fast enough to work on a pi3b+.

only 0 and 1 are registering in your config log file. If your happy using advanced mame just use that. I find stand alone emulators more pleasing to use as well :).

not all arcades use a separate joystick for player 2 they are turn based. What emulator are you using and what game? Need to debug ifs a joystick issue or not.

@Efriim said in PS3 Controller RP3+ issue:

sudo rpi-update

ok so I didnt have time to mess with this for a couple days but I started this morning by simply typing in sudo rpi-update and rebooting. bluetooth worked perfectly again on PS3 controller. Thanks for your help. If anyone else has this issue I would do this first and pardon the ignorance if this was obvious.