Direct X Input
Direct X Input
Good Evening,
I have an app that is not in the app database entitled RealFLight G4. I have it installed, but ut used the Direct X input method to talk to a hand held joystick like controller in which is embedded security and copy protection.
The application is griping about not being able to find the Interlink Controller. In dmesg it shows up and is usable in other applications, so Linux recognizes it.
I have spent the evening looking for a Direct X Input method and have been able to find only blurbs, yet no "How To's"
Can someone please educate me on Direct X Input and how to turn it on in Wine (if it is possible)?
I appreciate your help.
Dave Babb
I have an app that is not in the app database entitled RealFLight G4. I have it installed, but ut used the Direct X input method to talk to a hand held joystick like controller in which is embedded security and copy protection.
The application is griping about not being able to find the Interlink Controller. In dmesg it shows up and is usable in other applications, so Linux recognizes it.
I have spent the evening looking for a Direct X Input method and have been able to find only blurbs, yet no "How To's"
Can someone please educate me on Direct X Input and how to turn it on in Wine (if it is possible)?
I appreciate your help.
Dave Babb
Re: Direct X Input
You can check what it's doing by enabling +dinput debug channel. It should be enumerating through all the devices (or at least all joysticks).dcbdbis wrote:Good Evening,
I have an app that is not in the app database entitled RealFLight G4. I have it installed, but ut used the Direct X input method to talk to a hand held joystick like controller in which is embedded security and copy protection.
The application is griping about not being able to find the Interlink Controller. In dmesg it shows up and is usable in other applications, so Linux recognizes it.
Most likely it wants to see a particular device name and vendor. This part will be different on Wine then windows. Wine reports vendor and device name in one string ex : "Logitech Logitech Dual action".
From the directory where the exe is located:
For more info on debug channels: http://wiki.winehq.org/DebugChannels
Code: Select all
WINEDEBUG=+dinput wine LauncherG4.exe
Direct X Input
On Thu, Aug 21, 2008 at 9:54 AM, dcbdbis <[email protected]> wrote:
$ WINEDEBUG=+dinput wine LauncherG4.exeThank you for your reply. I am older, and have had some strokes. Would you please tell me how to enable the +dinput channel?
Thank you !
Dave
WINEDEBUG=+dinput.....
Thank you for the assistance.
Now I need to find where wine is storing the debug files. in the terminal, both as su and my normal user I get no debug messages.
Where can I find the logs so I can trck this thing down?
Thank you!
Dave..
Now I need to find where wine is storing the debug files. in the terminal, both as su and my normal user I get no debug messages.
Where can I find the logs so I can trck this thing down?
Thank you!
Dave..
Re: WINEDEBUG=+dinput.....
Then your problem has nothing to do with dinput. BTW DO NOT run Wine as root!!!dcbdbis wrote:Thank you for the assistance.
Now I need to find where wine is storing the debug files. in the terminal, both as su and my normal user I get no debug messages.
Next you might want to look at what your program tries to find in registry. I think that would be +reg channel.
Winedebug
Thank you again for the quick reply.
I think I get it now.
On the Winehq site there is a list of debug channels I can select with winedebug, and thuis track down where the error is really coming from.
Thank you so much for your help. I appreciate it.
Dave
I think I get it now.
On the Winehq site there is a list of debug channels I can select with winedebug, and thuis track down where the error is really coming from.
Thank you so much for your help. I appreciate it.
Dave