Open GoogleCodeExporter opened 9 years ago
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:
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
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
https://code.google.com/p/x360ce/wiki/ReportingGameCompatibility
Original comment by danialho...@gmail.com
on 22 Oct 2013 at 10:34
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
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
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:
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
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
try lib32 r848
Original comment by danialho...@gmail.com
on 9 Dec 2013 at 1:29
Original issue reported on code.google.com by
marco.ba...@gmail.com
on 22 Oct 2013 at 6:28Attachments: