UPDATE: Issue has been fixed with commit de5055c.
Thank you @barbudreadmon

Are you talking about the vice libretro core or the standalone emulator ? RetroArch input combos do not apply to the standalone emulator.

@mitu Thanks. After I built RetroArch with your commit, works well now.
스크린샷 2023-05-23 21-53-39.png

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

See here in RetroArch's source.

Yeah.

It took me awhile just to find the leaderboards section for Super-Punchout.

The site is a bit difficult for me to navigate through for some reason.

Anyway, I tied in the top 7 earlier tonight for knocking out Gabby the quickest. :D

The other times that were faster used the PAL version which is no longer supported, and to me, I considered that cheating. :P

Okay, so it seems as though what has happened is that changing the keyboard config in retroarch has basically broken the use of the onboard joystick and buttons that are connected to the Pimoroni hat that sits on top of the Pi4.

Again, this stuff is incredibly confusing... because inside of Retroarch when you are using the joystick and buttons it says that the device is "retropad" it says nothing about it being mapped to the keyboard.

Looking in Retroarch I can see now where all of my key mappings are busted and referencing the changes I made in the config file to remap KEYBOARD (not RETROPAD) config.

@mitu said in RetroArch UI - Gamepad issue:

My advice would be to back-up your current retroarch.cfg and use the RetroPie default one (retroarch.cfg.rp-dist).

It works now. Thanks
The problem seems to be from the new retroarch.cfg file . With no retroarch.cfg file, it works well. When I reinstall retroarch, the new retroarch.cfg file create that problem. I don't know why? Probably, a new setting create that

NEW EDIT:
In the new retroarch.cfg I changed all_users_control_menu = "true" for "false"
and now everything is fine. That was the problem.! Don't know if other people got this issue, but on on my side, this solved the problem.

Thanks a lot for the support !

@mitu Ok. Thank You.

@kcoconnor76

Slowdowns = lack of performance, your device is too weak to run this at full speed
Latency = delay between pressing a button and its result being displayed on screen
Runahead or preemptive frames = lesser latency at the cost of higher requirements, meaning more slowdowns if your device was already too weak without those features

Runahead and preemptive frames aren't features to remove slowdowns.

Note that some slowdowns can be native to the games (because the real hardware was too weak to run them) and some emulators have the ability to get around this by overclocking the emulated hardware, yet again at the cost of higher requirements.

Your pi4 is simply too weak to run n64, and the only way around this is most likely to use a better device.

@sleve_mcdichael
Many thanks! that helped!

the whole problems started becasue i am too tidy and have my Roms organized in each console in a seperate "Roms" folder. Now this tihngs makes sense to me.

@BuZz OK thanks, that got me back to the defaults.

After doing that the menu still wasn't responding so I deleted the emulationstation input configurations. Now it seems to be working better.

@FraIgna said in Some emulators doesn't work after changes:

When I launch a PS1 game I get a message on bottom left corner about "override". How I can disable it?

You go into the overrides menu and delete the override.

I suppose this option messes up the onfigurations file for other emulators. Could it be the case?

If you saved the override just for that system, it will not affect the other systems/cores. You may have changed a global option (like the video driver) and saved the configuration.

@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.

@DolphinCube said in Retroarch wont save after saving in-game a couple of times:

Certain games I played still has this issue. Especially with my n64 games. I think a fix is that when the system creates a new srm (for gba games). I have to manually delete it after the first save then reset the permissions of the roms folder for retropie using the retropie setup script.

That's weird, there's nothing that changes permissions during gameplay, all emulators/ports are run as the pi user. Did you modify the launching command to run as another user ?

But the configuration file error is still an issue

Why do you need to save the config file ? As a workaround, you can save a game/core override with the settings that you wish to change.

@sleve_mcdichael yes, that was an error on my part - I am accessing the SD card on another computer with Linux Reader and have to manually copy it across.

But I discovered something new: if I play a game, hotkey + Y, and set the overlay there, I can save the game config in the overrides section. This only works when assigning an overlay to a single game at a time, not a system via global override.

@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