There was a problem with mame2003 and plus that required the old mame2003/cfg (mame input files files need to be deleted). There are other options if that doent work for you. The only other time ive seen this is on a controller like an ipac thats a keyboard encoder. In this case you change the input type to keyboard only or press the game focus mode button.

@mitu @grant2258 thank you both for all your help. After I couldn’t get any of my controllers working, I imaged a new SD card and started fresh. I can successfully use the Dragonrise controllers. I’m thinking the problem may be permissions related as for some reason the default account (pi?) May have lost permissions to write config files. I’ll look into it. Thanks again, PacRat

@TimeDoctor said in Control works inside ES, but not in-game: None of this would be a problem if the ES input configuration were passed to retroarch properly. My suspicion is that you've reset the RetroArch configuration and it doesn't look for the gamepad auto-configuration file in the folder where Emulationstation saves it (/opt/retropie/configs/all/retroarch-joypads).

@grant2258 Oh my God!. Just found this post after a long time trying to get my DragonRise arcade controller to recognise left & right. Ran the above and it worked immediately. Thanks you so much :-)

Hi, firstly, the thing of DragonRise Controller is weird, I have agamepad and is also recognizable as a DragonRise, but I guess it happens when the controller s not officil. Second, arcade joysticks (The ones you bought) are not analog, they are 8-way sticks. Anyway, there are a few N64 games that work with the pad, like Kirby one.

@mediamogul No, the joysticks have digital microswitches. I noticed an error in my reasoning: The buttons have nothing to do with the problems, as their ports are generating type 1 events. Only the joystick ports on the decoder board (four for each joystick, one per microswitch) generate type 2 events. That said, the joysticks' microswitches are connected to the ports for axis number 0+1, whereas the ghost inputs only come from axis number 2, which nothing is connected to. I tried to set the dead zones of axis 2 on both joysticks to its whole range of -32767 to 32767, hoping that would lead to the driver ignoring them alltogether. After that, jstest doesn't show any input from them anymore, but the screensaver still recognizes some input in irregular intervals and quits back to ES. $ jscal -s 7,1,0,127,127,4227201,4194176,1,0,127,127,4227201,4194176,1,10,-32767,32767,2147483647,2147483647,1,0,127,127,2147483647,2147483647,1,0,127,127,2147483647,2147483647,1,0,0,0,2147483647,2147483647,1,0,0,0,2147483647,2147483647 /dev/input/js0 $ jscal -s 7,1,0,127,127,4227201,4194176,1,0,127,127,4227201,4194176,1,10,-32767,32767,2147483647,2147483647,1,0,127,127,2147483647,2147483647,1,0,127,127,2147483647,2147483647,1,0,0,0,2147483647,2147483647,1,0,0,0,2147483647,2147483647 /dev/input/js1 The part for axis 2 is 1,10,-32767,32767,2147483647,2147483647, see jscal's manpage for more information. I got this idea after some research, from these two sites: https://ubuntuforums.org/showthread.php?t=1079284 (a similar problem to mine) https://blog.gimx.fr/joystick-calibration-in-gnulinux/ (it explains the working of jscal -s in some more detail)

@lonestarbarf Wo so cool guys you saved many hours to me! My daughter will be able to play this week end, thx so much. once joystick physically reversed it works. thx

Well you could: Open the retroarch.cfg file of the emulator you're using and see if there is any button configuration in the file. Open the joystick configuration file of your controller and see if the key ID of the button down isn't being used by an another variable. The button could simple be broken.

So just to confirm, this is still not working? I have the same exact setup and the issue I am having is my button mapping changes for player 1 but not player 2. Player 2 is working perfect. The config file is accurate and the lsusb command shows them both: Bus 001 Device 005: ID 0079:0006 DragonRise Inc. Generic USB Joystick Bus 001 Device 004: ID 0079:0006 DragonRise Inc. Generic USB Joystick My config file is there too: /opt/retropie/configs/all/retroarch-joypads DragonRise Inc. Generic USB Joystick .cfg input_device = "DragonRise Inc. Generic USB Joystick " input_driver = "udev" input_l_btn = "2" input_load_state_btn = "2" input_start_btn = "8" input_exit_emulator_btn = "8" input_up_axis = "-3" input_a_btn = "5" input_b_btn = "4" input_reset_btn = "4" input_down_axis = "+3" input_r_btn = "6" input_save_state_btn = "6" input_r2_btn = "7" input_right_axis = "+0" input_state_slot_increase_axis = "+0" input_x_btn = "1" input_menu_toggle_btn = "1" input_select_btn = "9" input_enable_hotkey_btn = "9" input_y_btn = "0" input_left_axis = "-0" input_state_slot_decrease_axis = "-0" input_l2_btn = "3" Any thoughts?

@ULTRA-MAGNUSS not worried about credit at all glad its working for you unfortunately thats the way these games are mapped on the hardware youll find the same issue with a lot of flying games down goes up.

@jamesarm97 I think I've got what you're saying. And I think it's simple to solve. Let's consider that the rotated one is the player2, then your retroarch-joypads/DragonriseInc.GenericUSBJoystick.cfg will look like this: # ... some configs ... #input_up_axis = "-1" #input_down_axis = "+1" #input_left_axis = "-0" #input_right_axis = "+0" input_player1_up_axis = "-1" input_player1_down_axis = "+1" input_player1_left_axis = "-0" input_player1_right_axis = "+0" input_player2_up_axis = "-0" input_player2_down_axis = "+0" input_player2_left_axis = "-1" input_player2_right_axis = "+1" # ... remaining configs ... I mean, you have to hardcode the rotated axis for the player2. I'm not sure if these numbers will work for you, but I hope you get what I'm trying to say. ;-) Cheers!

The fix has now been applied: https://github.com/raspberrypi/linux/issues/1755

@gazi It appears solved: https://retropie.org.uk/forum/topic/5962/dragonrise-usb-driver-issue

i think i also have this issue! any help?