Wii U Pro Controller double input problem (uses a virtual gamepad driver)

[GoogleCodeExporter]

Steps will reproduce the problem?
1. Configure a virtual joystick (which is handled by windows as random no-brand 
gamepad)
2. Setup x360ce
3. Run DMC

What is the expected output? What do you see instead?
I expect DMC to use the Xbox controller emulated by x360ce, and it does. But 
DMC does not stop taking inputs from the "normal" gamepad configured by 
Windows. In my case vJoy. Therefore I do get double input.

The same configuration works flawless with Tomb Raider, Darksiders II and Alan 
Wake. So for some reason DMC won't use x360ce as primary device.

What versions of x360ce and Windows are you using?
x360ce: 3.4.0.766
Windows: Windows 7 x64

What gamepad do you use? On what drivers version?
I am using a virual gamepad since I'm using Wii U Pro Controller. The virtual 
gamepad is the latest version of vJoy. vJoy device is seen by Windows (and 
other software like DMC) as a standard joystick device. That's why I'm using 
x360ce.

Log and ini attached in post.

Thanks for your great work!

Original issue reported on code.google.com by kroo...@gmail.com on 12 Aug 2013 at 5:53

Attachments:

• DMC-DevilMayCry.exe_20130812-194418.log
• x360ce.ini

[GoogleCodeExporter]

Give this dll a try

Original comment by danialho...@gmail.com on 13 Aug 2013 at 12:24

Attachments:

• xinput1_3.dll

[GoogleCodeExporter]

Hi, tested it now after work. Still same issue. Do I need to change something 
in my btw?

Original comment by kroo...@gmail.com on 13 Aug 2013 at 7:34

[GoogleCodeExporter]

can you provide a dxdiag log and a screenshot of ditool

https://x360ce.googlecode.com/svn/trunk/x360ce/Support/ditool.exe

Original comment by danialho...@gmail.com on 14 Aug 2013 at 4:31

[GoogleCodeExporter]

Sure! I will post that after work today. Thanks for the help

Original comment by kroo...@gmail.com on 14 Aug 2013 at 6:40

[GoogleCodeExporter]

Here you go.

Original comment by kroo...@gmail.com on 14 Aug 2013 at 8:50

Attachments:

• ditool.png
• DxDiag.txt

[GoogleCodeExporter]

Is there an actual Xbox 360 pad attached to the computer?

Original comment by danialho...@gmail.com on 15 Aug 2013 at 2:04

[GoogleCodeExporter]

The wii-u pad pro is not present in the dxdiag log, the wiimote is but this is 
not the device being read into x360ce.

It looks like an issue on vjoys end, since its not giving us any dx device 
information to bind the COM injection to.

Original comment by danialho...@gmail.com on 15 Aug 2013 at 2:18

[GoogleCodeExporter]

The Controller named Xbox 360 is vJoy. I just renamed it. So it's that one 
thats being used by x360ce and it's that one that gives double input in DMC.

Original comment by kroo...@gmail.com on 15 Aug 2013 at 6:26

[GoogleCodeExporter]

Can you send me teamviewer information so i can inspect your system directly

Original comment by danialho...@gmail.com on 15 Aug 2013 at 8:59

[GoogleCodeExporter]

I'm at work atm.
The device you can see from ditool names Nintendo RVL... is the bluetooth 
connected physical controller. But Windows do not understand what kind of 
device it really is and there are no drivers for it.

To get a Wii U Pro Controller to communicate with Windows I need a software 
called WiinUPro.  The software automatically maps itself to a virtual gamepad 
(recognized and understood by windows), in my case vJoy (guid product 
bead1234-0000-0000-0000-504944564944) but named "Xbox 360 For Windows 
(Controller)" in Windows.

So by using WiinUPro I can map inputs to the virtual game pad Windows 
recognizes and after that I start games with your neat x360ce to have perfect 
and standard button configuration in all games. And it works so good until this 
DMC game just messes up.

I'm starting to think there is something wrong with the game since all other 
games automatically stops using Windows game pad when x360ce is detected.

http://gbatemp.net/threads/wiinupro-pro-controller-to-pc-gamepad.348537/ 

Original comment by kroo...@gmail.com on 15 Aug 2013 at 9:32

[GoogleCodeExporter]

Its the fact that the string is not being rewritten by x360ce to include _IG

this is required to prevent the game enumerating the device under both xinput 
and dinput, other games do this, mark of the ninja, maybe dead light as well.

a healthy x360ce log would appear like this

Original comment by danialho...@gmail.com on 15 Aug 2013 at 9:51

Attachments:

• DMC-DevilMayCry.exe_20130815-194749.log

[GoogleCodeExporter]

Hm ok. So the issue is with the game and can't be overridden in some way?

Original comment by kroo...@gmail.com on 15 Aug 2013 at 11:09

[GoogleCodeExporter]

Maybe string of this device is strange as Ouya one :P?

Original comment by tapcio on 15 Aug 2013 at 11:19

• Changed state: Accepted

[GoogleCodeExporter]

I tested for that with the dll in comment 1

Original comment by danialho...@gmail.com on 15 Aug 2013 at 11:27

[GoogleCodeExporter]

Original comment by danialho...@gmail.com on 9 Dec 2013 at 1:33

• Changed title: Wii U Pro Controller double input problem (uses a virtual gamepad driver)

[GoogleCodeExporter]

Issue 779 has been merged into this issue.

Original comment by danialho...@gmail.com on 14 Dec 2013 at 2:24

[GoogleCodeExporter]

Issue 779 has been merged into this issue.

Original comment by tapcio on 14 Dec 2013 at 2:27

[GoogleCodeExporter]

Issue 779 has been merged into this issue.

Original comment by tapcio on 14 Dec 2013 at 2:29

[GoogleCodeExporter]

Issue 779 has been merged into this issue.

Original comment by danialho...@gmail.com on 14 Dec 2013 at 2:36

[GoogleCodeExporter]

we might have a no-hacks-required fix

Original comment by danialho...@gmail.com on 21 Mar 2014 at 10:29

Attachments:

• xinput1_3.zip

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Cool Ive almost forgotten this.

Original comment by kroo...@gmail.com on 21 Mar 2014 at 10:47