@markyh444 yeah I got it for £80 from [removed]a few years ago, but looking now it doesn't seem to be running online anymore, anyway this'll be enough info for now, thanks dudes ! Happy New year again!

@dochartaigh said in "Core Override" for Shader NOT saving + changes Video settings on its own:

• Arcade/Mame/FBNeo, to change 3-4 player settings: For "in-game system menu options" (i.e. hold Start), those should automatically save a .fs file I'll be on the lookout for. ------ ones where I have to go into (Select+X) RetroArch Menu > Options to change the 3/4-player settings I'll try the "Create game-options file" which should safe a .opt file in /opt/retropie/configs/all/retroarch/config/fbneo)

like i said, you don't need to create a game-options file in lr-fbneo if these are dipswitch settings, as it will create unique entries for every game in the global /all/retroarch-core-options.cfg, so just change the setting and it will save automatically.

@lostless got it thanks. Just wanted to make sure because it didnt matter to me prior to doing the cabinet with the PS3 controllers and stick...Happy New Year!

@iandaemon @mitu
Booting into terminal fixed the problem and the games worked.
Thank you for the help 🙏

@mitu
Thanks for the straight answer. This works !! It looks so much better. I'm not sure why so many people like their themes gamelists all in uppercase letters ?

@postmanpat247 what is the bin file from?
PSX game???

@mitu thanks for the codeblocks sugerence i never ear about it.
In raspberry 3 retroflag cases if you use default script if you push power button it shutdown the pi and reset button reboot it.
With this code the power button, shutdown the pi saving changes and the reset button restart only emulationstation if you are in main menu, or exit game if you are in a game.

I checked pins and are the same but i dont know why in pi4 you push the button and the pi do nothing 😟

Several other users are reporting the same issue on the github for xpadneo:
https://github.com/atar-axis/xpadneo/issues/259

I paired the controller in windows and copied the link key to my raspberry pi as one of the users on github mentioned. Now the pairing works and I can use the controller. Now the Xbox-Button doesn't work as hotkey for both controllers anymore. But this might be an issue because of updating the whole system.

For getting the keys I followed these instructions:
https://bbs.archlinux.org/viewtopic.php?pid=1678405#p1678405

Problem solved! :)

@silvergamer said in Retropie/Odroid xu4 controllers configuration:

But yes, the odroid xu4 came installed with retropie and emulationstation.

We don't support systems sold with RetroPie/EmulationStation & roms. You can install RetroPie on Odroid XU4 as indicated here, this will get you the most recent version of RetroPie.

Can you post a verbose log from running the emulator (on pastebin.com) ?

@androidonpi The errors appears because you're running RetroPie from the desktop environment. As @dankcushions mentioned, this is not a supported configuration. On the Pi4, drastic will run by starting an X server first (as a few other ports already do), if you're already running in a desktop environment, that won't work.

@clyde it was already moved to a new thread

@moonston333 said in How to shrink a retropie image?:

@mitu yep true

but im asking ow do i make an image from all my files as ive got all the files extract how do image them back up

Hello @moonston333 I'm digging up this thread to ask if there is any further info on how to do that as I am facing the exact same issue.

@dankcushions This worked! Thank you so much.

Please add a better title for your post and some details about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

For what it's worth, I was able to fix the issue. Pretty basic fix: uninstalled the lr-rpboom package from the retroarch config menu, restarted the system and then reinstalled it. Poof! Everything works fine now. Not sure how or why, but I'll take it. B-)

David

Hey it WORKED!

~/.config/openbox/autostart

gnome-terminal --full-screen --hide-menubar -- bash /home/pi/autostart.sh

and
~/autostart.sh (chmod +x)

#!/usr/bin/env bash kodi-standalone sleep 2 emulationstation

So on boot, Kodi launches. On first Kodi exit, the script will launch ES. From then on, ES does what it does when launching Kodi and returning to itself on exit.

Thanks for your help @mitu!