Thanks for pushing me to try from the ground, using a fresh/official/empty image.
I've installed the retropie-buster-4.7.1-rpi2_3.img available on your download page here, add the rom and... no more controls issue! :-) Damn! I spent days on this issue... and it was so easy :-)
Long live to Retropie :-)
@buzz oh wow I would never have considered the multi tap options as they've never affected it before! That worked better than expected, now I've got analog on psx that I've never ever been able to get working. Thanks for your help!
Ok, will sort the Logging...my bad, thought I did it right🙄
Ok on adding 'new' P1 to retro.cfg. I must admit (from memory on the multiple tries) that, after installing as 'Gamepad' thru ES, that it did/does correctly show up in autoconfig directory 'but' (again memory) the joystick didnt work. I then added the 'js0' line in retro.cfg and it started working. Hence why I put in/tried to get as far as I did.
Anyhoo. I'll sort logging 'first' and if we can fix from there...great, if not then i'll do whatever you suggest/remove new 'P1' etc.
The quick menu does not let me remap the controls, but the retroarch menu does. There is one problem with that, though: it uses the right analog as the c-pad for the n64, and there is nothing that the d-pad in retroarch does.
That's not needed, since PikeyD doesn't look like it uses python. There's - similarly - a Linux kernel module named uinput, that I think it's used, but it's loaded by default on a RetroPIe image (you can check /etc/modules).
From what I understand, the version of DraStic that we have access to is just a generic ARM build and isn't well optimized. It works ok on previous pi models under the legacy Vc4 drivers, but using fkms on the pi 4 it seems to have issues.
ps3 controllers are good, windows drivers used to be hard to install.
My problem with arc arena, I tried the usual things including HLE bios but I didnt get a full reset for it to work because of autoload. I didn't think of deleting the config, doing so changed the default system directory to the content folder so no BIOS was found and so it loaded the HLE and worked. System Directory was the first setting I changed back, and the controller stopped working when it loaded the SCPH bios again. Anyways thanks.
@retropieuser555 I notice in your picture that the User 1 Device Type is set to Sinclair 1 Joystick. I tested this setting and Hen-House Harry moves to the left if I press the B button and to the right if I press the X or Y button even though I have nothing mapped to those buttons. Could you try selecting the User 1 Device Type to the Cursor or Kempston joystick?
From a terminal please do rm /opt/retropie/configs/snes/retroarch.cfg or delete the file over windows networking
Go to Emulation Station -> RetroPie and do Update RetroPie-Setup script
Go to Manage Packages -> Main section > lr-snes9x-next - and choose "Update from binary"
and all should be good.
@mitu I redid the controls again for the "v" key (from everything I can tell this is not used elsewhere). This time I used the in game menu with the tab key. Still the right direction does not work. Also I have several existing directional buttons mapped to keys that are used for other functions but all of those keys are functioning normally.
ive hit this as well and was confused. i see auto stuff and explicit buttons, so its confusing. I checked the input bindings and saw some map to auto and some map to explicit buttons, so i'm assuming this means it depends on the input settings--this mostly works but ive found a few situations where it isn't working, so im not sure.
Actually, I think I did update it and that caused some of the issues again with it not working properly. It's working well enough as is so I'm a little leery of messing with it at this point. I don't have any games that require thumbstick or trigger input so I'm happy enough with the good D-pad.