Hacking WiinUPro - Pro Controller to PC Gamepad

[SidusObscurus]

Interesting, some things that may help with troubleshooting:
- What games has this happened with?
- What commands have you noticed this with?
- Are you using turbo?

Still trying to find some time to work on updates and everything. Been pretty busy with my new job. Thanks for being patient.

I'm not using turbo nor am I using analogue inputs. All buttons and joysticks are mapped straight to keyboard and numpad keys. Since then I've taken to putting the button mapping client on my second monitor so I can watch it when this problem occurs, and I have observed the client reporting stuck buttons after I stopped pressing them in this manner, so I suspect it is a problem between the controller and the client, rather than the client and the game.

I've noticed button sticking occurring mostly with the Dpad (mapped to WASD), the A button, and the ZR trigger. I suspect this can occur for the other buttons as well, but I haven't noticed the other buttons since they are discrete commands. Dpad, A, and ZR are mapped to actions that can be continuous (movement, jumping, and machine gun fire respectively) rather than discrete, so I notice them most of all. I've confirmed seeing Dpad and A button being registered when not pressed by the client on my second monitor. I have also noticed command delays and unresponsiveness being reported by the client on my second monitor for most of the buttons (I tap B, B doesn't immediately register on the client, then 1 second later B registers on the client, my game executes the B command, then stops).

Primarily I've noticed it with Cave Story+ run via Steam. As a test on a different game, I've run about 90 minutes gameplay of Muramasa - The Demon Blade on Dolphin emulator, and I noticed the dpad sticking twice for about 1-1.5 seconds each time during the gameplay. One of the two times in Muramasa, I observed the client reporting the button pressed while I was not pressing it. This is a typical frequency. It seems to happen every time I play for a significant amount of time, which is what I meant by "frequently" in my earlier post, though it only happens noticeably about once every 30-45 minutes. I plan to test an hour or two gameplay on an SNES game via Retroarch emulator as well, but I haven't gotten around to it. I could also try testing another ordinary PC game (Bastion or Bioshock or something) if you'd like me too.

Lastly, I switched my bluetooth dongle to make sure it wasn't the hardware. I got the same problem on the second dongle as well (I'm using Kinivo BTD-400, blutooth 4.0 class 2 adapter; and Cirago BTA7300 bluetooth 3.0 class 2 adapter with wifi). Neither are Toshiba by default, and both are class 2, so it could be because of one of those properties perhaps?


Overall, this is a very minor problem. Doesn't make games unplayable at all, but it is still a problem. Thanks for the quick response!


Edited Addition - I've also tested Megaman X for SNES via RetroArch for about two hours, and didn't notice a single delay or button stick.

I also tested Castlevania SotN for PSX via ePSX, and the results were much worse than with other programs. Within the first minute of gameplay, I had command delays and button sticking. Controller going unresponsive happened several times in the 30 minutes I tested. In addition, my controller actually disconnected from Bluetooth... for some reason. That last one has me stumped; I have no idea why the controller would completely disconnect. While for other programs, this was only a minor problem, for ePSX, the games are unplayable.

I hope this is useful feedback for you.

Solution Update - In a later post, KeyPuncher suggested I try another USB port. After testing several hours on multiple different programs with 0 problems at all, I can confidently say checking my other USB ports fixed this problem. So if you're getting command delays and non-responsive commands, try another USB port! Thanks again KeyPuncher!

 

[Warrior_Elite]

I'm having a separate issue altogether.

I had this installed in Win7, and it worked perfectly. Now, I just upgraded to Win8 x64, and followed all of the instructions set on the first post for Win8 users. vJoy recognized my Wii U Pro controller, and I set the amount of buttons to 17. However, when I open the beta 7, I can only use up to 8 joystick buttons. When I open the Hardware devices on the Control Panel, it shows that the device has 17 buttons as well, but I can't configure them. I'll try to post useful images.

Any help would be great, I can't use it much with only 8 buttons to configure.

 

[jakobs98]

Greetings! I'm looking into getting a Wii U pro controller for PC gaming (Xbox 360 one's cable is breaking, giving me bluescreens, and generally doesn't fit me) but I'm wondering some things.

I know my bluetooth thingy is too wimpy for regular Wiimotes but might it work with Pro controllers? I'll probably get one that works with Wiimotes eventually but I'd like to know regardless. Pardon me if this is the wrong place to ask.

As for this program, does it support analogue stick input? I remember reading somewhere that it does not but I'm hoping that information was outdated.

 

[Motobug]

Greetings! I'm looking into getting a Wii U pro controller for PC gaming (Xbox 360 one's cable is breaking, giving me bluescreens, and generally doesn't fit me) but I'm wondering some things.

I know my bluetooth thingy is too wimpy for regular Wiimotes but might it work with Pro controllers? I'll probably get one that works with Wiimotes eventually but I'd like to know regardless. Pardon me if this is the wrong place to ask.

As for this program, does it support analogue stick input? I remember reading somewhere that it does not but I'm hoping that information was outdated.

First off, make sure you have Toshiba Bluetooth stack installed to use Wiimotes and Pro Controllers. That may be why the remotes aren't working with your Bluetooth dongle (I won't go into that here, it's on other pages). And yes, there is analog support.

 

[jakobs98]

I use Toshiba BT stack. Close, but no cigar.

Another question (this one is for my fellow Swedes): Any tips on BT adapters that do work with Wiimotes/Pro Controllers available here in Sweden? I just find those super small generic ones
(mostly Deltaco) on Pricerunner.
WiiBrew has a list on compatible ones here:
http://wiibrew.org/wiki/List_of_Working_Bluetooth_Devices

EDIT: Okay so I goofed a bit. Turns out, there are several confirmed working BlueTooth adapters if you look here. Any tips on particular ones? I feel like I can trust Trust (hah). It's a pretty well known brand and stuff.

EDIT 2: Maybe I'm going too off topic? I can make a thread or post elsewhere if it's a problem.

 

[redkeyboard]

I use Toshiba BT stack. Close, but no cigar.

Another question (this one is for my fellow Swedes): Any tips on BT adapters that do work with Wiimotes/Pro Controllers available here in Sweden? I just find those super small generic ones
(mostly Deltaco) on Pricerunner.
WiiBrew has a list on compatible ones here:
http://wiibrew.org/wiki/List_of_Working_Bluetooth_Devices

EDIT: Okay so I goofed a bit. Turns out, there are several confirmed working BlueTooth adapters if you look here. Any tips on particular ones? I feel like I can trust Trust (hah). It's a pretty well known brand and stuff.

EDIT 2: Maybe I'm going too off topic? I can make a thread or post elsewhere if it's a problem.

My cheap bluetooth adapter that I got from ebay has been working fine for years, it looks like this.

 

[jakobs98]

I've basically got the same thing but it doesn't work so I'm not going to take any chances.

 

[tehspeleengpolise]

Another question (this one is for my fellow Swedes): Any tips on BT adapters that do work with Wiimotes/Pro Controllers available here in Sweden?

As far as I know, you don't need a specific Toshiba dongle to use the stack. If you have a non-compatible one, all you need to do is edit the .ini file (as shown in the setup video in the first post of this thread), and then uninstall then reinstall the stack every 30 days (due to the evaluation period that gets enabled if you have an "unsopported" adapter). So get any bluetooth adapter you want, provided it works. (I'm using in-build bluetooth, so can't help with that, sorry.)

 

[tehspeleengpolise]

I have a suggestion for beta 8: a "Clear" button to clear all the mapping of the currently displayed shift quickly.

Also, would it be possible to merge profiles that use only one shift into one profile with several shifts, or on the other hand separate different shifts in one profile into several profiles automatically? Not a big deal if it's too annoying to implement though.


EDIT: Also, if I load a profile which has a button assigned to "cycle shift", cycle to a shift colour other than None, and load a different profile which does not use shift assignments, the controller will be stuck on that alternate shift. To get it back to None, I have to set a button to Cycle, then cycle to none, then set the button back to what it was before, which is kinda annoying.
A possible fix might be setting the controller to the None shift every time you load a profile. However, a much better fix and a really nice feature would be the ability to change the controller's current shift colour through WiinUPro itself. Is there a way to get this implemented?

 

[jakobs98]

As far as I know, you don't need a specific Toshiba dongle to use the stack. If you have a non-compatible one, all you need to do is edit the .ini file (as shown in the setup video in the first post of this thread), and then uninstall then reinstall the stack every 30 days (due to the evaluation period that gets enabled if you have an "unsopported" adapter). So get any bluetooth adapter you want, provided it works. (I'm using in-build bluetooth, so can't help with that, sorry.)

I'm in need of an adapter; I've got Toshiba BT stack set up and all. Sorry if I didn't make it clear. Need one available here in Sweden, more specifically.

I'll just go make a thread of my own, anyway. Think I've got this mostly figured.

 

[Senoue]

So I finally got everything working but now when I try to reconnect my controller, the connection in Toshiba Stack keeps disconnecting the controller. How do I fix it?

 

[wiinox]

Hi there, i got the same prob than Senoue, everything working but controller is always disconnected one second after so i can't launch wii u pro

 

[tehspeleengpolise]

@ Senoue and wiinox:

Try this, and the next post too.

 

[wiinox]

thanks for the trick but it worked just one time, IDK why.
im too lazy for mashing 100 time my controller before playing ^^'. Good job anyway

 

[Warrior_Elite]

I'm having a separate issue altogether.

I had this installed in Win7, and it worked perfectly. Now, I just upgraded to Win8 x64, and followed all of the instructions set on the first post for Win8 users. vJoy recognized my Wii U Pro controller, and I set the amount of buttons to 17. However, when I open the beta 7, I can only use up to 8 joystick buttons. When I open the Hardware devices on the Control Panel, it shows that the device has 17 buttons as well, but I can't configure them. I'll try to post useful images.

Any help would be great, I can't use it much with only 8 buttons to configure.

Does anyone have any possible suggestions to guide me in the right direction with my issue?

 

[Patbatch]

Hey thanks for all the support Keypuncher, using the tutorial videos and info on this thread I managed to have this working perfectly at 100%. The next day I just had to turn on the controler open Wii U pro and I was good to go, still worked perfectly.

But 2 days later.. I was gonna do the same thing again but the Toshiba tray icon was red. The controller won't turn on. Its as if the bluetooth dongle was disconnected. I tried rebooting.. and after rebooting the bluetooth tray icon was just gone. So I went in the device manager looking for where its supposed to be "Bluetooth Radio" at the top.. but there is nothing.

So I unpluged the bluetooth dongle a couple time thinking it might be dead. But no... Windows makes a "device detect" sound.. but there is just no bluetooth stuff in the device manager at all.

This is frustrating.. I had some trouble getting this to work the first time(I think I had skipped a couple reboot during my first attempt, and this was the reason that nothing was working). When I finnally got it to work I thought everything would be fine from now on (exept the toshiba liscence each month). By the way is there a way around reinstalling the Toshiba drivers each month?

Well anyway.. I'm not sure what I should do now..

*edit*
Well I went to look inside the Toshiba installation folder.. but when I got there.. no folder? wtf I never uninstalled this... Lucky for me I still had my device ID number written down, so I could add it up in the INF file while reinstalling. (otherwise I would have had no way of checking it, since it wouldn't appear in the device manager).

So I reinstalled the Toshiba stack and it seems to work.

 

[tehspeleengpolise]

Does anyone have any possible suggestions to guide me in the right direction with my issue?

Sorry, I don't think many people here have Win8... Try going back to 7? Otherwise, maybe add more than 17 buttons, might help.

 

[KeyPuncher]

I'm having a separate issue altogether.

I had this installed in Win7, and it worked perfectly. Now, I just upgraded to Win8 x64, and followed all of the instructions set on the first post for Win8 users. vJoy recognized my Wii U Pro controller, and I set the amount of buttons to 17. However, when I open the beta 7, I can only use up to 8 joystick buttons. When I open the Hardware devices on the Control Panel, it shows that the device has 17 buttons as well, but I can't configure them. I'll try to post useful images.

Any help would be great, I can't use it much with only 8 buttons to configure.

Some other windows 8 users have ran into this issue. I believe it's a compatibility issue on why the vJoy library I'm using only returns 8 buttons maximum. Try setting up a different joystick, sometimes this is only an issue with joystick 1.

 

[KeyPuncher]

Snip

It sounds like there is something going wrong in the connection between the controller and the dongle(s) but your dongle switching seems to lower the support for that conclusion. I don't think interference is typically an issue with bluetooth devices, but I suppose it could be possible.. I assume you are not sitting that far from the bluetooth dongle.

Maybe try another usb port? There's a chance something could be wonky with the one you are using, although the difference in responses from the different programs seems to go against that idea as well.

I was actually talking about showing the battery level in-program. Just a little icon near the visualization of the Pro controller. That light flashing thing is great too.

I could probably have it create a notification when the battery life is low. Reading the battery life from the Pro Controller doesn't give you the same accuracy as the Wiimotes (as far as I've been able to tell) so even if your battery is half way done, it still reads the same as it would when full, it's not until it really starts dying when you get a difference. Which makes the red light that comes up on the Pro Controller probably more useful than the info the controller returns. But I will look into it more when I get a chance.

 

[Warrior_Elite]

Some other windows 8 users have ran into this issue. I believe it's a compatibility issue on why the vJoy library I'm using only returns 8 buttons maximum. Try setting up a different joystick, sometimes this is only an issue with joystick 1.

Thanks KeyPuncher!

You solved my problem. Yeah, it looks like it doesn't like having more than 8 buttons on Joystick 1. I deleted the device through vJoy and configured Joystick 2, and that fixed my problem. Thanks! You're the best!