Controller rumble (Nvidia Shield)

[Moukrea]

Hi ! I just got my hands on the Shield and I'm really enjoying Dolphin on it. I managed to make custom .INI files per games, load custom textures, tweak controllers settings per games... AR codes and so on, BUT! I can't get rumble to work, no matter the controller (Shield Controller or Xbox One Controller)

When I try to map Rumble from Dolphin it says "Device rumble not found". I also tried to edit my goto GameCube controller .INI to "Rumble/Motor = `Motor L` | `Motor R`" (instead of "`Rumble 700`) or set "EmuRumble0" to "= Device 'aa84ea5ff09a6e1945446a5a4fe2e5ca93809493'-Motor L" (the long number being my controller ID, working for any other buttons) into Dolphin.ini but none of these appear to work!

I'm kinda out of solutions for this one, anyone has it figured out?

Cheers

[billygoat]

The Nvidia shield controller doesn't report that it has an available vibrator to the Android APIs. The xbox 360 controller was the only controller of mine that did report it's vibrator during testing.

[Moukrea]

Does that mean that we're out of luck for the Shield Controller?

I wonder something... let's say I want to map the A button... The default profile sets it to "Buttons/A = `Button 0`", in Dolphin.ini (or per game .INI), my A button is "InputA_0 = Device 'devicenamehere'-Button 96" (same for Shield Controller than Xbox One), in Dolphin Windows, A button is "Buttons/A = `Button A`"... They're all different, which make sense on Android as the default settings are for touchscreen and controller settings are set under the [Android] section in Dolphin.ini (or custom .INI). In Windows it's pretty straight forward.

So here's a theory (in order: Android default settings > [Android] section in Dolphin.ini > GCPad settings on Windows):
for A button "Buttons/A = `Button 0`" > "InputA_0 = Device 'devicenamehere'-Button 96" > "Buttons/A = `Button A`"
for Rumble "Rumble/Motor = `Rumble 700`" > "EmuRumble0 = 'devicenamehere'?????" > "Rumble/Motor = `Motor L` | `Motor R`"

I wonder if there is a way to fetch the "button" name for rumble in order to make it work?

[billygoat]

It has nothing about 'mapping' to the controllers rumble, it's the fact that android doesn't detect a vibrator in the controller at all. Trust me, I spent some time trying to figure out why that controller doesn't report a vibrator. Maybe when I have more time I'll revisit the issue.

[Moukrea]

Hopefully there will be a way to assign the controller vibrators to Dolphin directly, maybe without the need to detect it?

[thien2304]

(01-18-2019, 02:09 AM)billygoat Wrote: It has nothing about 'mapping' to the controllers rumble, it's the fact that android doesn't detect a vibrator in the controller at all. Trust me, I spent some time trying to figure out why that controller doesn't report a vibrator. Maybe when I have more time I'll revisit the issue.

Sorry to bring up an old thread... but have you guys happened to figure out any solution for this? 
I'm also looking into the vibration issue and this thread is the only one that is close enough to what I'm trying to find. (In fact, I have just created a forum account only for this :v) 
In my opinion, I think it worths a try to test out what @Moukrea suspected.
Could @billygoat provide us an dolphin.ini file with the xbox360 controller's vibrators fully working to see if we can find out the proper name for the controller rumble in it?