Rumble option not showing Motors

[afro_Jezuz]

As in the title, I cannot get rumble to work and now I'm trying to see if it's client-side.

Is there a driver, code or general fix I can use?

I'm using 5.0-14790 and the rumble selection is empty regardless of the controller or adapter I plug in (my 5.0 doesn't have it either.)

The adapter I'm now using is the YCCteam WH-046 4-port adapter w/ dedicated vibration USB & Official Wired Xbox 360.

   

[mbc07]

Does your adapter has a Xbox mode? Switch to that mode and access the controller via XInput instead of DInput. Most controllers doesn't expose the rumble when accessed over DInput...

[afro_Jezuz]

(12-24-2021, 07:16 PM)mbc07 Wrote: Does your adapter has a Xbox mode? Switch to that mode and access the controller via XInput instead of DInput. Most controllers doesn't expose the rumble when accessed over DInput...

It is a 4-port GC>USB adapter made for Switch/WiiU & PC. 

It has a 2-option toggle on the back for PC and Sw/WU, respectively.

[mbc07]

Hmm, okay. Put it on Switch/Wii U mode and follow that guide...

[afro_Jezuz]

(12-25-2021, 08:01 PM)mbc07 Wrote: Hmm, okay. Put it on Switch/Wii U mode and follow that guide...

All that did was break the 3rd party hub and require a direct reinstallation. For both the PC and the Switch/WiiU options Dolphin failed to identify the input.

I have the suspiscion that it is a Dolphin-side error, not the device.

I converted both HidUsb drivers to WinUSB, libusbK and USB Serial and none of them made any improvements of the total failure to register or communicate to dolphin until I deleted and reinstalled the original HidUsb drivers which brought me back to square one: No Rumble on an Original Gamecube Controller. On the both the GC and Switch consoles both my Purple and Orange rumble so I know it works hardware-side.

I am Using a 3rd-party 4-port & Rumble-compatible hub from Yccteam.com that I can confirm rumbles when connected to the Switch.

[afro_Jezuz]

(12-25-2021, 08:01 PM)mbc07 Wrote: Hmm, okay. Put it on Switch/Wii U mode and follow that guide...

I seem to have put the cart before the horse.

While I'm aware reversion to HidUsb would fix this problem of total failure, I cannot reinstate the previous version and all new installations install the failed WinUSB.

Following the Zadig process effectively broke my hub entirely and now I'm struggling to undo the conversion.

Edit: Fixed. (I think..) It is registering as 4 HID-Compliant game controllers (1 for each of the 4 ports.)

While I was returning to the starting point, I found that converting the Driver resulted in it registering as "Gamecube Adapter PC" and "Gamecube Adapter Switch" under the Graphics Tablet category.
This may be why it ceased to function entirely, but I could not redefine it as an HID or anything else.

Perhaps I could find a way to do so I could pull it into the HID umbrella? I'm exceptionally new to drivers, but I have a greenhorn's suspiscion that the catagory of driver is vital to a device's use.

I'd like to try working with Dolphin before I pursue this angle.
Maybe Dolphin is failing somewhere in the identification of present motors. It is empty, afterall, and I'd like to find out how or why that is or could be.