Sorry, I didn´t read that mb.

But I will try to get it running with the officcial retropie image!

Thanks for replying anyway :)

@rogeriol Please open a new topic and add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, don't bump old topics.

@mitu By saying that I use Archlinux, it was to say that I understand how it works. In the end I found the "xpad driver" bug. I could already see myself doing a new installation.

The only thing that doesn't work for me is when I run .sh to run retroarch, generate favorites ... from ssh yes. But it is a lesser evil that will have a solution.

My next system with retropie will already be a minipc with ryzen. That although I have all the consoles, I love to emulate.

Turning off "parse gamelists only" setting did the trick. NES loaded and I was able to scrape again and have a new gamelist.xml. Thanks for pointing me in the right direction!

Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

If you run the RetroPie-Setup script from the terminal - see https://retropie.org.uk/docs/Updating-RetroPie/ - can you see any error messages ?

@TheRog third party images are not supported here (as outlined in this post), particularly those sold with games already installed. You'll have to contact the seller for support or you can create your own image as outlined here: https://retropie.org.uk/docs/First-Installation/.

I just tested with 1944.
Mame2010 saves the hiscore.
Mame2016 doesn't.
Unfortunately mame2010 only recognizes 1 joystick.
So it must be due to the mame2016 configuration (?).

Hi Mitu, Thanks for confirming that. I'll move the effected games to use a different Emulator. Cheers Simon

We don't support 3rd party images, especially ones loaded with ROMS. Ask the author(s) for support or start with the image from retropie.org.uk/download.

@mitu Again thank you so much! I really appreciate your help.

I had the same issue on my PC with that stick. There's a TINY little note in the instructions that I found:

"DINPUT Mode: press and hold 'Start' and 'Y/triangle' for 3-5 seconds to switch to DINPUT mode."
(with the switch down in DIN/PS3/SNK position)

That might help.

Could it also be 4 way vs 8 way controller? I read 8 way controllers on these games can have glitches when transitioning....it could manifest as control delays. I happen to have a 4 way plus an 8 way setup so I always use 4 way for the old games.

@steve8091 said in Setting up Asteroids Control Panel with USB Controller:

I want to be able to fine tune vector settings, which the default-installed MAME doesn't allow me to do.

But mame2003-plus does. Just FYI.

Thanks for sharing your solution, have fun with RetroPie.

@mitu

Pi Model or other hardware: RPi 4 B+
Power Supply used: (If using a Pi)
RetroPie Version Used 4.6.6 version
USB Devices connected: none
Controller used: ps4 replica

sorry I'm late with this. Could this bluetooth connection problem be connected to the recent hack?

Main Menu => UI Settings => set to off the Quick System Select.

Check this RaspberryPi forum post for issues when using the Pi4 with USB3 SSD disk - https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931.

Sadly, it didn't work

If you use a Euro (PAL) rom on a US (NTSC) machine, the game will run fast.
If you use a US (NTSC) rom on a Euro (PAL) machine, it will run slow.

So, if you are in the US running RetroPie on a US TV, you should not use a European rom. You can switch the Pi into PAL mode (if you have a TV that can tolerate it) and it will run at normal speed, but I wouldn't recommend it if you can just get the US version instead.

hdmi_safe will set the resolution to 640x480, if your monitor supports a higher resolution, you can set it by using hdmi_group=2 and hdmi_mode set to one of the values detailed in https://www.raspberrypi.org/documentation/configuration/config-txt/video.md. You'll probably have to add hdmi_ignore_edid=0xa5000080, my guess is that your monitor supplies a wrong EDID and the Pi tries to set the video resolution to an unsupported value.

This issue is now fixed as of 8-24-2020. Update from source if you experience this issue.