@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

@retropieuser555 Thanks so much!

@mitu I see... Thanks for the info. At least I can stop wasting time trying to change this.

@iandaemon yes it should be blank

@remocscott there isn't image

@mahoneyt944 Sorry, my explanation was not completely correct: It's the firmware that is updated, as far as I can see the PCB itself looks identical. But you can find out which firmware runs on your PCB, simply by pressing both mouse buttons simultaneously and keeping them pressed for 10 seconds. If this switches the mouse axis from horizontal to vertical, your PCB is running the latest firmware. Otherwise it still runs the old firmware.

Apparently there is no simple way to update the firmware yourself, they simply sent me a new PCB.

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

@cargorunner said in Playstation - Suddenly stopped working:

@mitu The file has 3 lines, I just listed the one line I changed. The full file from the prebuilt image is...

lr-pcsx-rearmed = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/pcsx_rearmed_libretro.so --config /opt/retropie/configs/psx/retroarch.cfg %ROM%"
default = "pcsx-rearmed"
pcsx-rearmed = "pushd /opt/retropie/emulators/pcsx-rearmed; ./pcsx -cdfile %ROM%; popd"

this isn't the file from Retropie's prebuilt image. it does not default to pcsx_rearmed (standalone), so not sure what happened here, but good you got it sorted!

This issue has been fixed with an RPI OS update for the Bluetooth packages, so the workaround is no longer necessary - an update of the packages/OS is enough.

You can update the packages as part of RetroPie's update menu or manually with

sudo apt update sudo apt upgrade

The bluez package version that fixes the issue - 5.50-1.2~deb10u2+rpt1.