RetroArch UI - Gamepad issue

mitu

@DTEAM said in RetroArch UI - Gamepad issue:

Is It the good log file?

No, enable verbose logging and post the /dev/shm/runcommand.log contents on pastebin.com.

Also, can you provide some info about your system/gamepad/RetroPie version/etc. ?

DTEAM

It does that with 3 gamepads including one already auto-configured in
/home/pi/RetroPie-Setup/tmp/build/retroarch/autoconfigs

My gamepads:
DragonRise Inc. Generic USB Joystick (already autoconfigured)
USB Gamepad (commercial one)
Teensyduino KeyboardMouseJoystick (homemade with Arduino)

Here's my pasrebin file: https://pastebin.com/TgwUjZ0D

Another one with another game: https://pastebin.com/h7JUEfCk

Thorr69

@DTEAM You still haven't given the most important info

Pi Model
RetroPie version
Installation source

DTEAM

@Thorr69
Pi4
Original image from Retropie website v. 4.8
Actual version 4.8.4
Core packages updated via binary (last versions)

mitu

@DTEAM said in RetroArch UI - Gamepad issue:

Here's my pasrebin file: https://pastebin.com/TgwUjZ0D

I don't see anything special in the logs. If the gamepad works in-game, the same mapping should work in the RetroArch's menus - I don't think that's changed. Is the Teensyduino controller configured as a gamepad or as a keyboard in RetroArch ? Try re-configure it again in EmulationStation, this will re-generate the configuration profile for RetroArch.

The /home/pi/RetroPie-Setup/tmp/build/retroarch/autoconfigs/ has nothing to do with the RetroArch's configuration, the tmp/build folder is used for source installation and it's usually empty - emulators don't load any configuration from it.

DTEAM

@mitu
Hi,
I did some tests and the problem seems to be the link between ES controllers configuration and Retroarch .
I reinstalled retroarch and I got no error in the installation log (/home/pi/RetroPie-Setup/logs).

I deleted es_input.cfg and all my controllers .cfg (such as Teensyduino KeyboardMouseJoystick.cfg). When I set my controllers again, it set es_input.cfg but didn't create .cfg files in :

/opt/retropie/configs.hdmi/all/retroarch/autoconfig

It's seems to be a communication problem between ES and retroarch. I don't know what to do with that.

mitu

@DTEAM said in RetroArch UI - Gamepad issue:

It's seems to be a communication problem between ES and retroarch. I don't know what to do with that.

It's because you deleted the input.cfg file. This is where the path to the auto-configuration script that takes EmulationStation's configurations and writes the configuration profile for RetroArch (and other emulators) is kept. I said to just re-configure the gamepad, not to delete any file(s).

I advise you to re-install EmulationStation and check if the input.cfg is created, then configure your joystick again in EmulationStation.

DTEAM

@mitu said in RetroArch UI - Gamepad issue:

I advise you to re-install EmulationStation and check if the input.cfg is created, then configure your joystick again in EmulationStation.

Thank you, I solved this problem with your recommendation. Unfortunately, the Retroarch UI problem remains.

Is there a file somewhere in the opt folder that can cause this problem? A file that takes precedence over . cfg files in /opt/retropie/configs/all/retroarch/autoconfig for UI only?

mitu

Post your retroarch.cfg on pastebin.com, the one from /opt/retropie/configs/all. Also, post your controller .cfg file.

DTEAM

@mitu

See hyperlinks below:

retrorch.cfg

/opt/retropie/configs/all :

Teensyduino KeyboardMouseJoystick.cfg
USB Gamepad .cfg

/opt/retropie/configs/all/emulationstation :

es_input.cfg

Thanks

DTEAM

@mitu

/opt/retropie/configs/all :

retroarch.cfg.rp-dist

Another point, I must press "select" first in UI to activate it. It wasn't the case before. Only the arrows doesn't work. It dosn't work with the keyboard also but F1, enter, esc, etc work. It's an "up" and "down" buttons problem

mitu

The entire retroarch.cfg has more than 3000 lines, so there's no way to discern what's the option that may be causing this. I don't know what version of RetroArch you were using before, but the current version (1.15) has received a number of input related changes recently (after 1.12) and your issue may be triggered by those changes and some options you have saved in your .cfg.

My advice would be to back-up your current retroarch.cfg and use the RetroPie default one (retroarch.cfg.rp-dist).

Another point, I must press "select" first in UI to activate it.

I'm not sure that this means - you need to press Select to open the menu or to change an option in the menu ? If it's opening the menu, then it's normal - the opening is a combination of the hotkey_enable (which is mapped to Select) and the menu_toggle hotkey (which is mapped to X).

It wasn't the case before.

What was the behavior before ?

DTEAM

@mitu said in RetroArch UI - Gamepad issue:

My advice would be to back-up your current retroarch.cfg and use the RetroPie default one (retroarch.cfg.rp-dist).

It works now. Thanks
The problem seems to be from the new retroarch.cfg file . With no retroarch.cfg file, it works well. When I reinstall retroarch, the new retroarch.cfg file create that problem. I don't know why? Probably, a new setting create that

NEW EDIT:
In the new retroarch.cfg I changed all_users_control_menu = "true" for "false"
and now everything is fine. That was the problem.! Don't know if other people got this issue, but on on my side, this solved the problem.

Thanks a lot for the support !