The RetroPie usbmount scripts don't transfer ROMS if you setup the USB for ROM transfer.
Please add more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first, and what is the name of the folder you created on the USB stick

@mitu said in Creating a custom SDL2 gamepad mapping?:

Try maybe adding the export command to $HOME/.bashrc.

That also worked from terminal but not from ES.

So what I think is happening is this: autostart.sh is called from /etc/profile.d/10-retropie.sh which runs as part of /etc/profile. Then once that's complete it calls .profile and .bashrc.

But since the environment var is set in autostart it is perhaps disconnected from the profile service and so maybe the variable is local only to that shell. So it works from inside ES but when I exit ES and the autostart shell terminates, the var goes away and it doesn't work from terminal.

When I set it in .profile or in .bashrc it works from terminal, but these aren't processed until after ES exits because that's part of autostart which happens while /etc/profile is still going on.

@barbudreadmon surely 👍. check your PR though, build issues.

@mitu

Hello,

I had the same problem when making the backup, it would be interesting to add these notes in:
https://retropie.org.uk/docs/Updating-RetroPie/#making-a-backup
Change "Make sure you have the correct drive letter for your SD card!" to "Make sure you have the correct drive letter for your SD card! (Choose the partition which is readable by Windows, 'boot' as the source of the backup)" or something similar.

Thank you.

@flagrant99 I have since learned some things.
glsl Shader format available to OpenGL.
glslp for GLSL stack these shaders to create a combined effect.

Only a glsl will get reloaded not the glslp with video_shader_watch_files ON.

@glovewithsauce i'm sorry, but asking for/providing links to to BIOS files is against the forum rules

@stoltzy Something related to your WM maybe or a bug in SDL which doesn't correctly set up fullscreen. What WM/DE are you using ?

Combined with --resolution WxH, you can use --windowed to start ES as 'full screen', just to avoid this issue.

Then it means the retroarch.cfg was not a problem, but can't think of a reason why running it from EmulationStation has this problem.

@sleve_mcdichael Thank you, I'll begin to try this once I setup my Pi

@chaoseffect said in lr-flycast new GitHub repository source for setup script?:

I have ports 1 and 2 set to "keyboard" in the RetroArch menu, and I think that's it for keyboard settings. The keyboard works fine for me for player 1, and I was just curious if this update would bring a core option for keyboard indices so that a separate keyboard could be used for player 2.

I think that's the RetroPad -> Emulator core part settings, i.e. the core expects a Keyboard type input from Port 1 (2), the Device -> RetroPad mapping is done by RetroArch.
Usually 1 keyboard can be used for 2 players (as explained here), but I'm not sure 2 keyboards can be used independently (via dev index, how gamepads are handled). This depends on the input driver used, I know some of them don't support it (like Windows winraw). RetroPie should use the udev driver, so it might be supported, but I don't have 2 keyboards right now to test.

@roslof The release event is not counted for the unlock passkey, so it doesn't matter what's the mapping reported. At some point, the HAT events have been discarded as valid input from the passcode matching (here) and this causes your issue.
For a Dualshock controller (like yours) unlocking works using one of the joysticks, but not the D-Pad (which is a HAT type input).

@averagespearman Quick question How did you get the IPEGA 9139 to connect to retropie

@mbernier said in DOSBOX exit key mapping on gamepad issue:

In my case i did not notice immediatly because it only affected non libretro package like redream, dosbox, vice and jzintv. All the others was working properly so it's something that can easily go unnoticed.

My guess is only SDL1 apps would not be able to work reliably without the trigger_to_buttons param, all other SDL2 applications, should have better support for this configuration.