![]() That your time spent on me has actually helped me quite a lot, I've I'm sorry for wasting your time, but I can at least tell you I know how frustrating user support can be too, I've done it for a I've been polite and as thorough as I'm able toīe. Hey man, I don't see the need to get angry, I wasn't jerking you aroundīecause I wanted to. Instead of wasting my time you should have said something about that in the beginning. Use to get the game running, along with d3dx9_36. Get the sense this is somehow a core part of the failure. What kind of reaction wine would have to this extra dinput library, ifĪny (assuming that question even makes sense)? Is there any method ofĭebugging it's activity? I don't understand this stuff very well but I It says that it uses a different API and it's specifically for xbox 360Ĭontrollers among other things. Xinput1_3.dll is, and wikipedia has an entry for it: Off on a tangent I wanted to figure out what Saved each session to a CSV file and I'm looking over a ton of plain The guitar controller working then again with it not even plugged in, Process Monitor (sysinternals) to dump all activity from GH3.exe with Unfortunately I don't know where exactly can that be.Īh very cool, it kind of seemed to way to me also, just wasn't even So it must be looking somewhere else (registry?) to see if it's controller present or not. Well looking at it - this program does not query, enumerate or otherwise ask for joystick. Your expertise on the subject would be great, I'm at a loss of what I can test next, or look at. My command lines were redirected like 'WINEDEBUG=opts wine prog.exe > outputfile.txt 2>&1' which I think is right. +joystick didn't spit out anything I recognized, but the output is there for review if you want it. 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. The 7z has two text files, each with different WINEDEBUG settings, noted in the file name itself for clarity. I ran some isolating tests and I posted the terminal output here: so you can view the flat text files instead of 40 pages in the forum. Here's my terminal output (new hostname ) Files/Aspyr/Guitar Hero III$ WINETEST_INTERACTIVE=1 wine dinput_test joystick ![]() I'm curious if this makes sense, or tells someone what might need to be looked at next. I then run GH3 with +dinput on debug and don't get a single line mentioning 'joy'. I then run the test to see if dinput is seeing/reacting to my controller, and it seems to. I compiled wine (with some help and manually copied the dinput_ file into my /usr/lib32/wine directory and made it's permissions match the other exe.so files (644). 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. 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 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 Files/Aspyr/Guitar Hero III$ Joystick.c:335:You have 30 seconds to test all axes, sliders, POVs and buttons Joystick.c:202:- Xbox Gamepad (userspace driver). Joystick.c:386:- Testing Direct Input Version 0x0700. ![]() ![]() This is a continuation/evolution of what I've been trying to do, get some response from my controller(s) in Guitar Hero 3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |