WiinUPro and WiinSoft are both unable to create a recognizable Xinput device

[draybryan]

1. Both programs are able to sync my WIndows 10 PC with the official Nintendo Wii U Pro Controller
2. WiinUPro does nothing when trying to create an XInput device, I tried uninstalling and reinstalling both the SCP drivers and WiinUPro & restarting my computer and nothing worked.
3. WiinUSoft appears to create an Xinput device, at least visually in the program, but when I try to navigate Windows 10 Settings with the controller for example, nothing happens and no Xinput devices show up in Dolphin either. The program is able to calibrate control sticks, remap buttons and send a vibration to the controller, but no functionality outside of the program. I uninstalled and reinstalled everything just like WiinUPro. This was a colossal waste of time, and the closed issues on here were of no help.

[alextorres50]

same here, the keyboard and the mouse emulation is fine, but XIpunt Devices doesn't works

[LastLicht]

Dunno how much it matters, but I'm running into this with the current version as well on a machine with an older version.

[cupnooodle]

Exactly the same issue running Windows 11 here

[Shane14705]

same problem here, on two different machines as well

[cupnooodle]

same problem here, on two different machines as well

I had resolved the issue by installing the included scp drivers

[KeyPuncher]

I'll try to look into this either when the current semester is over or during spring break if I can tuck away some time. Please post your versions of Windows. I only have a few machines available to me, two 10s and two 11s. Reproducing is usually key. The behavior does sound like a communication breakdown going to the SCP driver or an incorrect version being installed based on past reports. It could of course be any number of things as updates to Windows role out and the most likely thing is not always the answer.

[Shane14705]

I'm on windows 11 on both, I installed SCP and that did in fact fix it! I was a bit confused though, as even without SCP both wiinusoft and wiinupro were able to connect to my controller, and register input just fine (I could bind keyboard keys to my controller and use it that way). But for some reason, using it as an xinput controller just refused to work on either, no matter what I did. SCP fixed it, but isn't that just a Bluetooth stack (and it was connecting fine anyway)? I'm down to get more logs and what not when I get home if it helps!

[KeyPuncher]

SCP is the dependency for XInput emulation, so that is all expected behavior. The dependencies for mouse and keyboard emulation are built into the application and of course the controller detection and reading is handled by the application itself via Bluetooth APIs. SCP also has a Bluetooth driver for DS4 controllers, which is not needed and not recommended to be installed if not using DS4 controllers elsewhere due to scenarios other users have ran into in the past. It is installed depending on if the little Bluetooth Drivers checkbox is checked (which it is by default) when installing the SCP drivers.

[Shane14705]

Ooo thanks for the info, that makes a lot of sense! I didn't install SCP originally since my Bluetooth adapter is kinda wonky when it comes to non Microsoft stacks, but it seems like I can just uncheck the Bluetooth driver box to get SCP with the Microsoft driver! Thanks for keeping this project taken care of :)

[draybryan]

I decided to revisit this app since I really wanted to connect my controller for some netplay, and I was met with the same issues as I described. But based on the feedback above I assumed I'd try to mess with the SCP drivers again. What I believe fixed it for me was ticking the force install option when installing the SCP drivers. I restarted my computer like the installer told me to, and everything was working just fine in WiinUSoft. Never tested WiinUPro, can only assume it would work too. Cheers guys, and I really appreciate this project.