To owners of xbox360 joysticks..
To owners of xbox360 joysticks..
I'm looking for people who have an xbox360 joystick to help run some
tests so I can get information on implementing xinput for wine.
The more 360 joysticks plugged in the better.
Can you please go to the forum post I made and test:
http://forum.freegamedev.net/index.php? ... 80&start=0
Thanks,
Andrew
tests so I can get information on implementing xinput for wine.
The more 360 joysticks plugged in the better.
Can you please go to the forum post I made and test:
http://forum.freegamedev.net/index.php? ... 80&start=0
Thanks,
Andrew
To owners of xbox360 joysticks..
It's not been completely implemented yet so many functions are missing
if that is your problem. You can get around this by using the
Microsoft dll. ( xinput1_3.dll )
Yes if you could run the tests and email me the data it would help,
the more data the better. The more controllers plugged in the better
too.
Regards,
Andrew
On Sun, Dec 7, 2008 at 5:48 PM, chourmovs <[email protected]> wrote:
if that is your problem. You can get around this by using the
Microsoft dll. ( xinput1_3.dll )
Yes if you could run the tests and email me the data it would help,
the more data the better. The more controllers plugged in the better
too.
Regards,
Andrew
On Sun, Dec 7, 2008 at 5:48 PM, chourmovs <[email protected]> wrote:
do you still need it ? maybe i can help
In any case, i've problem with every xinput game since it's implementation in wine
is it normal ?
here are my result with one computer connected
xinput.c:88: -- Results for controller 0 --
xinput.c:89: XInputGetCapabilities: 0
xinput.c:90: Type: 0x00000000
xinput.c:91: SubType: 0x00000001
xinput.c:92: Flags: 0x4
xinput.c:94: Gamepad: 0xfffff3ff
xinput.c:95: Gamepad.wButtons: 0xf3ff
xinput.c:96: Gamepad.bLeftTrigger: 0x000000ff
xinput.c:97: Gamepad.bRightTrigger: 0x000000ff
xinput.c:98: Gamepad.sThumbLX: -64
xinput.c:99: Gamepad.sThumbLY: -64
xinput.c
Gamepad.sThumbRX: -64
xinput.c:101: Gamepad.sThumbRY: -64
xinput.c:103: Vibration: 0x00ff00ff
xinput.c:104: Vibration.wLeftMotorSpeed: 0xff
xinput.c:105: Vibration.wRightMotorSpeed: 0xff
xinput.c:84: Tests skipped: Controller 1 is not connected
xinput.c:84: Tests skipped: Controller 2 is not connected
xinput.c:84: Tests skipped: Controller 3 is not connected
xinput.c:49: -- Results for controller 0 --
xinput.c:50: XInputGetState: 0
xinput.c:51: State->dwPacketNumber: 21163
xinput.c:53: Gamepad: 0x00000000
xinput.c:54: Gamepad.wButtons: 0
xinput.c:55: Gamepad.bLeftTrigger: 0x00000000
xinput.c:56: Gamepad.bRightTrigger: 0x00000000
xinput.c:57: Gamepad.sThumbLX: -584
xinput.c:58: Gamepad.sThumbLY: -275
xinput.c:59: Gamepad.sThumbRX: 1229
xinput.c:60: Gamepad.sThumbRY: 981
xinput.c:45: Tests skipped: Controller 1 is not connected
xinput.c:45: Tests skipped: Controller 2 is not connected
xinput.c:45: Tests skipped: Controller 3 is not connected
xinput.c:88: -- Results for controller 0 --
xinput.c:89: XInputGetCapabilities: 0
xinput.c:90: Type: 0x00000000
xinput.c:91: SubType: 0x00000001
xinput.c:92: Flags: 0x4
xinput.c:94: Gamepad: 0xfffff3ff
xinput.c:95: Gamepad.wButtons: 0xf3ff
xinput.c:96: Gamepad.bLeftTrigger: 0x000000ff
xinput.c:97: Gamepad.bRightTrigger: 0x000000ff
xinput.c:98: Gamepad.sThumbLX: -64
xinput.c:99: Gamepad.sThumbLY: -64
xinput.c
Gamepad.sThumbRX: -64
xinput.c:101: Gamepad.sThumbRY: -64
xinput.c:103: Vibration: 0x00ff00ff
xinput.c:104: Vibration.wLeftMotorSpeed: 0xff
xinput.c:105: Vibration.wRightMotorSpeed: 0xff
xinput.c:84: Tests skipped: Controller 1 is not connected
xinput.c:84: Tests skipped: Controller 2 is not connected
xinput.c:84: Tests skipped: Controller 3 is not connected
xinput: 15 tests executed (0 marked as todo, 0 failures), 9 skipped.
xinput.c:88: -- Results for controller 0 --
xinput.c:89: XInputGetCapabilities: 0
xinput.c:90: Type: 0x00000000
xinput.c:91: SubType: 0x00000001
xinput.c:92: Flags: 0x4
xinput.c:94: Gamepad: 0xfffff3ff
xinput.c:95: Gamepad.wButtons: 0xf3ff
xinput.c:96: Gamepad.bLeftTrigger: 0x000000ff
xinput.c:97: Gamepad.bRightTrigger: 0x000000ff
xinput.c:98: Gamepad.sThumbLX: -64
xinput.c:99: Gamepad.sThumbLY: -64
xinput.c
xinput.c:101: Gamepad.sThumbRY: -64
xinput.c:103: Vibration: 0x00ff00ff
xinput.c:104: Vibration.wLeftMotorSpeed: 0xff
xinput.c:105: Vibration.wRightMotorSpeed: 0xff
xinput.c:84: Tests skipped: Controller 1 is not connected
xinput.c:84: Tests skipped: Controller 2 is not connected
xinput.c:84: Tests skipped: Controller 3 is not connected
xinput.c:49: -- Results for controller 0 --
xinput.c:50: XInputGetState: 0
xinput.c:51: State->dwPacketNumber: 21163
xinput.c:53: Gamepad: 0x00000000
xinput.c:54: Gamepad.wButtons: 0
xinput.c:55: Gamepad.bLeftTrigger: 0x00000000
xinput.c:56: Gamepad.bRightTrigger: 0x00000000
xinput.c:57: Gamepad.sThumbLX: -584
xinput.c:58: Gamepad.sThumbLY: -275
xinput.c:59: Gamepad.sThumbRX: 1229
xinput.c:60: Gamepad.sThumbRY: 981
xinput.c:45: Tests skipped: Controller 1 is not connected
xinput.c:45: Tests skipped: Controller 2 is not connected
xinput.c:45: Tests skipped: Controller 3 is not connected
xinput.c:88: -- Results for controller 0 --
xinput.c:89: XInputGetCapabilities: 0
xinput.c:90: Type: 0x00000000
xinput.c:91: SubType: 0x00000001
xinput.c:92: Flags: 0x4
xinput.c:94: Gamepad: 0xfffff3ff
xinput.c:95: Gamepad.wButtons: 0xf3ff
xinput.c:96: Gamepad.bLeftTrigger: 0x000000ff
xinput.c:97: Gamepad.bRightTrigger: 0x000000ff
xinput.c:98: Gamepad.sThumbLX: -64
xinput.c:99: Gamepad.sThumbLY: -64
xinput.c
xinput.c:101: Gamepad.sThumbRY: -64
xinput.c:103: Vibration: 0x00ff00ff
xinput.c:104: Vibration.wLeftMotorSpeed: 0xff
xinput.c:105: Vibration.wRightMotorSpeed: 0xff
xinput.c:84: Tests skipped: Controller 1 is not connected
xinput.c:84: Tests skipped: Controller 2 is not connected
xinput.c:84: Tests skipped: Controller 3 is not connected
xinput: 15 tests executed (0 marked as todo, 0 failures), 9 skipped.
To owners of xbox360 joysticks..
On Sun, Dec 14, 2008 at 9:10 AM, chourmovs <[email protected]> wrote:
Thankshere are my result with one computer connected
Another contribution
I tested this device mapper under wine 1.1.10 with your incuded xinput implementation
All worked fine except LT and RT button seen as axes
I think xinput is involved because it stopped working for me with native xinput1_3.dll
http://www.lejoueurlibre.com/wp-content ... mapper.exe
Maybe it can be usefull
I tested this device mapper under wine 1.1.10 with your incuded xinput implementation
All worked fine except LT and RT button seen as axes
I think xinput is involved because it stopped working for me with native xinput1_3.dll
http://www.lejoueurlibre.com/wp-content ... mapper.exe
Maybe it can be usefull
drivers/input/joystick/xpad.c in the Linux kernel source will tell you id's of xbox and xbox360 joysticks supported by Linux kernel.
There is a chance doing such a broad test that the you find joysticks not support by the Linux kernel. First basic advice if its not turning up as a linux joystick no point any more tests problem is in the xpad section of the kernel.
Even worse doing a broad test like this be aware that your reading could be off because the kernel is off. So I would recommend getting kernel version number and wine version number as well as device/s in test information.
Sorry cannot help you any more than good advice. No xbox joysticks of any form.
There is a chance doing such a broad test that the you find joysticks not support by the Linux kernel. First basic advice if its not turning up as a linux joystick no point any more tests problem is in the xpad section of the kernel.
Even worse doing a broad test like this be aware that your reading could be off because the kernel is off. So I would recommend getting kernel version number and wine version number as well as device/s in test information.
Sorry cannot help you any more than good advice. No xbox joysticks of any form.
To owners of xbox360 joysticks..
These tests are suppose to be done in windows not Linux. I am lookingSorry cannot help you any more than good advice. No xbox joysticks of any form.
specifically at the xinput API and what data is returned.