Request for Flydigi Direwolf support - Connected but no inputs detected

[luiseduardo26costa-design]

Hardware: Xbox 360 Slim (Retail/Non-RGH)
Mod Type: Profile/Avatar Exploit Controller: Flydigi Direwolf (Wired via USB)

Issue:
I am using an Avatar Exploit to run homebrew and games. I’ve tried using UsbdSecPatch.xex and hiddriver.xex to get my Flydigi Direwolf working. The controller is recognized (the LED turns white in X-Input mode), but the console does not register any inputs (no movement or button presses).

Since I am using a Profile Exploit and not a full RGH, is there any specific way to load these plugins so they can intercept the USB security layer? Or is this driver strictly for RGH/JTAG kernels?

I would appreciate any guidance on whether this setup is supported for non-RGH exploits.

[EinTim23]

Hiddriver works fine using BadUpdate, a physical RGH/JTAG isn't required. But your controller shouldn't be in xinput mode and somebody would need to create a mapping from your controllers button report to an xbox 360 controller. For XInput mode UsbdSecPatch should usually do the thing, but I guess the version of xinput the 360 uses is too old for that specific controller.

In conclusion hiddriver would be the right thing for your controller(at least in non xinput mode), but somebody would need to create a button mapping for it.

[luiseduardo26costa-design]

Update with Hardware IDs:

I managed to get the Hardware IDs for my Flydigi Direwolf. When connected via Bluetooth (which is the non-XInput mode for this controller), it identifies as follows:

VID: 045E

PID: 02FD

Full Hardware ID string: HID{00001124-0000-1000-8000-00805f9b34fb}_VID&0002045e_PID&02fd

Could you (or someone in the community) help me with the correct button mapping for this device?

I am willing to run tests on my console to help verify if the mapping works correctly.

[EinTim23]

Hi, for this to work the controller needs to have a non xinput mode accessible via USB (which seems to be available on this specific controller, as it also supports direct input and mobile devices according to my Google search.), as the 360 doesn't have any Bluetooth adapter. Xbox 360 controllers use 2.4ghz wireless.

[luiseduardo26costa-design]

Update: Hardware IDs via USB Cable

I have now connected the Flydigi Direwolf using a USB cable, as requested. In this mode, the hardware IDs are:

VID: 045E

PID: 028E

Full Hardware ID string: HID\VID_045E&PID_028E&IG_00

In this wired mode, the controller identifies itself as a standard Xbox 360 Controller (PID 028E). However, the console still recognizes the connection but doesn't register any inputs.

I am using the Avatar/Profile exploit (BadUpdate/Xeunshackle). Is there a way for HidDriver360 to override this specific PID to fix the input issue, or should I try switching the controller to a different mode (like Android/D-Input) while connected via USB to get a non-Microsoft PID?

[EinTim23]

Android/D-Input should be the correct way to proceed here. In addition to the PID/VID we also need to capture the format of the controllers button report. I can guide you through that process once we get there. For easier communication we can also switch to discord or telegram.

[luiseduardo26costa-design]

I agree that switching to a more direct chat would be much faster. I have both Discord and Telegram available. I've just sent you a message on Telegram so we can start the mapping process for the Flydigi Direwolf. Looking forward to hearing from you there!

[EinTim23]

Should be supported with v0.6-beta