(04-08-2016, 12:08 PM)ETAPRIME Wrote: [ -> ]Having the same problem i tried editing the my INI but it still wont work. is there anyone who has a working controller ini i could have? older builds crash when i select setting.
i tried to edit my Dolphin.ini And My GCPadNew.ini
That is very weird that the above doesn't work, I will upload my ini tonight, nothing special but it works.
(04-15-2016, 10:16 PM)Emexrulsier Wrote: [ -> ]That is very weird that the above doesn't work, I will upload my ini tonight, nothing special but it works.
I'm in the exact same boat as ETAPRIME. I've tried the below in the Dolphin.ini and GCPadNew.ini files (separately and at the same time to no avail). I even tried downloading an older version, setting up the controller, and jumping back to the newer version with the dolphin.ini file and still nothing. I glanced through the source on github and it seems the GCPadNew file that the desktop versions are using now (and that Android seems to partially implement...?) are in a different format than the ini code posted above. I wonder if the build ETAPRIME and I have tried are just broken? I did try using the "new" format shown in the source code's Source/Android/app/src/main/assets/GCPadNew.ini file, but that did not work at all. What version are you running that works for you?
I should note that when I do NOT have the [Android] mapping, pressing the "B" button on the shield controller pops open the side menu, while when the [Android] mapping is present, this is not the case. Anyway, I'd be interested to see your working ini file as well, and maybe get the same build revision you're running. Thanks in advance Emexrulsier!
Firstly, I thank you guys so much for working on this fine emulator. You rock just for that.
I have an Nvidia shield android TV. I am currently trying build 4.0.9328 for Andriod.
I understand the UI for configuring the keymaps is being reworked.
For those (Emexrulsier) that have had luck editing the .ini files to set up the mappings, can you post your .ini file contents? I saw the one you posted above. Which file is that? I have seen 2 .ini files mentioned in this thread.
Also, if you say that button mapping used to be working, can you reference a certain build number that I can try to achieve the same results?
Thanks a bunch!
(First post!)
(05-18-2016, 01:34 PM)Comrade Wrote: [ -> ]Also, if you say that button mapping used to be working, can you reference a certain build number that I can try to achieve the same results?
The one before
https://github.com/dolphin-emu/dolphin/pull/3547
So 4.0-8766-g3f5f523 was the last working revision.
I have had some limited success mapping 3 controllers with the following in my dolphin.ini:
Code:
[Android]
ScreenControls = False
InputA_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 96
InputB_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 97
InputX_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 99
InputY_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 100
InputZ_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 22-
InputStart_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 108
DPadUp_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 16-
DPadDown_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 16+
DPadLeft_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 15-
DPadRight_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 15+
MainUp_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 1-
MainDown_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 1+
MainLeft_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 15+
MainRight_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 15-
CStickUp_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 14-
CStickDown_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 14+
CStickLeft_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 11-
CStickRight_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Axis 11+
InputL_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 102
InputR_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 103
InputA_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 96
InputB_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 97
InputX_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 99
InputY_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 100
InputZ_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 22+
InputStart_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 108
DPadUp_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 16-
DPadDown_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 16+
DPadLeft_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 15-
DPadRight_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 15+
MainUp_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 1-
MainDown_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 1+
MainLeft_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 0-
MainRight_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 0+
CStickUp_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 14-
CStickDown_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 14+
CStickLeft_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 11-
CStickRight_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Axis 11+
InputL_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 102
InputR_1 = Device '8126b3c1c5d60105c2e1f2d1658dfd8db0f9720e'-Button 103
InputA_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 96
InputB_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 97
InputX_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 99
InputY_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 100
InputZ_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 22-
InputStart_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 108
DPadUp_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 16-
DPadDown_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 16+
DPadLeft_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 15-
DPadRight_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 15+
MainUp_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 1-
MainDown_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 1+
MainLeft_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 0-
MainRight_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 0+
CStickUp_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 14-
CStickDown_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 14+
CStickLeft_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 11-
CStickRight_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Axis 11+
InputL_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 102
InputR_2 = Device '55a2f3ac6ee48d8c5001798eea99cb24dae91703'-Button 103
Unfortunately I still cannot start any of the New Super Mario Bros. games as they want me to input button 1. In my dolphin folder on Android there is a file called WiimoteNew.ini, and the following is an extract from it:
Code:
[Wiimote1]
Device = Android/4/Touchscreen
...
Buttons/- = `Button 102`
Buttons/+ = `Button 103`
Buttons/Home = `Button 104`
Buttons/1 = `Button 105`
Buttons/2 = `Button 106`
Trying to use this to guess how to map buttons for 1 and 2 I added the following to dolphin.ini:
Code:
Buttons/1_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 96
Buttons/2_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 97
Input1_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 96
Input2_0 = Device 'a691ea53a0f5aabd5e2dd0674f6ce7c0c6aca61f'-Button 97
Unfortunately that made no difference.
Does anyone know how to map Nvidia Shield Controller Buttons to Wiimote buttons 1 and 2?
(05-18-2016, 06:47 PM)degasus Wrote: [ -> ]The one before https://github.com/dolphin-emu/dolphin/pull/3547
So 4.0-8766-g3f5f523 was the last working revision.
Hi guys
I have been struggling with my Shield controller for a while now until i stumbled across this thread
I am playing the Super Mario Bros and i haven't tested any other games
I tested the build above and it works marvelously. I am still ironing out the small details. NOT all the controls seem to be working, however the main ones are ok and the game is playing fluently with no hiccups
After installing Dolphin go into the settings, Control bindings and select the Wiimote1 then simply map the controls however you want. I used the Shield remote to select them one by one but should be working if you have a keyboard. As long as you can navigate the menus.
Ex: selected DpadUp, a popup window comes on and asks "press the control for DpadUp".
Went back a couple of times and re-adjusted them a little bit.
The shake i tried mapping on the left stick and seems to be working if i move the stick quickly up and down
When exiting the game you have to exit Dolphin not the game or else Dolphin will crash / So bring the Dolphin menu to the left and press exit there.
I don't see why it wouldn't work for anybody else.
Good luck
Cheers!

Me 2.
Shield Android TV + Dolphin without controller configuration.
Is there some hope?
this is a simple way to map your controller
1-install the newest build of the Dolphin
2- download the following apk and install it
https://drive.google.com/file/d/0BwJWBP1RgpGYY1pXN2pLdnRUZlk/view?usp=sharing
this is the old version of the dolphin that accept mapping (with deterrent name and icon [color=#ff66cc]
Color[/color])
3- after mapping open the new dolphin build and change the controller setting to Emulated
Now Enjoy
