1.9.1 for Windows doesn't seem to include js_demo.exe at all. Does anyone know where I might find it?
Saitek x52 pro don't work under Ubuntu 9.10
Hello to everyone, I have an X52 pro flight control system.
I can't use it under ubuntu. I don't know why.
I have followed the FG getstartguide.pdf to check the device.
The commands that I've used to check:
1) andrea@andrea-IBM:~$ lsusb
Bus 004 Device 004: ID 06a3:0762 Saitek PLC
2) andrea@andrea-IBM:~$ dmesg | grep Joystick
[ 875.178360] generic-usb 0003:06A3:0762.0002: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0
[ 983.266631] generic-usb 0003:06A3:0762.0003: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0
[ 4743.317355] generic-usb 0003:06A3:0762.0004: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0
3) Confirming that the driver recognizes your joystick
Joystick test program.
Joystick 0 not detected
Joystick 1 not detected
Joystick 2 not detected
Joystick 3 not detected
Joystick 4 not detected
Joystick 5 not detected
Joystick 6 not detected
Joystick 7 not detected
Can anyone help me? --Andreasantopietro 22:42, 6 August 2010 (UTC)
Different configurations for the same stick depending on OS (Linux vs. Windows)
I'm using js_demo on Linux (here: Ubuntu Lucid x64 with joystick "SpeedLink Black Widow")
On Linux it's detected as "Mega World USB Game Controller", on Windows js_demo detects a "SL-6640 Black Widow Flightstick".
I define cooliehat left/right and up/down for view direction and view elevation. On Linux the numbering of the cooliehat axis differs from what is detected on Windows. This I can respect by using the number-tag in my XML. Additional view elevation is opposite in both OSs. Linux move up = axis 5 -> -1, move down = axis 5 -> +1; Windows move up = axis 7 -> +1, move down = axis 7 -> -1. How can I respect these differences in my config.xml?
--D-SKY1 10:54, 7 August 2010 (UTC)
Some suggestions for improvement
Under Built-in Joystick Support:
- Bullet 2: Seeing as they might be adding another "joystick" or they might be starting off with a yoke, rudder and throttle-quadrant, they need to look at ALL the Joystick #n entries.
- Bullet 3: After editing xml file, re-run FG (or from v2.8, Debug Reload Input) to see if it is now using that file (instead of default).
All over the article: Start > Control Panel > Game Controller doesn't work in later versions of Windows.
Also, I am prepared to write details about how to achieve specific things, showing how (and when) to use <binding></binding>, <script></script>, <mod-ctrl></mod-ctrl>; how to handle Unix and Windows assigning different button and axis numbers, and all that stuff.
Macnab 05:39, 10 October 2012 (EDT)
- looks okay to me. Please make your edits as you please. We can always revert/finetune them whenever there is a need for that, so don't feel shy ;-)
- Gijs 10:38, 10 October 2012 (EDT)
Getting different mouse modes when using another control
|I want to disable the mouse-as-yoke control so that right clicking changes only between pointer and view control.
$ fgfs --prop:input/mice/mouse/mode/button/binding/value=2
I just don't know where to put it.
- Nowhere. The upcoming release has a built-in function to change the mouse behaviour ;-)
- Gijs 18:12, 21 May 2013 (UTC)
Multiple devices on Windows
Is this tip really necessary anymore? Did it get fixed for Windows? If so, then I don't think it should really be recommended. Also is it version specific, e.g. win XP? —Philosopher 18:07, 21 May 2013 (UTC)
- No idea if it's still valid. But, it's not a "recommendation" for everyone. The article clearly reads "(..) there may be cases, where the same driver name is reported twice. In this case (..)" It could use some rewording though, to make it more clear that this is in general not required.
- Gijs 18:12, 21 May 2013 (UTC)
Name: "Joystick" or "Input Device"
I'm wondering if we should move this back to "Joystick" as, contrary to Gijs' message , it seems like it only covers what it calls "joysticks". I mean, yes it does have a section "Joystick or yoke?", but after that "joystick" is used to denote both types of device, while "input device" could refer to mice, keyboards, and other things (like 3DConnexion products). So I would suggest that we move it back to "joystick", because even though that term doesn't technically include yokes, it sorta does imply it at least ;-). (As evidenced by the fact that Yoke already redirects to Joystick.) Just my 2¢. —Philosopher (talk) 14:16, 4 April 2014 (UTC)
- What about "Joysticks and other controls" or "Joysticks and other input devices"?
- —Johan G (Talk | contribs) 10:00, 21 April 2014 (UTC)
Saitek ST290 Pro Joystick with Windows 10
The following information are notes I made to document the symptoms I am having.
Valid for FlightGear version 2020.3.8 and earlier using default config file with Windows 10 64 bit.
Years ago, the joystick worked correctly. But I can't remember with what FlightGear version.
I also created a fix when the problem first started. But I can't remember what I did and I apparently didn't create a notes file saying what I did.
Problem is there using the default drivers from Windows 10 64 bit and with Saitek's drivers.
To get a nice graphical image to verify the joystick works, install driver and software from saitek.com:
- Open Windows Settings / Devices / Devices and Printer. Right-click on the joystick. Select "Game Controller Settings". Click on Properties.
- That opens a dialog box showing an image of the joystick and its controls.
- Can use it to verify that the joystick works.
For me: the dialog box shows that everything works properly.
However, FlightGear's Joystick Configuration window shows:
..... = control's input value changes proportionally to control's position.
Axis 0 Aileron = -1.0 at full left aileron ...... 1.0 at rest, 1.0 at full right aileron. Bad = Should be 0.0 at rest. Also, no change from at rest to full right aileron.
Axis 1 Elevator = -1.0 at full nose down ..... 0 at rest ..... 1.0 at full nose up. This works correctly.
Axis 2 Throttle = 0 at no throttle, -1.0 for anything other than no throttle. Values at bottom of window shows .5 and 1.0. Bad = Input values do not change proportional to control position.
Axis 3 rudder = -1.0 at full left rudder, 1.0 at rest, 1.0 at full right rudder. Bad = Should be 0.0 at rest. Also, no change from at rest to full right rudder.
Axis 6 & 7 are assigned to the hat button and work correctly.
—This unsigned comment was added by J8d4c3 (Talk | contribs) 09:21, 18 May 2021 (UTC)