@mitu I need you to unlock that recent post of mine about the splashscreen. I reposted on that topic because nobody was able to help me with my previous post and the one that you locked had more detail and pictures that might be able to be diagnosed by someone who actually knows how to fix my issue.

@abj said in Import ROMs into Mame:

@jak75

This message is the runcommand launch menu, it's not an error message. It's appearing every time you start a game. More info here : https://retropie.org.uk/docs/Runcommand/.

Ok regarding the message I saw, but I can't get the audio, I reset the audio to default settings but nothing to do, it works well with other operating systems, any advice?

@god-of-pie

Installing Retropie on a Raspberry Pi 5 is possible, but I have only been able to do so by installing it on top of Raspberry Pi OS. I have also had success with it running on top of Ubuntu as well but I don't think it works quite as well.

To do this go to

https://retropie.org.uk/docs/Manual-Installation/

and scroll down to the section that says "Install RetroPie" and follow the prompts. You'll be up and running in just under 40 minutes or so.

Once installation is complete just open a terminal and type "emulationstation" and it will boot you right in. I hope this helps

@mykee said in Running electron apps inside RetroPie / ES:

Hey all!
I'm trying to run Tetr.io inside of the retropie as an electron app, but some errors about display are getting sent to me on the shell. I plan on running emulation station and the game inside it if possible but I don't have read the docs about the console lists fully (yet). My first step is to be able to run the game natively but it's displaying an error about displays, which is down below stated.

Pi Model or other hardware: B Model 4
Power Supply used: Samsung 5V
RetroPie Version Used : 4.8
Built From: Pre made SD Image on RetroPie website.
USB Devices connected: Keyboard and Dualshock 4 Controller
Controller used: PS4
Error messages received:

[916:0417/001957.934669:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY [916:0417/001957.934831:ERROR:env.cc(257)] The platform failed to initialize. Exiting.

File: pi@retropie:~/RetroPie/teto-armv7l

Seems like i already had questioned it about it on here and since there was no arm build at the time, i have gotten one now, so running it really is the issue to me right now.

@mitu thanks for the info I didn't know there was one for windows similar to this will check it out

@abj OK great, thanks for the reply! That was what I suspected but helpful to have confirmation.

The triggers_to_buttons is no longer applied automatically to the xpad driver , since it breaks the Xbox controllers mappings in SDL and subsequently any applications that use the SDL's GameController subsystem. Existing installs are not affected, but new installations will not get this configuration automatically, though you can manually add it and will stay configured.

EDIT: how did you try to map the Z/C buttons - to which gamepad inputs ?

@Lolonois got to love linux.
so i did a clean load to start all my comparing and what not.
and now it works just fine.
even though on friday even with a fresh and updated RP it would not start a game

as you said. you need to update the RP script and update everything.

i did a fresh load and with out updating it didn't work ( as you said it wouldn't) then i updated everything to the same commit that you did and it worked just fine after that. No error

so i did a new card and fresh image
this time i just updated retroarch, that didn't work. (was not expecting it too)
did a full update and like before it now works

So i agree, it is working as it is designed, why it didnt work before for me. i will never know

@Retrodade sorry, as

@Lolonois said in Apple2e: AppleWin Libretro:

[INFO] RetroArch 1.8.5 (Git 8bcd74b)

As I mentioned already in another thread: With this outdated version you are on your own (v1.8.5 was added at 2020-04-17 to RetroPie).

Currently RetroPie is on retroarch v1.16.0, I tested lr-applewin with retroarch v1.12 onwards.

theres not much I and @Lolonois can do.

the only thing i can say if you want to get applewin to work. you will have to update your system.
as i said above, updating retroarch to the latest which it 1.16.0 will not make it work. you need to the main Retropuie system files also

There's no resolution related setting in EmulationStation - are you sure you haven't set-up the resolution in your desktop ?
Please post the EmulationStation log taken after starting EmulationStation with

emulationstation --debug

@abj ok

If you're using the standalone emulator and not the libretro core, then it's normal. The hotkey enable button/shortcuts are generally available only for libretro cores (emulators names lr-<something>).

No, use a PS1 emulator.

Yes, it's a typo on the documentation page - thanks for the heads up. I fixed it, the change should be published soon.

@ExarKunIv It did not work for my Xbox S wireless controller, but it did work for my Dualsense. Once that was connected, all I had to do was start the binding process by pressing enter on the keyboard while selecting the first binding and then going down the binds with my Dualsense. Thanks!

@mitu I have. On the Pi, when I plug into the second HDMI port I don't get any display at all. And I've tried all three HDMI ports on the back of the TV as well.

ok, it's got to be the Pi. I just found a backup from 3 years ago. Did the same thing. Audio played fine for the first few clicks, then went out. I'm going to contact them to see if they concur, but since everything software-wise seems correct, that's got to be it.

Check if the mapping corresponds with the one described in the docs - see the previous link I posted. If you wish to change the mapping, then you can do so by using the core input remaping menus in RetroArch.
You can also try using the standalone emulator to check whether the default mapping for it is better suited for your needs.