PadSend lets you use Gamecube pads connected to a Wii, or a DS, as a PC gamepad. PPJoy must be installed. Just run the server on your computer (requires .NET framework 2.0) and run the client on your Wii or DS. It will only work right now if your DS or Wii has an IP address that starts with 192.168.1. (this will be fixed soon)

You can download it here: http://dl.dropbox.com/u/211987/pad_send.zip

Wii features:

• Support for all four controller ports, simultaneously.
• Analog sticks and triggers are supported.
• Mouse control using either (or both) of the analog sticks and L/R buttons. Mouse movement is choppy, though, due to how messages are handled

DS features:

• Support for up to 16 connected DS systems.
• Relative mouse control using the touch screen and L/R buttons.
• Absolute joystick control using the touch screen (must be calibrated in the Windows joystick panel)

Server features:

• Automatically creates PPJoy virtual joysticks for each unique device connected. It does not automatically delete them, though, because it turns out that is really annoying. (manual deletion will be added later)
• Writes button and axis names to the registry, which means games that bother to look for this can use accurate button labels.
• You can rename each device connected through the program interface-- you can have two systems connected named "Nintendo DS Lite" and "Nintendo 3DS" for example.
• An icon is displayed on the status window next to each device, the color of which can be changed to match your controller or system.
• Mouse control can be enabled or disabled, and this setting can be applied per-controller.
• All settings are saved and loaded automatically. The MAC address on the DS is used as a unique identifier, so settings can be saved, loaded per-system.
• Sits quietly in the tray, and if it works (I can guarantee it works on my machine, as they say), then it never requires any settings or attention.

You must install PPJoy before this will do anything. The newest version of PPJoy does work with 64-bit systems-- I'll add an explanation on how to install it later.

First run the server application on your computer. It will pop up for a second and then hide itself in the tray. When you click the tray icon, the status window will appear. The behavior and appearance is intended to mimic the way Windows 7's volume, network, etc, tray icons work. If you have Wiiload configured or if you know your Wii's IP address, you can send the Wii client directly to your Wii from here-- open the Homebrew Channel on your Wii, and click Wiiload Client. If wiiload is already configured, it will send it over right then. If it's not configured, it will prompt for you to enter your Wii's IP address, then send it. You can also do this from the tray icon's right click context menu, if you don't want to bring up the full status window.

Once a device is connected, it will be shown on the status menu. You can click the device icon to change its name or color. Right clicking the icon will change how the color is displayed, but this isn't saved, so it's not very useful.

Click About/Help to see descriptions for what each checkbox does.


For developers who want to write apps to interface with my server, UDP messages are sent to 192.168.1.255, on port 9501. The data structure for both types of controllers is (bytes):
00 - Counter (not used yet)
01 - Unique ID
02 - Identifier (explained below)
03 - Extension (not used yet)
04 - Buttons 0 (each bit is one button state)
05 - Buttons 1

After this it's different for each; GC:
06 - Left Analog X
07 - Left Analog Y
08 - Right Analog X
09 - Right Analog Y
10 - Analog Trigger L
11 - Analog Trigger R

DS:
06 - TouchX1 (each two bytes makes up a single unsigned 16-bit number-- maximum is 4000 though)
07 - TouchX2
08 - TouchY1
09 - TouchY2

Identifier:
01 - Gamecube Port 1
02 - Gamecube Port 2
03 - Gamecube Port 3
04 - Gamecube Port 4
09 - Nintendo DS

The server expects at least one message every second, or it assumes the device has disconnected.

Known bugs:

• Only the last byte of the MAC address is used to identify the connected DS, so two systems may identify as one and fight over a single virtual joystick.
• The Wii does not send a unique identifier, so you can't use more than four Gamecube controllers by connecting multiple Wiis. Not that I figure anyone would want to do this.
• Color settings either do not save or load properly for Gamecube controllers.
• If the virtual joysticks configured by ppjoy are not sequentially numbered, the server may (probably will) create duplicate joysticks.
• There's no dead zone for Gamecube analog sticks, so if your pads are worn out, you may find your mouse pointer wandering.
• Input is only updated each time a new message is received, so mouse control is not consistent when controlling it with an analog stick.
• It will only work if your router assigns addresses that start with 192.168.1.-- You might be able to hex edit the executables to change this to match your situation (leave the last octet as 255, though). ndslib and libogc do not seem to properly handle broadcasting or multicasting, so I don't know how to fix this and still be "configuration-free". Anyone have any ideas? Either way, I'll add a manual configuration in the future.
• There are a million features I still want to add

Please post any bugs or issues you find. I don't even know if this will work for anyone else!

 

PadSend Server has been updated to revision 3 and the Wii .dol client has had a bug fixed (no version change). Anyone who tried to use it before and couldn't, please download it again and try the new version.

 

I think it's the right one. I made the changes to the dol file not long after I first posted this, I just got around to updating all of the files.

Have you tried to use it?

 

I'll try to release an updated version soon that should work on more network configurations. I was just lazy with the 192.168.1. thing because I figured it would work for most people. The 255 is used like a wildcard to indicate a broadcast on network addresses-- anything that matches the rest can receive packets sent like that. I'm not an expert on network stuff (not even close) so I could be doing everything wrong, but it does work for me right now, so it should also work for you once I make it adapt to different ranges of network addresses.

There is a button combo to exit, I forgot to mention it. Press L+R+Z+A+Y+Start on the first controller. I meant to make the reset button work too, but I was in a hurry to get everything working and released so I forgot. I'll fix that in the next release, too.

Edit: Did you use the hex editor on both the server and the client? The client sends to 192.168.1.255, and the server receives on 192.168.1.255, so they would both need to be changed for it to work.

 

Yeah there's also private Class-A (10.x.x.x) networks and other such configs, so getting people to help make it auto-detect should fix this.

 

Great, thanks! I created an updated version that should work for more network configurations. Try it here: http://dl.dropbox.com/u/211987/ps-beta.zip

No DS client yet. If someone reports that this works for them, I'll update the DS client as well.

 

I don't think that you have a 10.0.0.0.2 network. That is about 1 octate too much. 10.0.0.x in that case would be possible yho.

 

How exactly is the Wii communicating with the computer? Local wifi? Internet? Bluetooth?

 

Does this work for wireless gamecube controllers? I'd have mine connected to the Wii... but downstairs while I'm playing something like... Minecraft? IDK, but this might have useful applications.

 

So, I've gotten past the Windows 7 64-bit trite and got PPjoy working. I restarted Windows in 'disable driver signature enforcement' mode. My problem is with the Wiiload client.

Basically, I used the split second that the Padsend Wii app tells me my Wii's IP address (it would be helpful if this stayed on the screen), and then used it to try and connect to the Wii.

But then, nothing happens. The Wiiload client opens for about a second, says 'transfer failed' and then closes. Padsend still tells me 'Waiting for connections'.