@mitu Cool, thanks! That puts my mind at ease.

Hi @Ruidog

I got some troubles too with two DragonRise controllers and a PI3b+.
Look at this thread, it helped me:

https://retropie.org.uk/forum/topic/9259/so-close-dragonrise-arcade-sticks-and-button-sets-joystick-on-a-player-reverses/6

@iandaemon Thanks, done!

Does this happen even outside of EmulationStation ? If you exit EmulationStation and move your joystick left, does it restart the Pi ?

@mitu That did it! Thank you!!!

update: I think I found the main problem with my config. I installed the joystick selection tool
https://retropie.org.uk/forum/topic/1167/here-is-a-way-to-select-joystick-for-players-1-4-global-or-emu-specific
to check what's been set up for the players.

alt text
Yeah, okay... ;-) No idea what caused that configuration...
I moved The DragonRise Controller to P1 now and set P2-P4 to ** UNSET **

Now, in lr-genesis-plus-gx all keys are working as expected, Retroarch GUI is showing up also! :-)

@George-Spiggott said in Blood Money AmiBerry Control issues:

I have a PS3 pad in port 1 set to Joystick. I have no custom inputs defined. You can save settings in the configurations tab in Amiberry. You may need to save settings for for several of your games.

Hope this helps.

Hey George, thanks for that tip. Now got Blood Money working with my Dragonrise controller. So massive thumbs up for your help.

I know this topic is really old but i had the same problem myself and solved it. I noticed that the button mappings in RetroArch interfered with MAME 2010's mappings. One button could mean one thing in RetroArch but another in MAME so RetroArch would say to MAME something like - Hey! We also want to press this button!

What i did was that i blanked out the button mappings in RetroArch so they're seen as ---. After this my MAME mappings worked straight away. Then saved it as a content (game) specific configuration.

@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).

I installed and tried hypseus, it solved the problem! My DragonRise controller works well again. Thank you!

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)

@anasazi29

I just want to say that....two years later...this thread is still helping people. Easily spent hours hitting my head against a wall until reading this thread.

Thank you :)

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.