[Wine] Re: dinput_test works but WINEDEBUG shows no joystick for game?

[gnivler]

vitamin wrote:
> 
> gnivler wrote:
> > This is a continuation/evolution of what I've been trying to do, get some response from my controller(s) in Guitar Hero 3.  I compiled wine (with some help :) and manually copied the dinput_test.exe.so file into my /usr/lib32/wine directory and made it's permissions match the other exe.so files (644).  I then run the test to see if dinput is seeing/reacting to my controller, and it seems to.  I then run GH3 with +dinput on debug and don't get a single line mentioning 'joy'.  I'm curious if this makes sense, or tells someone what might need to be looked at next.  Here's my terminal output (new hostname :)) :
> > 
> > mason at beast:~/c/Program Files/Aspyr/Guitar Hero III$ WINETEST_INTERACTIVE=1 wine dinput_test joystick
> > joystick.c:408:DLL Version: 5.1.2600.881
> > joystick.c:386:-- Testing Direct Input Version 0x0700 --
> > joystick.c:202:---- Xbox Gamepad (userspace driver) ----
> > joystick.c:335:You have 30 seconds to test all axes, sliders, POVs and buttons
> > joystick.c:340:
> > joystick.c:360:X -136 Y  -82 Z  -63 Rx   54 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -136 Y  -82 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 1 0 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -122 Y  -75 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -136 Y  -75 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 1 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -129 Y  -75 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -129 Y  -82 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 1 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -129 Y  -75 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 0 0 0 0 0 0 0 0 0
> > joystick.c:360:X -129 Y  -82 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 1 0 0 0 0 0 0 0 0
> > joystick.c:360:X -129 Y  -75 Z -160 Rx   35 Ry-2000 Rz-2000 S0    0 S1    0 POV0   -1 POV1   -1 POV2   -1 POV3   -1 B 0 0 0 0 0 0 0 0 0 0 0 0
> > mason at beast:~/c/Program Files/Aspyr/Guitar Hero III$ WINEDEBUG=+dinput wine GH3.exe 2>&1 | grep -i joy    (I believe vitamin suggested find_joydev in another post, what I'm basing my smaller match on)
> > mason at beast:~/c/Program Files/Aspyr/Guitar Hero III$
> 
> 
> Then this program is not using dinput. Try WINEDEBUG=+joystick


I ran some isolating tests and I posted the terminal output here:  http://www.mediafire.com/?a2tngxntdlx so you can view the flat text files instead of 40 pages in the forum.  The 7z has two text files, each with different WINEDEBUG settings, noted in the file name itself for clarity.  One output file is +joystick and the other is -all,+dinput which actually shows quite a bit of dinput debug but it looks like all keyboard and mouse stuff to me only.  +joystick didn't spit out anything I recognized, but the output is there for review if you want it.

My command lines were redirected like 'WINEDEBUG=opts wine prog.exe > outputfile.txt 2>&1' which I think is right.

Your expertise on the subject would be great, I'm at a loss of what I can test next, or look at.  Thank you