I am not able to configure the control sticks and the d pad.
I can assign buttons to the configuration of the sticks, but not the directions axis of the sticks.
I can navigate within the menus of dolphin with the sticks and the d pad...
Moving to the Android subforum.
(03-31-2021, 03:59 AM)Bantumi Wrote: [ -> ]I am not able to configure the control sticks and the d pad.
I can assign buttons to the configuration of the sticks, but not the directions axis of the sticks.
I can navigate within the menus of dolphin with the sticks and the d pad...
I have this exact issue!
Do you or anyone else knows how to fix this?
(03-31-2021, 08:07 PM)P0nch0 Wrote: [ -> ]I have this exact issue!
Do you or anyone else knows how to fix this?
Nope ?
Any update on this? I have the same issue, with any controller
(04-24-2021, 02:48 AM)ssmith Wrote: [ -> ]Any update on this? I have the same issue, with any controller
not on my side
I am having the same issue with my 8bitdo SN30 pro bluetooth controller. The d-pad and analog sticks are not recognized during mapping. They used to work just fine until recently, I think it stopped working after my tablet received the Android 11 update.
Previously the controller mapping woukd work and properly identify the 8bitdo controller but now I can only map the buttons and Dolphin calls it "virtual: button" unlike before where the mapping would show the controller name.
Any idea how to fix this? Cannot use dolphin in this current state. Thanks.
(04-30-2021, 01:16 PM)Bigcletus Wrote: [ -> ]I am having the same issue with my 8bitdo SN30 pro bluetooth controller. The d-pad and analog sticks are not recognized during mapping. They used to work just fine until recently, I think it stopped working after my tablet received the Android 11 update.
Previously the controller mapping woukd work and properly identify the 8bitdo controller but now I can only map the buttons and Dolphin calls it "virtual: button" unlike before where the mapping would show the controller name.
Any idea how to fix this? Cannot use dolphin in this current state. Thanks.
This should be fixable by disabling accessibility services in Android's settings. This is a new problem in Android 11.
(04-30-2021, 03:17 PM)JosJuice Wrote: [ -> ]This should be fixable by disabling accessibility services in Android's settings. This is a new problem in Android 11.
That worked! Thank you so much! I think it was also related to an app installed called sMouse. I disabled that and was able to properly map the controller.
Edit: Not out of the woods just yet... the controller will map now but it doesn't function during game play. Am I missing something else? Everything in accessibility service is disabled. Other Android apps are working with the controller, just Dophin is not. Thanks again.
(04-30-2021, 01:16 PM)Bigcletus Wrote: [ -> ]I am having the same issue with my 8bitdo SN30 pro bluetooth controller. The d-pad and analog sticks are not recognized during mapping. They used to work just fine until recently, I think it stopped working after my tablet received the Android 11 update.
Previously the controller mapping woukd work and properly identify the 8bitdo controller but now I can only map the buttons and Dolphin calls it "virtual: button" unlike before where the mapping would show the controller name.
Any idea how to fix this? Cannot use dolphin in this current state. Thanks.
I am having a similar issue with 8bitDo SF30 Pro. When i map the right analog stick it goes like that:
C-Stick up: 8Bitdo SF30 Pro: Axis 14+
C-Stick Down: 8Bitdo SF30 Pro: Axis 14+
C-Stick left: 8Bitdo SF30 Pro: Axis 11+
C-Stick right: 8Bitdo SF30 Pro: Axis 11+
The axis are wrong even if i press correctly and C-stick doesn't work in any directions. The rumble function doesn't work but my controller have support for it too. All other buttons works fine.