Cessna 550 Citation II: Difference between revisions

Jump to navigation Jump to search
m
→‎Recently updated: add state overlay options
m (→‎Recently updated: add state overlay options)
Line 162: Line 162:
* New support for state overlays. Will be available with FG-2017.3 or recent dev-Version. Activate state overlay by adding <code>--state=$state</code> to your command-line.
* New support for state overlays. Will be available with FG-2017.3 or recent dev-Version. Activate state overlay by adding <code>--state=$state</code> to your command-line.
   $state can be:
   $state can be:
   * parking  (cold and dark, all systems off) (same as without <code>--state=$state</code> )
   * parking  ( cold and dark, all systems off) (same as without <code>--state=$state</code> )
   * taxi    (engines and all systems running - ready to taxi)
   * taxi    ( engines and all systems running - ready to taxi )
   * take-off (flaps and AP set - just throttle up and go)
   * take-off ( flaps and AP set - just throttle up and go )
   * cruise  (flying at FL360 on AP)
   * cruise  ( flying at FL360 on AP )
   * approach ( !experimental! use with <code>--glideslope=degrees --offset-distance=nm --in-air</code> )
   * approach ( !experimental! use with:
    --glideslope=degrees       ( usually 3 ) '''or'''
    --altitude=ft-above-msl    ( alt above sea level ) '''or'''
    --offset-distance=nm       ( 10 seems like a good start )
    Never use all 3 options at once! Only 2 of them. Triangle calculation - remember?
    --in-air                   ( well, just do it... )
    if you want, you can add options like this:
    --nav1=rad:freq            ( Going into LOWI 26 enter --nav1=255:111.100 meaning NAV1 is set to 111.100 with a radial of 255°, which is the G/S of LOWI26 )
    )


==== Systems ====
==== Systems ====
177

edits

Navigation menu