@GreenHawk84 which version of Emulationstation are you running?

There has been a corner case [1], which escaped my mind in the first place, but then has been corrected by @pjft .

If your ES is below 2.10 (which I assume):

Either update to 2.10 onwards If you don't want to update use this workaround: Edit your ~/.emulationstation/es_settings.cfg while ES is not running and check the value of SlideshowScreenSaverCustomImageSource. Make it read false (you can also do it during ES is running in the Screensaver Options Menu).

Rationale: Your behaviour can happen on ES < 2.10 if you set your slideshow screensaver to use a custom image source and then switch to video screensaver (without disabling the image source flag).

Please report back if it solves your issue. And if it does, mark this topic with [solved] in your initial posting header.

[1] https://github.com/RetroPie/EmulationStation/commit/a8ccd0a75ba81b3e4af88ed3ebcfe08e57520ab6

0 pjft committed to RetroPie/EmulationStation Fix video screensaver launch game controls Video screensaver wasn't launching games when the Image screensaver had been set to use custom images, even if not in use. Introduced in #673 . Reported in https://retropie.org.uk/forum/topic/29291/video-screensaver-black-screen-with-omx-on-and-controls-not-working/

@rasp_renegade said in Wiring GPIO to arcade machine control panel:

I am not installing the pi that close to the control panel. They dont make these 3-6 ft long.

With that wire length I would refrain from using GPIO directly!

Why is GPIO for longer wires not advisable? Mainly because the Rpi4 has weak internal pull up resistors (50-60 kOhm) and the long wires act like an antenna for stray and input capacitance. In short: You may get ghost inputs.

You can mitigate it by using external pull ups (at least 2k) next to the GPIO header and disable software wise the internal pull ups, but I guess you were asking for less effort, not for more effort. :)

Better place the beforementioned USB based solution or a MCP 23017 which uses I2C for transmission (much cheaper than the USB boards, can also be driven by the mk_arcarde_joystick module as you may know from your previous builds) close to the control panel. Then use USB / I2C for transmission on the longer distance. They both have more robustness/error detection. With 6ft you are far below the maximum cable length of USB2.0 respective I2C.

@dankcushions Thx, good info so far. Layout looks like this:

PXL_20211202_193151257.jpg

@theatomicfire said in Trying to make my own motion control with retropie:

However, I have been running into problems getting the gamepad "configured" within retropi. I created cfg file for my "input device" which retopi recognizes, but none of the commands i input through the script actually go through

Do you mean EmulationStation will not recognize and configure your input ? Is your device working with jstest or sdl2-jstest ?

Do you have any ideas as to how I could implement this?

Difficult to say without any more details or a look at the code you used.

@flopsi said in Using Gamepads and Arcade Controls At the same time.:

Waht can i do ??

As the printed error hints - do you have the RetroPie-Setup folder in /home/pi ? How did you install RetroPie ? Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu happy to report that after installing 20.04 on another HD I am able to natively use my controllers in the menus. Now to go through the process of redoing all the OS tweaks.

Thanks for all your help @mitu

@mitu tried changing out the wires and that didn't work, so I guess I'll have to get a replacment button

@barbudreadmon said in Is there any way to use two joysticks for Wonderswan?:

@jimmyfromthebay said in Is there any way to use two joysticks for Wonderswan?:

Not sure what you mean by that. There's no such option that I can find under Controls (I have Show Advanced Options set to On).

You need to update RetroArch, this option is only a few months old, see https://www.libretro.com/index.php/retroarch-1-9-6-released/

Ah, thanks. I'm absolutely terrified to update core features like Retroarch in case they've done something moronic that requires the manual alteration of literally thousands of CFG files, like that time they added a new video aspect ratio which renumbered all the other ones :(

@mitu : Thank you very much. After installing Joy2key, the navigation works again with the gamepad. Thanks for the good advice.

@mitu I did indeed configure my controller when I first booted up. Had to re-do it a few times because I was having issues with the blue tooth. I guess I must have mucked something up when I re-configured my controller, because I went back to re-configure my input from the emulationstation ui just to make sure, and now the problem is fixed, I feel like such a dope for not trying this, thanks.

@sleve_mcdichael yep, that did the trick, I located the .rmp and the permissions were set to [root] so I changed to [pi]. It works now, thanks.

@folly IWill do. I've spent the last couple of days mostly wading through over 1000 Atom files just called 1, 2, 3, 4 etc, which actually turned out to be Retropie-compatible DSK files, just figuring out what they all were. (I'm about 30% done.) Once I've identified the games and got their controls configured I'll upload the configs.

@fadangalini
Fixed the problem.
By putting KEY_#302 in place of where you would put BTN_THUMB for example, works.

Thanks @brandflake11

I got this one figured out. It was a PITA! :)

Long and short of it is this...

xrandr treats both displays and one large one (extended). You can see below that Screen 0: is recognized as 5760x1080 (4K TV + 1080P monitor):

Screen 0: minimum 320 x 200, current 5760 x 1080, maximum 16384 x 16384 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 3840x2160 30.00 + 24.00 29.97 23.98 4096x2160 30.00 24.00 29.97 23.98 1920x1080 60.00* 59.94 30.00 24.00 29.97 23.98 1920x1080i 60.00 59.94 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.00 30.00 59.94 29.97 24.00 23.98 1024x768 75.03 70.07 60.00 800x600 72.19 75.00 60.32 720x480 60.00 59.94 720x480i 60.00 59.94 640x480 75.00 72.81 60.00 59.94 720x400 70.08 DP-2 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.00*+ 50.00 59.94 1920x1080i 60.00 50.00 59.94 1680x1050 59.88 1280x1024 60.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 70.07 60.00 800x600 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 66.67 60.00 59.95 59.94 720x400 70.08 HDMI-2 disconnected (normal left inverted right x axis y axis)

This is what my autostart.sh file looks like:

#! /bin/bash #set primary display and resolution. xrandr --display :0 --output HDMI-1 --mode 1920x1080 --primary & #call cvlc to play a startup animation. Wait for it to end before continuing. cvlc --random --play-and-stop --play-and-exit --fullscreen --video-on-top --no-video-title-show --quiet --gl=any --preferred-resolution=1080 ~/RetroPie/splashscreens &> /dev/null #start ES in a terminal (openbox). gnome-terminal --full-screen --hide-menubar -- emulationstation --no-splash

Naturally, feh sees the display the same way so you need to use the --geometry switch to identify the starting pixel on the 2nd monitor. This is what my runcommand-onstart.sh looks like:

#! /bin/bash ROMPATH="$3" ROM_BN_EXT="${ROMPATH##*/}" ROM_BN="${ROM_BN_EXT%.*}" CONTROLSIMAGE="/home/pi/RetroPie/roms/$1/images/$ROM_BN-controls.png" feh --geometry +3840+0 "$CONTROLSIMAGE" &>/dev/null &

This essentially gets the full path to the romfile and trims the extension to get the rom base name.
It then builds the path to the controls image I need and displays at the starting position I tell it to (3840x0) which is the entire screen of the 2nd monitor. When I exit the game, and merely kill feh via runcommand-onend.sh:

#! /bin/bash killall feh &

This is working perfectly. Now I just need to find a fancy graphic to display on the 2nd monitor when it isn't showing controls. :)

John

@pianoman72 said in Port 2 Controls Not Working After Upgrade to Buster:

I upgraded to Buster today with a fresh .img and copied over .cfg files, etc from the old install.

Some configuration files might not be correct with the new versions of RetroArch. Which version of RetroArch did you have before the update ?

PROBLEM 1 - If I'm in the emulationstation menu, the player 2 controls DO work (all players can control the menu), but select and start are swapped. I thought if I swapped the values for those inputs in /opt/retropie/configs/all/retroarch.cfg it would resolve this, but has no effect.

input_player2_start_btn = "22" input_player2_select_btn = "21"

Not sure if configuring in retroarch.cfg overrides the autoconfig profile values. Where did you get the 21, 22 values ? The numbers look way high for a button number.

In games, the 2nd player controls don't work at all. I think this has something to do with "Port 2" if I go to settings-->input---Port 2 Binds. There is a new device index (index #2) that wasn't there before the upgrade to Buster.

Did you install any aditional drivers in RetroPie ? If you have a 2 player controller, you should have index 0 and index 1.

So in order to get any input on that screen I have to switch to index #2 and it will assign new numbers to all of those old values. So for example what was button '22' becomes '6' but at index #2.

How many gamepads does the system detect ? Did you add the USB quirks for this controller - see https://retropie.org.uk/docs/Xin-Mo-Controller/ ?

@kman0318 said in controller buttons open command line:

RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): retropie 4.7.1

Try to update the latest version (4.7.12) and update your OS/packages also (the installer will prompt you to do so). Then reboot and install the xpadneo driver before trying to pair again via Bluetooth.

@gabbo999 said in Retroarch input setting problem:

I have a Raspberry pi4 with obviously retropie installed, I finished today to build my cabinet and I wanted to set all the right buttons for each emulator.

Please add the complete info, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

In N64 emulator i went in the Retroarch quick menu and i noticed that in port 1 controls B button and Y button are both button 3, same A and X both button 1... (see photo attached)

Actually, the B/Y buttons are not mapped at all - the right side (which shows the emulated system's mapping) is empty. How did you configure the gamepad ?

@mitu You're totally right, the ROMs I have just aren't the two control set versions, I just tried Gauntlet and everything worked fine. Thanks for your help!!!