22
edits
No edit summary |
m (Changed some minor details in the Windows instructions.) |
||
Line 37: | Line 37: | ||
$ js demo | $ js demo | ||
Under Windows, open a command shell ( | Under Windows, open a command shell (Start>All Programs>Accessories>Command Prompt), go to the FlightGear binary folder and start the program as follows (given FlightGear is installed under '''c:\Flightgear''') | ||
cd \FlightGear\bin | cd \FlightGear\bin\Win32 | ||
js_demo.exe | |||
On our system, the first few lines of output are (stop the program with C if it is quickly scrolling past your window!) as follows: | On our system, the first few lines of output are (stop the program with C if it is quickly scrolling past your window!) as follows: | ||
Line 59: | Line 59: | ||
First note that js demo reports which number is assigned to each joystick recognized by the driver. Also, note that the “name” each joystick reports is also included between quotes. We will need the names for each bindings file when we begin writing the binding xml files for each joystick. | First note that js demo reports which number is assigned to each joystick recognized by the driver. Also, note that the “name” each joystick reports is also included between quotes. We will need the names for each bindings file when we begin writing the binding xml files for each joystick. | ||
===Identifying the numbering of axes and buttons=== | ===Identifying the numbering of axes and buttons=== |
edits