Input for specific ROM not working
-
Let me start by listing the hardware and software
- Raspberry Pi 3 B
- 5V 2A Micro USB Wall Charger
- RetroPie V 4.2.3
- Installed on Raspbian Jessie With Pixel (I installed from the Github Repo)
- I have a keyboard, wireless mouse, and a PS4 controller plugged into the USBs (I use the PS4 controller for RetroPie)
Alright so I have a PS4 controller that works perfectly in the menu of RetroPie. The PS4 controller didn't work well at first in the menu so I had to manually edit the input config file (at opt/retropie/configs/all/retroarch-joypads/Sony_Computer_Entertainment_Wireless_Controller.cfg) and now it works perfect in the menu.
The controller also works in games, but if I try to change the input for a specific game like Doom (USA) on the SNES emulator, the input doesn't change. Here is my input config file at ~/RetroPie/roms/snes/Doom (USA).sfc.cfg hope you can help.
-
but if I try to change the input for a specific game like Doom (USA) on the SNES emulator, the input doesn't change.
Are you making sure to save the game-specific configuration after it has been set? The option is located in the same menu used to set the controls.Edit: I missed that you have. Looking over it now.
-
Is it that the new controls don't persist between sessions, or does the new scheme also fail to work in the same session it was mapped?
-
Looking over your config file, it appears as though no changes have been made from the default. For example:
input_b_btn = "1" # Name: Cross, Default: 1
'B' is mapped to "1" and the default is also mapped to "1". It looks like it's simply a mirrored map of your default layout all the way through.
-
@mediamogul said in Input for specific ROM not working:
Looking over your config file, it appears as though no changes have been made from the default. For example:
input_b_btn = "1" # Name: Cross, Default: 1
'B' is mapped to "1" and the default is also mapped to "1". It looks like it's simply a mirrored map of your default layout all the way through.
Yeah I changed them all back because the X button on my controller started moving the player forward when it was only supposed to shoot. But even though I changed it all back to the default the X button still moves the player forward and shoots.
@mediamogul said in Input for specific ROM not working:
Is it that the new controls don't persist between sessions, or does the new scheme also fail to work in the same session it was mapped?
I have no clue.
-
As a troubleshooting method, try deleting the file completely. Then, run the game and see how it controls. After that, try remapping again and see if the new controls work before you quit back to ES. Finally, exit out to ES and see how the controls behave when launched again.
-
@mediamogul I'm kinda confused on the input cfg
Like:- input_x_btn = "3" # Triangle Button
- input_l_btn = "3" # Name: L1
They have the same numbers but they do different things
Oh and the deleting and remapping didn't work
-
If you'll notice, it's not that way on your main controller config.
-
@mediamogul
Ok so I reset the Doom (USA).sfc.cfg to have all the defaults, and now the PS button (the button with the Playstation Logo on it) is moving the character to the right. WHAT IS WRONG YOU CURSED CFG FILES -
Ha! Well, that is strange. What happens when you delete
~/RetroPie/roms/snes/Doom (USA).sfc.cfg
outright? -
@mediamogul said in Input for specific ROM not working:
Ha! Well, that is strange. What happens when you delete
~/RetroPie/roms/snes/Doom (USA).sfc.cfg
outright?All the controls stay the same PS button moves me to the right, X button shoots and moves me forward
-
Am I correct in assuming that this is only happening in your SNES emulator and that it started when you tried to remap 'Doom'?
-
@mediamogul said in Input for specific ROM not working:
Am I correct in assuming that this is only happening in your SNES emulator and that it started when you tried to remap 'Doom'?
No it is not working in other games/emulators. Are there other logs other than ~/.emulationstation/es_log.txt
-
There's
/dev/shm/runcommand.log
. You'll want to use the runcommand menu to enable 'Launch with verbose logging' to get the most information possible. -
@mediamogul
Well here is some useful info (maybe)
EDIT: Check link again more detailed log now :) -
Nothing that I see. Unfortunately these kinds of issues don't usually present themselves there. Can you post the contents of
/opt/retropie/configs/snes/retroarch.cfg
? -
@mediamogul look at link again
-
@mediamogul said in Input for specific ROM not working:
Nothing that I see. Unfortunately these kinds of issues don't usually present themselves there. Can you post the contents of
/opt/retropie/configs/snes/retroarch.cfg
?Settings made here will only override settings in the global retroarch.cfg if placed above the #include line
input_remapping_directory = "/opt/retropie/configs/snes/"
input_player1_analog_dpad_mode = "1"
input_overlay = ""
#include "/opt/retropie/configs/all/retroarch.cfg" -
OK, it seems to still be loading the Doom config file.
RetroArch [INFO] :: Config: appending config "/home/pi/RetroPie/roms/snes/Doom (USA).sfc.cfg"
Is this another attempt you've made or is it the original?
-
@mediamogul said in Input for specific ROM not working:
OK, it seems to still be loading the Doom config file.
RetroArch [INFO] :: Config: appending config "/home/pi/RetroPie/roms/snes/Doom (USA).sfc.cfg"
Is this another attempt you made or is it the original?
This is another attempt.
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.