Dolphin, the GameCube and Wii emulator - Forums

Full Version: Controller mapping returning for Android?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5
Grabbed latest build 1418 and it works fine with the mapping intact.
On version 5.0-1354 (when bindings was re-implemented) and every other build since, going to the GC controller bindings menu immediately crashes the app on my SHIELD TV and boots me back to the desktop.

Anyone know why this might be? It's odd that it works fine for some people and not for others. it's not like with PCs where everyone has different specs: Shouldn't every SHIELD TV respond the same?
(12-06-2016, 01:51 AM)KingChublis Wrote: [ -> ]On version 5.0-1354 (when bindings was re-implemented) and every other build since, going to the GC controller bindings menu immediately crashes the app on my SHIELD TV and boots me back to the desktop.

Anyone know why this might be? It's odd that it works fine for some people and not for others. it's not like with PCs where everyone has different specs: Shouldn't every SHIELD TV respond the same?

Could you try deleting your Dolphin.ini (located in dolphin-emu/Config) and clearing app data? Make sure to run a game to regenerate the ini before trying again.
5.0-1418 worked for my the the axis positives and negatives on d-pad, c-stick and joystick were all inverted.
(12-06-2016, 04:17 AM)SeannyM Wrote: [ -> ]Could you try deleting your Dolphin.ini (located in dolphin-emu/Config) and clearing app data? Make sure to run a game to regenerate the ini before trying again.

Worked like a charm. Thanks mate
(11-30-2016, 03:42 PM)nitro001 Wrote: [ -> ]Hi, I finally got back to being able to test this.  I downloaded the latest build from the development site: 5.0-1389 which included your changes as well as a few others after, although one of those looked like an input redesign from someone else for MacOS, not sure if it affects your code.

The reason I say this is when I loaded it, the Wii Mappings went fine, although I made one mapping that I didn't want and couldn't find a way to clear it.  When I tried to click the button do clear it assigned that button as the mapping. I am trying this on a Shield TV with the Shield Game Controller.

When I tried to map the GameCube controls, the emulator crashed just as it did when I tested the PR build for the Wii Controls.  I see a GCPadNew.ini file there that is close to the size that the old one was.

I completely removed the old install and configs and started from scratch, backing up my config first.

I also noticed that the WiimoteNew.ini file generated from the Wii Mappings has Wiimotes 1 - 4 in the file even though I only mapped Wiimote 1. And all 4 are identical in their mappings, besides the Device line.  They also include mappings for buttons I didn't assign, such as the stuff for Drums or Guitar.

Finally, while this isn't an issue with the application, is it possible to implement the sideways wiimote setting in the mapping?  Perhaps a popup with True/False Toggle?  It would enable the Options/Sideways Wiimote = 1.0000000000000000 option in the WiiMoteNew.ini file.  When I add that line under a Wiimote entry, the Up/Down, Left/Right get flipped like you were holding the WiiMote sideways like you need for Super Mario Wii.

Thanks, Nathan

@SeannyM,
I wanted to build the Android product to try to add this feature to the settings since I had not heard back. I know this is kind of hijacking the thread, but I loaded Android Studio, pulled the project from GIT, but when I build it to test, I get a INSTALL_FAILED_NO_MATCHING_ABIS error.  Have you seen this error? I am not sure if I need to use an ARMv7, ARM64 or X86 Emulator for testing the build.  Thanks.
(12-08-2016, 07:52 AM)nitro001 Wrote: [ -> ]I wanted to build the Android product to try to add this feature to the settings since I had not heard back. I know this is kind of hijacking the thread, but I loaded Android Studio, pulled the project from GIT, but when I build it to test, I get a INSTALL_FAILED_NO_MATCHING_ABIS error.  Have you seen this error? I am not sure if I need to use an ARMv7, ARM64 or X86 Emulator for testing the build.  Thanks.

64-bit ARM is required for Dolphin on Android. I recommend only running it on a real device, not emulators.
gamecube control stick on wii games do not work well. can only go up or down but can not in all directions, if I want to start a game and start on the right side of the gamecube controller can stick to the right to start, other controllers do not react only with some game need to use a gamecube controller stick, android platform, please help and please correct it thanks! Revision 5.0-1444
(12-08-2016, 07:55 AM)JosJuice Wrote: [ -> ]64-bit ARM is required for Dolphin on Android. I recommend only running it on a real device, not emulators.
And because of the lacking OpenGL ES 3.0 compatibility of those emulators.

Feel free to ask me for help on IRC: #dolphin-emu @freenode
Ive got a similar issue with my ipega 9023 controller.  I can map controller buttons however c sticks are either opposite directions or don't. Work at all
Pages: 1 2 3 4 5