Dolphin, the GameCube and Wii emulator - Forums

Full Version: XBOX One S Controller
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
(03-18-2018, 10:04 AM)DaniSahne Wrote: [ -> ]I solved the problem.

After many attempts, this worked for me.

1. Uninstall Dolphin apk from your device.
2. Delete folder "dolphin-emu" from the storage.
3. Install the last working build "dolphin-master-5.0-5681.apk" (that has no axis35+ bug)
4. Start Dolphin
5. Choose "Wii input" then "Wii Remote 1 Controller" then choose "Extension", click on Classic Controller
6. Now map every key and axis
7. Save this
8. Close Dolphin app
9. Uninstall Dolphin app
10. Delete "Dolphin-emu" folder
11. Download latest "Dolphin build"
12. Install
13. Start Dolphin
14. Choose "Wii input" and disable every "Wii Remote Controller", except of "Wii Remote 1 Controller", then choose the "Wii Remote 1 Controller" and choose "Extension" Classic Controller
15. Map your keys and axis

--> and simsalabim, now you can map your axis in the latest build, without axis35+ bug.

I tested it with Luigi's Mansion. For that, I repeated step 14-15 with the "GameCube controller input"

This worked for me, can you confirm this?
My Xbox One S Controller was constantly connected through Bluetooth to my smartphone, during step 1 to 15.

Google Pixel 2.

Greets and sorry for my English

Hello, Thank you for your help with this issue but unfortunately the axis 32+ problem still exists for me on my NVIDIA Shield TV and I followed instructions very closely.

Can a dev chime in in maybe why the following may fix the issue ? 
(03-18-2018, 12:50 PM)Pinchy123 Wrote: [ -> ]Hello, Thank you for your help with this issue but unfortunately the axis 32+ problem still exists for me on my NVIDIA Shield TV and I followed instructions very closely.

Can a dev chime in in maybe why the following may fix the issue ? 


Sorry.  Mmmh. I checked different versions of Dolphin emulator. Then I installed the last one that worked and mapped all buttons and axis. Then uninstall and install the newest one. GameCube controller worked fine.

An interesting thing is: Any controller changes in the Dolphin app does not have an effect on the files in the config folder, and vice versa.

Does every gamepad has the axis 32+ problem?
People have reported the issue with other controllers also within this thread

https://forums.dolphin-emu.org/Thread-every-build-after-5-0-5684-has-problems-binding-inputs
(03-20-2018, 11:25 AM)Pinchy123 Wrote: [ -> ]People have reported the issue with other controllers also within this thread

https://forums.dolphin-emu.org/Thread-every-build-after-5-0-5684-has-problems-binding-inputs

Okay, thank you very much. 

I thought about buying another controller (Ipega or PS4 Controller) but if there are the same problems. I'm just new here, Is it possible to play with the last known working version (5681) any serious gamebreaking bugs?
(03-20-2018, 05:50 PM)DaniSahne Wrote: [ -> ]Okay, thank you very much. 

I thought about buying another controller (Ipega or PS4 Controller) but if there are the same problems. I'm just new here, Is it possible to play with the last known working version (5681) any serious gamebreaking bugs?

While 5681 fixes the Axis 32 issue the sticks still don't bind properly as shown in a video I linked. We just have to hope a dev checks it out when they have time as I have filled an bug on the official page here

https://bugs.dolphin-emu.org/issues/10909
(03-20-2018, 06:19 PM)Pinchy123 Wrote: [ -> ]While 5681 fixes the Axis 32 issue the sticks still don't bind properly as shown in a video I linked. We just have to hope a dev checks it out when they have time as I have filled an bug on the official page here

https://bugs.dolphin-emu.org/issues/10909

I would donate $ 10 directly if this gets fixed  Big Grin

Otherwise it is time to wait.
Pages: 1 2