Got it. I figured out my issue anyway. Thanks.

@spud11 said in Mapping a keypress to a joystick (Fuse/others):

My runcommand-onstart file is now 113Kb in size, but I've found it has to be devoted purely to xboxdrv and case $2. If I try to add anything else to it with more general application like trying to invoke a bash script unrelated to xboxdrv, runcommand-onstart just doesn't work.

I run 26 systems that make use of xboxdrv, sometimes having several dozen exceptions made for individual games. I've managed to keep the size of my runcommand-onstart.sh down to 39.9k by offloading the execution of xboxdrv itself to separate scripts. All the if/then stuff is still there, but once the conditions are met, it launches an outside script with the xboxdrv command. That may help to alleviate your situation.

@nemnadogg said in Input configuration for each console:

@dankcushions In my case it's a retrolink N64 USB controller. I call it a generic joypad because that's how retropie calls it. The controls are weirdly scrambled for every console. Even for the NES, which is supposed to have the same controls as Emulation Station, yet for some reason is different.

this is the suggested layout for n64 pads: https://retropie.org.uk/docs/RetroArch-Configuration/#nintendo-64

if you bind it to that in initial setup, it will be this layout for all libretro cores, and a number of standalone cores.

I've wanted to change the button configuration that my PS3 controller uses for N64 emulation. But I'm not using one of the libreto emulators, so I'd have to do that in the system files, I believe. And as someone who knows nothing of software, I'm afraid of ruining something.

again, this all happens automatically. if you bind it during initial setup (https://github.com/retropie/retropie-setup/wiki/First-Installation#configure-controllers) to the PS layout (https://retropie.org.uk/docs/RetroArch-Configuration/#ps1) then it should create the relevent config files for mupen64plus standalone.

@xc-3730c as detailed in the read me first page we don't support 3rd party images.

Thanks, I'll dig into it, I forgot to say I'm using Xin-Mo interface

Regarding quake:

Again I'm an idiot. I never checked to see if the +3 and -3 were the actual values. The axis on a PS4 controller is actually + and - 5. So all I had to do was replace the 3s with 5s. Not sure why binding it to 3 made the controller unresponsive though.

input_remapping_directory = "/opt/retropie/configs/ports/quake/" input_player1_r_y_minus_axis = "+5" input_player1_r_y_plus_axis = "-5" #include "/opt/retropie/configs/all/retroarch.cfg"

@jblock22 On the bright side, you do have what sounds like a Pi3, which is a supported computer, you have a cabinet someone built with arcade controls, USB ports, a display, and a nice enough design that you were interested in buying it. A build project with just this hardware alone is a serious undertaking, and getting one that looks nice enough to sell is no small feat. Depending on how it was built, you might also have a controls interface of some kind.

Now, the software is the real questionable part of all of this, but you can easily re image the SD card with a known working image from this website and join the community. You will need to open up your system and do some investigating into what exactly you have which might entail some google searching as well, but once you know what you have and you are willing to work with it, you can probably turn this in to a great system. It will take work and interest, but it can be a fun hobby.

Maybe that is not why you bought it, but there could be a silver lining.

Sounds like you've got everything set up fine in EmulationStation, but not in retroArch.

Make sure you're using "lr-" versions of an emulator, then try going into the retroArch menu (Select+X). You should be able to configure your buttons in there.

@dankcushions oh, I was just looking at the core information when you go into the Retroarch GUI. It's listed as 1.6.7 - FB Alpha v0.2.97.42 928a4d6.

@mitu I've already reinstalled retropie like 4 times and I swear, every time I touch the controls and attempt to enable the analog stick on FF7, the controls just break forever. Even if I don't save anything. It's so incredibly weird.

I've reinstalled for the fourth time and it's working (without analog) on FF7, so I'm just going to not even touch the settings. I really don't want to redo my RetroPie image anymore.

I'm just honestly baffled I'm the only person that's ever had this problem with FF7 on RetroPie.

@rbaker said in 2 player start button?:

What is in your retroarch.cfg file regarding player two controls? Did you add them?

Please answer this ^^^^^^^^^^ the file is located at /opt/retropie/configs/all/retroarch.cfg

do you see entires that reference player two?

input_player2_a = "x" input_player2_b = "z" input_player2_y = "a" input_player2_x = "s" input_player2_start = "enter" input_player2_select = "rshift" input_player2_l = "q" input_player2_r = "w" input_player2_left = "left" input_player2_right = "right" input_player2_up = "up" input_player2_down = "down"

Have you read this with regard to /opt/retropie/configs/all/retroarch-joypads

nor does it offer a solution

It offered possible explanation......."Reading around the inter webs, it seems that that brand of joystick has general issues in Linux of all flavors. It may be that there is no good solution other than getting a tried and tested controller that is known to work well"

Thanks for the continued help...you guys are really awesome!

I mamaged to create an Ssh and used winSCP to visually check the directories but I couldn't find default.cfg file at those locations? Managed to find all my recent Rom cfg files and removed those. Ran a search for the whole sd card for default.cfg and found it relating to lr-mame2003 but with a different pathway(file had unreadable symbols) Removed that and rebooted.
I feel really successful in what I have learned the last few days but my S,Q,W keys are still bound!? I'm using a conventional usb keyboard tonight at home so the issue doesn't seem to be related to my iPac.

My next plan is to change the key definitions in winipac for the iPac board. My player 1&2 pin numbers sw7 & 8's are not used so I will try swapping these keys designations over.
S-L
Q-K
W-C
This will hopefully change the conflicting s q w keys to unassigned pins. L K C don't seem to have any adverse effects in mame. So this might be the solution. On the plus side I've learned heaps the last few days-never thought I'd be able to this stuff

I can map the "parameter" keys 0-9 by hitting "Tab" to bring up the MAME menu, and the game will work fine until I close out and re-open it....then those settings aren't saved. Does anybody else have that problem?

I was trying to accomplish the same thing, but couldn't find anything specific. I found a general solution, but it's a bit ugly and it would be better if lr-mgba could add a turbo button enable/disable core option (similar to fceu). I know this is an old thread but hopefully it helps someone.

Note: If you have a controller without L3 or R3 stick buttons, you can just map all the turbo functions to those buttons from the RetroArch menu and you won't need to do any of this.

Buttons can be completely disabled by changing them to "nul" in the joypad-specific files in /opt/retropie/configs/all/retroarch/autoconfig but that would affect all cores. You can make the change core-specific by making a copy of those file(s) and putting a joypad_autoconfig_dir line in your gba retroarch.cfg:

First, open the RetroArch menu while lr-mgba is running and map the turbo A and turbo B buttons to L2 and R2 (the same as turbo L and turbo R default mapping). This way you'll only need to disable those 2 buttons.

Then make a copy of your joypad configs:

cp -R /opt/retropie/configs/all/retroarch/autoconfig /opt/retropie/configs/gba/retroarch-joypads

In each of the .cfg files in the new /opt/retropie/configs/gba/retroarch-joypads directory (if you have more than one type of joypad), change these lines to disable the L2 and R2 buttons:

input_r2_btn = "nul" input_l2_btn = "nul"

Then add to /opt/retropie/configs/gba/retroarch.cfg

joypad_autoconfig_dir = "/opt/retropie/configs/gba/retroarch-joypads/"

You can comment out that line and re-map turbo A and turbo B to change back to the default behavior later. Be careful not to set any buttons you need to navigate the RetroArch menu to "nul" because it disables them there as well.