wine users - Nov 2006 - USB-joystick not detected

Hi,
I am using a CH Flightstick gameport-stick converted by a gameport-usb converter
(Rockfire). This works well under OpenSUSE Linux 10.1, ie. with FlightGear.
When I try to use this joystick with Wine wine-0.9.24 it is not detected with
two running (with keyboard) sims: Fly!II and A320 Simulator.
I also set a link # ln -s /dev/input/js0 /dev/js0 as suggested in other posts.

Here is my debug output when starting FLY!II:
georg@dhcppc3:~> wine --version
wine-0.9.24

HID 0583:2032 (/dev/input/js0)

# ln -s /dev/input/js0 /dev/js0

georg@dhcppc3:~> WINEDEBUG=joystick wine "c:\Programme\Terminal R
fly2.exe"
fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x173a58) :
g 64MB for now, returning 64MB left
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x16c398)->(0x10
fixme:d3d:IWineD3DDeviceImpl_CreateAdditionalSwapChain The app re
quests more than one back buffer, this can't be supported properl
y. Please configure the application to use double buffering(=1 ba
ck buffer) if possible
fixme:win:WIN_CreateWindowEx Parent is HWND_MESSAGE
fixme:dinput:IDirectInputDevice2AImpl_GetDeviceInfo (this=0x351c1
48,0x34f4b8): stub!
fixme:dinput:JoystickAImpl_SetProperty Unknown type 0xa (<guid-0x
000a>)
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1
48,0x34f37c,0,0x00000001): stub!
fixme:dinput:JoystickAImpl_SetProperty Unknown type 0xa (<guid-0x
000a>)
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1
48,0x34f37c,4,0x00000001): stub!
fixme:dinput:JoystickAImpl_SetProperty Unknown type 0xa (<guid-0x
000a>)
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,20,0x00000001): stub!
fixme:dinput:JoystickAImpl_SetProperty Unknown type 0xa (<guid-0x
                                                        000a>)
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,24,0x00000001): stub!
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,48,0x00000001): stub!
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,49,0x00000001): stub!
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,50,0x00000001): stub!
fixme:dinput:IDirectInputDevice2AImpl_GetObjectInfo (this=0x351c1              
                                                       
48,0x34f37c,51,0x00000001): stub!
err:ole:CoGetClassObject class {d67c0280-c743-11cd-80e5-00aa003e4              
                                                        b50} not registered
err:ole:CoGetClassObject class {d67c0280-c743-11cd-80e5-00aa003e4              
                                                        b50} not registered
err:ole:create_server class {d67c0280-c743-11cd-80e5-00aa003e4b50              
                                                        } not registered
err:ole:CoGetClassObject no class object {d67c0280-c743-11cd-80e5              
                                                        -00aa003e4b50} could be
created for context 0x7
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x16c398)->((nil),00000008)
fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblock

I am thankful for any help!
Regards
Georg

On Sat, Nov 18, 2006 at 09:22:38AM +0000, Georg Vollnhals wrote:

Hi Georg,
> I am using a CH Flightstick gameport-stick converted by a gameport-usb
> converter (Rockfire). This works well under OpenSUSE Linux 10.1, ie.
> with FlightGear.  When I try to use this joystick with Wine
> wine-0.9.24 it is not detected with two running (with keyboard) sims:
> Fly!II and A320 Simulator.  I also set a link # ln -s /dev/input/js0
> /dev/js0 as suggested in other posts.
please first try to run the game/wine using a proper setup with the
input-devices. as the device is HID and your stick and sim are more the
"sim" kind of rig you will run in less problems using the input
interface (proper button/axis detection, no implied deadzones, ...). you
should see /dev/input/eventXXX devices. also a trace to see what the app
does and why it fails should trace ``dinput`` (WINEDEBUG=+dinput ...)

-- 
cu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url :
http://www.winehq.org/pipermail/wine-users/attachments/20061120/0ee5c81d/attachment.pgp