@callycoon said in Mame Roms quit working:

arcade console games

I'm not sure what you mean by that, could you give an example ?

@callycoon said in Mame Roms quit working:

Mame 2003

The purpose of those vintaged cores was to be snapshots of how the concerned emulator was back in that year, amongst other thing to guarantee the romsets don't change and to prevent the performance regressions coming from bugfixes. Well, i recently learnt that the situation might be more hazardous though, but i don't think retropie is auto-updating so i suppose your issue is elsewhere.

Thank you.

..
Should I just fill out the rest of the missing values (in a PR) so it has all of the mappings (and labels) for both modes, do you think?

Normally yes, but I think because of the vendor/product IDs collision it wouldn't work properly - see https://github.com/libretro/retroarch-joypad-autoconfig/pull/893. You can submit the profile with the vendor/product IDs commented, so it won't clash with the existing profile.

As far as I can tell from the (more) recent documentation available, the only configuration for the screen needs to be done in config.txt and any other configurations/installed packages are not necessary (any more).
I don't have experience with this and we don't get many configuration questions for this kind of displays, you may get better support if you ask directly int he Raspberry Pi forums.

@mitu said in RetroArch UI - Gamepad issue:

My advice would be to back-up your current retroarch.cfg and use the RetroPie default one (retroarch.cfg.rp-dist).

It works now. Thanks
The problem seems to be from the new retroarch.cfg file . With no retroarch.cfg file, it works well. When I reinstall retroarch, the new retroarch.cfg file create that problem. I don't know why? Probably, a new setting create that

NEW EDIT:
In the new retroarch.cfg I changed all_users_control_menu = "true" for "false"
and now everything is fine. That was the problem.! Don't know if other people got this issue, but on on my side, this solved the problem.

Thanks a lot for the support !

We don't support 3rd party images and yours looks like it was customized and changed from the default RetroPie image.
I see you have a number of services (like snapd or bt-device) which are not standard on RaspiOS and I see also an error related to CPU throttling - maybe the system boot is slow because the CPU's frequency is scaled down.
You can use systemd-analyze how long it takes each system service to start, it may help identify which one is responsible for the slowdown.

@mitu I agree with you.
I was experimenting recently on pi0 and checked the RetroFlag "patch" for their GPi Case and it has by default disabled#dtparam=audio=on applied to the config .txt which causes the exact error posted
If the # is removed and reboot the sound is back to normal.

They should update their scripts/info rather users get troubles and need to apply cmdline alsa or edit sudo nano /usr/share/alsa/alsa.confand change

defaults.ctl.card 0 defaults.pcm.card 0 to defaults.ctl.card 1 defaults.pcm.card 1

@memorylane said in Cannot compile lr-ppsspp (ffmpeg arc4random implicit declaration error):

@mitu Is it only a matter of updating the source version in the install script?

Seems like it.

Which version did you try?

Latest stable release is 14.4 AFAIR.

hello, good morning, I have no personal interest, I had read about it improving graphic performance, but I don't feel urgently, when the version with debian 11 is ready, I'll try it with pleasure, thanks to both of you for your answers

@boogyman062190 please add some more details about your system as outlined in https://retropie.org.uk/forum/topic/3/read-this-first

Can you post the relevant log file from ~/RetroPie-Setup/logs?

@sleve_mcdichael said in Some images missing in the docs:

Edit: I got the raw image url from the GitHub page, and when I follow that I get "error 503 backend is unhealthy":

Seems like an error on the Github side I haven't encountered this kind of errors so far, but Github has issues from time-to-time and I wouldn't be surprised they'd show up as missing images.

@mitu this was it. After digging in I did find the same problem and was able to just swap the <theme> tag and get it working

@rrrule32 "RetroPie" is a collection of shell scripts to assist with the download, installation, and configuration of various different emulator and front-end softwares on Linux computers running a Debian-based distribution.

Raspberry Pi is a single-board computer that runs Raspberry Pi OS, a Debian-based Linux distribution, and can output via HDMI to a television or computer monitor.

You can put RetroPie on a Raspberry Pi and connect it to your TV. You probably cannot put RetroPie on the TV itself, but really I don't know what they're doing with smart TV's these days so what do I know. If it runs a Debian-based Linux, it just might work.

You can force a certain resolution on the screen, though depending on your version of RetroPie that option may not be available through the Raspi Config menu (as it was recently removed).
What kind of TV is that (model) ? Can you try setting it to Game Mode so it's not doing any image pre-processing ? I think it's i the Picture settings of the TV, under Picture style (?).

@mitu It worked, in fact updating retroarch to version 1.15.0 fixed the issue.

@JeffwithaG no, I don't think anything like that is included with RetroPie.

Okay, so it seems as though what has happened is that changing the keyboard config in retroarch has basically broken the use of the onboard joystick and buttons that are connected to the Pimoroni hat that sits on top of the Pi4.

Again, this stuff is incredibly confusing... because inside of Retroarch when you are using the joystick and buttons it says that the device is "retropad" it says nothing about it being mapped to the keyboard.

Looking in Retroarch I can see now where all of my key mappings are busted and referencing the changes I made in the config file to remap KEYBOARD (not RETROPAD) config.

@sleve_mcdichael Thanks for your reply. I will look again in file manager. I am pretty sure the system rom folders were empty but will confirm and delete if they are in there.

(Side note to the forum: Sorry for not saying it sooner, but I’m running retropie on a Pi 3b plus and just reinstalled retropie. No change to the tab not working in-game since I boneheadedly unassigned it even with the freshy).