@mitu that's what I am doing. I have reverted back to Carbon through this method but it doesn't fix the crashes at boot

@mitu I wasn't able to get the debugging to work, I don't think I know how to do that correctly. Ultimately I installed and configured this and it seems to be working.
https://github.com/eberhab/bluetooth-repair

@DTEAM Thanks for letting me know, I will have to look into that. It's great that Smash 4 is working for you on the Pi, I am honestly surprised to hear that it is.

I dumped my cart and so I am not sure what version I was using, I will look into the one that you are suggesting. That said, I don't think it was a bad dump because the game played fine on Vulkan except for the usual Citra Vulkan visual artifacts. That said, on GLES with my build, most of the Smash stages were completely unplayable for multiple reasons. First is because of various colored boxes obstructing the screen on battles stages and even the menus (I assume that these are problematic textures for GLES such as incomplete mipmaps but I am not sure). Also Little Mac was neon green and looked like the Hulk for some reason. Finally, the game ran at ~30% on my aggressively OC'ed Pi4 and I recall that disabling right eye did very little to help (I am surprised to hear that it is 100% on the Pi5).

I am still running MESA 24.2.9 (the current default for sudo apt install mesa-vulkan-drivers), and so that could definitely be a possible reason for our difference in experiences. I do want to eventually upgrade to 25.1.0 to get the dual source blending functionality (especially for dolphin) but I decided to just wait for mesa-vulkan-drivers to catch up. I may need to fast-track that though if these newer mesa drivers are truly delivering this kind of enhanced Borked3DS gles performance.

@ltspicer If you're referring to the flags summary that @Lolonois mentioned, x86 covers both 32 and 64 bit architectures. There's really no reason to choose 32bit over 64bit when a PC is involved.

I updated the script and database to 280.
There is no progettosnaps data in the new database and if new all_in1 drivers are found then they need to be added later.

Password protected binaries for mame 280 have been added too.
The password can be requested on : mamebinaries@gmail.com .

p.s.
Please, do not quote this message.

@DTEAM

For 280 my awk script detected fxmcr165a for classich.
Can you check what needs to be added for all_in1 ?

Here's is a realistic Arcade Bezel for the game 1944: The Loop Master using the Mega Bezel Reflective Shader for Retroarch.

pic.jpg

Quick question I'm hoping someone has an answer to.

After getting this far I'm so close to having this perfect I can taste it.

Below is a photo of my start up that I get, it seems almost random.

One of the guides I read about moving to a drive (the guide was for an SSD whit I am not using) said to add I think it was a wait=10 I'm the cmdline.txt (I'd have to look at my cmdline.txt to tell u exactly what it was).

Is that what is causing this odd boot up I keep getting?
If not what is or how can I fix it?

https://ibb.co/xtN52zF0

strange i can't edit previous post....

So... i rename the file to Lair.ogv. Emulationstation found it on daphne system:
b934ec2b-fdd5-4837-a444-a0a7d7681a62-immagine.png

This is runcommand windows:
3f7ef555-1838-42a2-bff4-88cddfddcf3e-immagine.png

Now try to set lr-dirksimple......and omg:
e023905f-574e-40f8-8675-3e8fe0d07e7c-immagine.png

It's work!!! Great..... case closed @mitu :)

++++ edit ++++
now i can only need to change it's name on metadata and add scraping image like other...lol :)

@mitu I think I got it figured out. I was using the wrong splashscreen.sh script. I took the contents of asplashscreen.sh from /opt/retropie/supplementary/splashscreen and created splash-omxplayer.sh in /home/pi/RetroPie and now it seems to work. Here's what I have in that updated script file:

#!/bin/sh ROOTDIR="/opt/retropie" DATADIR="/home/pi/RetroPie" REGEX_VIDEO="\.avi\|\.mov\|\.mp4\|\.mkv\|\.3gp\|\.mpg\|\.mp3\|\.wav\|\.m4a\|\.aac\|\.ogg\|\.flac" REGEX_IMAGE="\.bmp\|\.jpg\|\.jpeg\|\.gif\|\.png\|\.ppm\|\.tiff\|\.webp" # Load user settings . /opt/retropie/configs/all/splashscreen.cfg is_fkms() { if grep -q okay /proc/device-tree/soc/v3d@7ec00000/status 2> /dev/null || grep -q okay /proc/device-tree/soc/firmwarekms@7e600000/status 2> /dev/null ; then return 0 else return 1 fi } do_start () { local config="/etc/splashscreen.list" local line local re="$REGEX_VIDEO\|$REGEX_IMAGE" local omxiv="/opt/retropie/supplementary/omxiv/omxiv" case "$RANDOMIZE" in disabled) line="$(head -1 "$config")" ;; retropie) line="$(find "$ROOTDIR/supplementary/splashscreen" -type f | grep "$re" | shuf -n1)" ;; custom) line="$(find "$DATADIR/splashscreens" -type f | grep "$re" | shuf -n1)" ;; all) line="$(find "$ROOTDIR/supplementary/splashscreen" "$DATADIR/splashscreens" -type f | grep "$re" | shuf -n1)" ;; list) line="$(cat "$config" | shuf -n1)" ;; esac if $(echo "$line" | grep -q "$REGEX_VIDEO"); then # wait for dbus while ! pgrep "dbus" >/dev/null; do sleep 1 done omxplayer --no-osd -o both -b --layer 10001 "$line" elif $(echo "$line" | grep -q "$REGEX_IMAGE"); then if [ "$RANDOMIZE" = "disabled" ]; then local count=$(wc -l <"$config") else local count=1 fi [ $count -eq 0 ] && count=1 [ $count -gt 12 ] && count=12 # Default duration is 12 seconds, check if configured otherwise [ -z "$DURATION" ] && DURATION=12 local delay=$((DURATION/count)) if [ "$RANDOMIZE" = "disabled" ]; then "$omxiv" --once -t $delay -b --layer 10001 -f "$config" >/dev/null 2>&1 else "$omxiv" --once -t $delay -b --layer 10001 -r "$line" >/dev/null 2>&1 fi fi exit 0 } case "$1" in start|"") do_start & ;; restart|reload|force-reload) echo "Error: argument '$1' not supported" >&2 exit 3 ;; stop) # No-op ;; status) exit 0 ;; *) echo "Usage: asplashscreen [start|stop]" >&2 exit 3 ;; esac

Let me also ask this question: If I wire the coin button switches to the usb encoder, and hit the start button to bring up the Main Menu in Retropie and Configure Input...is it going to recognize the Gamepad I am currently using? Like, if I use Player 1 (Gamepad 1) is it going to let me re-map that specific Gamepad?

Thank you All! I figured out that my problem was with using CLR-MamePro.
Now I have mame2016 roms that work great and only use mame2000 with vector games.

So after doing this update, the splashscreen no longer appears when I load up the RetroPie. It just loads directly into the emulationstation loading screen.

Any ideas?

@Bravo88 according to the error message it is most likely something on your side. I do not encounter that error in my setup (Rpi5 with vanilla RaspiOS 12 Lite and vanilla RetroPie setup).

I assume you have mounted the working directory for image creation on a separate partition, which lacks execution for root. I would check the respective documentation on how to enable execution for root on the partition in question to remediate.

@retropieuser555 as far as i understand that changing the sound from hdmi0 to 1 did the trick (but for me it was too late i have already deleted all the packages i had)
right now I'm reinstalling everything (not sure if it solves the x4 speed or idk rom speed problem)
I'll keep this post updated as far as i go with this issue.
but thanks anyway ( yes it might be it i forgot that it installs an desktop environment) much appreciated!

Worth noting the above here for posterity and the DLP page that described the checkpoints in PAYG as discovered by @DirtBagXon .

https://www.dragons-lair-project.com/tech/enhancements/dle2xsequence.asp

Pay As You Go interruption point When the PAYG option for 2 interruptions per game is enabled, this is the 1st point at which coin(s) are required to continue play.

@Brote For anyone that ever has this issue (For the very few people that are as dumb as me.) I was taking a closer look and realized that I was plugging my usb in upside down. So yeah... make sure you don't do that.

@Rockman98 said in Installing different desktop environment rather than the default one over retropie os?:

Hello,

Is it possible to install a different desktop, specifically Trinity Desktop Environment adn boot over emulation station interface?

Which platform ? On a Raspbery Pi, RetroPie doesn't use a desktop at all.

How can i install it top of retropie os?

RetroPie is not an OS, but runs on top of a Linux distribution - on a Raspberry Pi it's running over RaspiOS, on other platforms is runs over Debian/Ubuntu.

Look up how the desktop environment you want to install is installed on Debian/Ubuntu if you want to install it on your RetroPie - compatible - system.

Would there be any performance issues?

Depends on the system, if it's a Pi3 or less it's probably going to affect the performance, for newer Pi models it's less noticeable and on a PC the difference is basically insignificant.

Can i make it launch like how i start raspberry pi's default desktop environment over retropie os?

Probably, but depends on the platform you're using (PC / Raspberry Pi / etc.).

@BigGold said in RetroPie recommended x86-x64 system? Also, questions about Rpi5 vs 4:

I don't really play anything beyond a PS1, so I was wondering if it would be possible to run it on a core2duo system with integrated graphics or possibly a AMD HD 5000 series card for the ability to use a tv via component. would 2gb suffice or should i be looking at a more powerful setup?

A Core2 Duo system is waay too old to be a recommended system. If you're looking to 'downgrade', then a Pi4 would be perfectly fine.

Hi

I sucessfully to created a service for activate the Reset Button with this documentation : https://wiki.52pi.com/index.php?title=C-0063#How_to_Program_the_Reset_Button_on_Retro_Flag_Dream_Case

I notice some error, because I installed :
sudo apt install python3-rpi-lgpio
And not :
sudo apt-get install python3-rpi.gpio
The script doesn't work.

I replaced sp.getoutput("sudo init 0") with sp.getoutput("sudo reboot") in the reset_button.py file.
And I removed the user / group from the file reset_button.service

Before activate the service I used :
sudo chmod +x /path/to/your/reset_button.py

For finish :
sudo systemctl daemon-reload
sudo systemctl enable reset_button.service
sudo systemctl start reset_button.service
sudo systemctl status reset_button.service

And the reset button will work !