basic 2 player support not working correctly
@puppetj It's what I suggested in my previous post:
Finally, you should run the games with verbose logging and show us the contents of the file
i dont undetstand what this means...
When launching Libretro cores (those prefixed by lr-) the Runcommand launch menu presents the option to Launch with verbose logging, let alone half of the other stuff on that page for logging
@puppetj Ah, that was a quote from the linked artikle. I thought those were all your own words and wondered why you don't just select verbose logging from the menu you already seemed to be in. You should put a
>before quotes to mark them as such (like I did below).
If you don't know the Runcommand menu, the first paragraph of the article in my link tells you what to do:
Each time you load a ROM there is an option to open what is called the Runcommand Launch Menu. This is accessed by pressing any button on a controller (the bottom face button is recommended as to not accidentally change anything) or pressing any key on a keyboard, while the prompt in the image below is displayed or right after a launching image disappears, if you have those set up.
If you do that, you'll get a menu with the option Launch with verbose logging.
That said, we should first ensure that you can get to the logfile
/dev/shm/runcommand.logafterwards to show it to us. You can get it via SSH and a program like WinSCP like @mitu told you above, or, if you can connect a keyboard to your Pi, I can tell you a handful of console commands to copy the file to a directory that you can already access, like your roms directory.
The former takes a few more steps to setup, but could be handy for more maintenance in the future. The latter should be easier, but you'll learn not much more than to type some commands which someone else tells you. So what should it be?
@Clyde yeah i can hook up a keyboard, let me know about the commands.
- Run a game that has the controller problems with verbose logging, and exit it again.
F4in Emulation Station to get to RetroPie's command console.
cp /dev/shm/runcommand.log /home/pi/RetroPie/roms. This will copy the log file to your roms directory which I guess you have access to.
exitto return to Emulation Station.
You should then upload the file to https://pastebin.com/ and give us the link.
If there are any questions or obstacles, let us know.
@puppetj According to the log, there's 2 controllers:
Player 1 is the Logitech Cordless RumblePad 2 - this is the controller which can use the hotkeys, including Hotkey + Start to exit the emulator.
Player 2 is _THRUSTMASTER FireStorm Dual Power _.
... [INFO] [udev]: Keyboard #0 (/dev/input/event0). [INFO] [udev]: Plugged pad: Logitech Logitech Cordless RumblePad 2 (1133:49689) on port #0. [INFO] [udev]: Pad #0 (/dev/input/event1) supports force feedback. [INFO] [udev]: Pad #0 (/dev/input/event1) supports 16 force feedback effects. [INFO] [udev]: Plugged pad: THRUSTMASTER FireStorm Dual Power (1103:45824) on port #1. [INFO] [udev]: Pad #1 (/dev/input/event4) supports 0 force feedback effects. [INFO] [Joypad]: Found joypad driver: "udev". ...
@mitu well i was playing double dragon as you see in the log and the hot key didnt work, and had to press escape on the keyboard to go back to the station menu
@puppetj In this case, check the controller configuration file - it should be in
\\retropie\configs\all\retroarch-joypads, named probably
Logitech Logitech Cordless RumblePad 2.cfg. Does it have a hotkey defined ? You can post its contents here in the topic.
@mitu its defined, it worked in a few games, but not the double dragon game.
@puppetj Does it work in any NES game ? You may have saved a configuration just for the NES system and that changed the input handling.
@mitu no i didnt touch the nes cfg, it seems to hand a mind of its own, i had the same thing happen with snes 3 ninjas kick back no working hot key
Then maybe the configuration is global (for RetroArch). Can you post the following files' contents on pastebin.com and link it:
@puppetj The conf files are ok - I don't see any remapping or controller index switching.
what could be the problem then?
@puppetj let’s see the controller configuration file as mentioned before
@dankcushions i dont understand
@clyde i dont know if this is a hint of the issue, but as the other person said, about the usb ports having order and controller 1 needs to be in usb port 0 and controller 2 needs to be in usb port 1, i had controller 1 in usb port 0 and controller 2 in usb 2 and they worked fine.
input_device = "Logitech Logitech Cordless RumblePad 2"
input_driver = "udev"
input_r3_btn = "11"
input_l_btn = "4"
input_up_axis = "-1"
input_left_axis = "-0"
input_select_btn = "8"
input_r2_btn = "7"
input_l_y_plus_btn = "h0leftanalogdown"
input_right_axis = "+0"
input_l2_btn = "6"
input_l_x_minus_btn = "h0leftanalogleft"
input_l3_btn = "10"
input_r_btn = "5"
input_l_y_minus_btn = "h0leftanalogup"
input_y_btn = "0"
input_x_btn = "3"
input_down_axis = "+1"
input_start_btn = "9"
input_b_btn = "1"
input_a_btn = "2"