@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.
@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.
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
1280x1024 75.02 60.02
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
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
1280x720 60.00 50.00 59.94
1024x768 70.07 60.00
800x600 60.32 56.25
720x480 60.00 59.94
640x480 66.67 60.00 59.95 59.94
HDMI-2 disconnected (normal left inverted right x axis y axis)
This is what my autostart.sh file looks like:
#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:
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:
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. :)
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.
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.
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.
@thorr69 Absolutely! When my girlfriend came to my home for the first time more than two years ago, she was very surprised by my RetroPie upright arcade cabinet (subsequently, she told me that she thought "okay, kissing later"), and soon after that, we played together next to another. 😊 We held hands for the first time when we looked up special moves for Street Fighter II Champions Edition online. 💞😄
(Her interest in playing retro games waned over time, but she still likes my "Automat" – German for "machine" – up until this day.)
Sorry for the off-topic, but this triggered some fond memories … 😇
For completeness, I've done some more work...
I checked fuse.rmp, it did not have the "-1" settings applied to anything.
Each game remap would have been created from the fuse.rmp (using the retroarch menus.)
I then checked all my game remap files. 13 of 28 files had this problem.
Next I tried to recreate using the retroarch controls menu.
Cycling right through the available options that can be mapped to the port 1 controls I have:
Then back to "---"
The (1) etc are my addition, "Fire" appears 3 times, "up" twice.
I set some buttons to each of these values, wrote a game remap file and checked for "-1". None of these options generated the "-1".
Next I cleared the options on buttons A, L, L2, R, R2 & X (all originally set to differently) and bingo, I recreated the problem :
There appears to be a bug. When clearing a mapping using the retroarch "Controls/ port X Controls" menu from any value to "---" the resulting remap file contains "-1" for that key and this stops you mapping the button using the Retroarch "Options" menu.
Its just working ingame now after removing xbox drivers and some tampering with the PS 3 driver like remove and install again and switching to antherone and back to shanwan.
Not yet tested in Retroarch