usb interface support

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
Jörg Kühne

usb interface support

Post by Jörg Kühne »

Dear wine user group

I removed the whole installation under the root path and reinstalled the application to the user directory -thanks to mr. vitamin.
But the effect is the same - the usb interface has not be enabled although the driver works correctly, see
jstest /dev/input/js0 ->

Driver version is 2.1.0.
Joystick (IPACS Ikarus Gamecommander) has 7 axes (X, Y, Z, Rx, Ry, Rz, Throttle)
and 6 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0:-16891 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0:-16891 1:-17229 2: 0 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0:-16891 1:-17229 2:-20269 3: 0 4: 0 5: 0 6: 0 Butt
Axes: 0:-16891 1:-17229 2:-20269 3:-32767 4: 0 5: 0 6: 0 Butt
Axes: 0:-16891 1:-17229 2:-20269 3:-32767 4:-32767 5: 0 6: 0 Butt
Axes: 0:-16891 1:-17229 2:-20269 3:-32767 4:-32767 5:-17229 6: 0 Butt
Axes: 0:-16891 1:-17229 2:-20269 3:-32767 4:-32767 5:-17229 6:-32431 Butt
Axes: 0:-17229 1:-17229 2:-20269 3:-32767 4:-32767 5:-17229 6:-32431 Butt
ons: 0:on 1:off 2:off 3:off 4:off 5:off

During the installation of the simulator an icon was placed on the desktop. This has following properties:

command: env WINEPREFIX="/home/joerg.kuehne/.wine" wine "C:\Programme\IPACS\AeroFly Professional Deluxe\flyrun.exe"
working directory: /home/joerg.kuehne/.wine/dosdevices/c:/Programme/IPACS/AeroFly Professional Deluxe

May someone has an idea how I get to the debug information in the console -> WINEDEBUG=+dinput wine your_program.exe
Or may someone has an idea how I could map the usb device to the application?

thanks in advance.

best regards.

joerg


--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
Tlarhices
Level 4
Level 4
Posts: 101
Joined: Sun Mar 02, 2008 9:28 pm

Post by Tlarhices »

jstest /dev/input/js0
If I remember correctly :
/dev/input/js* is an event system, but it's not the one used by wine.
Wine use the /dev/input/event*

First you have to find which one is the one for your joystick, so test these ones and also look if your current user has access to it.

To test an event you can type in a terminal :

Code: Select all

evtest /dev/input/event0
Press a few buttons, if it react to it you have the good one. If it tell you you can't access it, you have a problem with the rights. Check with your distribution how to solve these rights problems if any. There is a better tool than evtest, but right now I can't remember, sorry.

Note that this event number can change every time you plug the joystick and/or restart the computer. If it's the case, see with your distribution how to make a fixed one for your joystick.

To have the debug information, start a terminal and type :

Code: Select all

cd ~/.wine/drive_c/Programme\IPACS\AeroFly\ Professional\ Deluxe
WINEDEBUG=+dinput wine flyrun.exe > dinput.log 2>&1
And you will have all the informations in the file dinput.log then put the content of this file here so it can be looked over.
Jörg Kühne

usb interface support

Post by Jörg Kühne »

dear wine user group

I have a problem with my usb commander (7-channel commander) which is not mapped correctly to the application. If I test the event handling as root with the following command:

evtest /dev/input/event8 -> this has the following output:

Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x127f product 0xe008 version 0x100
Input device name: "IPACS Ikarus Gamecommander"
etc.
and it reacting correctly to the usb commander events reps. it is responding to the axes-movements of the usb commander.

the command:

cd ~/.wine/drive_c/Programme\IPACS\AeroFly\ Professional\ Deluxe
WINEDEBUG=+dinput wine flyrun.exe > dinput.log 2>&1
gives following output:


trace:dinput:find_joydevs Found a joystick on /dev/input/event8: IPACS Ikarus Gamecommander ({9e573eda-7734-11d2-8d4a-23903fb6bdf7})
trace:dinput:find_joydevs ... with axis 0: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 1: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 2: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 3: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 4: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 5: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 6: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:fill_joystick_dideviceinstanceA 580 0x33fab0
trace:dinput:IDirectInput7AImpl_CreateDeviceEx

and even more:

race:dinput:JoystickAImpl_SetProperty proprange(-1000,1000) obj=-1
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:joystick_map_axis (0 <0> 255) -> (-1000 <2> 1000): val=-127 ret=-996
trace:dinput:IDirectInputAImpl_EnumDevices - checking device 2 ('Wine Linux-input joystick driver')
trace:dinput:IDirectInputAImpl_EnumDevices - checking device 3 ('Wine Linux joystick driver')
trace:dinput:joydev_enum_deviceA Enumerating the linux Joystick device: /dev/input/js0 (IPACS Ikarus Gamecommander)

and even more:

trace:dinput:IDirectInputAImpl_EnumDevices - checking device 3 ('Wine Linux joystick driver')
trace:dinput:hook_thread_proc Processing hook change notification lp:0
trace:dinput:JoystickAImpl_Unacquire (this=0x14abd0)
trace:dinput:JoystickAImpl_Unacquire (this=0x14abd0)
trace:dinput:JoystickAImpl_SendForceFeedbackCommand (this=0x14abd0,1)
trace:dinput:release_DataFormat Deleting DataFormat: 0x14ac34
trace:dinput:IDirectInputAImpl_Release (0x147518) releasing from 3
trace:dinput:JoystickAImpl_Unacquire (0x15ac18)
trace:dinput:JoystickAImpl_Unacquire closing joystick device
trace:dinput:hook_thread_proc Processing hook change notification lp:0
trace:dinput:hook_thread_proc Processing hook change notification lp:0

thanks for your help in advanced.

best regards

joerg


--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/e ... le/6169196
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: usb interface support

Post by vitamin »

Jörg Kühne wrote:trace:dinput:find_joydevs Found a joystick on /dev/input/event8: IPACS Ikarus Gamecommander ({9e573eda-7734-11d2-8d4a-23903fb6bdf7})
trace:dinput:find_joydevs ... with axis 0: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 1: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 2: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 3: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 4: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 5: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:find_joydevs ... with axis 6: cur=0, min=0, max=255, fuzz=0, flat=15
trace:dinput:fill_joystick_dideviceinstanceA 580 0x33fab0
trace:dinput:IDirectInput7AImpl_CreateDeviceEx
Everything looks fine. Open a bug report and attach complete output (as a text file).
Locked