Madden NFL 2008 pc - Exchanged right stick axes

[GoogleCodeExporter]

Steps will reproduce the problem?
1. Set up controller to work correctly in x360ce App
2. Play (simplest thing would be offense only practice)

What is the expected output? What do you see instead?
I would expect the R-stick behave as configured: pushing R-stick up should 
perform a "power move", pushing it down should briefly stop running, pushing it 
left or right should juke accordingly.
What instead happens is pushing it up jukes left, pushing it down jukes right, 
pushing it left "pushes through defenders", pushing it right stops the run.
In a prospect:

R-stick move --> should do --> does
Up --> pushes through --> jukes left
Down --> stops run --> jukes right
Left --> jukes left --> pushes through
Right --> jukes right --> stops run

Of course I tried exchanging axes in x360 app, having them acting WRONG in the 
app, but nothing changes. Actually I tried various combinations of hooks, hook 
modes and so on, but nothing changes at all with right stick. It always acts 
the way I described above.

What versions of x360ce and Windows are you using?
x360ce 2.1.2.191b2 with Windows 8

What gamepad do you use? On what drivers version?
Generic USB gamepad (which I have been able to configure with x360 and both NBA 
2k14 and FIFA14). Driver is standard Microsoft version 6.2.9200.16656

Please attach a log file created with Log=1 setting in x360ce.ini file.
Also make sure you use latest x360ce libraries !
I am attaching a log created with the controller configured to behave correctly 
in x360 app, no game database in game dir, only Hookmode=1 in [InputHook] 
section of the ini file and another one using gdb with input mask set to 
0x00000002

Original issue reported on code.google.com by marco.ba...@gmail.com on 22 Oct 2013 at 6:28

Attachments:

• MAINAPP.EXE_20131022-081005.log
• MAINAPP.EXE_20131022-082334.log

[GoogleCodeExporter]

Update. I have read issues 597 and did some more attempts.
First and foremost: I confirm without dinput8.dll in the gamedirectory x360 
does not even produce a log file as the other user reported.
With this version of xce360 and/or my gamepad instead it has no problem 
starting either with:

Hookmode=1
HookDI=1
HookCOM=1
HookPIDVID=1

OR

Hookmode=1
HookDI=1
HookCOM=1
HookName=1

Here's a log produced with the PIDVID hook set, but the one with HookName is 
identical. In these tests the gamepad was configured to work correctly in 
x360app

Everythink looks just fine, except it does not handle the right stick...

Original comment by marco.ba...@gmail.com on 22 Oct 2013 at 7:42

Attachments:

• MAINAPP.EXE_20131022-093442.log

[GoogleCodeExporter]

the xinput pad itself is not being created, so Xinput is not even being used. - 
that'd explain why the right stick isn't working.

Original comment by danialho...@gmail.com on 22 Oct 2013 at 9:06

[GoogleCodeExporter]

What else could I try to have it created?
(Also, I understand it is not related to the bug but I would appreciate if you 
could point me to some docs on how Hookinput translates to Hookmask - as it is 
my understanding that the two are the same thing)

Original comment by marco.ba...@gmail.com on 22 Oct 2013 at 9:10

[GoogleCodeExporter]

https://code.google.com/p/x360ce/wiki/ReportingGameCompatibility

Original comment by danialho...@gmail.com on 22 Oct 2013 at 10:34

[GoogleCodeExporter]

Thanks danialho,

Meanwhile I could find some of the documentation too. This afternoon I will 
make some tests.
Am I correct in my understanding that I can work with the InputHook section in 
x360ce.ini file (and removing any hookmode), and then translating it to a 
hookmasks for gdb once I found a working combination?

Original comment by marco.ba...@gmail.com on 22 Oct 2013 at 10:45

[GoogleCodeExporter]

that is correct, the game might also use a different xinput file name too, so 
check that as well.

Original comment by danialho...@gmail.com on 22 Oct 2013 at 2:03

[GoogleCodeExporter]

No luck, I tried adding more and more hooks, with all the xinput file name in 
the game directory, but to no avail. Here's my latest ini file and the 
corresponding log, where you can see the xinput pad is not being created at all.
I know that putting all the .dll together does no harm, how about packing all 
the hooks? I tried with HookCOM and HookLL first, then added PIDVID, then DI, 
then Name etc. etc.... Shall I try with only some enabled and other disabled 
(i.e. COM PIDVID disabled, LL and DI enabled), or are also hooks safe to be 
added when not needed, and we can give up on Madden NFL 08?

Original comment by marco.ba...@gmail.com on 22 Oct 2013 at 5:21

Attachments:

• MAINAPP.EXE_20131022-191034.log
• x360ce.ini

[GoogleCodeExporter]

uh, having all the dll's in the game folder can cause problems actually,  
atleast it did with GTA4 way back when.

Original comment by danialho...@gmail.com on 22 Oct 2013 at 10:34

[GoogleCodeExporter]

Hm, I tried with 1 dll at a time, still no luck, the pad is not created.
Seems like it won't work with some kind of new developments, at least with my 
gamepad. :(

Original comment by marco.ba...@gmail.com on 23 Oct 2013 at 10:20

[GoogleCodeExporter]

try lib32 r848

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