Retroarch GUI controls broken after update to 4.1.5
-
How did you update ?
does the pigrrl2 inputs act as a joypad or keyboard ?
If you mean you can't exit with the menu hotkey - it is a known retroarch issue - you can use the menu to exit.
-
@BuZz said in Retroarch GUI controls broken after update to 4.1.5:
How did you update ?
does the pigrrl2 inputs act as a joypad or keyboard ?
If you mean you can't exit with the menu hotkey - it is a known retroarch issue - you can use the menu to exit.
Sorry. I've found an older topic that seems to be a better fit.
To answer your questions though: I updated through the retropie setup script. I've since found this issue exists in the default retropie 4.1 img. Keyboard controls aren't being passed to retroarch correctly. Controllers work fine.
-
@aspiringnobody Please describe how you updated - did you just update the retropie-setup cript or did you update all packages ?
There have been upstream changes to retroarch regarding the menu input which may be affecting this - but need more information.
Please also provide the output of(via pastebin or similar)
cat /opt/retropie/configs/all/retroarch.cfg cat /opt/retropie/configs/all/retroarch/autoconfig/* /opt/retropie/emulators/retroarch/bin/retroarch --version -
@BuZz said in Retroarch GUI controls broken after update to 4.1.5:
cat /opt/retropie/configs/all/retroarch.cfg
I updated by first updating the script and then updating all packages. I first tired it with OS updates, and encountered the rgui issue so wiped my SD and tried again without. Same issue.
I then downloaded the stock retropie 4.1 image (as opposed to adafruit's pigrrl 2 image) and discovered the issue exists in stock un-altered 4.1.
output as requested (note this shows I'm using the xmb -- issue persists either way, I didn't feel like changing it back just for the paste)
cat /opt/retropie/configs/all/retroarch.cfg
cat /opt/retropie/configs/all/retroarch/autoconfig/* -- Xbox Controller (WORKS)
/opt/retropie/emulators/retroarch/bin/retroarch --versionI'm not getting an autoconfig for the keyboard at the moment and I'm in the middle of copying some roms to the pi via USB. As soon as that's done I'll reboot and check for the autoconfig of the keyboard. I tried starting retroarch after configuring the controls via GUI and that didn't update the config -- that might be the problem.
- Evan
-
@aspiringnobody you don't get an auto config for the keyboard.
to rule out something in your config, please back up
opt/retropie/configs/all/retroarch.cfgthen remove it, andupdate all packages. Then go to EmulationStation and reconfigure your keyboard based input.I will then be able to more easily test it here myself.
-
give me a few minutes I'm gonna nuke the card and start fresh.
I'll redump configs when I'm done. To confirm, you'd like me to update all (moving to 4.1.5 again)?
-
@aspiringnobody yes please.
-
Updating now. I'll dump the configs here for you in when it finishes. any other info you can think of that you'll want?
I've mapped the controls as follows:
up -> up arrow
down -> down arrow
left -> left arrow
right -> right arrow
start -> enter
select -> shift
a -> z
b -> x -
-
@aspiringnobody and still the same issue ? i will test and get back to you (tomorrow or so).
-
Yeah, I made sure the first thing I did was test it with just the 4.1 image and no changes at all (other than to configure the controls as required on first boot).
After the update to 4.1.5 the issue still exists.
In rgui you have the arrow keys and start as the only functioning buttons. so you can scroll down to exit and hit start and it works -- but if you go into any other menu you are stuck there.
- Evan
-
@aspiringnobody How did you configure retroarch ? did you do it manually ? I noticed
input_menu_togglewas not set in your config, and this should be set when configuring controls in emulationstation.I can confirm issues though and I think it might be related to some tickets already open, however I will open a ticket upstream for you (It's a Retroarch issue).
-
This is literally the 4.1 image from the retropie website. All I did was update to the newest version via the retropie-setup script.
If there's a problem it's with the default config. It seems to have completely changed in the newest version 4.1.5 (it's fully commented out now and calls itself a stub config or some such).
- Evan
Note that installing retroarch on raspbian doesn't have these issues. If it's an upstream regression it's due to something retropie uses that the "normal" retroarch Linux build doesn't.
-
Also, thanks for all the help!
-
@aspiringnobody input_menu_toggle is configured when setting up a controller in emulationstation. I'm not sure how yours was commented out - I have just done a fresh install and that ini variable is configured correctly so something was different in the way you set this up. I would need you to tell me each step you went through to end up with the retroarch.cfg you linked above.
This is not related to the issue with navigating though which is a retroarch problem. I have opened a ticket here https://github.com/libretro/RetroArch/issues/4211
The default configuration has not completely changed - it's always been a detailed configuration like that. If you allow settings to be saved from RGUI, it gets overwritten which was your original config.
You need to provide more details. - when you say "Note that installing retroarch on raspbian doesn't have these issues. " what do you mean ? Installing from where ? What version ? Please be as verbose as possible.
The navigation issue is a new issue in RetroArch since their menu input changes (since v1.3.6).
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
Interesting. I obviously had to set up the keyboard on first boot, but I didn't do a full set of controls (just the bare minimum in fact). Not sure if it would be different now that I've mapped the whole keyboard control set and an actual controller. I could check it for you if you think it's relevant.
When I tried troubleshooting i installed raspbian with pixel and then installed retroarch from the repos. It seemed to work with the keyboard.
Not 100% sure what version of retroarch is in the repo though. I assumed it was 1.3.6 but I didn't actually look.
I'll check it out when I get home.
- Evan
-
@BuZz I have been informed on IRC this was a design decision - the RGUI can only be controlled via joypads with the joypad configuration or a set keyboard configuration with pre-configured controls (not the player1 configuration). This was a decision they made due to complaints from windows users related to the default mapping etc - I don't know the full details - there is some reddit discussion I believe. They are considering adding an option to bring back the old behaviour.
I don't agree with the change (I don't fully understand the problem people had with it before), and I think it will break stuff for a lot of people that don't want to keep a keyboard handy, and have a controller than maps to keyboard keys. However with a backward compatibility option, all will be well.
-
As much as I love libretro, their developers are boneheads.
That's absolutely unacceptable regression. Did they specify what was causing such a code maintenance burden as to require them to drop keyboard support?
I guess I'll look at their git tonight and see about making us a patch for retropie.
Every interaction I've had with their devs has been a disaster. Seriously who would even think that's a good idea?
-
Also see if you can tease what their default hardwired config is. It might be easier to just remap all my gpios to different keys to match what they have "decided" is appropriate and then remap through emulationstation so the games work.
sigh
-
@aspiringnobody They are implementing an option to enable the old behaviour currently.
I'll find out the controls.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.