Madden NFL 2008 compatibility

[GoogleCodeExporter]

Steps will reproduce the problem?
1. I'm using a Snakebyte PS3 USB controller and Madden NFL 2008 (the controller 
works with x360ce with other more recent games, such as Saints Row 3 and The 
Witcher 2)
2. I've used either the VS2010 or VS2012 x86 libraries and tested with the most 
recent few executables
3. Madden's mainapp.exe needs dinput8.dll and xinput1_3.dll to have x360ce to 
hook in as well as hookmasks HookDI and HookName to change the behavior of the 
controller in game. I have tried other combinations of hookmasks. WT doesn't 
seem to do anything different, SA, LL, and COM don't seem to initialize very 
far, and without DI the log doesn't get beyond the first two lines, reporting 
x360ce's and Windows' versions.

What is the expected output? What do you see instead?
Unfortunately, the buttons are completely incorrect in game with the above 
settings. For instance, the right analog stick functions as some of the buttons 
A-B-X-Y, the right trigger is the Start Button and the left trigger is Select, 
but the left analog stick and d-pad work fine. 

This is likely because, as you'll note in the log, x360ce does not successfully 
create the pad, but only changes the name and then gets stuck on
[HookDI ] *CreateDeviceA*
[HookDI ] Hooking GetPropertyA

What versions of x360ce and Windows are you using?
x360ce 3.4.0.732
Windows 7 Professional, x64, fully updated

What gamepad do you use? On what drivers version?
Snakebyte PS3 USB controller. Windows 'generic' PS3 driver 6.1.7601.17514

I'm completely willing to post further log files from other hookmasks, etc if 
that would be useful. My .ini is also included.

Please attach a log file created with Log=1 setting in x360ce.ini file.
Also make sure you use latest x360ce libraries !

Original issue reported on code.google.com by taleworl...@gmail.com on 23 Jun 2013 at 8:58

Attachments:

• mainapp.exe_20130623-163822.log
• x360ce.ini

[GoogleCodeExporter]

all of EA's sports games use a similar engine, and work with HookCOM.

Original comment by danialho...@gmail.com on 24 Jun 2013 at 6:33

[GoogleCodeExporter]

HookCOM + HookDI + HookPIDVID should sort it out.

HookCOM prevents the control from creating 2 instances (DI and XI) while 
HookPIDVID requires HOOKDI to fake the controller id

Original comment by danialho...@gmail.com on 24 Jun 2013 at 6:36

[GoogleCodeExporter]

Thanks for the reply!

With
[InputHook]
HookDI=1
HookCOM=1
HookPIDVID=1

I get the attached log result. HookCOM hangs at "CoCreateInstance"

Original comment by taleworl...@gmail.com on 24 Jun 2013 at 2:24

Attachments:

• mainapp.exe_20130624-102216.log

[GoogleCodeExporter]

remove dinput8.dll from the folder

Original comment by danialho...@gmail.com on 27 Jun 2013 at 9:17

[GoogleCodeExporter]

Thanks again for the reply.

Without dinput8.dll, x360ce doesn't appear to hook in or get called at all: the 
debug console doesn't come up and no log file is generated, though both are 
still set on. I tested this with the above InputHook settings and with multiple 
copies of the xinput .dll--xinput1_1, 1_2, 1_3, and 9_1_0.

Original comment by taleworl...@gmail.com on 27 Jun 2013 at 1:50

[GoogleCodeExporter]

You might be better off trying Scarlet Crushes DS3 driver, since it has native 
xinput.

Original comment by danialho...@gmail.com on 27 Jun 2013 at 5:38