JordanBenson1029
commented
1 year ago Hello
I did actually sort my issue out. Meant to reply to this.
I've attached a screenshot of the setting that was causing the issue I had. Turning this off solved the problem and retroarch then recognised my controller straight away. Mapped without issue.
Let me know if this resolves your problem. If not, I'll try assist.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: Sara Sinback @.> Sent: Tuesday, November 14, 2023 6:35:35 PM To: libretro/RetroArch @.> Cc: JordanBenson1029 @.>; Author @.> Subject: Re: [libretro/RetroArch] Only D-Pad won't map Android (Issue #15487)
Having this issue as well. I checked that accessibility services for all apps were turned off since some people online say that can interfere with this. For me, the d-pad works fine with the Android UI (for navigating menus, etc), and until I saw OP say things worked fine out-of-the-box with another emulator, I was thinking Android may be intercepting the input at a system level that might require root or adb or something to work around.
I have an app called Button Mapper which I tried to use to remap the d-pad input. It could intercept the d-pad input enough to activate whatever action I set them to, but I saw they were still interacting with the Android UI first before they could make their way to doing the Button Mapper action.
I can remap analog sticks to the d-pad successfully, but I think using an analog stick for a d-pad is awkward so it would be cool if there was a fix/workaround for this.
I have Android 13.
— Reply to this email directly, view it on GitHubhttps://github.com/libretro/RetroArch/issues/15487#issuecomment-1810907453, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBKO52663TCH3BLRJ7MUFVLYEO2XPAVCNFSM6AAAAAA2NBFKAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQHEYDONBVGM. You are receiving this because you authored the thread.Message ID: @.***>
jj9189
I've been using my Ipega 9087s for over a year without issue with Retroarch. All of a sudden when starting after a month of not using it with Retroarch, when pressing any button that is not the d pad, it assigns correctly my ipega 9087s correctly to port 1. The moment I touch the dpad, it says Virtual configured on port 2. When playing any game, all buttons work, regardless of core in use except the dpad. Even when I disable the port in 2. Nothing works.
When I try to map the controls manually, I see the config as per attachment.
It doesn't allow me to map the dpad. It doesn't even recognise an input.
Initially, I though the dpad was just broken, however, this is not the case. In AetherSX2, which is a superb PS2 emulator for android for those reading that are interested, no shade on Retroarch, the d pad and remapping of the dpad works no issues whatsoever. Therefore it would seem to be isolated to Retroarch.
Please help peeps. I don't want to have to use another emulator to PS1 and older.