@mitu I opened a couple and they seem ok. I will check the space left on the card. I don’t think that’s it though. It’s a 64 gb card and I formatted it before using and the only thing on it is RetroPie and the ROMs. Maybe I’ll start with a fresh new SD and new install and see if that solves it. Thank you.

I help myself ....
If you install pixeldesktop and pikiss and vulkan driver on retropie (now I had upgraded to retropie 4.8.2 )you can simply integrate lr-ppsspp vulkan driver support installed by pikiss simply editing es_systems.cfg and add a new system called (for example) ppsspp vulkan and edit the command line to execute with xinit lr-ppsspp (from the new directory created by pikiss)...
So retroarch in emulationstation remain the same (without vulkan support) but when you execute from emulationstation the new emulator lr-ppsspp vulkan driver supported is correctly launched and executed ....
You don't need to install retroarch from pikiss because retropie won't see the new retroarch...
Yes this is a (great) trick ...but works on
Duckstation and lr-ppssspp installer by pikiss (with vulkan drivers) and launched from emulationstation with desktop initialization thank to xinit command before the launch script of every emulators...
You can watch my solution

@mitu Heya! As an update, I got it working! Worked with a friend of mine who is a Linux expert and he walked me through it step by step, which did include the steps that you had pointed out. Thanks so much for your help!

@Retro-Arcade-Fan The shops listed on the pi website are approved resellers and are reliable. I would then compare them to see which ones charge less shipping.

Hello Thank you for the information.
It was useful for me as well.

Please allow me to add:

How to find out the Vendor ID and Product ID
It is briefly displayed along the info message on the bottom left hand side of the screen:
Tetris Opening Screen showing Error message and the values for the controller presenting the issue

With lsusb we can see in Hexa the values
Bus 001 Device 014: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller (model 1914)
Changing the controller does not change the ID.
However, changing the controller for a generic controller changes the ID:
Bus 001 Device 016: ID 045e:028e Microsoft Corp. Xbox360 Controller
Hence causing this to happen AGAIN, which is annoying.
We have to manually edit the config file again.

One thing that bothered me is that in all know previous versions of Retropie this was not an issue and now it's presenting one new, more issue than the previous version.
I've used Retropie for years now and I have never had this issue.
The only "new things" I have are

Operating System [Ubuntu 22.04 LTS freshly installed]; THIS Specific controller (Tested and proven to be working in all other games, also the old controller presented the same issue); USB Cable (Tested and proven to be working on other games, and able to "quickly charge" a Phone and perform fast data transfers)

Please let me ask:

Is there any way I can make it Automatic when I change controller to change the configuration.
-- Bear In mind I did the controller configuration at the start of Retropie every time I change the controller, and I tested quite a handful of times, I went as far as deleting , removing configuration files, and recompiling Retropie from the source 3 or 4 times. Would there be any test you'd like me to perform?
-- I may test it again on another Ubuntu version (or Ubuntu based distribution);
-- I don't discard the possibility to install it on a different Linux Distribution;

Thank you very Much.

@sleve_mcdichael I tried your suggestion for Dreamcast and Playstation and it worked perfectly. Thanks!

If you have SSH enabled, can you check whether retroarch is still running after you issue the exit command (and the black screen shows up) ?
Did you add anything in the onstart/onend scripts that may run before the emulator stops ?
What's your screen resolution and what type of display are you using ?

@cyberBoy90 I don't know. I happened upon it by chance and it looked cool, so I saved the Github page. The 'Readme.md' in my link does state "Emulationstation Theme (AVAILABLE IN RETROPIE THEME LIST !)", so I'd wager it probably is.

EDIT: I just checked and it is in there. There are also a couple more that mention stuff like 'pixel' or '240p' or what have you in their titles, so those might be worth checking out as well. There are a few minimal themes out there with no metadata or art, so maybe you'll find something to your liking.

@Sailing_Nut said in lr-mame2016 Questions:

I was lead to believe that the mame-libretro was a generic folder for all MAME variants. I'll look at it more closely.

It is. If you have roms in that folder and several libretro Mames installed, you can press A when launching a game to choose which of your Mames should launch that rom (or set ot as default for everything in the folder). That said, I don't know from memory if Mame2016 is a libretro core.

I wound up imaging a new memory card and just moving my roms, bios & collections over.

What it seems like the prob was, is that when you rotate it back to 0 in the sudo nano /boot/cmdline.txt the screen default resolution wasn't doing the trick. When you go to the settings of raspi-config for screen resolution and set that to default it shifts everything to the left but doesnt stretch it all from left to right. it basically stops at the center of my computer screen.

Anyway I would be nice to figure this out for others..

@Folly said in Super Pitfall PC-88- lr-quasi88 - Jump Button Mapping?:

@duglor

Strange key, but F7 is the key for jumping.
You can assign it in the retroarch-gui -> controls -> port 1 controls -> retro keyboard -> (assign, for example, "s" to "keyboard F7" -> go back 1 step and you should be able to save a game-specific remap file.
This is save in :
/opt/retropie/configs/pc88/QUASI88
and loaded next time you start the game again.

Worked like a charm. F7 eh? I swore i tried every key, perhaps in the speed in which i did it with , i didn't notice.lol. Thanks VERY VERY much!

@Retro-Arcade-Fan Maybe @Clyde can elaborate a bit further on it. AFAIK he had tested/compared some Models (and made his decision in favour of the mag-stik).

@mitu Alrighty and thanks for the help.

@BuZz said in I have to know - Imy upgrade procedure it's ok ? It's present some errors inside the LOG ?:

@DjDiabolik it's normal. They are built in packages (the code they install is part of RetroPie-Setup) and always update to ensure the latest runcommand, joy2key etc is installed. It's just how it works

OOOOKKK........ now i have a lot of knowledge about that :)
but in fact, the NOT presence of errors in the log it's peacefull.

How i already say... have to know :) And now i know :)

Thanks for info :)

@BuZz said in Install failure on ODROID-XU4:

@Sailing_Nut You will have to use the older ubuntu distro for now I think. There's no-one really maintaining the ODroid compatibility (apart from me when I get the time and connect mine up).

Also there are issues with the packaged drivers conflicting with Debian packages - this is the fault of the distro.

(Or alternatively use another emulation distro for your board)

I found the 20.04 image and got RetroPie installed. Still working to see if I can get a game to run.

@mitu I just saw this after posting my response. Nevertheless, thanks for your help!

@Recordspinner Didn't work, renamed files and I had to reinstall Retropie

thx @mitu , I think that explains it.

Retropie-Setup must have updated my retroarch.cfg when I update-all-packages, but I likely copied an "old reliable" one over from somewhere else and erased the new changes.

However I'd imagine that's still an unintended consequence when menu_disable_search_buttonis set to false?