@mitu Thank you!

It's possible I'm confused by the implementation vs. the Raspberry Pi version...EmulationStation uses X11 on x86? I assumed no, and that was my whole motivation for not doing so (plus the obvious memory and time burn from launching an X display you aren't going to use anyway). If that's not the case, it sounds like xrandr is absolutely the way to go (and the closest analog to what I'm doing today).

onstart will almost certainly be required, because my display lies and says it can't do PAL ;)

@mitu
tried that dtoverlay:

dtoverlay=max98357a,no-sdmode

because i don't have any pin attached to sd pin, but i have the same behavior: no audio, only pops and noise

@mike855 thanks for confirming. Could you pls add [solved] to this topic (1st post in the subject line).

For others stumbling across this and won't/can't update to ES-development: You may also set the option Use full page with LR/LB to off in the Main Menu -> UI Options, when off this effect described initially should not occour.

@raspberry79

Open EmulationStation menu then Sound Settings > Navigation Sounds .

@sleve_mcdichael I did it correctly(at least as it says in documentation), with the "retropie" folder and the USB in FAT32

@mitu thank you so much!!!!!

@stoogesfan87 asking for roms is against rules

@Leanne Thank you. It worked for me too.

@mitu Is there an exact reason for the coredump caused by this renderTextCache? Wsl2 is based on a virtual machine, it should be possible to adjust or fix the code to make retropie run normally in wsl2?

Try installing the hid-nintendo kernel module, should have better support for Nintendo related gamepads than the default kernel module included in RetroPie.

Driver page - https://github.com/nicman23/dkms-hid-nintendo

@sntpl said in Blank screen after game exit:

Is there any logging that I can enable to see what's happening at game exit?

Should be in the same place as regular logging (/dev/shm/runcommand.log).

https://retropie.org.uk/docs/

@KM_64

I tried the retropie extras script and could never get it to work either so I used the flatpak version of citra. It’s been a while but I basically made a new system in retropie and changed my theme for the 3DS. My notes may be a little vague but here you go.

Adding new Emu
/etc/emulationstation/es_systems.cfg move to /opt/retropie/configs/all/emulationstation
Change that file to add systems
In /opt/retropie/configs/ create new system folders and add runcommand script. Basically the start command followed by %ROM%

Here’s an example of my Xbox emu (don’t have access to my computer now to get the 3DS but should be close)

Config Files to create
Opt/retropie/configs/xbox emulator.cfg
xbox = "flatpak run app.xemu.xemu -dvd_path %ROM%"
default = "xemu"

Opt/retropie/configs/all/emulationstation es_systems.cfg
<system>
<name>xbox</name>
<fullname>XBOX</fullname>
<path>/home/pi/RetroPie/roms/xbox</path>
<extension>.iso .sh</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_xbox %ROM%</command>
<platform>xbox</platform>
<theme>xbox</theme>
</system>

Also if you wanted to use an iPad as the bottom screen this is what I found to get it sort of working. Touch screen is ok but not perfect

iPad as second monitor Citra
Dual monitors using wayland and rdp on iPad logged in through ip address. Separate monitors in citra then move and resize windows.
This is copied from a website:

First, open a Terminal window and run: gsettings set org.gnome.desktop.remote-desktop.rdp screen-share-mode extend. This step is needed to enable extendable virtual monitors over RDP. This feature is, at present, a hidden one because this stuff isn’t polished enough for the masses to make use of yet — so be aware!
Next, open the Settings app, navigate to the Sharing panel, and turn on Sharing, and turn on (once it appears) the ‘Remote Desktop’ option. You will want to set up a username and password too, to allow you to connect from a different device.

If nothing else maybe it’ll get you started in the right direction. But it is possible to have citra running through emulationstation on Ubuntu 22.04. And it’s really not that hard to do.

@sleve_mcdichael
Many thanks! that helped!

the whole problems started becasue i am too tidy and have my Roms organized in each console in a seperate "Roms" folder. Now this tihngs makes sense to me.

@kcoconnor76

Slowdowns = lack of performance, your device is too weak to run this at full speed
Latency = delay between pressing a button and its result being displayed on screen
Runahead or preemptive frames = lesser latency at the cost of higher requirements, meaning more slowdowns if your device was already too weak without those features

Runahead and preemptive frames aren't features to remove slowdowns.

Note that some slowdowns can be native to the games (because the real hardware was too weak to run them) and some emulators have the ability to get around this by overclocking the emulated hardware, yet again at the cost of higher requirements.

Your pi4 is simply too weak to run n64, and the only way around this is most likely to use a better device.

@Zentrifuge

Found solution for everything - Batocera - Works like a charm out of the box - Even with my N30 Pro + Bluetooth from internal device.

Thank you

No. No, no, no...just...no.

I don't know if there is a language barrier here or if what else is going on, but you are doing this so, so very, very wrong that it is hard to even know where to start correcting you.

I'm not even convinced you have any console roms at all. The one thing you actually posted, was a disc-image for a Windows game.

See previous answers here(1).

...and here(2).

...and here(3).

RPi4 and Pi 400 are the newer systems and the are faster than RPi3B. You can find a comparison graph with all models here : https://socialcompare.com/en/comparison/raspberrypi-models-comparison