@mitu
Yeah, still no luck. So strange, as I had been able to use my gamepads in Xinput mode for at least a couple years from maybe 2019 onward till I updated my whole RetroPie OS and packages just a couple weeks ago. However, in going through the comments in github for xpad, it does seem like others are having issues with connecting their wired controllers through Xinput mode. Either way, thanks for your help up to this point and I'll keep digging around.

@mitu I made another test replacing the SSD ( Kingston SSD KC3000, 2048 GB, M.2 2280, NVMe PCIe Gen 4.0, Read: 7000MB/s, Write: 7000MB/s, SKC3000D/2048G) for a SSD "Adata Legend 740 NVMe, 250GB, PCI Express 3.0, M.2"

ALEG-740-250GCS-6.jpg

And this SSD disk works!! (now I can see several folders inside "retropie-mount" folder, "BIOS", "roms", etc)... but is a very tiny SSD compared with the Kingston one, maybe it worked because this is a PCIE 3.0 and the Kingston is PCIE4.0? maybe raspberry pi 4 doesn't support PCIe 4.0 because that technology needs more power? I used the same enclosure for both SSDs (ORICO M.2 NVMe SSD Enclosure to USB-C PCIe Adapter 10Gbps USB 3.2 Gen2 for NVMe M-Key/M+B Key SSD 2230/2242/2260/2280)

@mrt88 If ES is just naming the device to configure as keyboard, you haven't switched the mode of the IPac. If it would be in one of the gamepad modes, ES would say something like "# gamepad(s) detected..."

AFAIK the mode is persistent once set and if possible you may well keep to @hopwon and change the mode to your desired one on a windows machine/observed checked via winipac.

Once it reports itself as 2 gamepads.... as I had downgraded (after updating from 1.39) my Firmware from the 1.5? to 1.49 (KBD only) I can't try it out and really don't recall how the multi-mode DInput/XInput differs for P1/P2 - Opening the configure input from emulation station I 1st would configure the parts connected to the P1 side of the I-PAC2 and see whether the P2 side responds afterwards (so both pseudo-devices are using the same identifier), but my guess would be that you have to configure the input again with the stick/buttons connected to the P2 side of the I-Pac [1].

Edit: If you opt for the "Keyboard" way, manual editing configs is the only way (AFAIK) of setting the keys for player 2+. The Docs @mitu linked to are pretty good, in addition you may have a look at this (maybe somewhat old) guide from theink. And the meta/shift-key from the IPac2 was one of the main reasons I switched back to keyboard only mode, as it opens up so much possibilities in key-assignment that I am unsure how to achieve the same from within a gamepad mode of the I-Pac.

1: Would be wise on ultimarcs behalve to report P1/P2 sides of the IPac (in Gamepad(s) Mode) with different IDs, as both parts could be configured in a different way/layout button assignment via Winipac.

I gave up as I see there is no support on Github or anywhere!

Uninstall and try something else

@martinbailey74
The only gamepad driver I have installed is xpad. I picked option 1 - DisplayYesNo for the security mode. I did have some trouble on the initial connection, so you'll want to select the background option under the Configure bluetooth connect mode. Once you have that, try connecting the Stadia again. Whether it connects or not, select to remove a bluetooth device, pick your Stadia from the list, and then re-connect after that.

I'm not sure why this would work for any reason, but these are the steps I took and it works for me now, and pairs right up after a reboot when ES is done loading. One other thing to think about is if the Stadia is pairing to something else before the RetroPie grabs it.

What color light are you getting on the Stadia when you're having difficulty connecting after a reboot?

**Update: I recently had some trouble with connecting my Stadia, so I changed the connection mode to "default", which seems to have fixed it. You can try both modes and see if one or the other works for you.

@TheAutisticGamer said in Run Games that require a Desktop for SDL:

EDIT. Is this how its suppost to be done in emulators.cfg?
sonic3air = "XINIT:/home/pi/RetroPie/ports/sonic3air.sh"
ports_sonic3air = "sonic3air"

No, it should be

sonic3air = "XINIT:/path/to/launch/script/or/program" default = "sonic3air"

I don't think your game is installed as a port - you should have the emulators.cfg in /opt/retropie/configs/ports/sonic3air and the /home/pi/RetroPie/ports/sonic3air.sh should contain:

"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "sonic3air"

@tielax11 said in Joystick not working in game:

Built From: [64gb]-CRT.Blast.Arcade.RPi4.ES.AM.Dual.Monitor-DynamicDuo image

This is a third party preconfigured image. Such unofficial images are not supported. Please seek support from the author of the image or install the official image.

@trapexit I'm on the latest lr-Opera and I am experiencing the same problem. Reload works for a while (few scenes), then it stops working until I reset the emulator.

@cornishrooster
I have a similar issue.
I set up the psp folder & installed the psp emulator from binary.

My psp ROM shows up in the RetroPie file manager but I cannot get the psp emulator to show on the menu carousel. I converted the iso file to a cso to save space. Hope that is not the issue.

Does anyone have any suggestions? I have been suspecting ES is the issue but I am not sure.

@bluecoffee said in Two MAME games, one works 2 player one doesn't:

Forgive my ignorance but how would I tell a single rom to use FBNeo?

You can use the runcommand launch menu to choose which emulator runs a rom.

https://retropie.org.uk/docs/Shaders-and-Smoothing/

@jdriscol This is an issue with EmulationStation, not streaming via Twitch. You should have opened a separate topic, instead of piggybacking on an existing one just be cause there's a similar error - I'm splitting this into a separate topic.

Your issue is most likely due to PulseAudio being installed - disable PulseAudio from the Audio menu in RetroPie and try again. If that doesn't work, post the output of amixer -l.

@windg Makes sense. I did fix the issue by making the resolution 640x480. It covered the entire screen. HOWEVER, it looked crappy and the aim was way off and it shot far to the side of the cursor in the light gun game.

The volume control error is not related to the crash - it comes from EmulationStation.
Assuming you're using RetroArch and one of the NES cores to stream, the problem is probably in RetroArch's streaming module. You haven't added any of the info asked https://retropie.org.uk/forum/topic/3/read-this-first, so it's difficult start diagnosing what's at fault here.

Thank you. Will look into that.

@bluecoffee said in Pi4 with vertical screen orientation - newest advice?:

Suggests that I should be modifying the file autostart.sh.
Is this correct?

Yes.

Could someone outline the steps that need to be taken in 2022 using a Raspberry Pi 4.
There also seem to be lots of conflicting questions about

Does this only affect Emulation Station, but not the actual games themselves?

Yes.

Does this cause a performance hit like the old method did?

For EmulationStation, not so much.

Do I need to modify each emulator to run vertically as well?

Yes, though for RetroArch you can change the main configuration and it will be applied to each core.

See this topic for a similar question and some recommendations on how to rotate the screen.

I remove lr-mupen64plus-next and lr-ppsspp from retroarch setup.
I install it again and it works ! I can go into the rgui menu (strange thing i mapped hotkey on the xbox button and i can with select + Y !!! (but i can !).
With another emulator (lr-beetle-psx, i can quit a game with select + start.
Not from fresh install emulator. Have i something to parameter in rgui menu

Regards.

@mitu I fixed retropie by adding some roms