@ogteeg If your controller is detected, then you're not experiencing the same issue as in this topic.
My advice is to make sure you're fully upgraded (OS/Packages and RetroPie), install the xpadneo driver from RetroPie-Setup (see here on how to install packages in RetroPie) driver section and then re-try the pairing. Make sure you remove the controller from the list of registered devices before attempting to re-pair.
If that doesn't work, then open a separate topic and provide more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

RetroPie uses the Raspberry Pi OS Lite image - if that will support GPT for the root drive (boot + root), then RetroPie will have no issues with it.

Since the current RPI OS images are using MBR, you'd have to re-partition your disc and copy over the files to the new partitions if you want to use GPT.

You can try with a different hdmi_group/hdmi_mode until you find one that works (240p modes maybe ?).

@weirdh said in Two PGM games that stopped working on Mame2003-plus:

@arcadez2003 That's so weird (on my part, for the record), as the runcommand still was set for 2003-plus, so I just assumed it was always that, as I hadn't tinkered with it to my recollection. Does the ARM7 thing mean 2003-plus doesn't run any PGM game?

@barbudreadmon Yeah, I must have had something set wrong, or maybe a funky bios indeed, because after some maintenance it launches fine. Thanks for looking into dw2001.

These are the pgm games that will work in MAME2003+
https://github.com/libretro/mame2003-plus-libretro/blob/master/src/drivers/pgm.c

@tekn0 it currently supports ES 3.1 if that's what you're asking?

@muldjord said in Skyscraper: determining search name for game entry?:

It does not work with screenscraper as it is checksum and "exact filename" based, which is probably why it works with Spears of Destiny.sh since that is probably in their database.

Ah yeah, that's the one I was using. I'll work something else out then, thanks!

EmulationStation does not know (nor care) how the controller is connected, so there's nothing to configure there.

You can however pause the RA software during gameplay and resume it afterwards using the onstart/onend scripts for runcommand - see here.

@fretman yeah anything will do just to get the bluetooth ones sorted. These are all things you'll learn as progress as a Raspberry Pier

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Did you disable BT in the bootloader configuration file (config.txt) ? What 'lines of code' (commands) are you executing ?

@mitu My apologies, I'm sorry. That wasn't I'm intent. Thank you.

@windg Thanks for this, everything works again. It's strange that these latest ppsspp updates broke a lot of games. Games that used to work without issues for me like peacewalker, manhunt, ultimate alliance 2, 3rd birthday, tony hawk, and burnout had become unplayable.

@momo said in ES main menu retropie:

How can I remove this ES menu. and that I do not have to put the kids mode. ty

If you don't want to use the Kid UI mode, you can remove the start key mapping for your controller(s) in the es_input.cfg file from /opt/retropie/configs/all/emulationstation. There's no other configuration that will disable the menu.

@mitu I read through that thread and I can't seem to figure out if they agreed that it was a core problem or a retroarch problem. In either case it seems that the problem was never addressed.

I thought that save states would be a good workaround but that doesn't solve the problem of having to disk swap between game areas. not to mention, the save states are named after the disks rather than the m3u file so any save after the first one made must be renamed in order to be used.

is there a way to force the core into naming the save state a certain way?

edit: I'm an idiot. loading creates new disk drives to the index. you just need to pick the proper index slot, hit insert and that's that. arggagahha

Thanks for the tip.
Could you explain what do you mean exactly by : "using the RGUI I assigned the enable Turbo function to the same button I want to apply the Turbo function"?
I cannot find how to do this in RetroArch.

So far I created the cfg file for the game :
input_player1_turbo_btn = 1
input_player2_turbo_btn = 1

And I put this code retroarch.cfg :
input_turbo_period = 6
input_turbo_duty_cycle = 3

@mitu im not spamming Mr duckstations refer to this post in one reply, now im back to give the anser for Sineater224 but ok, no more help i will delete all my spamming. Well i can delete, delete for me please

Deleted beacause other global moderator consider spamming the act of help!

@dankcushions i dont use bluetooth so never have that problem, the other one never happen im affortunate since i have the pi 4 never an issue. I understood the support but the answer need to be you can but is not recommended and only for pi4b model. The instructions i followed are that in docs, but never make the change in the memory, because i use like a pc the pi os. But all the steps are what are in the docs:

sudo apt update && sudo apt upgrade -y reboot sudo update-locale LANGUAGE="en_GB.UTF-8" LC_ALL="en_GB.UTF-8" reboot sudo apt install git lsb-release -y -》 This step isnt neccesary in Buster an Pi OS git clone --depth=1 https://github.com/RetroPie/RetroPie-Setup.git cd RetroPie-Setup sudo ./retropie_setup.sh **OK** then choose **Basic Install,** **OK**, Yes

And update the retropie script every week.

Thank you. Now it's working!!!

I add this rule to

/etc/udev/rules.d/99-input.rules

SUBSYSTEM=="input", ATTRS{name}=="button*", MODE="0660", ENV{ID_INPUT_KEY}="1", ENV{ID_INPUT_KEYBOARD}="1"

And now have GPIO key ID_INPUT_KEYBOARD parameter too.

pi@retropie:~ $ udevadm info --query all /dev/input/event1 P: /devices/platform/button@1a/input/input1/event1 N: input/event1 L: 0 S: input/by-path/platform-button@1a-event E: DEVPATH=/devices/platform/button@1a/input/input1/event1 E: DEVNAME=/dev/input/event1 E: MAJOR=13 E: MINOR=65 E: SUBSYSTEM=input E: USEC_INITIALIZED=28281822 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=platform-button@1a E: ID_PATH_TAG=platform-button_1a E: LIBINPUT_DEVICE_GROUP=19/1/1:gpio-keys E: ID_INPUT_KEYBOARD=1 E: DEVLINKS=/dev/input/by-path/platform-button@1a-event E: TAGS=:power-switch:

Bidding hotkey to GPIO key is now working.

Scanlines can be enabled by setting default_line_mode=2