@edmaul69 said in lr-FBA controller config:

@tr3v0r when you set up a 6 button layout it is supposed to be set up as

LXR
YBA

yes there is massive confusion at the moment with 6 and 8 buttons.

the Megadrive/Genesis (6 Button) layout you where using is probably for the megadrive emulator its no good in other cores. Keep in mind to remap your genesis core if your using this as a global

@jenny18 a spinner automatically detects as a mouse. You shouldnt have to do anything to get it working. In a mame game you might have to enable spinner/trackball/mouse in the game. A spinner never will detect as a controller.

@meleu No, I think it's still needed :). In this case, the modification in RetroArch (gamepad order is the same as connection order) helps, but it's not helping people with gamepads that are always connected or the ones that have cabinets and wish to plug in a controller and have it as P1.

@jthomas5150 The RetroArch version (1.7.3) that is installed with 4.4 now includes a patch for the issue, so the script should work fine.
I would make a backup of your old SD card image anyways.

@jdog35421 said in Controls mess up after I open a game.:

When I restart my pi by turning it off

are you pulling the power cord? if so, you could be corrupting your card!

@813_alex That stick, like any arcade one with microswitches is quite noisy (but I like that). Also the stick itself (spring ?) makes noise when moving it. On the other hand that's a real 4-way ;-)

try twisting your flat cable round thats usually the culprit

@jjr71 See point 5 of https://retropie.org.uk/forum/topic/3/read-this-first

I’m starting to think it may have something to do with the micro switches. The switches only have two prongs. One for ground at the bottom and only one additional prong. I’m thinking this makes it always open??

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

Blimey, blimey, blimey, blimey, blimey and blimey again! I swear that I'm not a paranoid schizophrenic, but I deleted the config files in /opt/retropie/configs/mame-mame4all/cfg/ rebooted a few times and the erroneous behavior was gone and my settings were not gone even though I deleted the settings files...

Now for that weird behavior from pcsx-rearmed. Maybe that will disappear itself too.

@kingrun Glad to hear it's all good now.

@lukabrazi the servo stik is the sanwa JLW just has the side car servo included. I bought just the servo by itself to install on a JLW. I was able to get the servo working in both windows and linux (from katie snow) as well as just using a switch on the top of the CP (this requires flashing the servo though and it will never work with software after that!).

I remember, when reading about xboxdrv that it had a specific option for this problem. Would you be able to use xboxdrv with your current controls to work around the problem

https://github.com/RetroPie/RetroPie-Setup/wiki/Universal-Controller-Calibration-&-Mapping-Using-xboxdrv#2d-restricting-directional-control-to-four-ways

Thanks old post. I was stumped for days. Tried this method and works! Thank you!

@alturis

To my knowledge you can't, but I haven't put a lots of time into experimenting either. Acceleration, for example, seems to only affect the max speed. If you continue to test and find out something different, I'd be very interested.

I think I have now resolved this issue - for anyone else who has suffered from similar woes, I quit out of Emulation Station and did

sudo rpi-update

to update the firmware. Now the left and up axes seem to be recognised properly - watch this space to see if I have other problems! (I'll bet good money that I do lol)