controller not mapped correctly in games :(

naddel81

I am using a fresh pi3 b+ and updated to the current retropie 4.4.4
unfortunately after first initializing my controller (wireless bluetooth) in ES, the emulators (does not matter which) do not use the right button mappings I entered in ES.
so I did it manually in retroarch (which was a hassle). but now the hotkeys (START+SELECT to exit) do not work.
I am lost here!

naddel81

I even tried to set the hotkey bindings to keyboard. but when in emulator none of them work. I cannot exit or toggle the menu.

mitu

@naddel81 said in controller not mapped correctly in games :(:

unfortunately after first initializing my controller (wireless bluetooth) in ES, the emulators (does not matter which) do not use the right button mappings I entered in ES.

The emulator matters, because not all of them are automatically configured from ES. The RetroArch/Libretro based emulators should be, the input configuration in Emulationstation should produce a configuration file in /opt/retropie/configs/all/retroarch-joypads, which you can look at and see if it's correctly written. See the docs for how it's done.

naddel81

I only use libretro emulators (snes etc.) and the hotkeys just won't work. I try to SSH in now.

mitu

@naddel81 Reset you input configuration again and re-configure your gamepad. Then take a look at the cfg file produced by the configuration.

naddel81

there I have several files. can I just delete them and start over fresh?

alt text

mitu

Are you using a 3rd party image or the one downloaded from retropie.org.uk/download ?

naddel81

downloaded directly from the website you linked. it was a 4.4 image that was then updated to 4.4.4 yesterday.

cyperghost

@naddel81

Please check if this header is present in your ES config file
nano /opt/retropie/configs/all/emulationstation/es_input.cfg
And if you change or delete something take care of the few lines the <command> is mandotary for autoconfig.

<?xml version="1.0"?>
<inputList>
  <inputAction type="onfinish">
    <command>/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh</command>
  </inputAction>

@mitu
It sometimes happen that the button numbering is wrong. So you can play arounf with udev and sdl... but imho it is better to enter a retroarch (with a working controller or controller) and then set the joypad there. Then you write down the numbers of each button and write it back to the specific autoconfig and then it should work.

naddel81

@ cyberghost: this is in the file you mentioned:
"<?xml version="1.0"?>
<inputList>
<inputAction type="onfinish">
<command>/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh</command>
</inputAction>
<inputConfig type="joystick" deviceName="Gamepad" deviceGUID="0500000049190000020400001b010000">
<input name="rightanalogdown" type="axis" id="3" value="1"/>
<input name="rightanalogleft" type="axis" id="2" value="1"/>
<input name="pageup" type="button" id="8" value="1"/>
<input name="start" type="button" id="11" value="1"/>
<input name="rightanalogup" type="axis" id="3" value="-1"/>
<input name="down" type="hat" id="0" value="4"/>
<input name="leftanalogright" type="axis" id="0" value="1"/>
<input name="pagedown" type="button" id="9" value="1"/>
<input name="right" type="hat" id="0" value="2"/>
<input name="select" type="button" id="10" value="1"/>
<input name="left" type="hat" id="0" value="8"/>
<input name="leftanalogup" type="axis" id="1" value="-1"/>
<input name="up" type="hat" id="0" value="1"/>
<input name="a" type="button" id="1" value="1"/>
<input name="b" type="button" id="0" value="1"/>
<input name="leftanalogdown" type="axis" id="1" value="1"/>
<input name="x" type="button" id="4" value="1"/>
<input name="leftanalogleft" type="axis" id="0" value="-1"/>
<input name="y" type="button" id="3" value="1"/>
<input name="rightanalogright" type="axis" id="2" value="-1"/>
</inputConfig>
</inputList>"

Will deleting the game controller files and resetting ES mappings fix this issue?

mitu

@naddel81 You configuration folder shows 4 gamepads already configured. The RetroPie image does not include any auto-configured gamepads obviously , so this is a little bit strange how those configurations got there. Re-install the image and configure your gamepad again, then post the .cfg file that Emulationstation produces.

cyperghost

@naddel81
Please use three backticks for code enclosure

So
```
CODE LINE
```
Looke this

CODE LINE

No... if if delete the file you loose your autoconfig. Not needed. But you can delete the autoconfig files in the folder if you want.
It was just for cross check

Please descripe

I enter a game, it does not recognize most of the buttons.
why is that? and how to I reset the retroarch input settings?

Does only the DPAD work and no other button?

@mitu

Strange files

I think he tried several PADs, see the creation date .... dated yesterday. So I think it's okay.

naddel81

I restarted from scratch now. Gamepad works, but hotkeys still don't.

cyperghost

@naddel81

@mitu will help you ;) you are already there ;)

mitu

@naddel81 Please see my previous post.

naddel81

you guys are my heroes, thanks!

hotkeys work now.

only problem left is the scrolling which is not smooth at all. see here

I don't think it has to do with the super eagle 2xsai preset I use. the pi 3 b+ should be more than capable of any video preset, right?

how do I get smoother scrolling?

mitu

@naddel81 said in controller not mapped correctly in games :(:

I don't think it has to do with the super eagle 2xsai preset I use. the pi 3 b+ should be more than capable of any video preset, right?

Not quite. The more advanced the shaders are, the more performance hungry they are and will impact your gameplay.

naddel81

yes, you are right. the super eagle + 2xsai made it stutter constantly when in motion.
the normal 2xsai runs fine.
is this CPU or GPU dependant?

mitu

@naddel81 said in controller not mapped correctly in games :(:

is this CPU or GPU dependant?

Shaders are mostly GPU dependant.

Darksavior

@naddel81 I believe the only shaders made for the pi are crt-pi and zfast. Zfast is slightly faster and even runs on a lower end pi2 or snes classic.