Hacking WiinUPro - Pro Controller to PC Gamepad

[Walker D]

I'll be creating a new test build tomorrow.

cool
If you have time, could you take a look at the problem with the Default Profile later too? (would be cool if WiinUPro could change profiles by itself depending on which controller it recognizes.. ...so we could set Default Profiles individually for wiimote, Pro controller, etc..)

 

[Blazer]

This is pretty awesome, but I am way too freaking intimidated by those instructions on Reddit. I gave up after downloading a couple of problems XD. If only this were more convenient for lazy non-tech savvy bums like me.

 

[Walker D]

KeyPuncher , found a kinda serious problem with vJoy. I've tried to play the game Kero Blaster and it's totally unplayable cause of vjoy. That's cause under calibrations vjoy always sends a first input automatically (without you pressing any buttons), and since this game does some kind of controller calibration at startup, the game messes up the controls (the player goes right for ever.. ...also more controls get broken at the game's menu, what also makes it impossible to configure the controls in game).

The game has a readme that says: "Make sure not to press any buttons on the gamepad when starting the game. Holding a button upon start-up can cause issues in-game."
After uninstalling vJoy, the game worked fine...

I've had noticed that vjoy does this "auto input" before when I was configuring my controller in other emulators ...but this is the first time that this bug actually breaks a game for me..

Edit: you can also replicate the issue if you want with the free demo preview for this game, named Pink Hour.

 

[Kurausukun]

Yeah, I'd sure like some workaround besides vJoy as well. Not that I'm complaining about all the work you've done, but vJoy is incredibly iffy for me and just kinda seems to work when it feels like it. Especially in the case of Sonic and All-Stars Racing Transformed as I've mentioned before.

 

[KeyPuncher]

This is pretty awesome, but I am way too freaking intimidated by those instructions on Reddit. I gave up after downloading a couple of problems XD. If only this were more convenient for lazy non-tech savvy bums like me.

Not to worry, a simple installer is planned to come with the version 1 of the final release.

... totally unplayable cause of vjoy. That's cause under calibrations vjoy always sends a first input automatically...[/quote]

Duly noted. Is this without the intent of using a vJoy device as a controller?

[quote="Kurausukun, post: 5018729, member: 347725"]Yeah, I'd sure like some workaround besides vJoy as well. Not that I'm complaining about all the work you've done, but vJoy is incredibly iffy for me and just kinda seems to work when it feels like it. Especially in the case of Sonic and All-Stars Racing Transformed as I've mentioned before.[/quote]

Same here. I'll be doing my research on writing drivers to see if I will be able to parse the controller's input directly in Windows.

 

[Walker D]

Duly noted. Is this without the intent of using a vJoy device as a controller?
Same here. I'll be doing my research on writing drivers to see if I will be able to parse the controller's input directly in Windows.

um.. I noticed that it's something vjoy do (that first weird/blank auto input) when I intend to use a controller device with it (in this case, my CC Pro with WiinUPro, following your instructions on how to do it). As I said before, the input is even visible, for example, when you first click on the place to start configuring inputs, at many emulators (like Snes9x).

But in the case of my previous post, no. I wasn't even intending to use vJoy device as a controller. I had no controller plugged, and wasn't using WiinUPro. Only by being installed, vjoy did that issue.

- just out of curiosity: when you save a device config at "Configure vJoy", you are actually rewriting a driver? (and that's what you pretend more or less for a "device configuration" built in WiinUPro to do in the future?)

Ah, and thank you for noting the issue, and good luck on the project

 

[KeyPuncher]

But in the case of my previous post, no. I wasn't even intending to use vJoy device as a controller. I had no controller plugged, and wasn't using WiinUPro. Only by being installed, vjoy did that issue.

Okay, I've noticed that when there isn't a controller connected, any vJoy devices have strange input. If you go to the game controller's calibration screen in Windows, there should be a button that says reset to default or something like that, and that should set all of the analog axis inputs to 0.

just out of curiosity: when you save a device config at "Configure vJoy", you are actually rewriting a driver? (and that's what you pretend more or less for a "device configuration" built in WiinUPro to do in the future?)

At that point, no. The driver from vJoy handles the input and output of those configured devices though. What I would like my driver to do is either directly translate a Nintendo controller connected via bluetooth to a Windows joystick or at min a non-HID device so games don't try to automatically pull info from it and just let WiinUPro handle it.

 

[Walker D]

Okay, I've noticed that when there isn't a controller connected, any vJoy devices have strange input. If you go to the game controller's calibration screen in Windows, there should be a button that says reset to default or something like that, and that should set all of the analog axis inputs to 0.

Did just that right now, and tested Pink Hour afterward. And seems like it worked.

That first weird auto input still seems to happen though (being visible when you first configure controllers in some emulators, as I said before). But not much of a issue right now since it's not crashing games for me anymore.

 

[Blazer]

Not to worry, a simple installer is planned to come with the version 1 of the final release.

That sounds awesome, I'll keep an eye out for it. Thanks for the heads-up!

 

[Pmyl]

I was trying to play Darksiders with Wiinupro but I encountered a strange behaviour (imho): the game see the controller as a x360 controller without any effort, but the controls are weird, unplayable. It's normal? I hoped it would work as a normal usb controller, it surely would have better behaviour and less problems.
I tried to just use x360ce to emulate the x360 controller without the weird controls (like any usb contorller), but it seems it does nothing. I'm a bit sad ._.

 

[del_delly]

Just a curiosity? Is there any planned method for ripping/replicating the firmware updates to the controller?

 

[TeconMoon]

Hi there,

I'm trying to test out your application: I have vJoy and Toshiba Stack setup on Windows 8.

When I open WiinUPro and select Joystick 1, no matter what options I configure in "Configure vJoy" WiinUPro doesn't seem to recognize that the axis and buttons are available, and only maps like 4 of the buttons as a result and won't show the rest. Here's a screenshot of what it looks like along with my config.

I appreciate the help!

 

[del_delly]

That looks pretty normal. Unless you can't select Joy4 for some reason when you configure say... Y, its working as "intended".

 

[TeconMoon]

That looks pretty normal. Unless you can't select Joy4 for some reason when you configure say... Y, its working as "intended".

It's not normal. Only buttons 1 2 and 3 are selectable. buttons 4 - 17 aren't even in the list as selectable options and neither are the axis.

 

[HunterZ]

It's a known issue that vJoy device #1 causes problems. Use a higher device number.

 

[TeconMoon]

Fantastic, that solved the problems I was having. Thanks a lot!

 

[Acidflare]

Does this work at all for windows XP? I can get glovepie to work but vjoy and wiinupro both terminate upon execution I have. Net 1-4 installed but still nothing is there something I am missing?

 

[HunterZ]

Are you using the 32-bit versions? vJoy at least says it supports XP.

 

[Acidflare]

Yep x86-x64 vjoy build but it may be my processor it's a p3 1.02 ghz Linux verifies it as an i386 CPU so that may be it

 

[HunterZ]

x64 means 64 bit so that would almost certainly be your problem