Hacking WiinUPro - Pro Controller to PC Gamepad

[KeyPuncher]

The Program will currently crash if you connect/disconnect controllers while it is running.

 

[kangaroogreen]

So when I press any buttons on the controller, it cunts as a button press when I press it down and release it.
So like it counts as two button presses whenever I do something. Taking it that's not supposed to happen.

 

[GameFreakDude]

This works flawlessly for my CC Pro (once I got vJoy to work, which was less trivial). Thank you! It just doesn't like it when I try to save a profile, but that's not a big problem for me.

Spoiler

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.
 
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at WiinUPro.MoteInfo.SaveAssignments(String path)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
 
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
WiinUPro
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/***/Apps/Input/WiinUPro/WiinUPro.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
WiimoteLib
    Assembly Version: 1.8.0.0
    Win32 Version: 1.8.0.0
    CodeBase: file:///C:/Users/***/Apps/Input/WiinUPro/WiimoteLib.DLL
----------------------------------------
vJoyInterfaceWrap
    Assembly Version: 2.0.1.2
    Win32 Version: 2.0.1.02
    CodeBase: file:///C:/Users/***/Apps/Input/WiinUPro/vJoyInterfaceWrap.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
InputManager
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/***/Apps/Input/WiinUPro/InputManager.DLL
----------------------------------------
 
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
 
For example:
 
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
 
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[del_delly]

Getting vJoy to work was less trivial? What?

 

[GameFreakDude]

I already had PPJoy installed on my computer, and vJoy and PPJoy don't get along at all if they're both installed at the same time (understandably, I suppose). I tried uninstalling them both and reinstalling vJoy, but for some reason their drivers and things weren't completely removed from the system after running uninstallers and rebooting, so I got to root around in system files for a while to get that one to work more reliably. Still haven't fixed it all, though; the very first vJoy joystick still doesn't work for some reason, so applications can only interface with the second joystick and onward. Even vJoy's own Feeder application can't use the first joystick - it doesn't think it has any buttons or axes or anything, even though Windows can see them.

 

[KeyPuncher]

So when I press any buttons on the controller, it cunts as a button press when I press it down and release it.
So like it counts as two button presses whenever I do something. Taking it that's not supposed to happen.

Only for keyboard emulation right? This is from the keyboard emulation library that I'm using. There is another library that doesn't cause duplicates but it's not directx compatible making it useless for most games and the other one is. If I find another I will substitute.

This works flawlessly for my CC Pro (once I got vJoy to work, which was less trivial). Thank you! It just doesn't like it when I try to save a profile, but that's not a big problem for me.

Thanks for the info, I think I know exactly what's causing the issue.

 

[del_delly]

The Program will currently crash if you connect/disconnect controllers while it is running.

Thats good and all, but how can it crash if the program never works in the first place?

 

[KeyPuncher]

Thats good and all, but how can it crash if the program never works in the first place?

If I read your issue right, the Pro Controller is disconnecting. By looking at the Error Log you posted the crash has to do with WiimoteLib, which is probably occurring when trying to read from your Pro Controller and is that the instance where the controller disconnects?

 

[del_delly]

Yes, starting the application: Its either disconnecting, or if I mash the face buttons, nothing happens in the program. It is still blank.
Because its really strange. When I start the 64-bit version, I get a blank window. Only the accept button is there. I suppose it is suppose to look like the one in the video, only with just one of the dropdowns for the controller.
The funny part is: It works for my wiimote. Yes, it connects properly.

So if it is the Wiimotelib that is the problem, how do I fix it? Or how do error report it properly?

 

[KeyPuncher]

... I get a blank window. Only the accept button is there....
The funny part is: It works for my wiimote. Yes, it connects properly.

So if it is the Wiimotelib that is the problem, how do I fix it? Or how do error report it properly?

The blank window shows because I should probably be closing the program here saying that no compatible devices were discovered.

It's actually not strange at all that your wiimote works fine. There are different types of wiimotes, one specific type has difficulties connecting to BT stacks other than Toshiba's. The Pro Controller's structure is based on that, plus it's newer so there's bound to be changes.

The issue you're having, as mentioned before, is still best solved by syncing the controller with a Wii U. For reasons unknown.

 

[del_delly]

Oh well. I will have fun with N64 emulation and the wiimote, until I get a chance to sync the Pro controller with a Wii U once.

 

[naxil]

KeyPuncher, can u make a program for use a pc like wiiremote/classicControllerPRo for play on wii?
I hope a pc with bluetooth can virtualize a wiiremote.... i think u know how the wiiremote send data via bluetooth can u replicate the same command via pc bluetooth to realwii?

 

[KeyPuncher]

KeyPuncher, can u make a program for use a pc like wiiremote/classicControllerPRo for play on wii?
I hope a pc with bluetooth can virtualize a wiiremote.... i think u know how the wiiremote send data via bluetooth can u replicate the same command via pc bluetooth to realwii?

Idk, maybe. I haven't done any sort of console homebrew, I'd have to have the time to research on what languages people use for coding Wii stuff (probably c++). Most of the important communication code comes from the WiimoteLib. It'd be cool to have advanced configuration on Wii, even better if a Pro Controller could be made to interact as a CCP.

 

[naxil]

KeyPuncher why u talk about wii homebrew? iam looking for linux/windows program for "emulate" or "virtualize" a real wiimote/classic controller for use it with real wii...

 

[del_delly]

I don't think I understand what you want. So do you want
A. A program that emulates a wiimote, so you can use the pc as a controller, for the wii
B. A program that will emulate a wiiremote, for a spesific device, and then send that as a wiimote signal to a Wii
C. Some weird homebrew thingy
The request just sounds very weird.

 

[KeyPuncher]

KeyPuncher why u talk about wii homebrew? iam looking for linux/windows program for "emulate" or "virtualize" a real wiimote/classic controller for use it with real wii...

I must've missed what you were asking.

Sounds like you are talking about connecting your PC to the Wii via a program that emulates a wiimote/classic controller.
Not sure that can be accomplished without some information that we don't have. It would require syncing the PC/program to the Wii. It might require some hardware depending on how they do it, and I haven't seen anyone who knows the pairing code to sync the wiimote, so don't think we'd be able to sync to the Wii.

 

[fernanduOTX]

Hello man, I was wondering if you can take a course . I recently bought a wii u control produced by third parties ( http://interworks-usa.com/index.php/products/view/19 ) to play on my notebook , because I had seen a few tutorials and I was convinced that by not being an official product of nintendo , might have more compatibility to connect to the pc ... and I confess that the design and the colors retro snes struck me to choose this product, although he has a very different grip control snes . I thought a lot about buying a control and an adapter for xbox360 does not have as much headache with complex settings , but I saw a lot of people complaining about the directional him it sucks , so I preferred to take a chance and bought this control InterWorks . The product arrived and liked the grip very comfortable , just got upset with the on / off button does not turn it over. For some reason , pressing the buttons off him after he keeps flashing the 4 leds , otherwise all right . Well , the long awaited time to see if it would work on pc had a lot of work because I was trying the method described in this link ( http://gbatemp.net/threads/wii-u-pro-controller-to-pc-program-release . 343159 / ) ... used this program along with the toshiba stack and Smoothboard but was having the problem where the program was not finding hid a device in the list . I stayed for two days when he was free time trying and could not , I thought these videos tutorials and their wiinupro earlier today to my delight . I did everything you said , but using a usb bluetooth adapter to skip the paperwork to edit that document in the folder of the toshiba stack . Could connect easily , but I had another problem ... like the control that I bought is not original nintendo , not being recognized correctly in wiinupro . This control has a key that got behind him to change the function wiimote classic controller , and it is found only in the bluetooth stack mode wiimote . After opening the configuration window vjoy , he only responds when it is in the wiimote , so the vjoy only shows the buttons a, b ??, 1 , 2 , up, down , left, right , + , - and home ... anything l , zl , r , zr nor analog . Do you have some knowledge about how to solve it , causing the program to recognize it as an original control ? I wanted to use it to play in snes emulator , ps2 and dolphin . I hope I'm not asking too much for you man, if you do not like and I understand since I'm already grateful. Sorry for the horrible english , I 'm Brazilian and I do not know much English , so I translated via google translator XD . Thanks and a big hug !

Note : I used wiinupro beta 7 , my laptop is a Samsung intel core i7 , 6gb ram , 1tb hd and windows 7 ultimate x64 .

 

[KeyPuncher]

.... I recently bought a wii u control produced by third parties ( http://interworks-usa.com/index.php/products/view/19 ) .....

This isn't actually a Wii U Pro controller at all. The controller is a Wiimote + Classic Controller made to look like a Wii U Pro Controller. So the only thing you should be able to find it as is a Wiimote + Classic Controller Extension. I'm not sure if the Extension will be properly recognized though, so it may just end up finding just a Wiimote.

 

[scitek]

Is there a way to use both triggers at the same time yet with x360ce? That's the only thing keeping this from being perfect for all my games (can't ADS in shooters).

EDIT: You can map the left and right mouse buttons to the triggers in WiinUPro. Not ideal, but it works.

 

[PolloDiablo]

The issue you're having, as mentioned before, is still best solved by syncing the controller with a Wii U. For reasons unknown.

Oh well. I will have fun with N64 emulation and the wiimote, until I get a chance to sync the Pro controller with a Wii U once.

I was looking forward to buy the Wii U Pro Controller to use on my PC... but I don't have a Wii U
Do I really need to sync the controller with the console in order to work with this? Just once? or is this a recurring problem?