X-Git-Url: https://git.mxchange.org/?a=blobdiff_plain;f=docs-mini%2FREADME.JSBSim;h=433495c6d68bdf5f1a676d715d7cd30f28d5fe1c;hb=560775393528545c89dc4c42050ad0e6af9fcdfb;hp=6115d4b361791165dd08fc6d0bd10313277e1bbc;hpb=33758efa2820ada8f6fbd41c9c35bda0bc9bdecd;p=flightgear.git diff --git a/docs-mini/README.JSBSim b/docs-mini/README.JSBSim index 6115d4b36..433495c6d 100644 --- a/docs-mini/README.JSBSim +++ b/docs-mini/README.JSBSim @@ -1,42 +1,53 @@ JSBSim -JSBSim is an ongoing attempt at producing an OO Flight Dynamics Model (FDM) -to replace LaRCsim as the default FDM for FlightGear. It can also be used -standalone. +JSBSim is an ongoing attempt at producing an OO Flight Dynamics Model +(FDM) to replace LaRCsim as the default FDM for FlightGear. It can +also be used standalone. -JSBSim uses config files to represent aircraft and engines. Also, the flight -control system is described in the config file. Normally, for use with -FlightGear, the config files are named this way: -/Aircraft//.cfg . Engines are named -like this: /Engines/.dat . +JSBSim uses config files to represent aircraft, engines, propellers, +etc. Also, the flight control system is described in the config +file. Normally, for use with FlightGear, the config files are named +this way [case is significant]: -Aircraft and engine config files are present in the FGFS-Base package which -must be downloaded from the FlightGear web site at www.flightgear.org or one -of the mirror sites listed there. +/Aircraft//.xml + +Engines are named like this: + +/Engines/.xml + +Aircraft and engine config files are present in the FGFS Base package +which must be downloaded. See the FlightGear web site for more +information. How to run FGFS using JSBSim -All the various FDMs are currently compiled into FGFS. You can specify which -FDM you want at run time. You can also specify which aircraft you want. -Currently, for JSBSim only the X-15 is available, and possibly the C-172. -Here is an example command line used to start up FlightGear using JSBSim as -the FDM: +All the various FDMs are currently compiled into FGFS. You can specify +which FDM you want at run time. You can also specify which aircraft +you want. Currently, for JSBSim only the X-15 and C-172 aircraft are +available. Here is an example command line used to start up FlightGear +using JSBSim as the FDM: fgfs --fdm=jsb --aircraft=X15 --units-feet --altitude=60000 --uBody=2000 --wBody=120 -[Note: uBody is the forward velocity of the aircraft, wBody is the downward -velocity - from the aircraft point of view. This essentially means that the -aircraft is going forward fast and has an angle of attack of about 4 degrees -or so] +or, + +fgfs --fdm=jsb --aircraft=c172 + +[Note: uBody is the forward velocity of the aircraft, wBody is the +downward velocity - from the aircraft point of view. This essentially +means that the aircraft is going forward fast and has an angle of +attack of about 4 degrees or so] - The above command line sets up the initial velocity and altitude to allow -the X15 to glide down. Note that if you fire up the engine, it will burn for -only about two minutes and then run out of fuel - but you will go very, very -fast! +The first command line sets up the initial velocity and altitude to +allow the X15 to glide down. Note that if you fire up the engine, it +will burn for only about two minutes and then run out of fuel - but +you will go very, very fast! The second command line example will +start up the C172 on the end of the runway. -Check out the JSBSim home page at www.hal-pc.org/~jsb/flightsim.html. Please -report any bugs to jsb@hal-pc.org, or apeden@earthlink.net, or post them to -the fgfs-devel mailing list. +Check out the JSBSim home page at http://jsbsim.sf.net. Please report +any bugs to jsb@hal-pc.org, or apeden@earthlink.net, or post on the +jsbsim web site using the SourceForge bug tracking system for the +project. -JSBSim is written by Jon S. Berndt and Tony Peden with contributions by -other FlightGear programmers, as well. +JSBSim is written by Jon S. Berndt and Tony Peden with contributions +by other FlightGear programmers, as well.