@mitu
After figuring out I shouldn't be using the 64bit version for this, I got the screen working with sound. Now it's just the usual gambling of installing stuff that's not just roms and emulators in retropie. :v

Thanks!

@mitu I decided to use the Ace with my PS4 instead (it works fine right out of the box on PS4) and use the dualshock controllers for retropie. However, even those I can't successfully pair with retropie. I will write a separate post.

Configuration editor will not help here. You can use jstest to check that each encoder outputs an identical input code for the same button.
Running jstest /dev/input/jsX will show you the inputs on the encoder and you can press all the inputs to see how they're recorded. Replace X with 0 to 3 and you should be able to test each of the 4 encoders. Interrupt the test by pressing Ctrl + C.

Please add some more details about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

If you're just starting, why did you choose the Pi5, which is not yet officially supported ?

@sugarfree thanks! Good to know there is a way to do this from the terminal window. I ended up following the instructions from this video to reset the emulation station input configuration for the controllers.

If you have Enter as hotkey_enable for the keyboard, then pressing Enter + F1 should open the menu with the keyboard.

@mitu said in problem with configuration file saving... (Treaded video always turned on issue):

Your RetroArch version is not up-to-date, did you only update the RetroPie-Setup script without updating the packages ?

Maybe-maybe....

Luckily I got another memory card with version 1.9.7 which worked perfectly 1.19.0 utterly sucks and has so many bugs and issues. I think I'll stick with the older version and never upgrade retroarc again. if it ain't broken don't fix it.

@mitu said in Assigning a Mouse to a Specific Device Node:

Feel free to experiment and report back your findings.

I'm trying to find out the systems normal behavior and trying to make sure I understand what you were saying - I'm not clear what you mean by "bump the indices." I do get that you've explained it, but I'm still not clear and I provided an example. I can experiment, but that will mean spending a few days working it out and, since it's a known behavior, I was hoping to start with a baseline.

So if I have my dev nodes as I asked about above:

/dev/input/event0
/dev/input/event1

But I'm finding those get switched if the USB plugs are switched, so I use udev to always create:

/dev/input/event50
/dev/input/event51

Then if I want to use event50, do I set the index in RetroArch to 50? Does RetroArch use the index numbers on the nodes, or does it just count the nodes and start at 0 and increment by 1 for each new node, in spite of whatever the index number on the node name is?

OK, the crash should be fixed in https://github.com/RetroPie/RetroPie-Setup/pull/3861.

It doesn't matter how many un-configured devices are detected, one is enough to trigger the bug whenever its input is procesed by joy2key (a button needs to be pressed to trigger the bug).

@Muckypaws I think you can do this with core input remapping.

For quick menu > controls > port 2 controls, you want to set the joystick directions to their right stick counterparts, and then set mapped port to port 1. Now the player 2 joystick should behave as player 1 right-stick. Save this as a game remap file and you should be all set.

https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

Just wanted to leave this last message here for anyone that finds themselves in a similar position.

I ended up using the below github to get this situation sorted out. I used the "remove orphans" feature after using notepad ++ to change all of the paths of the directory that I wanted to get rid of to "remove.zip"

The gameslist editor linked below then saw these xml entries as "orphans" and allowed for easy removal of the entries without messing with anything else in the gameslist.xml file.

https://github.com/NeeeeB/GameList_Editor/releases

Thank you @ getupor for leading my mind down this path.

After trying a few times, and it crashed my pi, it finally just worked, and I was able to map the buttons in emulationstation. The light will always move from left to right at the bottom of the pad, but it seems to work fine (for now).

@LeatherWing Thank you for the confirmation. The fix has been merged now.

@LLD said in Radiant Silvergun on Pi 4:

Could @roslof provide specific advmame settings if that's the case ? Or could it be that advmame changed since the edition of the sheet and gives now poorer performance for that game ?

Well, I can say that as of now, I also cannot get the game to run with either 2x or 3x magnification.

This is a Sega Titan game. It doesn't run well with any system, but still runs best with AdvMame. I've never had great success with the audio either. Always sounds "tinny" on the Pi4 builds, and why I have it at the bottom of the "recommendations" totem pole.

@retropieuser555 @LLD correct in that audio cannot easily be addressed. I added the note about ScreenUpdateSetting = 7 in the sheet. Note there is also a comment in there for Perfect Dark from @George-Spiggott

Could also try Next/640x360 16:9 with MSAA Level 2 (recommended by @George-Spiggott RetroPie forums)

Forgive that my pi is offline (building lr-mess) at the moment, but I recall Perfect Dark could not be perfectly emulated with any system and there were some sacrifices with any proposed solution.

@mitu Thank you very much, I have purchased a splitter and solved the issue for 20 bucks.

@ecto Thanks so much. This helps me a load to incorporate into my build.

Thanks a lot and I really appreciate the time.