@mitu Thanks for reply mitu !
If it's abandonned by the creator, i'll not lost my time (and yours !) to try to install it !!!

@tzium

These are the soldering s you should check :
usb-solderings.jpg
See if there are no breakages in them.

If you only connect both your controller and keyboard, without other devices, do they work OK then ?

that worked. THANKS!
yes it was 49686 for product id but i had a typo for vendor id, that's 1133 instead if 1133.

Thank you very much!

@mitu yeah i think, because i configured it normally, but dosen't work after some reset,

I have transfer Blade Runner (GOG) from my pc to Retropie. After the installation of the game, a GOG folder created into the C:\ inside was the game folder that i transfer to scummvm RetroPie folder.

@Souciot said in Audio devices not found GPi case:

@G30FF in the readme of the patch it's written : "Why need to install display GPi Case patch for Retropie and Recalbox?" so I suppose it shouldn't mess with retropie ?

I only have experience with the GPi Case 2, so my mistake. The GPi Case 2 patch includes one for Recalbox 7, one for Recalbox 8, one for Batocera, and one for RetroPie. I downloaded the GPi Case 1 patch, and I see why the recalbox string is there, because it's included in the patched config.txt. Sorry, I won't be much help here.

Please take note that you can use jpg format in addition to png.

At least I've been using a mixture of png and jpg images :)

Set the display to 800x600, but no dice, it seems like it possibly won't display at that res. Everything still says 640x480 (fbset, tvservice)

So i've turned off integer scale, and that did the trick. It's not exactly perfect, the pixels are a little fuzzy. But it's acceptable for now until I figure out more stuff I can try with the Pi config.txt stuff.

Thanks for the help!!

@10vorne No. What you can do is disable the launch menu temporarily while you test Dosbox games or launch the games directly (see the runcommand.log file for the actual command used to launch a game).

I did the reinstall. Convincing myself to actually do it was harder than the reinstall itself.

Now I got a completely functional and updated 64bit system. PSX roms run perfect.

Thanks for everything, I hope this can be helpful for someone.
Cheers

@duglor I think you could do quick menu > controls > port 2 controls > mapped port: 1 and then save it as a game or core remap file. Do this for each game or core that requires it.

@Darkwell did not work for me still no sound

@mitu thanks foru tour answer, in fact i compiled manually attractmode when 'attractmode' was not available in retropie downloads script for raspberry pi 4 but anyway it's working like a charm.
So i guess if is there a way

@mitu Thank you for your response and help.

Setting the Retroarch system settings for video aspect ratio within the EmulationStation Retropie configuration menu, worked perfectly and saves the settings for all cores.

Now when I open a game, in any core, I am able to "Save Core Preset" as well as "Save Game Preset" for an individual game within a core that already has a shader saved for that core. Brilliant!

Everything seems to be working now.

Just to better explain what I am doing with the system. I have a cocktail table that is used for 2-player alternating and simultaneous games.

I use the Arcade folder and lr-mame2003 core for Cocktail specific MAME ROMs that have the Cocktail option in the ROM “Dip Switches” for 2-player alternating games. Primary player has a turn and then the screen flips and the secondary player has a turn.

I then use the FBA folder and lr-fbneo for other MAME ROMs for 2-player simultaneous game play using a “Split Screen” Shader. The split screen shader allows both players to have their own screen (within the single monitor) for simultaneous play. I have three different “Split Screen” Shader files that I have to use because not all ROMs setup the same. I save one “Split Screen” Shader to the core that’s takes care of the bulk of the games and then I have to use one of the other two shaders to save for individual games that seem to setup differently than the bulk of them.

I save a custom shader to the core as well as individual games within the same core…

Cheers

@skizzles I am using buster in Retropie. I just bought an Xbox series S/X controller and to my surprise, there is no video explaining how to connect this with Retropie. All videos mention either 360 or Xbox one controllers which although similar have differences in connection. I followed the steps above and was able to connect this to pie but the connection was not persistent. Even xpadneo drivers didn't make the connection persist. And I made the following tweaks after experimenting and watching other videos. I have to share them in a noob-proof manner here so that I don't forget the steps. I request mods not delete this post as it was a headache to make it work.

Steps (Slightly modified to make them persistent): make sure to connect a keyboard as well for settings.

Update firmware on the Xbox series s controller through windows computer. Now get inside Retropie Setup>Manage packages>Drivers>Removed Xpad drivers (although it might not be necessary). Also, install Xpadneo drivers if not already installed. then Reboot I pressed F4 in Retropie and opened the command prompt terminal. Now open "main.conf" file as mentioned in the above post located inside "/etc/bluetooth/main.conf" and search for Privacy = off. Change that to: Privacy = device

make sure to remove "#" before Privacy=device to enable the command if it is there. Press Ctrl+X then "Y" and ENTER key to save the file.
5. On the command prompt type "sudo nano /opt/retropie/configs/all/autostart.sh"
6. Enter (these 2 lines must be entered above "emulationstation #auto" to make them persistent. When 'ertm' is disabled the Bluetooth needs to be refreshed to connect the Xbox series s controller on reboot. So, both lines are necessary.

sudo bash -c 'echo 1 > /sys/module/bluetooth/parameters/disable_ertm' sudo systemctl restart bluetooth emulationstation #auto

Press Ctrl+X then "Y" and ENTER key to save the file.
Type "sudo reboot" on the command prompt to restart. Again press F4 in the emulation station to enter the terminal.
7. Make sure that you xbox controller bluetooth is in connection mode. Press the button in front of the controller so that the xbox light will blink fast for pairing. Now Enter in terminal:

sudo bash -c 'echo 1 > /sys/module/bluetooth/parameters/disable_ertm' sudo systemctl restart bluetooth sudo bluetoothctl scan on (Note the mac address of your controller that is listed after this command. It's unique for every controller. For eg mine was "44:16:22:DB:C9:8E". Type this command again if your device is not shown initially) sudo bluetoothctl pair 44:16:22:DB:C9:8E (Use your own mac address discovered above) sudo bluetoothctl connect 44:16:22:DB:C9:8E sudo bluetoothctl trust 44:16:22:DB:C9:8E

If all these steps are successful then you can also type " bluetoothctl paired-devices" command to see whether your controller is paired successfully or not. Your device mac address must be shown after this command is entered.
then sudo reboot and restart your pi.
Press the Xbox icon(Light must blink) so that Pi4 sees it as it is starting up. At this point, you might also need to re-enter your controller keys according to your needs. And it should all work from here.
Note: Bluetooth GUI under settings didn't work for connecting to the Xbox Series s/X controller for me. I don't know why? Only connecting through the terminal worked. Deviating from the above steps didn't work for me. And so I had to write the step wise guide on what is currently working.

Thank you!

Cheers

@mitu

I figured it out!

Turns out, the zip contained .unh files, which is not supported. I've got some new files and it's up and running. As of n64, I had to unzip each file to get them to run.

Bonus question: is there something I can do to get n64 to run more smooth (rpi 3 B+)?

Again, thanks for taking your time. And for future googlers, hope this help you out.

@dankcushions Thanks for your very elaborate answer! I naïvely assumed that at least the region detection was straightforward (e.g. some flag in the internal ROM header), but after some reading it seems that the region was indeed only "coded" physically by incompatible cartridge sizes. Some bytes of code and data saved I guess.

I'll just manually set the 50Hz rate. I'm definitely grateful that it can be done conveniently in a few seconds!