@mitu Ahhh on the keyboard to be PAIRED? No, I did not understand. Thanks, I'll try that.

edit: of course, it now works. I can't quite believe I didn't understand that part of the instructions haha

@MiroKostovBG said in Refresh emulation station games without restarting.:

@sleve_mcdichael And can you do that with a command through SSH ?

Maybe something like:

pkill emulationstatio && emulationstation

(Note the misspelled emulationstatio in the first one -- this is intentional.)

This tries to kill ES and then, only if that worked, restart it.

Also it would be interesting what would happen if a game is running, would that break the game

This I'm not sure but should be easy enough to test using the above.

I'm guessing this is a "No", then?

Thanks. I'll try that when I can save up some money.

Also some other details. When I try to connect it to other devices like my phone or laptop, it also turns off by it's own, and what's more is that Windows 11 says that its a "Driver Error" when reconnecting to the controller.
Also when reconnecting with Android, there is also a pin requirement of "0000".
(Maybe my controller is just the Issue)

Also, Is there a way to run:

Bluetoothctl

and try to re-pair and connect when retropie Starts, Restarts, or Boot up?
Because this might solve my Issue.

@HeineBorel Yes, the naming of the overlay is unfortunate. Note that your link is for the PIZero2W patch, for the CM4 is a separate repository, but it has the same issue (similar overlay name with an existing one, distributed by the raspberrypi-kernel package).

There are 2 workarounds for this

either rename the overlays/dpi24.dtbo file to something else and update the config.txt with the new name when updating RetroPie, skip the kernel and system packages and update only RetroPie's packages.

@Fingerprint
Downloading a new image worked! for now.
Everything seems to be working, i'll refer back to this forum if i need anymore help. Thanks.

@Addison said in Update Failed {SOLVED}:

I would need something to copy and paste to the command line for that.

Move the existing setup folder out of the way, then clone the latest setup version

cd mv RetroPie-Setup RetroPie-Setup.old git clone --depth=1 https://github.com/RetroPie/RetroPie-Setup.git

You can then follow the installation instructions for @ExarKunIv's extra repository.

@windg Yeah, sorry for my rudeness. I dropped the thing and I feel better now :)
I'm just a little bit annoyed that retropie is the only versatile tool there is to do as much as I want (which is configure everything) but that its soooooo unorganized (it reminds me of Blender ah ah, wonderfull tool too but too messy for my taste)

I stopped trying to configure retropie, I'm tired to have to search in the doc for every little thing because nothing make sense. Even the folder tree is a nightmare -_-.

Well sorry again, I won't polute this forum any longer. Cheers.

@mitu That fixed it, thank you.

@mitu Thanks for your help again !

Please delete this topic when you can and sorry for the spam here. It seems that I overlooked the beginning of the log for whatever reason. I have all information I need with the default verbose logging.

Sorry again.

@mitu Thank you very much, I have purchased a splitter and solved the issue for 20 bucks.

You can install RetroPie to a USB 3.0 stick + USB 3.0 cable. I believe it will work. I have boot RetroPie from a USB 2 stick with 80cm USB cable and it was working.

@SavedByZero said in lr-pcsx-rearmed roms go black after title:

: [ERROR] [Environ]: GET_VARIABLE: pcsx_rearmed_async_cd - Invalid value.

This is probably caused by a change in the option values, you may try to changed it to 'Sync'/'Synchronized' (?) from the core options to get rid of the error. You can also reset the core option by opening retroarch-core-options.cfg from \\retropie\configs\all (file share) and removing any line starting with pcsx.

@chubsta said in ZX Spectrum keyboard - Pi400 mapping:

Even just a printout which shows which keys on the Pi relate to which keys on the Spectrum would be a nice start as I currently struggling to marry up the keys on the Pi with what I would like to achieve on the 'Spectrum'.

Assuming you're using the fuse core, I don't think the mapping is that complicated. The core docs show the keyboard is sent as is, but I assume this applies to the core when game focus mode is enabled in RetroArch. Unfortunately, the PI400's keyboard doesn't include the 'Scroll Lock' key which is used by RetroArch to toggle 'game focus mode', so you'll have to rebind it to another key.

Alternatively, you can give Zesarux a try and see how it fits with the Pi400.