https://wiki.flightgear.org/w/api.php?action=feedcontributions&feedformat=atom&user=F-JYLFlightGear wiki - User contributions [en]2026-05-06T23:23:32ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Template:POTM/2025-11&diff=143131Template:POTM/2025-112025-12-02T16:09:44Z<p>F-JYL: </p>
<hr />
<div>Vote in progress</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2025-11&diff=143130Template:POTM/2025-112025-12-02T16:07:20Z<p>F-JYL: Blanked the page</p>
<hr />
<div></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2025-11&diff=143129Template:POTM/2025-112025-12-02T16:06:28Z<p>F-JYL: </p>
<hr />
<div>{{POTM<br />
| image = Vote in progress<br />
| description = <br />
| article = <br />
}}<noinclude>[[Category:Picture of the month 2025]]</noinclude></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Kawasaki_Ki-61_Hein_on_approach_to_Habsheim_LFGS-by-Lester-Boffo.jpg&diff=143128File:SOTM-2025-11-Kawasaki Ki-61 Hein on approach to Habsheim LFGS-by-Lester-Boffo.jpg2025-12-02T15:24:48Z<p>F-JYL: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description=Kawasaki Ki-61 Hein on approach to Habsheim LFGS<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=Lester-Boffo<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-MI-6PS_Rare_earth_lements-by-michat.jpg&diff=143127File:SOTM-2025-11-MI-6PS Rare earth lements-by-michat.jpg2025-12-02T15:23:50Z<p>F-JYL: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=michat<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Nice_cloud_formations_around_the_Italian_hills.-by-doctor_rockter.jpg&diff=143126File:SOTM-2025-11-Nice cloud formations around the Italian hills.-by-doctor rockter.jpg2025-12-02T15:22:35Z<p>F-JYL: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=doctor rockter<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Nimrod_R1_over_the_UK-by-OrbitalMartian.jpg&diff=143125File:SOTM-2025-11-Nimrod R1 over the UK-by-OrbitalMartian.jpg2025-12-02T15:21:18Z<p>F-JYL: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=OrbitalMartian<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2025-11&diff=143124Category:Screenshot of the month/2025-112025-12-02T15:12:55Z<p>F-JYL: </p>
<hr />
<div>[[Category:Screenshot of the month]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2025-11&diff=143123Category:Screenshot of the month/2025-112025-12-02T15:12:20Z<p>F-JYL: Blanked the page</p>
<hr />
<div></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Over_Marseille_with_the_777_by_F-JYL.jpg&diff=143122File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg2025-12-02T15:11:13Z<p>F-JYL: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=F-JYL<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]<br />
[[Category:Boeing 777 screenshots]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Over_Marseille_with_the_777_by_F-JYL.jpg&diff=143121File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg2025-12-02T15:10:22Z<p>F-JYL: /* Summary */</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=F-JYL<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2025-11&diff=143120Template:POTM/2025-112025-12-02T15:09:12Z<p>F-JYL: Removed redirect to File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg</p>
<hr />
<div>{{POTM<br />
| image = SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg<br />
| description = Over Marseille (LFML) with the 777-300ER.<br />
| article = Boeing 777<br />
}}<noinclude>[[Category:Picture of the month 2025]]</noinclude></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2025-11&diff=143119Template:POTM/2025-112025-12-02T15:04:47Z<p>F-JYL: Redirected page to File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg</p>
<hr />
<div>#REDIRECT [[File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg|thumb|SOTM 2025 11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Over_Marseille_with_the_777_by_F-JYL.jpg&diff=143118File:SOTM-2025-11-Over Marseille with the 777 by F-JYL.jpg2025-12-02T15:03:40Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Nimrod_R1_over_the_UK-by-OrbitalMartian.jpg&diff=143117File:SOTM-2025-11-Nimrod R1 over the UK-by-OrbitalMartian.jpg2025-12-02T15:03:39Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Nice_cloud_formations_around_the_Italian_hills.-by-doctor_rockter.jpg&diff=143116File:SOTM-2025-11-Nice cloud formations around the Italian hills.-by-doctor rockter.jpg2025-12-02T15:03:39Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Kawasaki_Ki-61_Hein_on_approach_to_Habsheim_LFGS-by-Lester-Boffo.jpg&diff=143115File:SOTM-2025-11-Kawasaki Ki-61 Hein on approach to Habsheim LFGS-by-Lester-Boffo.jpg2025-12-02T15:03:39Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-MI-6PS_Rare_earth_lements-by-michat.jpg&diff=143114File:SOTM-2025-11-MI-6PS Rare earth lements-by-michat.jpg2025-12-02T15:03:39Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Hubble_Space_Transfer-by-eatdirt.jpg&diff=143113File:SOTM-2025-11-Hubble Space Transfer-by-eatdirt.jpg2025-12-02T15:03:38Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Clerget_9Bf-Near_the_Old_Rhinebeck_Aerodrome_(NY94)-by-VonS.jpg&diff=143112File:SOTM-2025-11-Clerget 9Bf-Near the Old Rhinebeck Aerodrome (NY94)-by-VonS.jpg2025-12-02T15:03:38Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:SOTM-2025-11-Concorde-BAWparked-At-EGLL-by-I-FABI.jpg&diff=143111File:SOTM-2025-11-Concorde-BAWparked-At-EGLL-by-I-FABI.jpg2025-12-02T15:03:38Z<p>F-JYL: Uploaded a work by X from forum SOTM 2025 11 with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2025 11}}<br />
|date=2025-12-02<br />
|source=forum SOTM 2025 11<br />
|author=X<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month]]<br />
[[Category:Screenshot of the month/2025-11]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2025-11&diff=143110Category:Screenshot of the month/2025-112025-12-02T15:01:05Z<p>F-JYL: Created page with "STOM 2025-11"</p>
<hr />
<div>STOM 2025-11</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month&diff=143109Category:Screenshot of the month2025-12-02T09:28:12Z<p>F-JYL: SOTM November 2025</p>
<hr />
<div>{{en|Category with winners of the ''Screenshot of the Month'' contests from April 2011 to April 2012, and since June 2015.}}<br />
<br />
{|class="wikitable" style="text-align: center"<br />
! Date<br />
! Screenshot submission<br />
! Vote<br />
! Subcategory<br />
|-<br />
| 2025-11<br />
| {{forum link|title=Submit your screenshot for the SOTM of November|t=43870}}<br />
| {{forum link|title=Voting for the SOTM of November|t=43924}}<br />
| [[:Category:Screenshot of the month/2025-11]]<br />
|-<br />
| 2019-01<br />
| {{forum link|title=Submit your screenshot for the SOTM of January!|t=35229}}<br />
| {{forum link|title=Voting for the SOTM January|t=35303}}<br />
| [[:Category:Screenshot of the month/2019-01]]<br />
|-<br />
| 2019-02<br />
| {{forum link|title=Submit your Screenshot for February's SOTM!|t=35319}}<br />
| {{forum link|title=Voting for the SOTM|t=35413}}<br />
| [[:Category:Screenshot of the month/2019-02]]<br />
|-<br />
| 2019-03<br />
| {{forum link|title=Submit your screenshot for the SOTM of March|t=35436}}<br />
| {{forum link|title=Voting for the SOTM|t=35554}}<br />
| [[:Category:Screenshot of the month/2019-03]]<br />
|-<br />
| 2019-04<br />
| {{forum link|title=Submit your screenshot for the SOTM of April|t=35574}}<br />
| {{forum link|title=Voting for the SOTM|t=35720}}<br />
| [[:Category:Screenshot of the month/2019-04]]<br />
|-<br />
| 2019-05<br />
| {{forum link|title=Submit your screenshot for the SOTM of May|t=35746}}<br />
| {{forum link|title=Voting for the SOTM of May|t=35880}}<br />
| [[:Category:Screenshot of the month/2019-05]]<br />
|-<br />
| 2019-06<br />
| {{forum link|title=Submit your screenshot for the SOTM of June!|t=35903}}<br />
| {{forum link|title=Vote for the SOTM of June|t=36046}}<br />
| [[:Category:Screenshot of the month/2019-06]]<br />
|-<br />
| 2019-07<br />
| {{forum link|title=Submit your screenshot for the SOTM of July|t=36088}}<br />
| {{forum link|title=Vote for the SOTM July 2019|t=36149}}<br />
| [[:Category:Screenshot of the month/2019-07]]<br />
|-<br />
| 2019-08<br />
| {{forum link|title=Submit your screenshot for the SOTM of August!|t=36188}}<br />
| {{forum link|title=Vote for the SOTM August 2019|t=36265}}<br />
| [[:Category:Screenshot of the month/2019-08]]<br />
|-<br />
| 2019-09<br />
| {{forum link|title=Submit your screenshot for SOTM of September|t=36316}}<br />
| {{forum link|title=Voting for the SOTM September|t=36361}}<br />
| [[:Category:Screenshot of the month/2019-09]]<br />
|-<br />
| 2019-10<br />
| - no contest -<br />
| <br />
|<br />
|-<br />
| 2019-11<br />
| {{forum link|title=Submit your screenshot for the SOTM of November 2019|t=36496}}<br />
| {{forum link|title=Voting for the SOTM of November 2019|t=36616}}<br />
| [[:Category:Screenshot of the month/2019-11]]<br />
|-<br />
| 2019-12<br />
| {{forum link|title=Submit your screenshot for the SOTM of December 2019|t=36643}}<br />
| {{forum link|title=Voting for the SOTM of December 2019|t=36702}}<br />
| [[:Category:Screenshot of the month/2019-12]]<br />
|-<br />
| 2019 SOTY<br />
| - Used previous month's winners -<br />
| {{forum link|title=Voting for the SOTY of 2019|t=36740}}<br />
| [[:Category:Screenshot of the year/2019]]<br />
|}<br />
<br />
[[Category:FlightGear screenshots]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Howto:Add_procedures_to_the_route_manager&diff=143054Howto:Add procedures to the route manager2025-11-20T14:20:23Z<p>F-JYL: navigraph procedures for linux users</p>
<hr />
<div>{{Stub}}<br />
{{Autoflight Navigation}}<br />
<br />
A free way to get more SID and STAR procedures for the FlightGear Route Planner.<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=313123#p313123 <br />
| title = <nowiki> routeplanner stir sid </nowiki> <br />
| author = <nowiki> Sarith </nowiki> <br />
| date = Jun 24th, 2017 <br />
| added = Jun 24th, 2017 <br />
| script_version = 0.40 <br />
}}</ref><br />
<br />
Make some procedures yourself. Charts are easy to find and a quick search will find you the syntax. This is what FlightGear is all about; doing it yourself and sharing it to others. A quick search would also find existing packages.<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=313128#p313128 <br />
| title = <nowiki> Re: routeplanner stir sid </nowiki> <br />
| author = <nowiki> Parnikkapore </nowiki> <br />
| date = Jun 24th, 2017 <br />
| added = Jun 24th, 2017 <br />
| script_version = 0.40 <br />
}}</ref><br />
<br />
== Installing procedure files ==<br />
=== Manually ===<br />
SID and STAR procedures are found in the <code>procedures.xml</code> file for an airport. There is at most one procedures file per airport and it is located in the root of the airport directory:<br />
<br />
<code>[[$FG_SCENERY]]/Airports/I/C/A/ICAO.procedures.xml</code><br />
<br />
With the ICAO code of your airport replacing <code>ICAO</code>.<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=313362#p313362 <br />
| title = <nowiki> Re: routeplanner stir sid </nowiki> <br />
| author = <nowiki> Parnikkapore </nowiki> <br />
| date = Jun 28th, 2017 <br />
| added = Jun 28th, 2017 <br />
| script_version = 0.40 <br />
}}</ref><br />
<br />
For example, to import SID or STAR procedures for Phuket International Airport (VTSP), you name the file <code>VTSP.procedures.xml</code> and put it in the directory<br />
<br />
<code>[[$FG_SCENERY]]/Airports/V/T/S/</code><br />
<br />
In there you will likely find for example <code>VTSP.twr.xml</code>, but not an existing <code>VTSP.procedures.xml</code> file.<br />
<br />
Replace <code>VTSP</code> in the directory and <code>procedures.xml</code> file name with your airport code.<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=313409#p313409 <br />
| title = <nowiki> Re: routeplanner stir sid </nowiki> <br />
| author = <nowiki> Parnikkapore </nowiki> <br />
| date = Jun 29th, 2017 <br />
| added = Jun 29th, 2017 <br />
| script_version = 0.40 <br />
}}</ref><br />
<br />
=== Bash script for organizing files ===<br />
ZirconiumX wrote a bash script for putting the XML files into the the right directories in the scenery.<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=280561#p280561 <br />
| title = <nowiki> Re: Non-Navigraph SID/STAR xml files </nowiki> <br />
| author = <nowiki> ZirconiumX </nowiki> <br />
| date = Mar 26th, 2016 <br />
| added = Mar 26th, 2016 <br />
| script_version = 0.40 <br />
}}</ref><!-- Where do you even get the original files? Navigraph? --><br />
<br />
<syntaxhighlight lang="bash"><br />
for file in $(ls *.xml)<br />
do<br />
# First, rename all the files to the correct convention<br />
mv "$file" "${file%.xml}.procedures.xml"<br />
<br />
# Then move it to the correct place<br />
icao=${file%.xml}<br />
icao1=$(echo $icao | cut -c 1)<br />
icao2=$(echo $icao | cut -c 2)<br />
icao3=$(echo $icao | cut -c 3)<br />
mkdir -p $icao1/$icao2/$icao3<br />
mv "${icao}.procedures.xml" "$icao1/$icao2/$icao3/${icao}.procedures.xml"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Navigraph procedures for linux users ===<br />
<br />
* Create a directory to install procedures, let's say navigraph<br />
* Download the bash script and make it executable<br />
* Download the IFMS data from navigraph down load page [https://navigraph.com/downloads navigraph downloads] (paid subscription)<br />
* Expand the data<br />
* Create an Airports directory<br />
* Start the navigraph.sh script with the directories as parameters : ie ./navigraph.sh navdata_native_2511 Airports<br />
<br />
<br />
Bash script inspired from the one from ZirconiumX<syntaxhighlight lang="bash"><br />
#!/usr/bin/bash<br />
#<br />
# Organize navigraph procedures<br />
# <br />
#<br />
if (( $# < 2 ))<br />
then<br />
printf "%b" "Error. Not enough arguments.\n" >&2<br />
printf "%b" "usage: navigraph.sh fromdirectory todirectory\n" >&2<br />
printf "use directories without trailing slash" >&2<br />
exit 1<br />
fi<br />
<br />
fromDir=$1<br />
toDir=$2<br />
<br />
for file in $(ls $fromDir/*.xml)<br />
do<br />
filename=${file##*/}<br />
name=${filename%.*} # delete everything after last dot <br />
upcase=${name^^} # uppercase everything<br />
<br />
target="$upcase.procedures.xml"<br />
# Then move it to the correct place<br />
icao=${name^^}<br />
icao1=$(echo $icao | cut -c 1)<br />
icao2=$(echo $icao | cut -c 2)<br />
icao3=$(echo $icao | cut -c 3)<br />
<br />
dirToCreate=$toDir/$icao1/$icao2/$icao3<br />
echo "creating dir $dirToCreate"<br />
mkdir -p $dirToCreate<br />
echo "copy $fromDir/$filename to $toDir/$icao1/$icao2/$icao3/$target"<br />
cp $fromDir/$filename $toDir/$icao1/$icao2/$icao3/$target<br />
done<br />
</syntaxhighlight>Now you can start flightgear using this directory as a scenery source <blockquote>...<br />
<br />
-- fg-scenery=/home/user/fg/Navigraph<br />
<br />
...</blockquote><br />
<br />
== File structure ==<br />
In the explanation below, the name like "ProceduresDB" is the tag - so it's actually <code>&lt;ProceduresDB&gt;</code> in the XML file.<br />
The subsequent parameters, like "build" are attributes - so it's actually <code>&lt;ProceduresDB build=""&gt;</code> in the XML file.<br />
<br />
<pre><br />
ProceduresDB [build] (one of these per file)<br />
|<br />
Airport [ICAOcode] (one of these per file)<br />
|<br />
Sid [Name, Runways (comma separated - example: "08L,08R")] (many of these per Airport)<br />
|<br />
Sid_Waypoint [ID (unique sequential integer)] (many of these per Sid)<br />
|<br />
Name<br />
Type<br />
Latitude<br />
Longitude<br />
Speed<br />
Altitude<br />
AltitudeCons<br />
AltitudeRestriction (one of "above" or "below" or "at")<br />
Hdg_Crs (optional. example value = "1")<br />
Hdg_Crs_Value (optional. heading degrees)<br />
Sp_Turn (optional. example value = "Auto")<br />
...<br />
Sid_Transition [Name] (just one of these per Sid)<br />
|<br />
SidTr_Waypoint [ID] (many of these per Sid_Transition)<br />
<br />
Star [Name] (many of these per Airport)<br />
|<br />
Star_Waypoint [ID] (many of these per Star)<br />
...<br />
Star_Transition [Name] (just one of these per Star)<br />
|<br />
StarTr_Waypoint [ID] (many of these per Star_Transition)<br />
<br />
Approach [Name] (e.g., ILS08L - uses IL, if appropriate, and the runway name by convention)<br />
|<br />
App_Waypoint [ID]<br />
App_Transition [Name] (just one of these per Approach)<br />
|<br />
AppTr_Waypoint [ID] (many of these per App_Transition)<br />
</pre><br />
<br />
== Sample procedures.xml files ==<br />
Here are some links to example XML files which follows the format specified above:<br />
* {{github source<br />
| proj = jojo2357<br />
| repo = flightgear-star-sid-manager<br />
| path = 2020.4/Airports/K/A/T/KATL.procedures.xml<br />
}}<ref>{{cite web<br />
| url = https://forum.flightgear.org/viewtopic.php?p=313583#p313583 <br />
| title = <nowiki> Re: routeplanner stir sid </nowiki> <br />
| author = <nowiki> eric </nowiki> <br />
| date = Jul 2nd, 2017 <br />
| added = Jul 2nd, 2017 <br />
| script_version = 0.40 <br />
}}</ref><br />
* {{github source<br />
| proj = terrasync<br />
| repo = main<br />
| path = Airports/L/F/R/LFRB.procedures.xml<br />
}}<br />
<br />
== Sources for procedure files ==<br />
=== Installing free community procedures ===<br />
The FAA provides the [https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/cifp/ CIFP] which provides procedure data for airports under the purview of the FAA, namely the US.<br />
<br />
There is a free project on {{github source<br />
| user = jojo2357<br />
| repo = flightgear-star-sid-manager<br />
| text = GitHub<br />
}} that aims to take FAA data and format it into the Level-D required by FlightGear. For instructions on how to install, see {{github source<br />
| user = jojo2357<br />
| repo = flightgear-star-sid-manager<br />
| path = README.MD#installation<br />
| text = this section<br />
}} of the README.<br />
<br />
This project uses GitHub Actions in order to automatically update the procedures at the start of a new AIRAC cycle.<br />
<br />
=== Commercial sources ===<br />
A process to import SID/STARs from Navigraph Level D (obtaining this data requires paid subscription to Navigraph) was described on the forum.<br />
<br />
Quoting here for reference:{{cite web<br />
| url=https://forum.flightgear.org/viewtopic.php?f=11&t=37975&start=15#p416078<br />
| title = <nowiki> Re: How to get SIDs and STARs in Airbus A320 mcdu </nowiki> <br />
| author = <nowiki> mpotra </nowiki> <br />
| quote = :<br />
# Download Level-D navdata from Navigraph (On the Downloads -> Manual Download page)<br />
# This is ZIP file with a Windows Installer executable inside. If you're on Windows already, run the installer, select a version (Prepar3D/PD3) and then skip to step 4.<br />
# The executable is a Inno Setup executable. In Linux you can extract the contents with `innoextractor -e leveld_2311.exe` for example, which will output a "code$AppName" directory.<br />
# In the extracted directory you'll find a "navdata" folder containing XML files with procedures for all airports for the AIRAC cycle with filenames as "<ICAO>.xml".<br />
# You can either rename in bulk or single file from "<ICAO>.xml" to "<ICAO>.procedures.xml" for desired airports.<br />
# Create a new directory somewhere (anywhere you want) say "AIRAC/2311", and inside it create the "Airports" directory. (camel-case formatted - "airports" with small letter A didn't work for me)<br />
# Inside this "Airports" directory, create new subdirectories for each airport you want to bring in, using the [I]/[C]/[A] format. For example, if you want to add Vienna airport LOWW, create the subdirectories "Airports/L/O/W" - do not create the fourth subdirectory [W] (it won't work)<br />
# Copy the renamed file from step 5 into this last subdirectory. For example, copy "LOWW.procedures.xml" into "AIRAC/2311/Airports/L/O/W" directory, resulting in "AIRAC/2311/Airports/L/O/W/LOWW.procedures.xml". Example 2: for Budapest airport copy "LHBP.procedures.xml" into "AIRAC/2311/Airports/L/H/B", resulting in "AIRAC/2311/Airports/L/H/B/LHBP.procedures.xml"<br />
# In FlightGear, add the "AIRAC/2311" directory to your sceneries paths.<br />
# Reload FlightGear and enjoy SID/STARs in your MCDU<br />
}}<br />
<br />
== References ==<br />
{{Appendix}}<br />
<br />
== Related content ==<br />
=== Wiki articles ===<br />
* [[Route manager]]<br />
* [[Flightplan XML formats]]<br />
<br />
=== Mailing list threads ===<br />
* [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/222DD5B1-B7F1-421B-84AE-A60353203085@flightgear.org/ <nowiki>[Flightgear-devel<nowiki>]</nowiki> Procedures SID/STAR/Approach]<br />
<br />
=== Source code ===<br />
* {{flightgear source|path=src/Navaids/LevelDXML.hxx}}<br />
* {{flightgear source|path=src/Navaids/LevelDXML.cxx}}</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Howto:Start_core_development&diff=142801Howto:Start core development2025-10-23T06:28:30Z<p>F-JYL: /* The source code */ link to building the project</p>
<hr />
<div>{{out of date}}<br />
<br />
''01/2012: I have taken my {{forum link|p=146436|text=forum response}} and copied/pasted it here. Everybody is invited to contribute. While we do have a [[Volunteer]] page, we don't currently have a page dedicated to people wanting to contribute to the C++ source code, so this is an attempt to get something like this started.''<br />
<br />
= How the Project works (Suggested reading!) =<br />
<br />
* [[http://home.flightgear.org/flightgear-policy-document/ | Flightgear Policy Document briefly covering what will be expected of a contributor]]<br />
* [[http://home.flightgear.org/info/ | Other Information to be Aware Of]]<br />
* {{forum link|p=149971|title=Flightgear Development}}<br />
* [[How the FlightGear project works]]<br />
<br />
Please see this short essay here: {{forum url|p=149971}}<br />
<br />
Also see [[Implementing new features for FlightGear]]<br />
<br />
= Welcome to FlightGear =<br />
<br />
Hi, and welcome to FlightGear!<br />
<br />
You have probably come here to learn more about implementing new features for FlightGear.<br />
<br />
Often, implementing new ideas and features doesn't necessarily require C++ knowledge, FlightGear has become so flexible and powerful that it is increasingly configurable even without touching the C++ source code. This is an important advantage, because building FG from source and finding your away around two fairly complex code bases (i.e. [[SimGear]] and [[FlightGear]]) can be a daunting task, even for experienced C++ developers.<br />
<br />
This isn't to say that C++ / programming knowledge wouldn't be useful though. And if that's where your interests are, you are certainly invited to contribute to the C++ code, too. <br />
<br />
== Not yet familiar with C++ ? ==<br />
<br />
If you don't yet know what a compiler is, what C++ is or how programming works, you may want to check out [[Howto: Understand the FlightGear development process]].<br />
<br />
While learning how to program is definitely possible, learning C++ in particular and becoming familiar with a complex code base like FG/SG does take a certain amount of time. In particular, setting up a working build environment to build FG from source, can be a daunting task for people without any corresponding background knowledge.<br />
<br />
If you know for sure, that you want to learn C++, we have a collection of helpful resources here: [[Resources#C.2B.2B_Courses|C++ resources]]. This includes a bunch of animated screen casts (i.e. video tutorials) on youtube: http://www.youtube.com/view_play_list?p=1D6727247CA35794<br />
<br />
== Developing without programming is possible and appreciated ==<br />
<br />
For non coding-related ideas on how to to start contributing, there's a dedicated article at [[Volunteer]]. Creating new aircraft, cockpits, scenery, instruments, GUI dialogs, etc. doesn't require any programming knowledge at all. If that's what you are interested in, please check out the links at the [[Portal:Developer|Developer Portal]].<br />
<br />
== Coding but not in C++ (scripting) ==<br />
<br />
If you are definitely interested in coding, but not in building FlightGear from source (C++), you may want to look into [[Nasal]] programming instead, which is FlightGear's built in scripting language, and doesn't require anything besides FlightGear itself.<br />
<br />
Many new ideas or features won't require any modifications to the C++ source code at all.<br />
You could probably get started and implement many ideas without even touching an IDE or a compiler for quite a while.<br />
<br />
That might actually be the easiest route for you to proceed in the beginning. Programming knowledge would obviously still be useful, because Nasal scripting is "real programming", many programming concepts (loops, functions, classes, events etc) you'll encounter in Nasal will seem familiar to people with previous programming experience.<br />
<br />
The "Nasal" programming language built into FG is syntactically very close to C and C++, it looks a lot like JavaScript - so you could run your own code inside FG without having to build FG from source, no need for compilers or an IDE. FlightGear IS the run time environment for Nasal code.<br />
<br />
If you are looking for immediate results, Nasal is probably the most promising route - simply because you don't need to look into all the tedious, non-coding related issues. Here's an overview giving you a rough idea about recent Nasal related efforts:<br />
<br />
{{Nasal Efforts}}<br />
<br />
For example, the tutorial system built into FG is entirely implemented in scripting space, and fully XML-configurable: [[Tutorials]]<br />
<br />
This means that you can create/modify and improve tutorials just by editing plain text files with any conventional text editor.<br />
<br />
There are many more things possible using Nasal, just see the wiki.<br />
<br />
And if you find something not being possible in scripting space, you could either fire up your IDE and extend the interpreter or ask another contributor to provide a corresponding patch.<br />
<br />
== Shader programming ==<br />
If you are not interested in C++ programming, but also not in Nasal scripting, there's another option: [[Shader|GLSL Shader programming]]. FlightGear has an extremely powerful "effects" framework and support for running GLSL shaders. While programming shaders for FlightGear doesn't by default require being a C++ developer, being able to build FG from source and knowing C++ can be really helpful though, especially in order to expose new properties to shaders (i.e. improving the property tree <-> shader interface).<br />
<br />
= Hacking the C++ code =<br />
<br />
From now on, this article will provide the required pointers to get you started hacking the FlightGear source code. Ideally, you already know C++, or a language very close to it, like C or Java. <br />
Also, you should preferably already have experience building programs from source code, otherwise this may seem pretty frustrating if you do this for the first time, simply because FlightGear has meanwhile become a fairly complex code base with many dependencies that need to be satisfied and built in a certain order.<br />
<br />
= Initial advice =<br />
<br />
Our advice would be: Start small, start simple, communicate a lot and most importantly '''release early & often''' (i.e. use topic branches and commit frequently, and encourage others to provide feedback)<br />
<br />
* if you know you want to contribute to the source code, make sure that you are actually able to build FG from source, you can get help using the forum, the mailing list, the issue tracker or live support using IRC chat - we have articles on building FG on various platforms, see [[Building FlightGear]]<br />
* read the documentation (wiki, $FG_ROOT/Docs, $FG_SRC/mini-docs)<br />
* it also helps running DoxyGen or Source Navigator to navigate the various source trees<br />
* start making tiny modifications to existing stuff (aircraft, scenery, source code etc)<br />
* try to get to grips with how git works (we have some resources to get you started, using GUI frontends like qgit or a good IDE can be helpful)<br />
* register an account at gitorious<br />
* clone the FG project (SimGear, FlightGear, fgdata)<br />
* browse the issue tracker for bug reports/feature requests, help triage problems, maybe provide patches too (i.e. to mute compiler warnings, to fix memory leaks, fix/add comments, clean up/refactor source code)?<br />
* search the archives (forum and mailing list) for discussions related to your area of interest, these contain often valuable pointers that may save you hours of work<br />
* subscribe to the developers mailing list<br />
* ask for advice/projects there<br />
* check out the wiki for ideas to get started (Watch out, there are plenty of "ideas" listed here, but not all of them are up to date or even "good" ideas, so talk to fellow contributors first before spending any significant amounts of time implementing something)<br />
* coordinate your effort with others, i.e. communicate your intentions early and ask for advice<br />
* release early and often<br />
* don't get frustrated :-)<br />
* enjoy!<br />
<br />
= Project architecture =<br />
FlightGear itself consists of a number of different projects and dependencies (libraries), please refer to gitorious for details. Most of FlightGear's supporting code is increasingly getting moved to the "SimGear" project.<br />
<br />
Basically, FlightGear depends on SimGear, while SimGear depends on some 3rd party libraries such as OpenSceneGraph (for rendering), plib (utility functions, joystick support, GUI etc), OpenAL (sound) and others like boost.<br />
<br />
Once you have satisfied all dependencies and built them in the right order, you can start FlightGear.<br />
Note however that FlightGear also has a run time dependency: its so called "base package", i.e. the data package that contains all resources such as scenery, GUI files, aircraft, sounds and so on. We commonly refer to this as "$FG_ROOT".<br />
<br />
The FG source tree is commonly referred to as $FG_SRC, while the SimGear source tree is often referred to as $SG_SRC.<br />
<br />
A while ago, Jim Wilson posted the following advice on the devel list:<br />
<br />
If you are familiar with C++ then you should have no trouble figuring things out. Take a look at the SGSubsystem class. This is the base for all the subsystems in flightgear. The most frequently used functions in this class are the init and the update functions.<br />
<br />
Then take time to look at a few subsystems. Generally for most subsystems you can figure that the update function gets called once per frame.<br />
<br />
The frame loop is in $FG_SRC/Main.cxx (function mainloop). Here you will see the various subsystem's update calls and the sequence they are done in. What I mean by frame loop is this loop is repeated for each frame (note the rendering down the bottom of it). There is also an event subsystem that is used to schedule calls to update() of certain subsystems on a timer interval.<br />
<br />
With this general overview (don't try to understand every line of code yet), you should be able to locate bits of code that you are interested in by<br />
perusing the directories of modules. Like I said most subsystems are based on SGSubsystem, so you should be able to locate implementations of init() and<br />
update(). Also note that some subsystems are updated by others, so if you don't see the update() called from in the mainloop then do a text search<br />
through the modules to find the code that actually does call the update() (look for references to the class you are interested in).<br />
<br />
Finally you will want to familiarize yourself with the data that is exposed in the property tree. This is an excellent learning tool. When running<br />
FlightGear, bring up the Property browser from the Debug menu. This property tree is essential for much of the way in which configuration and data output<br />
are handled in FlightGear. For example the flight instruments are all configured using XML defined references to values in the property tree in<br />
order to position needles, etc. Changing property values can be used to alter the configured behavior of FlightGear at startup using parameters and/or XML declarations, or on the fly using C++ property class functions in the code or from several other interfaces including the property browser (for example: try adjusting the cloud layer settings in the property browser under environment/clouds, you will see the effect right away).<br />
<br />
Speaking of instruments, you might want to take a look at how some of the instrumentation configuration (Aircraft/Instrumentation/*.xml files in the<br />
base package) in order to get an idea of how different parts of FlightGear can be configured to communicate with other parts in a certain way through the<br />
property tree. You can also look at the preferences.xml file to see an example of how startup configuration for various subsystems is handled through<br />
the property tree.<br />
<br />
By browsing the properties and tracing interesting data items to the code they are output from or read by, you can learn a lot about how FlightGear works. When you see something interesting do a text search through the source code for that property name and you will find out how it is utilized.<br />
<br />
Welcome aboard and do feel free to post any questions to the list as they come up.<br />
<br />
= The source code =<br />
<br />
FlightGear is multi-platform software, that runs on all major versions of MS Windows, macOS and Linux. That means, the FlightGear source code also needs to be written and maintained with cross-platform considerations in mind. <br />
<br />
The core FlightGear source code itself is largely written in C++, some C and a bunch of helper scripts. FlightGear is based on OpenGL (NOT DirectX !), OSG (OpenSceneGraph) and OpenAL (for sound). An increasing number of features are implemented in scripting space, using a high level scripting language called [[Nasal]], Nasal scripts are maintained in the fgdata repository and available at runtime under ($FG_ROOT).<br />
<br />
The SimGear and FlightGear source trees both make use of the [[Building using CMake|CMake]] build system as of 2012.<br />
<br />
The FlightGear project uses the decentralized source code management system "git" see [[Git]] for more info.<br />
<br />
The project sources are hosted at sourceforge: https://sourceforge.net/p/flightgear/<br />
<br />
Development is primarily on the 'next' branches of the three main git repositories:<br />
<br />
* {{repo link<br />
| site = sf<br />
| proj = flightgear<br />
| repo = flightgear<br />
| view = log<br />
}}<br />
<br />
* {{repo link<br />
| site = sf<br />
| proj = flightgear<br />
| repo = simgear<br />
| view = log<br />
}}<br />
* {{repo link<br />
| site = sf<br />
| proj = flightgear<br />
| repo = fgdata<br />
| view = log<br />
}}<br />
<br />
If you know for sure that you'd like to fiddle with the core source code, you'll inevitably need to be able build FG from source, see [[Building_FlightGear]].<br />
<br />
You can find tutorials for different platforms/OS at the end of the article.<br />
<br />
See also : [https://gitlab.com/flightgear/documentation/-/blob/main/src/contributors-guide/guidelines/building.rst?ref_type=heads development using the superbuild]<br />
<br />
= Continuous Integration (CI) =<br />
<br />
For CI purposes, there's a dedicated build server running which rebuilds the FlightGear sources for a handful of important platforms. The server provides a simple and quick overview, it can be found here: {{build link}}<br />
<br />
Please see [[FlightGear Build Server]] for more information.<br />
<br />
= Patches =<br />
<br />
Regarding patches, please see: [[Submitting Patches]].<br />
<br />
Note that this article is meanwhile somewhat deprecated and these days using gitorious (and filing merge requests there) is pretty much encouraged. If your patch is related to a previously reported bug/defect, you can obviously also use the issue tracker (see below).<br />
<br />
In general, the FlightGear gitorious project is the entry point for new developers.<br />
<br />
Some more recommendations can be found at [[Recommended Project Policies]].<br />
<br />
In general, it is always a good idea to clone the FG repositories (i.e. SimGear, FlightGear and FGData) and start working on your own branch there. This will enable fellow contributors to easily keep track of your work, so that they can test your changes and provide feedback as required. <br />
<br />
To send patches upstream, gitorious merge requests are recommended. The details of which are covered at [[Merge request]].<br />
<br />
A list of active FlightGear core developers is to be found at [[:Category:FlightGear Core developers|FlightGear Core developers]].<br />
<br />
= Ongoing efforts =<br />
<br />
Anybody working on FG's source code, should be aware of the [[FGViewer]] trend (decoupling the viewer from the simulation using a [[FlightGear_Headless|headless mode]] 1) to improve frame rate and latencies, but 2) also to support distributed multi-screen setups) and also the long-term goal to use [http://trac.openscenegraph.org/documentation/OpenSceneGraphReferenceDocs/a00108.html OSG's CompositeViewer] for all of the FG views - so modifications to the existing viewer in $FG_SRC/Viewer should probbaly keep these things in mind to align well with other ongoing developments: [[Howto:Use a Camera View in an Instrument#osgViewer::CompositeViewer]]<br />
<br />
An old PDF describing some of the challenges that FlightGear developers are trying to solve through HLA/[[FlightGear CIGI Support (Common Image Generator Interface)|CIGI]] adoption can be found at: [[File:New FG architecture.pdf]]<br />
<br />
The FlightGear state of all HLA things is documented at: [[FlightGear HLA support (High Level Architecture)]]<br />
<br />
Introductory HLA resources are collected at: [[Developing with HLA#Resources]]<br />
<br />
In developer's terms, that mostly boils down to:<br />
* expect more and more scenery functionality to be procedurally added (e.g. [[Terragear_roadmap#Runtime_Airport_Generation|runways, taxiways]], whole airports)<br />
* expect more and more viewer functionality to be decoupled from the simulator (fgviewer being the prototype here)<br />
* expect more and more viewer/GUI features to be made optional through a [[FlightGear Headless]] mode during startup<br />
* expect the 2D rendering backend (GUI, instruments, HUDs etc) to be increasingly unified through the [[Canvas]] system<br />
* expect [[FGPanel|FGPanel standalone panel rendering]] functionality to be merged back into the main fgfs code base, provided through [[FGViewer]]<br />
* expect more work towards better system-wide reinit/reset support: [[Reset & re-init]]<br />
* expect more and more launcher features to be integrated and provided as part of FlightGear {{forum link|p=191451}}<br />
* expect FDMs to become re-initializable at runtime, expect support for multiple FDMs per session<br />
* expect more subsystem to become re-initializable at runtime, so that they can be dynamically enabled/disabled to facilitate the fgviewer and headless efforts: [[FlightGear Run Levels]]<br />
* expect more and and more mainloop subsystems to eventually become standalone threads/processes (that is, HLA federates) (FDM, AI traffic, scripting etc) to guarantee better viewer performance<br />
* expect the existing multiplayer system to be completely phased out and replaced by HLA<br />
* expect [[Property Tree/Native Protocol Slaving|multi-instance slaving]] to be formalized and reimplemented through [[FGViewer]] and [[HLA]]<br />
* expect Nasal scripting integration to be increasingly decoupled from the fgfs main loop<br />
* expect OSG CompositeViewer to be eventually adopted (almost certainly not during the next 12 months though)<br />
<br />
Basically, help facilitate these change by at least not making these things more difficult through your own code<br />
<br />
For doxygen docs, see: http://docs.freeflightsim.org/<br />
<br />
In less broader (and more outdated) terms, a list of the latest development efforts can be found at [[:Category:Core development projects]]<br />
If you have anything to add, please feel free to create a new wiki article.<br />
Also, contributing such news to the FlightGear [[Next newsletter|newsletter]] is another good idea.<br />
<br />
If you are looking for ideas to get involved one way or another, some of the more long-term issues and most annoying glitches are discussed at [[Request for comments]]. <br />
<br />
However, please take everything you'll find there with a grain of salt, because many of these articles haven't been updated over the years, so what may have seemed like a great idea 2-3 years ago, may already be depreciated meanwhile. On the other hand, those articles may still help you get a better understanding of architectural issues. In case of doubt, please get in touch with fellow developers.<br />
<br />
Also, there's another outdated category titled "Code Cleanup": [[:Category:Code Cleanup]]<br />
<br />
Another option would be taking a look at the "Google Summer of Code" category which also lists project ideas collected over the years: [[GSoC: Candidate Projects]]. We also have a separate sub forum for GSoC here: {{forum url|f=38}}<br />
<br />
In other words: '''pick your poison :)'''<br />
<br />
= Issue tracking =<br />
<br />
Ideas (feature requests actually) and bug reports are ideally reported using the issue tracker here: https://sourceforge.net/p/flightgear/codetickets/<br />
<br />
Please make sure to first search the issue tracker before possibly reporting a dupe, thanks!<br />
<br />
Bug reports should ideally be accompanied with a test case to reproduce an issue, but also a backtrace, see: [[Howto:Debugging FlightGear Crashes#Debugging Segfaults & Obtaining Backtraces]].<br />
<br />
This is also an excellent place to get started helping and contributing to FG, i.e. by triaging bug reports, discussing feature requests, posting patches or finding new ideas to work on. This is also a very good place to get in touch with other core developers.<br />
<br />
Also, if you have some new ideas in mind, and would like to extend FlightGear in some way, it's a good idea to use the issue tracker to make feature requests. Fellow FlightGear developers will be able to provide feedback regarding your feature request and tell you directly if and how exactly your idea can be best implemented.<br />
<br />
For example, to view a list of feature requests that were accepted by other core developers, just go to: https://code.google.com/p/flightgear-bugs/issues/list?can=2&q=FeatureRequest%20status%3Aaccepted<br />
<br />
= Talking to fellow FlightGear developers =<br />
Most core development related discussions are handled using the developers mailing list: http://www.flightgear.org/mail.html<br />
<br />
There's a fully searchable archive available here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/<br />
<br />
In addition, the FlightGear forums are increasingly used for interesting development related discussions, please note though that these are usually not specific to FG core development, but instead general development (aircraft, scenery, shaders, scripting): {{forum url}}<br />
<br />
If there's something particular that you are interested in, it's always a good idea to search these resources (wiki, forum, mailing list) to find related discussions.<br />
<br />
= Flight dynamics =<br />
Improving the flight dynamics often doesn't require any C++ changes, FlightGear provides a powerful FDM interface and different FDM engines (namely JSBSim and YaSim), both of which are entirely configurable by using XML files.<br />
<br />
For JSBSim, please see: http://jsbsim.sourceforge.net/<br />
<br />
= Important docs =<br />
There's a wealth of documentation to get you started available in {{fg root file|Docs}}<br />
<br />
API docs auto generated from source are at http://api-docs.freeflightsim.org/<br />
<br />
Even more documentation can be found in this wiki. The wiki is divided into different "portals", you'll probably be interested in [[Portal:Developer|the developers portal]] here.<br />
<br />
You are obviously invited to start your own wiki articles, in order to document your projects or help improving existing documentation. Also, some core developers actually use the wiki to post their own development roadmaps. For example, see: [[Plan-zakalawe]] or [[Project Rembrandt]].<br />
<br />
== FlightGear ==<br />
Don't worry if your C++ experience should be dated: In many parts, the FlightGear code base is still somewhat archaic and not very modern, so you won't find too many occurrences of really advanced C++ concepts, in many places you'll just find simple "C with classes" uses, some STL and inheritance. <br />
But complex C++ features (such as advanced templates or meta-programming are not too common actually).<br />
<br />
One of the simplest ways to add new features to FlightGear is adding new commands to it, so called "fgcommands" (i.e. "FlightGear commands"). <br />
For additional information, please see this tutorial: [[Howto: Add new fgcommands to FlightGear]].<br />
<br />
== Programming resources ==<br />
If you need to read up on something programming related, such as C++, the STL, OpenGL, shaders etc, the wiki has plenty of programming resources to get you started: [[Resources]].<br />
<br />
== SimGear ==<br />
The SimGear code base is somewhat less archaic and more modern actually. And if you are interested in contributing to the OpenGL/SceneGraph department, you'll inevitably need to look into OpenSceneGraph (OSG), too - which really is "modern C++".<br />
<br />
SimGear is fairly well-maintained code base that contains a fair amount of doxygen comments, that means that it's easy to create doxygen documentation for SimGear. For example, see: http://api-docs.freeflightsim.org/simgear/<br />
<br />
Note that, at the time of reading, this may be outdated, so if you are interested in using the latest doxygen docs, you are well advised to run doxygen against your own latest simgear clone.<br />
<br />
Also, you can get a fair amount of information out of the FG sources by running them through doxygen, too.<br />
<br />
== Plain C ? (Nasal) ==<br />
If your C++ is rusty and you'd just like to get started quickly, there are also certain FG components that are strictly (largely) pure C, the Nasal interpreter is just one example (Nasal is FlightGear's built in scripting language): [[Nasal scripting language]]<br />
<br />
The Nasal interpreter is part of the SimGear project, and can be found in $SG_SRC/nasal: {{simgear url|trees/next/simgear/nasal}}<br />
<br />
The longest-standing issue related to Nasal scripting is fixing its Garbage Collector (GC) to become generational, incremental or even concurrent, this is to reduce main loop impact (frame rate & frame spacing), see [[How the Nasal GC works]] to learn more. Almost certainly, we're going to adopt an existing GC library, or even implement an interface to experiment with different GC schemes, and allow those to be selected at startup.<br />
<br />
Adding new extension functions to the built-in Nasal interpreter is documented here: [[Howto: Extend Nasal]].<br />
<br />
There's also a separate wiki article providing a list of known issues related to the Nasal interpreter itself: [[Improving Nasal]], specifically see [[Nasal Maintenance]].<br />
<br />
None of this requires any C++ knowledge!<br />
<br />
Only the scripting interface connecting the Nasal interpreter and FlightGear is implemented in C++, it can be found in {{fg src file|Scripting}}<br />
<br />
Basically, the scripting interface implements a custom SGSubsystem, so that the Nasal interpreter can be run as a FlightGear system. In addition, all FlightGear-specific extension functions are to be found there. Increasingly, this folder also contains wrappers to map FlightGear classes to Nasal space in an OOP fashion using the [[Nasal/CppBind]] framework, so that not just functions, but full "objects" are provided, which are computed lazily. If that's what you are interested in, you should take a look at the NasalPositioned_cppbind.cxx source code, which demonstrates how this is done.<br />
<br />
In other words, even without knowing C++, you can contribute to FlightGear core by extending the Nasal system. If you have some specific project in mind, you could probably implement it largely in scripting space using Nasal and only augment it as required with new extension functions in C space.<br />
<br />
= Getting started =<br />
Once you have found an area you are interested in, you can search the wiki, archives (mailing list and forums) or the issue tracker to find suitable projects to work on, for example: http://code.google.com/p/flightgear-bugs/issues/list?can=2&q=nasal&colspec=ID+Type+Status+Priority+Summary+Aircraft+Milestone&cells=tiles<br />
<br />
== Talk about your plans ==<br />
Before you start any serious efforts, please make sure to get in touch with other contributors. Ideally, using the developers mailing list or the forum. This is to ensure that others know about your plans, i.e. to avoid duplicate work, but also conflicting approaches. <br />
<br />
Often, FlightGear developers have certain ideas and plans for their projects, so it's good to coordinate your ideas with fellow contributors. In addition, you can get valuable feedback from experienced contributors this way, which may save you countless hours of time and lots of frustration.<br />
<br />
You may even find people interested in your idea and teaming up with you!<br />
<br />
== Scripting Hooks ==<br />
Another straightforward way to get started adding C++ code is using the [[Nasal/CppBind]] framework to expose built-in C++ classes to Nasal and enable base package contributors to make use of these, without bugging core developers to implement certain features directly. For C++ developers it is generally less time consuming (and often more rewarding) to implement abstract frameworks and infrastructure, rather than individual features.<br />
<br />
While the number of core developers has been decreasing during the last 12-18 months, we do have an increasing number of base package developers, so implementing generic hooks for them makes sense because core developers cannot possibly implement each requested feature.<br />
<br />
== Adding new subsystems ==<br />
If you are interested in adding new subsystems to FG, you may want to check out this: [[Howto:Create new subsystems]].<br />
<br />
Also, we have a step-by-step guide illustrating how a new system can be added to FlightGear, going into more detail. See [[Howto:Create a 2D drawing API for FlightGear]]<br />
<br />
== The property tree ==<br />
The FlightGear property tree is documented here: [[Howto:Work with the Property Tree API]]<br />
<br />
= Some Ideas =<br />
<br />
== Additional Scripting Bindings ==<br />
<br />
{{CppBind Ideas}}<br />
<br />
== CompositeViewer support ==<br />
This is a long-standing feature request, for details, please see [[CompositeViewer Support]].<br />
<br />
== World Scenery 3.0 ==<br />
The Terragear maintainers are looking for volunteers to help with development on the next world scenery project. If you've ever wondered how a full 3D model of earth can be generated from raw data, now is your chance. See the plan at [[World Scenery 3.0 roadmap]].<br />
<br />
<br />
== JPEGFactory ==<br />
{{Note|Also see [http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/053287a7-005d-4fd0-a1ee-96f1194ea904%40email.android.com/#msg32398628]}}<br />
{{cquote|actually the entire JPEGFactory option could likely be removed, and replaced with using the osgDB Image plugins to create a JPEG or PNG. And then it wouldn't need to be a CMake option at all. If anyone would like to attempt this, please ask and I can suggest where to start, it's a nice small project<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40211.html|title=<nowiki>Re: [Flightgear-devel] Enabling JPEG factory causes fgfs/GIT to fail compiling</nowiki>|author=James Turner|date=Tue, 11 Jun 2013 22:40:38 -0700}}</ref>|James Turner}}<br />
<br />
{{cquote|<nowiki>It's turned off for build reasons, not because it's new or untested. I believe <br />
many people have used it exactly the way you describe. If you encounter <br />
problems, they should be easy to fix and patches are welcome!<br />
<br />
(The build reasons could actually be solved by using OSGDB to write out the <br />
files instead of using libjpeg directly - this would mean the feature could be <br />
enabled all the time, i.e removed from CMake, and also we could write out PNGs <br />
instead of JPEGs if desired - if you have any interested in doing this, I can <br />
point you at examples since the screenshot code was converted to do the same <br />
thing recently -it's probably a couple of hours hacking at most)<br />
</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40749.html|title=<nowiki>Re: [Flightgear-devel] --jpg-httpd command line option</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Tue, 17 Sep 2013 04:17:15 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}}<br />
<br />
{{cquote|<nowiki>If someone decides to jump into this, another feature that would be cool<br />
would be to stream the display out as a video stream which could then be<br />
played by any number of video players on a remote computer (like mplayer.)<br />
ffmpeg probably would provide library support to make this pretty<br />
straightforward, but I haven't had a chance to dive in and see how<br />
easy/hard it would be.<br />
<br />
One area where this feature could be useful is in UAV research and<br />
simulation where you'd like to emulate a live video feed back to a ground<br />
station. It could also be fun for sharing/broadcasting your simulator<br />
session and probably could be made to work with a web video server.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40751.html|title=<nowiki>Re: [Flightgear-devel] --jpg-httpd command line option</nowiki>|author=<nowiki>Curtis Olson</nowiki>|date=<nowiki>Tue, 17 Sep 2013 11:51:00 -0700</nowiki>}}</ref>|<nowiki>Curtis Olson</nowiki>}}<br />
<br />
{{cquote|<nowiki>I wanted to capture the FG imagery and<br />
stream it over the web... (or some similar solution)<br />
</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg10533.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}}<br />
<br />
{{cquote|<nowiki>I've seen other<br />
apps that can do this so I know it's technically possible, and I imagine<br />
not too much coding once you figure out the magic to make it happen.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40751.html|title=<nowiki>Re: [Flightgear-devel] --jpg-httpd command line option</nowiki>|author=<nowiki>Curtis Olson</nowiki>|date=<nowiki>Tue, 17 Sep 2013 11:51:00 -0700</nowiki>}}</ref>|<nowiki>Curtis Olson</nowiki>}}<br />
<br />
{{cquote|<nowiki>VLC does this better than ffmpeg, so it's probably a good idea to study it's <br />
codebase for streaming code. Also, MJPEG is nice, but as a container I'd <br />
choose Ogg/Theora instead of H264 since they're entirely open.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40756.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}}<br />
<br />
{{cquote|<nowiki>Note if you want actual good performance from this system, there's much smarter <br />
things that could be done, such as grabbing the frame buffer each normal <br />
rendering frame, instead of re-rendering the scene each time an HTTP get is <br />
received. That would need much more drastic changes to the system however.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40757.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}}<br />
<br />
{{cquote|<nowiki>And obviously it does require that cmake finds the <br />
JPEG includes and libraries... I had earlier compiled <br />
and installed jpeg-9 into my 3rdParty folder... <br />
<br />
This dependency would go away if OSGDB was used, <br />
as James mentioned, but then JPEG would probably have <br />
to be found during the OSG build, unless OSG has <br />
alternate built-in jpeg code... not sure...<br />
<br />
Thereafter, running fgfs.exe with --jpg-httpd=1234 <br />
worked fine by putting http://localhost:1234 is a <br />
browser, and bingo had a jpg image of the screen <br />
in the browser ;=)) cool stuff...<br />
<br />
Of course it is a 'static' image, and had to refresh <br />
to get updated images of the flight... or an extension <br />
added to provide an actual video feed as Curt mentioned...<br />
<br />
So I would say it worked as advertised</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40884.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}}<br />
<br />
Also see: {{Issue|924}}.<br />
<br />
We could probably also look at using the [[Canvas]] system with some additional hooks, i.e. for getting a handle to the osg::Image, so that it can be serialized through Nasal and some cppbind glue, that would make it possible to depreciate the JPEGFactory code and use the Canvas system instead (i.e. unifying the 2d rendering backend). <br />
<br />
Being able to render camera views to a canvas texture has been previously requested a number of times, e.g. for implementing "mirrors" or tail cameras (A380) {{forum link|t=13798}} {{forum link|p=184284}} {{forum link|t=13798}} {{forum link|t=6184}} {{forum link|p=31252}}, and getting a handle to the buffer for serialization purposes would also allow us to reimplement the screenshot feature on top of canvas/Nasal, and even serve live image data through the httpd component.<br />
<br />
* [[Howto:Use a Camera View in an Instrument]]<br />
* [[Canvas_Properties#Serializing_a_canvas_to_a_buffer_or_file]]<br />
<br />
<references/><br />
<br />
= Finally =<br />
<br />
...please don't get discouraged if you shouldn't get too much feedback in the beginning, probably many contributors are busy preparing the next release: [[Release plan]]<br />
<br />
Lack of feedback doesn't necessarily mean that nobody likes your project or your ideas, probably it just means that you need to do some networking to get in touch with other contributors. <br />
<br />
Usually, getting involved in the forum, the issue tracker or in merge request discussions via gitorious is a good idea to familiarize yourself with the project. Please keep in mind that we get to see plenty of people each month announcing some fancy new FlightGear-related projects, so your signal/noise ratio is pretty important here. It's pretty likely that the type of feedback you get will be improving once you start contributing patches and help triage bug reports.<br />
<br />
People announcing that they want to work on FlightGear, without knowing C/C++ or without having ever built software from source, obviously have to face a steep learning curve, and we are aware of that.<br />
<br />
Sometimes, it may even take good ideas a while to be recognized as such, even if suggested by seasoned long-term contributors. So, please don't interpret lack of feedback as a general lack of interest.<br />
<br />
[[Category:Howto]]<br />
[[Category:Core developer documentation]]<br />
[[ru:Howto:Приступая к разработке ядра]]<br />
[[Category:Hackathon Materials]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142779Boeing 7772025-10-20T09:29:20Z<p>F-JYL: /* Aircraft Help */ fix headings</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
From the forum : <blockquote>"For anyone who might be interested, our discord server for 777 development is now open to everyone - both developers and flyers! You're welcomed to discuss everything about this craft in this server, including posting screenshots, reporting bugs, posting suggestions for development, or contributing directly to this plane here." [https://discord.gg/k5RXxFgGDA Discord Channel] </blockquote><br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
=== Landing ===<br />
[https://forum.flightgear.org/viewtopic.php?f=25&t=37701&p=373154#p373154 From the Forum thanks to Tdammers]<br />
<br />
Landing speeds: with a large airliner like the 777, the landing reference speed (Vref) depends hugely on weight. Between operating empty and max landing weight, there is a 50% difference, and clearly a landing speed that works well for a 140-ton aircraft is going to have you drop out of the sky when you weigh 210 tons; and conversely, the right landing weight at 210 tons is going to make your float or nosewheel-strike when you're landing empty. <br />
<br />
So what you need to do is find a resource for those landing speeds. Real-life pilots get a preliminary calculation from their dispatchers, who use dedicated software to calculate all the landing parameters; but it can also be done using tables from the FCOM, and in most modern airliners, the FMS can do the calculation as well. <br />
<br />
The same goes for the takeoff. Here, the crucial speeds are V1, Vr, and V2. V1 is the "safe rejection speed": until V1 is reached, the aircraft can be brought to a full stop safely within the available remaining takeoff distance; once you're faster than V1, rejecting the takeoff may lead to an accident, and you are committed to the takeoff except for very severe problems (like losing both engines, loss of control, or a fire). Vr is the "rotation speed": this is the ideal speed to pull up the nose to initiate the liftoff. V2 is the "safe single-engine climb speed": after liftoff, your goal is to attain this speed ASAP, so that loss of one engine does not compromise the aircraft's ability to meet the minimum climb requirements for this takeoff. <br />
<br />
In the FG 777, all these speeds are calculated automatically, and displayed on the PFD speed tape; Vref is shown as REF. <br />
<br />
For the landing: Use the initial approach segment to slow down to your initial approach speed; typically, this would be your "minimum clean" speed (the slowest speed you can safely fly with no flaps deployed), something around 200-220 knots usually. The approach procedure will have you descend to a suitable ILS intercept altitude, typically about 2000-3000 ft AGL. Make sure you have the correct ILS frequency set, that the ground spoilers are armed, and that you have selected a suitable autobrake setting. As you turn onto your intercept heading, slow down to your initial approach speed (160-180 knots should work fine), and set flaps accordingly, and arm APP on the autopilot. Watch the aircraft intercept first the localizer, and then the glideslope. Once established on the glideslope, deploy landing gear. As you approach the outer marker (5 miles out), slow down to final approach speed (usually Vref + 10 knots), and deploy landing flaps. <br />
<br />
Now you have the choice between autoland and landing manually. <br />
<br />
==== Autoland ====<br />
For autoland, I believe all you have to do is watch the aircraft fly itself down to minimums, flare, align, retard, and touch down. Once on the ground, select reversers and set reverse thrust, verify that the ground spoilers and brakes are deploying, and use rudder to maintain centerline. At 60 knots, retard the throttles to reverse idle, and take over manual braking (the autobrakes should automatically disengage as soon as you touch the brakes). At 40 knots ground speed, disable thrust reversers; you may now take a high-speed exit while slowing down to taxi speed, or slow down further on the runway before taking a sharp exit. While vacating the runway, retract flaps, and switch off landing lights. <br />
<br />
==== Manual Landing ====<br />
For a manual landing, the procedure is the same, except you disengage autopilot and autothrottle at some point during the approach - 1000 ft AGL is a good moment, but you can do it earlier if you want. Use pitch to control speed, throttle to control descent rate; keep airspeed at Vref + 10, and sink rate such that you stay on the ILS glideslope. Once you have a good visual of the runway, transition to a visual approach, using PAPI lights as your descent reference (two red, two white means you're on the glideslope). You should cross the runway threshold some 100-200 ft AGL, with some residual thrust on the engines (say 40-60% or so), a slight nose-up attitude, and a sink rate around 1000 fpm or so. At a suitable altitude (typically 50-100 ft AGL), retard the throttles; use pitch to arrest the descent - down to zero if you want a "butter" landing, or keep a little bit of sink rate if you want a safer, firmer landing. The aircraft should now just sink into the runway, main landing gear first. From here, the procedure is the same as above.<br />
<br />
=== TakeOff ===<br />
[https://forum.flightgear.org/viewtopic.php?f=25&t=37701&p=373154#p373154 From the Forum thanks to Tdammers]<br />
<br />
For the takeoff: Configure autobrake (RTO, "rejected takeoff"), flaps and trim, line up, arm A/T (the flip switches next to the speed selection on the glare-shield panel), and rotate the speed selector to a suitable departure speed - at least V2, but typically something like 200-250 knots. This is to make sure that when the autothrottle kicks in, it keeps setting takeoff thrust at least until you have achieved V2. Set a suitable lateral mode on the autopilot: LNAV if you're flying an FMS flight plan, otherwise probably HDG. Revv up the engines to 40%, wait until they stabilize, then set takeoff thrust. At the "rotate" callout, pitch up; watch the vertical speed, as soon as it's consistently positive for 1 second, gear up. Maintain center-line and an attitude that keeps you speeding up to V2. Engage autopilot a couple hundred feet AGL, or later if you prefer hand-flying the aircraft a bit longer. <br />
<br />
===Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
*Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
===Walker===<br />
Walker implementation<br />
{{#ev:youtube|GriEXRsr5q8}}<br />
<br />
==Tutorials==<br />
<br />
===Flights===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
===Outdated/Not Maintained===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
==Variants==<br />
===Boeing 777-200 ===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
==External links==<br />
*[[sourceforge:projects/xpc-777|Boeing 777 aircraft systems simulator]] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
*[http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
*[http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
*[https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]<br />
<br />
<references /></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142778Boeing 7772025-10-20T09:28:26Z<p>F-JYL: /* Aircraft Help */ Landing and Take off from the forum thanks to tdammers</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
From the forum : <blockquote>"For anyone who might be interested, our discord server for 777 development is now open to everyone - both developers and flyers! You're welcomed to discuss everything about this craft in this server, including posting screenshots, reporting bugs, posting suggestions for development, or contributing directly to this plane here." [https://discord.gg/k5RXxFgGDA Discord Channel] </blockquote><br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
====Landing====<br />
[https://forum.flightgear.org/viewtopic.php?f=25&t=37701&p=373154#p373154 From the Forum thanks to Tdammers]<br />
<br />
Landing speeds: with a large airliner like the 777, the landing reference speed (Vref) depends hugely on weight. Between operating empty and max landing weight, there is a 50% difference, and clearly a landing speed that works well for a 140-ton aircraft is going to have you drop out of the sky when you weigh 210 tons; and conversely, the right landing weight at 210 tons is going to make your float or nosewheel-strike when you're landing empty. <br />
<br />
So what you need to do is find a resource for those landing speeds. Real-life pilots get a preliminary calculation from their dispatchers, who use dedicated software to calculate all the landing parameters; but it can also be done using tables from the FCOM, and in most modern airliners, the FMS can do the calculation as well. <br />
<br />
The same goes for the takeoff. Here, the crucial speeds are V1, Vr, and V2. V1 is the "safe rejection speed": until V1 is reached, the aircraft can be brought to a full stop safely within the available remaining takeoff distance; once you're faster than V1, rejecting the takeoff may lead to an accident, and you are committed to the takeoff except for very severe problems (like losing both engines, loss of control, or a fire). Vr is the "rotation speed": this is the ideal speed to pull up the nose to initiate the liftoff. V2 is the "safe single-engine climb speed": after liftoff, your goal is to attain this speed ASAP, so that loss of one engine does not compromise the aircraft's ability to meet the minimum climb requirements for this takeoff. <br />
<br />
In the FG 777, all these speeds are calculated automatically, and displayed on the PFD speed tape; Vref is shown as REF. <br />
<br />
For the landing: Use the initial approach segment to slow down to your initial approach speed; typically, this would be your "minimum clean" speed (the slowest speed you can safely fly with no flaps deployed), something around 200-220 knots usually. The approach procedure will have you descend to a suitable ILS intercept altitude, typically about 2000-3000 ft AGL. Make sure you have the correct ILS frequency set, that the ground spoilers are armed, and that you have selected a suitable autobrake setting. As you turn onto your intercept heading, slow down to your initial approach speed (160-180 knots should work fine), and set flaps accordingly, and arm APP on the autopilot. Watch the aircraft intercept first the localizer, and then the glideslope. Once established on the glideslope, deploy landing gear. As you approach the outer marker (5 miles out), slow down to final approach speed (usually Vref + 10 knots), and deploy landing flaps. <br />
<br />
Now you have the choice between autoland and landing manually. <br />
<br />
===== Autoland =====<br />
For autoland, I believe all you have to do is watch the aircraft fly itself down to minimums, flare, align, retard, and touch down. Once on the ground, select reversers and set reverse thrust, verify that the ground spoilers and brakes are deploying, and use rudder to maintain centerline. At 60 knots, retard the throttles to reverse idle, and take over manual braking (the autobrakes should automatically disengage as soon as you touch the brakes). At 40 knots ground speed, disable thrust reversers; you may now take a high-speed exit while slowing down to taxi speed, or slow down further on the runway before taking a sharp exit. While vacating the runway, retract flaps, and switch off landing lights. <br />
<br />
===== Manual Landing =====<br />
For a manual landing, the procedure is the same, except you disengage autopilot and autothrottle at some point during the approach - 1000 ft AGL is a good moment, but you can do it earlier if you want. Use pitch to control speed, throttle to control descent rate; keep airspeed at Vref + 10, and sink rate such that you stay on the ILS glideslope. Once you have a good visual of the runway, transition to a visual approach, using PAPI lights as your descent reference (two red, two white means you're on the glideslope). You should cross the runway threshold some 100-200 ft AGL, with some residual thrust on the engines (say 40-60% or so), a slight nose-up attitude, and a sink rate around 1000 fpm or so. At a suitable altitude (typically 50-100 ft AGL), retard the throttles; use pitch to arrest the descent - down to zero if you want a "butter" landing, or keep a little bit of sink rate if you want a safer, firmer landing. The aircraft should now just sink into the runway, main landing gear first. From here, the procedure is the same as above.<br />
<br />
==== TakeOff ====<br />
[https://forum.flightgear.org/viewtopic.php?f=25&t=37701&p=373154#p373154 From the Forum thanks to Tdammers]<br />
<br />
For the takeoff: Configure autobrake (RTO, "rejected takeoff"), flaps and trim, line up, arm A/T (the flip switches next to the speed selection on the glare-shield panel), and rotate the speed selector to a suitable departure speed - at least V2, but typically something like 200-250 knots. This is to make sure that when the autothrottle kicks in, it keeps setting takeoff thrust at least until you have achieved V2. Set a suitable lateral mode on the autopilot: LNAV if you're flying an FMS flight plan, otherwise probably HDG. Revv up the engines to 40%, wait until they stabilize, then set takeoff thrust. At the "rotate" callout, pitch up; watch the vertical speed, as soon as it's consistently positive for 1 second, gear up. Maintain center-line and an attitude that keeps you speeding up to V2. Engage autopilot a couple hundred feet AGL, or later if you prefer hand-flying the aircraft a bit longer. <br />
<br />
===Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
*Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
===Walker===<br />
Walker implementation<br />
{{#ev:youtube|GriEXRsr5q8}}<br />
<br />
==Tutorials==<br />
<br />
===Flights===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
===Outdated/Not Maintained===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
==Variants==<br />
===Boeing 777-200 ===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
==External links==<br />
*[[sourceforge:projects/xpc-777|Boeing 777 aircraft systems simulator]] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
*[http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
*[http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
*[https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]<br />
<br />
<references /></div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Changelog_2024.1.2&diff=142616Changelog 2024.1.22025-10-03T13:12:28Z<p>F-JYL: Created page with "{{Note|As of FlightGear 2024.1, the changelog is [https://www.flightgear.org/download/releases/2024-1-2/ hosted on the FlightGear website] instead of the wiki and, therefore, written in {{gitlab source |proj=flightgear |repo=website |text=the corresponding GitLab repository}}.}}"</p>
<hr />
<div>{{Note|As of FlightGear 2024.1, the changelog is [https://www.flightgear.org/download/releases/2024-1-2/ hosted on the FlightGear website] instead of the wiki and, therefore, written in {{gitlab source |proj=flightgear |repo=website |text=the corresponding GitLab repository}}.}}</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142598Boeing 7772025-09-30T09:57:24Z<p>F-JYL: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
From the forum : <blockquote>"For anyone who might be interested, our discord server for 777 development is now open to everyone - both developers and flyers! You're welcomed to discuss everything about this craft in this server, including posting screenshots, reporting bugs, posting suggestions for development, or contributing directly to this plane here." [https://discord.gg/k5RXxFgGDA Discord Channel] </blockquote><br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
=== Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
* Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
===Walker===<br />
Walker implementation<br />
{{#ev:youtube|GriEXRsr5q8}}<br />
<br />
== Tutorials ==<br />
<br />
=== Flights ===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
=== Outdated/Not Maintained ===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries ==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
== Variants ==<br />
===Boeing 777-200===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
* [http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
* [http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
* [https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142597Boeing 7772025-09-30T09:56:34Z<p>F-JYL: Added discord channel</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
From the forum : <blockquote>"For anyone who might be interested, our discord server for 777 development is now open to everyone - both developers and flyers! You're welcomed to discuss everything about this craft in this server, including posting screenshots, reporting bugs, posting suggestions for development, or contributing directly to this plane here." [https://discord.gg/k5RXxFgGDA Discord Channel] </blockquote><br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
=== Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
* Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
===Walker===<br />
Walker implementation<br />
{{#ev:youtube|GriEXRsr5q8}}<br />
<br />
== Tutorials ==<br />
<br />
=== Flights ===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
=== Outdated/Not Maintained ===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries ==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
== Variants ==<br />
===Boeing 777-200===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
* [http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
* [http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
* [https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142596Boeing 7772025-09-30T08:51:58Z<p>F-JYL: Walker implementation</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
=== Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
* Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
===Walker===<br />
Walker implementation<br />
{{#ev:youtube|GriEXRsr5q8}}<br />
<br />
== Tutorials ==<br />
<br />
=== Flights ===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
=== Outdated/Not Maintained ===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries ==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
== Variants ==<br />
===Boeing 777-200===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
* [http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
* [http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
* [https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=142595Boeing 7772025-09-30T08:48:05Z<p>F-JYL: /* Tutorials */</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{screenshot cat<br />
| category = Boeing 777 screenshots<br />
| subject = the Boeing 777<br />
| image = CAS777.png<br />
}}<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350 XWB|A350 XWB]]. <br />
<br />
== Systems ==<br />
<br />
The Boeing 777 is an advanced fly-by-wire aircraft, and the systems are moderately complicated. <br />
<br />
=== Brief Overview ===<br />
The video below is a brief introduction of the Boeing 777's new system of the new Seattle Project working with FlightGear Version 3.2 Test Release.<br />
<br />
{{#ev:youtube|EoNQ1NpcnMw}}<br />
<br />
<br />
=== Controls ===<br />
The Boeing 777 series are fly-by-wire aircraft and like all Boeing aircraft have yokes. The signals are sent electrically to the hydraulic actuators which move the control surfaces. The fly-by-wire system has been simulated within the limitations of YAsim.<br />
<br />
- Roll Control Law with attitude holding and bank angle protection<br />
<br />
- C*U Pitch Law and Trim Ref function with Flare Mode and Autotrim<br />
<br />
- Rudder Ratio, Yaw Damper and Turn Coordinator<br />
<br />
=== Engines ===<br />
{{aero-stub|section=1}}<br />
{| class="wikitable"<br />
|-<br />
! Model<br />
! 777-200 !! 777-200ER !! 777-200LR !! 777F !! 777-300 !! 777-300ER<br />
|-<br />
! Engines (Turbofans)<br />
| [https://en.wikipedia.org/wiki/Pratt_%26_Whitney_PW4000 PW 4077] [https://en.wikipedia.org/wiki/Rolls-Royce_Trent_800 RR 877] [https://en.wikipedia.org/wiki/General_Electric_GE90 GE90-77B] || PW 4090 RR 895 GE90-94B || GE90-110B1 GE90-115B1 || GE90-110B1 GE90-115B1 || PW 4098 RR 892 GE90-92B/-94B || GE90-115B1<br />
|-<br />
! Max Thrust<br />
| 77,200 lbf (343 kN) || 84,700 lbf (377 kN) || 115,300 lbf (513 kN) || 115,300 lbf (513 kN) || 98,000 lbf (440 kN) || 115,300 lbf (513 kN)<br />
|}<br />
=== Electrical ===<br />
{{aero-stub|section=1}}<br />
<br />
=== Hydraulic ===<br />
The current Boeing 777 hydraulic system is basically working, it will be expanded in the future for more realistic behavior.<br />
<br />
The hydraulic systems can (and must) be fully controlled via the 3D cockpit switches on the overhead panel. As in real life, the following behavior should be expected:<br />
* The Left hydraulic system is powered by an engine driven pump (EDP) and supplemented by two on-demand Electric motor pumps (ACMP). It operates wing & tail flight controls (ailerons, elevators, rudder) and left thrust reverser operation.<br />
* The Right system is powered by by an EDP from the right engine and supplemented by an ACMP. It operates flight controls, right thrust reverser operation and the normal brake system.<br />
* The Center system is powered by two ACMP's and supplemented by two on-demand air turbine-driven pumps (ADP). It operates the landing gear actuation, nose & main gear steering, flaps & slats, flight controls and the reserve brake system.<br />
<br />
When no engine is running, the APU (if running) and/or Ground Power (if connected and activated) provide power to the center system's ACMP's. Make sure the ACMP's are on when you want to use the center system on APU/Ground Power.<br />
<br />
A realistic Ram Air Turbine (RAT) and reserve system have yet to be modeled.<br />
<br />
=== Autopilot ===<br />
[[File:777-300-APpanel.png|thumb|270px|777-300 Autopilot]]<br />
The 777 autopilot can be fully controlled using the 3D cockpit switches. For FG2.4.0 use left and middle mouse buttons to turn any switches left/right. For FG2.5.0 and newer, you can use the mouse scroll wheel on all cockpit knobs.An Autoland system is available as of v2.6.0<br />
<br />
You can also use the 777's built-in autopilot tutorial to learn about the different switches.<br />
<br />
Autopilot controls, from left to right, top to bottom:<br />
* '''A/P''' - Autopilot engage/disengage button<br />
* '''F/D''' - Flight director (the pink lines that show up on your attitude indicator)<br />
* '''A/T ARM (L/R)''' - Arm/disarm autothrottle for left/right engines. Must be armed to enable autothrottle for the respective engine.<br />
* '''CLB CON''' - Continue climbing using the vertical speed the plane was at, when this setting was first engaged<br />
* '''A/T''' - Autothrottle engage/disengage button. Like the real 777, the autothrottle is independent from the main autopilot, so autothrottle also also works when the autopilot is disabled (Note: this was different for FG2.0 and earlier!).<br />
* '''IAS <> MACH''' - Switch between IAS speed mode and Mach number speed mode<br />
* '''IAS window''' - Set your desired IAS speed or Mach speed here<br />
* '''LNAV''' - Tells the autopilot to follow the Route Manager settings laterally (control the heading).<br />
* '''VNAV''' - Same as LNAV, except vertically (control the altitude). The autopilot will climb to the flight level you set in the Route Manager (in the input field or at a specified waypoint).<br />
* '''FLCH''' - Flight Level Change, set the altitude and press FLCH to climb or descent to designated flight level. Thrust is set to a fixed value, speed is controled with pitch.<br />
* '''A/P DISENGAGE''' - Dedicated autopilot disengage button (click twice). It serves as an easy to reach "emergency disengage" button.<br />
* '''HDG <> TRK''' - Switch between heading bug and course track<br />
* '''HDG window''' - Set your desired heading or course track here.<br />
* '''HDG select''' - Engage/disengage heading or course hold mode and maintain SELECTED heading (FG2.5.0 and newer).<br />
* '''Bank limits''' (AUTO/5/10/15/20/25) - Define banking limits for turning, i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases.<br />
* '''HOLD''' - Engage/disengage heading or course hold mode and maintain CURRENT aircraft heading.<br />
* '''V/S <> FPA''' - Switch between Vertical Speed and Flight Path Angle<br />
* '''V/S window''' - Set your desired Vertical Speed or Flight Path Angle<br />
* '''VS/FPA''' - Engage/disengage Vertical Speed/Flight Path Angle hold mode<br />
* '''ALTITUDE window''' - Set your desired altitude here<br />
* '''Altitude selection''' (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog<br />
* '''HOLD''' - Engage/disengage altitude hold mode<br />
* '''LOC''' - Track LOCALIZER, flying by the heading given by the localizer<br />
* '''APP''' - Arm the ILS localizer and glideslope (laterally and vertically). Any current AP mode (HDG and ALTITUDE HOLD) remains active, until the NAV receiver captures the localizer or glideslope.<br />
* '''A/P''' - Engage/disengage autopilot<br />
* '''F/D''' - Flight director<br />
==== How to use ====<br />
* '''Default mode of when autopilot engage'''<br />
HDG HOLD mode: Maintain heading when engage.<br />
ATT mode: If bank angle exceeds 5deg when engaged, keep that bank angle. (there's bug, will be fixed)<br />
VS mode: using vs value when engaged.<br />
If FD mode was engaged, mode is inherited.<br />
<br />
* '''Mode'''<br />
Lateral control<br />
<br />
HDG HOLD: keep set heading.<br />
HDG SEL: follow the heading set on counter. Change value when HDG HOLD or press SEL button when other mode such as VNAV, LOC mode. Once reach to setting heading change to HDG HOLD.<br />
LNAV: follow the activated route.<br />
LOC: when arming, keep previous mode and then capture LOCALIZER, follow that course.<br />
<br />
Vertical control<br />
<br />
VS : keep targeted vertical speed to reach selected altitude.<br />
FLCH : keep fixed climb thrust or flight idle and control the pitch to maintain speed thus vertical speed varies.<br />
VNAV : Follow the FMS target altitude and thrust.<br />
ALT HOLD : When you press HOLD button, keep altitude when button pressed. Counter value does not change. Once VS of FLCH reaches targeted altitude, it holds that altitude.<br />
<br />
=== Flight Management Computer ===<br />
{{aero-stub|section=1}}<br />
<br />
==Aircraft Help==<br />
=== Start Procedure (Fast)===<br />
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected<br />
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up<br />
* Hold the 's' button for 10 seconds or until the engines are running at idle.<br />
<br />
=== Start Procedure (Extended Version) ===<br />
'''0. remember to'''<br><br />
''a) set the correct QNH (pressure) when below transition level<br><br />
b) set the fuel to a proper level in each tank (so you dont mess with the sliders when airborne)<br><br />
c) you can use ctrl+c to reveal all usable buttons and knobs''<br><br />
<br />
'''1. prepare systems'''<br><br />
a) turn on the battery, taxi lights and panel lights if you need it (button is placed)<br />
to tle left, left from the BCN light button.<br><br />
b) turn the APU knob clockwise (the knob next to the APU GEN), wait 1min for it to start-up<br><br />
b1) set APU knob to the middle position<br><br />
c) turn on all 4 hydraulic pumps/valves. 2 in the center are for the flaps and spoilers (both<br><br />
pumps MUST be enabled), the same with the other two, they are for landing gear. the<br />
buttons are between electrical and fuel part of the panel.<br />
<br />
'''2. prepare engines'''<br><br />
a) start fuel pumps. there are 6: 2 for each tank. to enable fuel flow from a tank, you have<br />
to enable BOTH (just like with the hydraulics) pumps.<br><br />
b) enable the engine starters (you can turn on both one after another, but thats not really realistic)<br><br />
c) after N1 reach ~45, engine should be running on its own, self sustaining, fuel cutoff valves open<br />
automatically. eicas shows up a message that L(R) ENG STARTER is on.<br><br />
d) turn on both engine generators<br><br />
e), turn off APU (knob position 1) and BAT<br><br />
<br />
=== Fuel Controls===<br />
====Jettisonning fuel====<br />
a) just press the JETTISON ARM button, its hidden behind some knob in the right part of the OH panel,<br />
go to 0. a) if you cant find it<br><br />
b) monitor the fuel levels, press the button again to stop the process. (jettisonning will automatically<br />
stop when theres ~1000 gallons in each tank)<br><br />
c) fuel flow is 30 gallons per second.<br><br />
<br />
====Crossfeed====<br />
a) enable FWD xfeed pump and AFTER IT enable AFT pump. if you mess this, it wont work and you will have<br />
to repeat.<br><br />
b) watch the fuel indicators on the eicas as the fuel level gets equalized in both tanks, left and right.<br><br />
c) fuel flow is set to 4 gallons per second.<br><br />
<br />
===Autopilot===<br />
====Bank Angle====<br />
a) position 0 activates the automatic bank limiter (limit based on airspeed)<br><br />
b) any other position sets a constant bank limit, 5, 10, 15, 20, 25<br><br />
c) for speeds below V2+15 use 15 degree bank limit<br><br />
<br />
===Tiller===<br />
'''Important notice:''' as of FlightGear 2.4.0, the 777 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (777-200ER > Tiller Steering) dialog to steer during taxiing.<br />
* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.<br />
* Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 777-200ER > Tiller Steering dialog).<br />
<br />
== Tutorials ==<br />
<br />
=== Flights ===<br />
<br />
[[File:Stars-2.png|100px]]'''[[Boeing_777_TutoriaI/KATL-KMIA | Atlanta to Miami]]'''<br />
<br />
[[File:Stars-3.png|100px]]'''[[Boeing_777-200_TutoriaI/KSFO-KLAX | San Fransisco to Los Angeles]]'''<br />
<br />
'''VATSIM Cross the pond 2020 - preflight, takeoff and climbout''' <br />
{{#ev:youtube|lZscu3THPJU}}<br />
<br />
=== Outdated/Not Maintained ===<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Liveries ==<br />
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries].<br />
<br />
== Variants ==<br />
===Boeing 777-200===<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
The '''Boeing 777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).<br />
<br />
===Boeing 777-200LR===<br />
[[File:777-200LR Alaska.jpg|270px||thumb|777-200LR in CathayPacific Colors above Alaska]]<br />
The '''Boeing 777-200LR''' ("LR" for Longer Range), a variant of the [[Boeing 777]], became the world's longest-range commercial [[airliner]] when it entered service in 2006. Boeing named this aircraft the ''Worldliner'', highlighting its ability to connect almost any two airports in the world. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The 777.200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore.<ref>[http://en.wikipedia.org/wiki/Boeing_777 Boeing 777] (Wikipedia)</ref><br />
<br />
===Boeing 777-300===<br />
The -300 features a 33.3 ft (10.1 m) fuselage stretch over the baseline -200, allowing seating for up to 550 passengers in a single class high-density configuration. The 777-300ER ("ER" for Extended Range) is the B-market version of the -300. It features raked and extended wingtips, a new main landing gear, reinforced nose gear, and extra fuel tanks. <br />
<br />
===Boeing 777-F===<br />
[[File:777F.png|270px||thumb|777-F]]<br />
The 777 Freighter (777F) is an all-cargo version of the twinjet, and shares features with the -200LR; these include its airframe, engines, and fuel capacity. With a maximum payload of 226,000 lb (103,000 kg), cargo capacity is similar to the 243,000 lb (110,000 kg) of the 747-200F. The freighter has a range of 4,900 nmi (9,070 km) at maximum payload, although greater range is possible if less cargo weight is carried. As the aircraft promises improved operating economics compared to existing freighters, airlines have targeted the 777F as a replacement for older freighters including the [[747-200]]F and [[MD-11]]F.<br />
The 777 for Flightgear is based on [[777-200]] developed by Justin Smithies, Syd Adams.<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
* [http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
* [http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
* [https://archive.org/details/Boeing777FlightManual Flight manual]<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=World_Scenery_3.0&diff=142592World Scenery 3.02025-09-29T14:26:30Z<p>F-JYL: Update global up-to-date WS3.0 airports link</p>
<hr />
<div>{{WS30 Navbar}}<br />
World Scenery 3.0 is a project to replace the tiled single-mesh World Scenery 2.0 with an LoD-based approach using a regular elevation mesh, landclass texture and vector line features.<br />
<br />
This leverages OSG's Virtual Planet Builder and OpenStreetmap APIs. <br />
<br />
<!--<br />
For further information:<br />
<br />
* [[World Scenery 3.0 roadmap]]<br />
* [[World Scenery 3.0 rendering]]<br />
* [[World Scenery 3.0 coastlines]]<br />
* [[WS3.0 Performance Testing]]<br />
* [[Howto:Create WS3.0 terrain]]<br />
* [[Virtual Planet Builder]]<br />
--><br />
== Currently Available Scenery ==<br />
<br />
=== Terrain ===<br />
Scenery is currently not distributed using the official Terrasync, Nia provides a terrasync compatible download, point your terrasync client to https://de1mirror.flightgear.org/ws3/ to make use of it. As of writing (2024-01-15) it contains all of the sceneries below (duplicates removed) and will get updated when a new Airports package is made and when Wayne provides her with new US scenery. If you don't wanna deal with changing your terrasync settings, you can always download sections of scenery via the links individually and added to your [[FG SCENERY|scenery path]]. If you set these in your scenery path ahead of any other scenery, it will pick up osm2city, scenery objects etc. from the underlying scenery as well.<br />
{| class="wikitable"<br />
|+<br />
Currently Available World Scenery 3.0<br />
!Scenery<br />
!Area<br />
!Size <br />
!Bottom Left<br />
!Top Right<br />
!Area (degrees^2)<br />
!Landclass Source<br />
!Landclass Resolution (m)<br />
!Raster format<br />
!Comments<br />
!Osm2city Scenery for WS3<br />
|-<br />
|[https://drive.google.com/file/d/1EapHG6qEYU6CWdXnp0_aqjUaX61Lk5EL/view?usp=sharing WS30_UK]<br />
|UK and Eire<br />
|1.5GB<br />
| -11,49<br />
|1,60<br />
|121<br />
|CORINE<br />
|10<br />
|PNG<br />
|Includes detailed roads and water features. <br />
|<br />
|-<br />
|[https://drive.google.com/file/d/120QOxfTWEm6EBmjK0eCNb07hrm3clavi/view?usp=sharing NL (terrain only)]<br />
|Amsterdam and Lelystad<br />
|716MB (ca. 8GB uncompressed)<br />
|2,50<br />
|10,53<br />
|24<br />
|CORINE<br />
|10<br />
|PNG<br />
|Includes high resolution water raster from OpenStreetMap. Check out the canals!<br />
|[https://drive.google.com/file/d/13inL4UqSyvRh5FVq62quVOYXnlEhxU1G/view?usp=sharing contains osm2city stuff incl. trees etc. also contains the static objects from Terrascync]. NB: contains also the terrain - no need to download the terrain seperatly (as per first column). Use with the new airport download and do NOT run on top of WS2.0 scenery.<br />
|-<br />
|[https://drive.google.com/file/d/1MrYuDKbMl4WhCEq9gnnt8Tz61lTAScvD/view?usp=share_link WS_Alps]<br />
|<br />
|49MB<br />
|6,45<br />
|8,47<br />
|4<br />
|CORINE<br />
|25<br />
|DDS<br />
|<br />
|<br />
|-<br />
|[https://drive.google.com/file/d/1x-kuCTfyMWddTi0fbr_nl41LR41Ylvwb/view?usp=share_link WS30_MTQ]<br />
|Martinique<br />
|7MB<br />
| -62,14<br />
| -60,15<br />
|2<br />
|CORINE<br />
|10<br />
|PNG<br />
|Small French Caribbean island. One airport (TFFF)<br />
|[https://drive.google.com/file/d/1QtojSTbnAAfkMzirQHnDJWbBDGOtnwIK/view?usp=sharing osm2city buildings, trees, maritime, pylons etc.] (ca. 40 MB).<br />
|-<br />
|[https://drive.google.com/file/d/14kbbgXbofDmqxho-bMCfOG4jDwcDqwBd/view?usp=share_link WS30_MTQ_25m]<br />
|Martinique<br />
|7MB<br />
| -62,14<br />
| -60,15<br />
|2<br />
|CORINE<br />
|25<br />
|PNG<br />
|Small French Caribbean island. One airport (TFFF)<br />
|(see above)<br />
|-<br />
|[https://drive.google.com/file/d/1-LS3yQZ0OkWX38Ne89n69wtrT7SreV69/view?usp=sharing WS_MTQ_5m]<br />
|Martinique<br />
|8MB<br />
| -62,14<br />
| -60,15<br />
|2<br />
|CORINE<br />
|5<br />
|PNG<br />
|Includes high resolution water raster from OpenStreetMap. Small French Caribbean island. One airport (TFFF)<br />
|(see above)<br />
|-<br />
|[https://drive.google.com/file/d/1Um7WC8h8Y4BlwgoVSd2xoVO5gTd3E-bI/view?usp=sharing Switzerland_5m]<br />
|Switzerland plus small border<br />
|1.4 GB (ca. 7 GB unzipped)<br />
| 5.75,45.75<br />
| 10.75,48<br />
|10<br />
|CORINE<br />
|5<br />
|PNG<br />
|By mistake taken default airports. If you are using Nia's updated airports, then it will most often work fine, but there might be residuals with osm2city (e.g. tree on APRON).<br />
|included<br />
|-<br />
|[https://de1mirror.flightgear.org/hosting/wayne/ WS3.0 USA]<br />
|USA<br />
|200 to 400 KB (zipped)<br />
| 125,48<br />
| 81,24<br />
|<br />
|NLCD, Tree Canopy Data<br />
|30<br />
|<br />
|by state<br />
|<br />
|-<br />
|[https://github.com/SP-NTX/PolandWS30/ Poland]<br />
|Poland<br />
|1.2GiB<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://drive.google.com/file/d/1hDuTA9DVnAySxQvicqZK9u0JlE8irTqA/view?usp=sharing Scotland_5m]<br />
|Scotland without Orkney/Shetland<br />
|1.8 GB (ca. 16 GB unzipped)<br />
| -8,54<br />
| -1,59<br />
|<br />
|CORINE<br />
|5<br />
|PNG<br />
|<br />
|included<br />
|-<br />
|[https://drive.google.com/file/d/10M-K0XA_MQV8eCx4Xaidfje_4Uw2STQC/view?usp=drive_link WS30_FR]<br />
|Mainland France<br />
|3.5GB (ca 3.8GB unzipped)<br />
| -5,43<br />
|8,53<br />
|129<br />
|CORINE<br />
|10<br />
|PNG<br />
|Terrain, water features and roads only<br />
|<br />
|-<br />
|[https://drive.google.com/file/d/1NqBq8iEC6oqYCKgsllZfw5sT1lPPY5it/view?usp=sharing WS30_UG]<br />
|Uganda and Lake Victoria<br />
|1.3GB<br />
|28,-4<br />
|36,3<br />
|56<br />
|SENTINEL-2<br />
|10<br />
|PNG<br />
|Terrain, water features and roads only<br />
|<br />
|}<br />
<br />
=== Airports ===<br />
In addition to the selected areas above, global up-to-date WS3.0 airports have been built. You can find them [https://us1mirror.flightgear.org/terrasync/ws3/ here]<br />
<br />
=== Scenery Files Placement ===<br />
Uncompress the downloaded scenery files into a folder of your choice, such as E:\MySceneryFolder. To be recognized by FlightGear, the selected scenery (from the table above) must be located in a folder with a "vpb" subfolder, such as (EX: C:\mysceneryfolder\hawaii\vpb). The scenery files above are compressed and include the "vpb" folder.<br />
<br />
=== Installing ===<br />
Using the FlightGear [[FlightGear_Qt_launcher]] both the terrain and the airport are "installed" by going to tab "Add-ons" and then add the respective folders to "Additional scenery folders". When adding an additional scenery folder, you need to point to the folder immediately above the "vpb" subfolder. <br />
<br />
If you add the airports the first time you might have to close the launcher and reopen it again to get the navigation data loaded properly into the session.<br />
<br />
== Running World Scenery 3.0 ==<br />
To run WS3.0 you need to set the <code>/scenery/use-vpb</code> property to <code>true</code> at startup. Either set <code>--prop:/scenery/use-vpb=true</code> on your command-line, or in the Launcher in "Settings" -> "Rendering" (you might need to click on "Show more" on the right side to see the choice for "Scenery version".<br />
<br />
WS3.0 can use a lot of memory - significantly more than WS2.0. You can control the memory usage with the following properties:<br />
<br />
* <code>/sim/rendering/max-paged-lod</code> controls the minimum number of objects that will be kept in memory. The default setting is 200.<br />
* <code>/sim/rendering/plod-minimum-expiry-time-secs</code> controls how long objects remain loaded for after they are no-longer in view. The default value is 180 (3 minutes).<br />
<br />
Reducing these properties will reduce the memory footprint of WS3.0.<br />
<br />
If you have lots of spare cores, you can run multiple threads to load scenery by setting <code>/sim/rendering/database-pager/threads</code> to a number greater than 4 on startup. E.g. <code>--prop:/sim/rendering/database-pager/threads=8</code>.<br />
<br />
=== WS 2.0 scenery might still be needed ===<br />
To have airports displayed plus some of the default scenery objects, you might still want to have the WS 2.0 scenery for the same area installed.<br />
<br />
However, if you want updated airports, checkout the global WS3.0 airports above. To avoid collisions you need to not have any WS2.0 airports enabled if you use these.<br />
<br />
=== Using osm2city ===<br />
WS3.0 has built-in support for OpenStreetMap roads, so you should not have it enabled in rendering settings.<br />
<br />
You have 2 options:<br />
<br />
* If you have WS2.0 world scenery, then it already contains osm2city buildings etc. You can just use these and live with slight elevation offsets.<br />
* The other option is to use the provided osm2city scenery in the table above instead. If doing so you need to makes sure that WS2.0 osm2city has not been downloaded (or delete the folders manually). E.g. if you are using [[TerraMaster]] then you can remove the ticks in Settings for "Buildings", "Pylons" and "Roads". <br />
<br />
Using the explicitly provided osm2city scenery gives you trees in gardens/parks and some improvements only available on NEXT.</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump&diff=69795FlightGear wiki:Village pump2014-04-21T07:33:05Z<p>F-JYL: /* Very dispersed Boeing 777 articles! */</p>
<hr />
<div>{{Archives|[[/Archive 2012|2012]]}}<br />
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].<br />
<br />
: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.<br />
<br />
: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.<br />
<br />
----<br />
<br />
== Help needed with Howto:Edit a livery ==<br />
See [[Howto talk:Edit a livery#Help needed with xml etc.]] —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 21:12, 4 March 2013 (UTC)<br />
<br />
== Semantic MediaWiki ==<br />
<br />
Just a possible suggestion for the FlightGear wiki. It's called Semantic MediaWiki, it's a fairly easy to install extension that will bring more semantic data to the wiki. For example, you could organize Aircraft with more than just categories. You could define an Aircraft term and any time it's tagged or referenced to it's term you begin gettin stats you don't get with normal mediawiki. I use it on a private wiki to where I am constantly referencing a question term in the content. Something like [Question:What is Sematic MediaWiki?]. What I end up with are stats that tell me that I've asked 642 questions etc. It's just a way to bring more meaning to the wiki. If you understand what Semantic Web is you should understand the value this could bring.<br />
<br />
Anyway, here is a link: http://en.wikipedia.org/wiki/Semantic_MediaWiki --[[User:Kaleblex|Kaleblex]] 16:32, 29 March 2013 (UTC)<br />
<br />
== Keyboard shortcut conventions ==<br />
To better illustrate keyboard shortcuts and key combinations, and to make them easier to find on a page, I have recently created the {{tl|key press}} template. I am worrying about a potential problem related to conventions regarding how keyboard shortcuts are written.<br />
<br />
In the FlightGear community the use of the shift key has often just been signified by using a upper-case letter and otherwise using lower-case letters. My template was meant to mimic key caps, so I had the intention to only use upper-case letters and signify the use of the shift key by showing it instead, in essence '''g''' and '''G''' would become {{key press|G}} and {{key press|Shift|G}}, which in my eyes was the only convention out there. However, only hours had passed since I implemented it in all places i could find before some of them was changed to {{key press|g}} and {{key press|Shift|G}}. That considered, it might be better to only use lower-case letters as i see less risk of confusion because I am sure someone will write {{key press|G}} instead of {{key press|Shift|G}}.<br />
<br />
Finally, I am a strong believer in that consistency will make things intuitive, so my question is: What convention should we insist on in documentation, always use and persistently change to (preferably not 1.):<br />
# {{key press|g}}, {{key press|Shift|G}}, {{key press|Ctrl|g}} and {{key press|Alt|g}}<br />
# {{key press|g}}, {{key press|Shift|g}}, {{key press|Ctrl|g}} and {{key press|Alt|g}}<br />
# {{key press|G}}, {{key press|Shift|G}}, {{key press|Ctrl|G}} and {{key press|Alt|G}}<br />
<br />
I am leaning towards 2, but could probably be persuaded given good enough arguments.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:53, 29 April 2013 (UTC)<br />
<br />
== Default search should include the Howto namespace ==<br />
Default search namespaces should include both the article namespace and the Howto namespace. Currently the Howto namespace (in essence all articles beginning with the namespace prefix ''Howto:'') is slightly hidden unless you know what to look for, and even then you forget that at times.<br />
<br />
For registered users this is easily fixed by setting the [http://wiki.flightgear.org/Special:Preferences#mw-prefsection-searchoptions search options on the the preferences page] to include the Howto namespace in searches. For unregistered users this is yet another reason they sometimes wont find what they are looking for (unless the Howto page is linked from another page).<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:43, 16 May 2013 (UTC)<br />
<br />
: Ouch, that's pretty stupid. I've asked Simon to fix this. Please remind us if it isn't fixed by the end of the week.<br />
: [[User:Gijs|Gijs]] 12:08, 20 May 2013 (UTC)<br />
<br />
:: Not fixed yet, so here is that gentle reminder. ;-)<br />
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:38, 27 May 2013 (UTC)<br />
<br />
: Done! Sorry for the delay.<br />
: [[User:Gijs|Gijs]] 12:44, 2 July 2013 (UTC)<br />
<br />
:: Sorry Gijs, but try that while not logged in. It still does not worked for visitors not logged in.<br />
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:23, 3 July 2013 (UTC)<br />
<br />
::: Oops, fixed now ;-)<br />
::: [[User:Gijs|Gijs]] 14:21, 21 July 2013 (UTC)<br />
<br />
:::: Confirmed working today. Thanks Gijs (and Simon?)!<br />
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:40, 21 July 2013 (UTC)<br />
<br />
::::: <strike> Hmm, I don't think searching '''only''' in the HowTo namespace when not logged in qualifies as working </strike><br />
::::: <strike> [[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 18:50, 28 July 2013 (UTC)</strike><br />
::::: Working now, thanks Gijs?<br />
::::: [[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 16:12, 31 July 2013 (UTC)<br />
<br />
== iPod compatibility? ==<br />
I use my iPod a LOT and have noticed since registering that the box for editing is rather incompatible with the iPod. It's slow, heavy, and inefficient. Now the one over at the forums works better and crashes Chrome a lot less -- is there a way to improve this or copy it from there? I'm not a web developer, so I don't know, but it would ''really'' help and would increase the number of my contributions. Thanks!<br />
<br />
[[User:Philosopher|Philosopher]] 21:42, 19 May 2013 (UTC)<br />
<br />
: According to wikimedia, there's a "mobile theme" available which also provides IPod support:[http://en.wikipedia.org/wiki/Help:Mobile_access#Official_mobile_access]. To check if the theme works for you, go to http://en.m.wikipedia.org/ Probably something for Gijs to look into. --[[User:Hooray|Hooray]] 00:34, 20 May 2013 (UTC)<br />
<br />
:: Lol, that's the same but worse: when you go to preview changes it take you to the current site in the mobile theme! (instead of a previews either the desktop or mobile themes – it doesn't have a mobile theme for history or edits.) Anyways, just having a different text box would be O.K., no need for full-blown theming. [[User:Philosopher|Philosopher]] 01:28, 20 May 2013 (UTC)<br />
<br />
: The MediaWiki people are working on built-in mobile support. I prefer to wait for that, so we'll get it in our normal updates.<br />
: [[User:Gijs|Gijs]] 09:59, 20 May 2013 (UTC)<br />
<br />
== FlightGear Newsletter ==<br />
<br />
As of now it seems that the list of latest articles, using <nowiki><DynamicArticleList></nowiki> tags is broken and none of the list are rendered. Which brings me to the next topic: I was going to comment that on the talk page, but as of now the talk page is sort of a template for the next newsletter.<br />
<br />
Maybe it would be better to have the next newsletter as a pure template which could be substituted, like <nowiki>{{subst:</nowiki>''name of template''<nowiki>}}</nowiki>, or maybe only needing a mouse click to get started like:<br />
<nowiki>[{{fullurl:FlightGear Newsletter {{CURRENTMONTHNAME}} {{CURRENTYEAR}}|action=edit&preload=Talk:Next_newsletter}} Create next newsletter]</nowiki>.<br />
The caveat of the last solution is that there must only be the text to be included on that page, so it would have to be on a subpage to the template page which in itself would only have the documentation.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:30, 23 July 2013 (UTC)<br />
<br />
: The dyanmiclist issue is caused by our update of MediaWiki yesterday. Takes a while to update and re-configure all the extensions accordingly.<br />
: I don't understand your Newsletter template suggestion(s) though. There are various places that link to the next newsletter, so adding a creation link to a template on one of them isn't going to do much. I would say it isn't worth the hassle, but feel free to code something :-) To prevent stuff from being included in a template, use <code><nowiki><noinclude></nowiki></code>.<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:37, 23 July 2013 (UTC)<br />
<br />
:: If you can come up with a flexible template that helps us to implement the newsletter more easily, I will surely help adopt it - my wikimedia template skills are just pretty basic, as Gijs can confirm ... so I haven't bothered to look into it, but even just having an automated way to lock newsletters at the end of the month and create new ones automatically would be helpful.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:01, 23 July 2013 (UTC)<br />
<br />
== Unification and improvement of maintenance templates ==<br />
<br />
I feel that there is a bit of a need to unify the [[:Category:Maintenance templates|maintenance templates]]. I am thinking in the direction of:<br />
* Having a main template for their layout, a few classes of them depending on their importance. For example is speedy deletion, {{tl|Delete-sp}}, more important than work in progress, {{tl|WIP}}.<br />
* All of them should have parameter for time stamping, probably mith month and year, and be added to a dated category, like [[:Category:Articles considered for deletion as of February 2013]]. Knowing that something has been amiss for a long time is probably a good incitement.<br />
* All of them should have a parameter with a link to a talk page if needed, since there might be sometime before someone else will try fix the reason for the template. Also what is obvious to one may be anything but obvious for someone else.<br />
* Named parameters should only be used when needed (though using named parameters would for example probably be very helpful when using a bot for time stamping). This to speed up filling in parameters.<br />
* There should be a copy-pastble example with as much as possible already filled in in the templates documentation.<br />
* I think it could be nice to have a slight bit of humour and self distance, in that the icons and texts could be a bit into flying terms, though not more than that someone not into that would understand what they are about.<br />
<br />
In some cases there seem to be some need for a style guide. What is for example "the wiki's quality standards", as mentioned in {{tl|cleanup}}? However, that is another discussion altogether.<br />
<br />
Comments, questions and suggestions are welcome!<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:27, 31 October 2013 (UTC)<br />
<br />
<br />
:Some initial thoughts, mostly copied from above, can for now be found at [[User:Johan G/Unification and improvement of maintenance templates]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:30, 1 November 2013 (UTC)<br />
<br />
:A list of the very most of the message box templates, which include many of the maintenance templates have been put together in [[Help:List of messagebox templates]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:11, 6 November 2013 (UTC)<br />
<br />
== Moving around contents in the help articles ==<br />
<br />
I am considering moving around some stuff in some of the help articles. More or less moving most of the current Help:Your first article] to Help:Tutorial and the current Help:Tutorial to Help:Editing.<br />
<br />
First off, the current Help:Editing is a two-edit stub. The current [http://wiki.flightgear.org/index.php?title=Help:Tutorial&oldid=42573 Help:Tutorial] though is all about editing, so I would consider it quite ok to delete the current Help:Editing and move Help:Tutorial there. That would leave Help:Tutorial as an empty redirect page which could the be rewritten into a tutorial about what a wiki is and how to efficiently use and contribute to it. The tutorial should probably also mention what this wiki is about, which just so happens is what [http://wiki.flightgear.org/index.php?title=Help:Your_first_article&oldid=64321 Help:Your first article] is all about (it actually only mentions how to create a new article in a few sentences at the end, and doesn't touch things like selecting a good title or wiki editing at all).<br />
<br />
After all this Help:Tutorial would be a tutorial on how to use the wiki's different features such as page histories, discussion pages, categories etc, Help:Editing would be about, well, editing, and Help:Your first article would be about what to write about, what to think of when choosing an article name, the basics of editing, and the advantages of categorisation.<br />
<br />
With all that done I think the new users that have been lurking a bit would get a slightly better start as well as give us a better starting point to direct the other ones to.<br />
<br />
Any further thoughts or ideas is welcome.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:58, 23 November 2013 (UTC)<br />
<br />
: I have now deleted the old Help:Edit and moved Help:Tutorial over there. I have also started rewriting it.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 23:20, 28 November 2013 (UTC)<br />
<br />
: The rewrite of the new [http://wiki.flightgear.org/index.php?title=Help:Editing&oldid=64926 Help:Edit] (former Help:Tutorial) is now nearly complete. What is left to do is moving some of the text to more fitting articles, probably the new Help:Tutorial, and probably some rephrasing here and there and fixing a few typos.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 02:46, 30 November 2013 (UTC)<br />
<br />
:: I have now moved Help:Editing to the more common [[Help:Formatting]], moved the former [http://wiki.flightgear.org/index.php?title=Help:Your_first_article&oldid=64321 Help:Your first article] to [[Help:Tutorial]], and made a entirely new [[Help:Your first article]] which is more to the point.<br />
:: What is left is rewriting the new Help:Tutorial to be more general about the wiki, and find a way to make all the potential translators aware of the big changes I have done (which probably have made for a ''big'' mess).<br />
:: The next time I do something this big I will probably announce it in the [[FlightGear Newsletter|Newsletter]] as well as here to get a bit more response and opinions (this page is still way to obscure).<br />
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:54, 8 December 2013 (UTC)<br />
<br />
== Style guide ==<br />
I have begun work on a [[Help:Style guide]] and welcomes opinions, thoughts and suggestions on its [[Help talk:Style guide|discussion page]] and additions on the page itself.<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 01:15, 9 December 2013 (UTC)<br />
<br />
== Automating Template:Git status ==<br />
<br />
{{cquote|@Johan_G: it would be AWESOME if you could come up with some template magic to automate the whole GitStatus stuff :-)|Hooray}}<br />
I got [http://wiki.flightgear.org/index.php?title=Template:GitStatus:frozen&curid=7722&diff=65887&oldid=65866 sort of a request] from Hooray on automating {{tl|GitStatus}}. I believe this can be done with parser functions and "magic words" (yes, they are actually called that).<br />
<br />
Judging from the [[release plan]] there are some fixed dates when the status changes (Open from Jan/Jul 17th, frozen from Dec/Jun 17th and closed for a few hours around 12:00 UTC Jan/Jul 17th).<br />
<br />
My question is how long it should be shown as being in the closed status? Could I arbitrarily set it to that status for 12:00 UTC &plusmn; 2 hours or even for the entire day (which would be ''much'' easier)?<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:11, 22 December 2013 (UTC)<br />
<br />
: sure, why not - let's keep it simple for now. Previously, the template hasn't been updated in months - so being off by a day (or even a week) would still be an improvement - if someone doesn't like it, it can still be improved later on. BTW: thanks for looking into this !--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 09:03, 22 December 2013 (UTC)<br />
<br />
:: Why would we need to update a status template when the status doesn't change? Remember that there's 5 months between frozen and the next frozen. {{tl|GitStatus:frozen}} isn't supposed to show all states, it only shows the frozen state and should thus only be updated once every 6 months...<br />
:: Anyhow, automating it is easy-peasy. {{done}} The closed state needs to be set by hand, because it doesn't have a fixed time frame.<br />
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 14:05, 22 December 2013 (UTC)<br />
<br />
::: right, that's better now - but as can be seen in the history of the template, this hadn't been updated in months - of course, these things are fairly trivial, but we only need to look at our duties here to see that "automation is key" - otherwise, we would still need to document everything that cannot be automated and work through all open items - personally, I would even wan to lock the newsletter automatically at the end of each month, after 3-7 days, and copy the new template to current month if it isn't there already. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:32, 22 December 2013 (UTC)<br />
<br />
:::: You keep saying that "it hadn't been updated in months", but why/when did it need an update? The status of the repositories has been "open" ever since July 17, so I didn't expect any updates until December 17, apart from my edit on September 22 to bump the next version number.<br />
:::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:54, 22 December 2013 (UTC)<br />
<br />
<br />
== MediaWiki updated to 1.22.0 ==<br />
I've updated MediaWiki to the latest stable, 1.22.0 today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.22<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:00, 26 December 2013 (UTC)<br />
<br />
=== Found bugs ===<br />
* Clicking the category link at the bottom of some articles will give a fatal error. For clicking the [[:Category:FlightGear]] at [[FlightGear]] will give the error message: ''Fatal error: Class 'Services_JSON' not found in /home/wiki/wiki/extensions/CategoryTree/CategoryTreeFunctions.php on line 224''.<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:44, 28 December 2013 (UTC)<br />
:: The CategoryTree extension relies on a function that was removed as of 1.22.0, so the extensions needs some fixing. I've disabled it for now.<br />
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)<br />
<br />
* Also, the mobile theme results in an error: ''Fatal error: Call to undefined method MobileFormatter::setHtmlMode() in /home/wiki/wiki/extensions/MobileFrontend/includes/MobileFormatter.php on line 62'' (works fine after selecting desktop mode).<br />
: Thanks,<br />
: [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 03:59, 28 December 2013 (UTC)<br />
:: I forgot to update the mobile extension. Works again ;-)<br />
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)<br />
<br />
== Got any ideas for a better name for this page? ==<br />
As this is for this page in particular, see the [[FlightGear wiki talk:Village pump#Any ideas for a better name|talk page]].<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:44, 5 March 2014 (UTC)<br />
<br />
== Template for announcement of changes and new features ==<br />
<br />
From a forum PM from Hooray (posted here with his permission):<br />
<br />
<div style="background: #fafaf0; padding: 1em;"><br />
hi, whenever we announce a new feature, we typically need to do this in three places:<br />
<br />
* newsletter<br />
* changelog<br />
* the docs (corresponding wiki articles)<br />
<br />
so far, we have always copied & pasted things, I would prefer to have a single template for this instead, something like<br />
{{tlx|Announce|version|description}}<br />
<br />
This could add announcements to each release cycle (i.e. 3.2 currently), and we could maybe automatically add things to the newsletter and the release changelog.<br />
<br />
Like I said, I would like to avoid redundant efforts, i.e. less copy & paste<br />
<br />
Do you have any ideas on how to implement this using existing wiki means ?<br />
<br />
Ideally, we would create a new announcement, like for example "canvas mouse button support", and could then use this announcement in all 3 places by calling the corresponding template.<br />
<br />
<br />
Thanks<br />
</div><br />
My take is that to use a separate template for each new feature is not a good idea, but if I understand him correctly his intention is to gather up each months new features in one template.<br />
<br />
Any thoughts on this?<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:14, 5 March 2014 (UTC)<br />
<br />
== Very dispersed Boeing 777 articles! ==<br />
<br />
Hi, I got interested in Flightgear and was taking a look at the Boeing 777 articles and noticed that it was incredibly spread out. <br />
<br />
Each aircraft has it's own page with information to varying degrees of completeness. Having a look at the A330 articles, they are much more 'aligned' and it's a lot easier to find stuff. Maybe this could be something that could be done with the Boeing. Since both seem to be very similar, I'm thinking that there could be a common page on help and tutorials respectively, with the individual type pages catering to unique information. I started on some stuff but pretty quickly figured out it was a better idea to check here first :)<br />
<br />
--[[User:Manfred|Manfred]] ([[User talk:Manfred|talk]]) 11:55, 25 March 2014 (UTC)<br />
<br />
: Doing a simple search for pages containing "777" (see [http://wiki.flightgear.org/index.php?search=777&title=Special%3ASearch&fulltext=1 this link]) I quickly see what you mean.<br />
<br />
: I assume that the different versions may have different authors and thus probably are slightly different from each other when it comes to handling and completeness. It might be a good idea to start by going through each of the help pages and tutorials (preferably while playing with the different aircraft at the same time), as well as having a look at help dialogues and any readmes in the aircraft packages.<br />
<br />
: Making a common page, while highlighting differences between the different versions, could probably help other users a lot and may perhaps be a help for aircraft developers to use features from more complete versions to improve the other ones as well as help motivate harmonizing handling like for example key bindings.<br />
<br />
: If I understand your intention I can not see why anyone would do anything but trying to give you helpful hints, after all this is a wiki. :-)<br />
<br />
: One hint for starters is to begin working on a page as a subpage to your user page, like for example [[User:Manfred/Boeing 777 Autopilot]] (I just moved it) and then moving it to the article namespace when you feel it has reached the level where you are comfortable with it (though this is not by any means necessary, it's just that I like doing so myself).<br />
<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 28 March 2014 (UTC)<br />
<br />
: I am interested to help, this page could be a model of what we could offer : [http://wiki.flightgear.org/Boeing_787-8_Dreamliner 777-8 Dreamliner]<br />
: -- [[User:F-JYL|F-JYL]] 21 April 2014 09:32</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=User:F-JYL&diff=69602User:F-JYL2014-04-10T05:19:44Z<p>F-JYL: </p>
<hr />
<div>http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
<br />
A voir :<br />
<br />
* Queenstown, New Zealand<br />
* EPWR-Wrocław-Strachowice<br />
* LKPR Prague<br />
* SKRG Jose Maria Cordoba Intl, Airport, located in the Rionegro, Colombia<br />
* KAKR, KCAK, 29G (Portage Co.), 1G5 (Medina Muni), and 1G3 (Kent State University).<br />
* LIRP<br />
*SBCX<br />
*SBPA<br />
* LIPY</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=User:F-JYL&diff=69546User:F-JYL2014-04-07T18:37:57Z<p>F-JYL: </p>
<hr />
<div>http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
<br />
A voir :<br />
<br />
* Queenstown, New Zealand<br />
* EPWR-Wrocław-Strachowice<br />
* LKPR Prague<br />
* SKRG Jose Maria Cordoba Intl, Airport, located in the Rionegro, Colombia<br />
* KAKR, KCAK, 29G (Portage Co.), 1G5 (Medina Muni), and 1G3 (Kent State University).<br />
* LIRP<br />
*SBCX<br />
*SBPA</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=User:F-JYL&diff=69424User:F-JYL2014-03-31T16:32:58Z<p>F-JYL: </p>
<hr />
<div>http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
<br />
A voir :<br />
<br />
* Queenstown, New Zealand<br />
* EPWR-Wrocław-Strachowice<br />
* LKPR Prague<br />
* SKRG Jose Maria Cordoba Intl, Airport, located in the Rionegro, Colombia<br />
* KAKR, KCAK, 29G (Portage Co.), 1G5 (Medina Muni), and 1G3 (Kent State University).<br />
* LIRP</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=User:F-JYL&diff=68639User:F-JYL2014-03-09T21:51:12Z<p>F-JYL: </p>
<hr />
<div>http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes<br />
<br />
A voir :<br />
<br />
- Queenstown, New Zealand<br />
- EPWR-Wrocław-Strachowice<br />
- Prague</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Boeing_777&diff=67191Boeing 7772014-02-03T20:58:09Z<p>F-JYL: Links to 777 documentation</p>
<hr />
<div>[[File:777-200.jpg|thumb|270px|[[Boeing 777-200]] in British Airways livery]]<br />
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]<br />
<br />
The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.<br />
<br />
As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350|A350 XWB]], which is currently under development. <br />
<br />
You can see a guide on how to fly this plane for Flightgear 2.0 at [[Boeing 777 Tutorial: Version 2.0.]].<br />
<br />
== Variants ==<br />
* [[Boeing 777-200]]<br />
* [[Boeing 777-200LR]]<br />
* [[Boeing 777-300]]<br />
* [[Boeing 777-F]]<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ] (not too relevant, X-Plane only support, last updated in 2007, AND: written in LISP!!!)<br />
* [http://www.theairlinepilots.com/forum/viewforum.php?f=32 Airline Pilots 777 forum] Detailled info on procedures, manuals and documents<br />
* [http://www.smartcockpit.com/plane/BOEING/B777.html Smart cockpît Boeing 777] manuals and procedures<br />
<br />
[[fr:Boeing 777]]<br />
{{Boeing}}</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=User:F-JYL&diff=66723User:F-JYL2014-01-26T17:16:30Z<p>F-JYL: Created page with "http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes"</p>
<hr />
<div>http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Canvas_Nasal_API&diff=66168Canvas Nasal API2014-01-05T17:02:54Z<p>F-JYL: Show how to draw arcs using canvas</p>
<hr />
<div>{{Template:Canvas Navigation}}<br />
<br />
Canvas consist of a class with various nestable classes (elements).<br />
<br />
See inside the 2.10 API [https://gitorious.org/fg/fgdata/blobs/release/2.10.0/Nasal/canvas/api.nas here].<br />
<br />
== Canvas ==<br />
For constructor see: [[Howto:Add_a_2D_canvas_instrument_to_your_aircraft#Initialize_a_Canvas|Initialize a Canvas]]<br />
=== addPlacement ===<br />
See: [[Howto:Add_a_2D_canvas_instrument_to_your_aircraft#Place_it_somewhere_on_your_aircraft|Place a Canvas]]<br />
=== setColorBackground ===<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Fills the background of the entire canvas with the supplied color.<br />
=== createGroup ===<br />
'''Parameters:''' ()<br />
<br />
'''Parameters:''' (name)<br />
<br />
'''Returns:''' Group<br />
<br />
Create a new group under this Canvas. Supplying name is optional.<br />
=== getPath ===<br />
'''Parameters:''' ()<br />
<br />
?<br />
=== del ===<br />
'''Parameters:''' ()<br />
<br />
Deletes this Canvas.<br />
=== wrapCanvas ===<br />
'''Parameters:''' ()<br />
<br />
?<br />
=== get ===<br />
'''Parameters:''' (name)<br />
<br />
'''Returns:''' Canvas<br />
<br />
Returns the canvas with the specified name.<br />
=== parsesvg ===<br />
'''Parameters:''' (group, file)<br />
<br />
'''Parameters:''' (group, file, font-mapper)<br />
<br />
See: [[Howto:Use_SVG_inside_a_Canvas|SVG inside a Canvas]]<br />
== Element == <br />
Note that in each element there are 2 transformation matrices. The first will be applied first, then the second.<br />
<br />
=== set ===<br />
'''Parameters:''' (key, value)<br />
<br />
''Key = "z-index":''<br />
<br />
Default= 0<br />
<br />
Value indicates the explicit Z sort order, highest on top. If this is not set, elements that are added later gets drawn on top.<br />
<br />
FG 2.10.0.3: Elements added after z-index has been set will overrule it. (fix is in GIT)<br />
<br />
=== update ===<br />
'''Parameters:''' ()<br />
<br />
Normally an element gets updated in the next frame. Calling this will make it update in the current frame.<br />
Note that visibility methods do get updated in the current frame.<br />
=== getVisible ===<br />
'''Parameters:''' ()<br />
<br />
'''Returns:''' visible<br />
<br />
Returns 0 if not visible, 1 if visible.<br />
=== setVisible ===<br />
'''Parameters:''' ()<br />
<br />
'''Parameters:''' (visible)<br />
<br />
Sets if this element should be visible. 0 sets it not visible, 1 visible. No parameters sets it visible.<br />
=== show ===<br />
'''Parameters:''' ()<br />
<br />
Sets the element visible.<br />
=== hide ===<br />
'''Parameters:''' ()<br />
<br />
Sets the element not visible.<br />
=== toggleVisibility ===<br />
'''Parameters:''' ()<br />
<br />
Toggles if element should be visible.<br />
=== setGeoPosition ===<br />
'''Parameters:''' (lat, lon)<br />
<br />
Sets the geographic coordinates for a map element. Parent element must be of type "map".<br />
<br />
'''Example:''' setGeoPosition(37.615223, -122.389978)<br />
<br />
Places element at [[San Francisco International Airport]].<br />
<br />
=== createTransform ===<br />
createTransform creates a new matrix on top of the existing matrix stack. A while ago I've added an example for a HUD built using the Canvas to the wiki: http://wiki.flightgear.org/Canvas_HUD<br />
It doesn't use SVG but manually creates everything instead. As loading an SVG should basically do the same than handcrafting icons there shouldn't be much of a difference.<br />
<br />
'''Parameters:''' ()<br />
<br />
'''Parameters:''' ([a, b, c, d, e, f])<br />
<br />
'''Return:''' The new (second) transform <br />
<br />
Creates a new (second) transformation matrix for this element. No parameters will create a default identity matrix transform. Otherwise supply a 6 element vector for the matrix:<br />
<br />
{| class="wikitable"<br />
|-<br />
| a || b || c<br />
|-<br />
| d || e || f <br />
|-<br />
| 0 || 0 || 1 <br />
|}<br />
<br />
You should probably change the order of creating the transforms for pitch and roll as normally one would rotate first and then move according to roll and then move according to pitch up and down. Keep in mind that rotations always happens around the origin of the local coordinate frame of the object being rotated. For a rotation around another point you would need to move the object first until the center coincides with the local origin then rotate and afterwards move back. Instead of applying three transformations there exists a shortcut to pass the center of rotation as second argument to setRotation.<br />
<br />
To further shorten the code an especially to allow rotating objects imported from SVG there exists setRotation also for canvas Elements (not only Transformation) and additionally setCenter which instead of passing the center as an argument sets the center which is being used while calling setRotation on this element. setCenter only affects setRotation of this not object but not for any matrix added with createTransform. If you set the center of rotation in Inkscape (switch to rotate mode and drag the cross to the center of rotation) it is automatically loaded with setCenter so you just need to call setRotation and automatically get a rotation around the correct center.<br />
<br />
You don't need to care about tf[0] being reserved as it only reserves the index 0 and doesn't affect anything if not used. createTransform creates a new matrix with the next unused index starting at 1 (0 is reserved). If you later call setRotation directly on an element a new Transform will be created but this time using tf[0] to ensure it is applied before all other matrices and therefore rotating the object around its own center before being moved around.<br />
<br />
For the HUD I'd set the rotation center correctly inside Inkscape and later on just call ladder.setRotation to rotate for changes in the roll angle. Afterwards create a Transform and use setTranslate for changes in pitch angle.<br />
<br />
=== setTranslation ===<br />
'''Parameters:''' (x, y)<br />
<br />
Translates the element. The translation is set on the second transform.<br />
=== setRotation ===<br />
'''Parameters:''' (x, y)<br />
<br />
Rotates the element around the center. The rotation is set on the first transform.<br />
<br />
setRotation really just combines a rotation with two translations -> translate(-center[0], -center[1]) * rotate * translate(center[0], center[1])<br />
<br />
You can also have a look in the property browser and check the bounding box (/canvas/by-index/texture[i]/[group[j]+]/path[j]/bounding-box) and use its coordinates to determine the correct center of rotation.<br />
<br />
=== setScale ===<br />
'''Parameters:''' (x, y)<br />
<br />
Scales the element. The scale is set on the second transform.<br />
=== getScale ===<br />
'''Parameters:''' ()<br />
<br />
'''Return:''' 2 element vector [x,y]<br />
<br />
Returns the scale of this element.<br />
=== setColorFill ===<br />
'''Parameters:''' (r, g, b)<br />
<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Sets the color/alpha to be used as fill value. If you do not want the element to be filled, do not call this method.<br />
=== getBoundingBox ===<br />
'''Parameters:''' ()<br />
<br />
'''Returns:''' [minX, minY, maxX, maxY]<br />
<br />
Returns the bounds of the element.<br />
=== updateCenter ===<br />
'''Parameters:''' ()<br />
<br />
Sets the center to be the center of the boundingbox in relation to the elements position in its parent.<br />
=== setCenter ===<br />
'''Parameters:''' (x, y)<br />
<br />
Sets the center of the element that is used for rotation.<br />
=== getCenter ===<br />
'''Parameters:''' ()<br />
<br />
Gets the center of the element.<br />
<br />
== Group ==<br />
Inherits from Element.<br />
=== set ===<br />
'''Parameters:''' (key, value)<br />
<br />
''key = "clip"''<br />
<br />
Makes a clipping bounds for the group, only what is inside the clipping bounds will be shown.<br />
<br />
It uses same coordinate format as [http://www.w3.org/TR/CSS21/visufx.html#clipping Clipping]<br />
<br />
'''Example:''' my_grp.set("clip", "rect(62px, 587px, 262px, 437px)"); # top,right,bottom,left<br />
<br />
''key = "font"''<br />
<br />
Sets the default font.<br />
<br />
'''Example:''' my_group.set("font", "LiberationFonts/LiberationMono-Regular.ttf");<br />
<br />
''key = "stroke"''<br />
<br />
?<br />
<br />
''key = "fill"''<br />
<br />
?<br />
<br />
=== setDouble ===<br />
'''Parameters:''' (key, value)<br />
<br />
''key = "character-aspect-ration"''<br />
<br />
?<br />
<br />
''key = "character-size"''<br />
<br />
?<br />
<br />
=== createChild ===<br />
'''Parameters:''' (type)<br />
<br />
'''Parameters:''' (type, name)<br />
<br />
'''Returns:''' Element<br />
<br />
Creates a child element under this Group. Name can be supplied. Type can be "text", "group", "path", "image", "map".<br />
Return an Element of the particular type specified.<br />
=== createChildren ===<br />
'''Parameters:''' (type, count)<br />
<br />
'''Returns:''' [Element]<br />
<br />
Creates a number of child elements under this Group. Return a vector of Elements of the particular type specified.<br />
=== getChildren ===<br />
'''Parameters:''' ()<br />
<br />
'''Returns:''' [Element]<br />
<br />
Returns all the child elements of this group.<br />
=== getElementById ===<br />
'''Parameters:''' (name)<br />
<br />
'''Returns:''' Element<br />
<br />
Returns the first found child element with the specified name.<br />
=== removeAllChildren ===<br />
'''Parameters:''' ()<br />
<br />
Removes all the child elements from this group.<br />
== Text ==<br />
Inherits from Element.<br />
<br />
=== setText ===<br />
'''Parameters:''' (text)<br />
<br />
Sets the text to be displayed.<br />
=== setAlignment ===<br />
'''Parameters:''' (alignment)<br />
<br />
Sets how the text should be aligned with its position.<br />
<br />
'''Examples of alignment:''' "left-top", "center-center", "right-bottom", "left-baseline", "center-bottom-baseline"<br />
<br />
Possible bug: At least 1 person (me) have trouble with center- and right- alignments when not using a monospaced font. [http://code.google.com/p/flightgear-bugs/issues/detail?id=1054 Bug #1054]<br />
<br />
=== setFontSize ===<br />
'''Parameters:''' (size, aspectRatio)<br />
<br />
Sets the size and aspectRatio of the font. AspectRatio is the Ratio between character height and width. Default aspectRatio is 1.<br />
=== setFont ===<br />
'''Parameters:''' (fontName)<br />
<br />
Sets the font to be used. See $FG_DATA/Fonts for list of fonts.<br />
=== setDrawMode ===<br />
'''Parameters:''' (mode)<br />
<br />
Sets the drawing mode. You can use the values below and add those you need.<br />
<br />
'''Text.TEXT:''' Draws the text<br />
<br />
'''Text.BOUNDINGBOX:''' Draws the boundingbox<br />
<br />
'''Text.FILLEDBOUNDINGBOX:''' Draws the filled boundingbox<br />
<br />
'''Text.ALIGNMENT:''' Draws a cross where the element position is<br />
<br />
'''Example:''' my_text.setDrawMode(Text.TEXT + Text.BOUNDINGBOX);<br />
=== setPadding ===<br />
?<br />
=== setMaxWidth ===<br />
?<br />
=== setColor ===<br />
'''Parameters:''' (r, g, b)<br />
<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Sets the color the text should be drawn in.<br />
=== setColorFill ===<br />
'''Parameters:''' (r, g, b)<br />
<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Sets the color the text background should be drawn in.<br />
== Path ==<br />
Inherits from Element.<br />
<br />
A path is similar to drawing with a pen on paper. The move and moveTo methods represent lifting the pen from the paper and moving to a new position. The drawing methods like lineTo would then be seen as starting from the current position of the pen. Therefore offcause the order the methods is called in, is important.<br />
=== moveTo ===<br />
'''Parameters:''' (x, y)<br />
<br />
Moves the position to an new absolute position.<br />
=== move ===<br />
'''Parameters:''' (x, y)<br />
<br />
Moves the position to an new relative position from the current.<br />
=== reset ===<br />
'''Parameters:''' ()<br />
<br />
Remove all existing path data.<br />
=== lineTo ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws a line to specified position.<br />
=== line ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws a line to specified relative position.<br />
=== horizTo ===<br />
'''Parameters:''' (x)<br />
<br />
Draws a horizontal line to specified position.<br />
=== horiz ===<br />
'''Parameters:''' (x)<br />
<br />
Draws a horizontal line to specified relative position.<br />
=== vertTo ===<br />
'''Parameters:''' (y)<br />
<br />
Draws a vertical line to specified position.<br />
=== vert ===<br />
'''Parameters:''' (y)<br />
<br />
Draws a vertical line to specified relative position.<br />
=== quadTo ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws quadratic Bézier curve.<br />
=== quad ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws quadratic Bézier curve. Relative coordinates.<br />
=== cubicTo ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws cubic Bézier curve.<br />
=== cubic ===<br />
'''Parameters:''' (x, y)<br />
<br />
Draws cubic Bézier curve. Relative coordinates.<br />
=== scubicTo ===<br />
=== scubic ===<br />
=== arcSmallCCWTo ===<br />
=== arcSmallCCW ===<br />
=== arcSmallCWTo ===<br />
=== arcSmallCW ===<br />
'''Parameters:''' (xRadius, yRadius,0,xEnd,yEnd)<br />
<br />
Draws an arc with the specified radii, up to the specified end point. The end point is relative to the starting point.<br />
<br />
To draw half a circle with radius 20 around the origin:<br />
.moveTo(-20,0)<br />
.arcSmallCW(20,20,0,40,0);<br />
<br />
To draw a circle with radius 20 around the origin:<br />
.moveTo(-20,0)<br />
.arcSmallCW(20,20,0,40,0)<br />
.arcSmallCW(20,20,0,-40,0);<br />
<br />
=== arcLargeCCWTo ===<br />
=== arcLargeCCW ===<br />
=== arcLargeCWTo ===<br />
=== arcLargeCW ===<br />
<br />
Drawing arcs examples : <br />
[[File:Canvas arc.png|thumb|Canvas arc draw examples]]<br />
<syntaxhighlight lang="nasal"><br />
var fpv = group.createChild("group", "FPV");<br />
<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,255,1)")<br />
.moveTo(100, 100).arcSmallCCW(50, 50, 0, 50, 50);<br />
fpv.createChild("path").setStrokeLineWidth(4) .set("stroke", "rgba(255,0,255,1)")<br />
.moveTo(300, 100).arcSmallCCW(50, 50, 0, 100, 0);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,255,1)")<br />
.moveTo(500, 100).arcSmallCCW(50, 50, 0, 50, -50);<br />
<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(55,0,255,1)")<br />
.moveTo(100, 300).arcSmallCW(50, 50, 0, 50, 50);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(55,0,255,1)")<br />
.moveTo(300, 300).arcSmallCW(50, 50, 0, 100, 0);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(55,0,255,1)")<br />
.moveTo(500, 300).arcSmallCW(50, 50, 0, 50, -50);<br />
<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(100, 500).arcLargeCCW(50, 50, 0, 50, 50);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(300, 500).arcLargeCCW(50, 50, 0, 100, 0);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(500, 500).arcLargeCCW(50, 50, 0, 50, -50);<br />
<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(100, 500).arcLargeCCW(50, 50, 0, 50, 50);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(300, 500).arcLargeCCW(50, 50, 0, 100, 0);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(500, 500).arcLargeCCW(50, 50, 0, 50, -50);<br />
<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(100, 700).arcLargeCW(50, 50, 0, 50, 50);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,55,1)")<br />
.moveTo(300, 700).arcLargeCW(50, 50, 0, 100, 0);<br />
fpv.createChild("path").setStrokeLineWidth(4).set("stroke", "rgba(255,0,5<br />
</syntaxhighlight><br />
<br />
=== close ===<br />
=== setColor ===<br />
'''Parameters:''' (r, g, b)<br />
<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Sets the color of the drawn path<br />
=== setColorFill ===<br />
'''Parameters:''' (r, g, b)<br />
<br />
'''Parameters:''' (r, g, b, a)<br />
<br />
Calling this will make the path get filled in the specified color. For example if you draw a 'V' and fill it, the fill area will be a triangle inside the 'V'.<br />
=== setStrokeLineWidth ===<br />
'''Parameters:''' (width)<br />
<br />
The width of the path.<br />
=== setStrokeLineCap ===<br />
'''Parameters:''' (type)<br />
<br />
Caps the path. Type can be "butt", "round" or "square".<br />
=== setStrokeDashArray ===<br />
'''Parameters:''' (pattern)<br />
<br />
Make dashed path. Pattern is a vector of alternating dash and gap lengths. ? horizontal, or misunderstood the vector ?<br />
<br />
'''Example:''' my_path.setStrokeDashArray([10, 20, 10, 20, 10]);<br />
<br />
=== setData ===<br />
=== setDataGeo ===<br />
=== addSegment ===<br />
== Map ==<br />
Inherits from Element.<br />
<br />
See: [[Canvas_Maps|Canvas Maps]] and [[Canvas_Map_API|Canvas Map API]]<br />
== Image ==<br />
Inherits from Element.<br />
<br />
See: [[Canvas_Image|Canvas Image]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=File:Canvas_arc.png&diff=66167File:Canvas arc.png2014-01-05T16:57:47Z<p>F-JYL: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Canvas arc draw examples}}<br />
|date=2014-01-05 17:56:55<br />
|source={{own}}<br />
|author=[[User:F-JYL|F-JYL]]<br />
|permission=<br />
|other_versions=<br />
|other_fields=<br />
}}<br />
{{Location dec|0|0}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-3.0}}<br />
<br />
<br />
[[Category:Canvas Elements]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=List_of_abbreviations&diff=65545List of abbreviations2013-12-10T07:44:56Z<p>F-JYL: /* M */ MCP</p>
<hr />
<div>__NOTOC__<br />
<br />
{{abc}}<br />
<br />
=== A ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| A || <u>A</u>t or <u>A</u>bove (constraint altitute) || <br />
|-<br />
| A || <u>A</u>utotuning || <br />
|-<br />
| AAR || <u>A</u>ir-to-<u>a</u>ir <u>r</u>efuelling<br />
|-<br />
| ACARS || [http://en.wikipedia.org/wiki/ACARS <u>A</u>ircraft <u>C</u>ommunications <u>A</u>ddressing and <u>R</u>eporting <u>S</u>ystem] || A digital datalink system for transmission of short, relatively simple messages between aircraft and ground stations via radio or satellite<br />
|-<br />
| ACAWS || <u>A</u>dvisory, <u>C</u>aution <u>A</u>nd <u>W</u>arning <u>S</u>ystem. || A system which monitors the aircraft's systems and provides warning messages to the crew (similar to EICAS).<br />
|-<br />
| ACCEL HT || <u>Accel</u>eration <u>H</u>eigh<u>t</u> || <br />
|-<br />
| ACT || <u>Act</u>ive|| <br />
|-<br />
| A/C || <u>A</u>ir<u>c</u>raft ||<br />
|-<br />
| ACC || <u>A</u>rea <u>c</u>ontrol <u>c</u>entre ||<br />
|-<br />
| ADC || Air Data Computer || <br />
|-<br />
| [[ADF]] || [http://en.wikipedia.org/wiki/Automatic_Direction_Finder <u>A</u>utomatic <u>d</u>irection <u>f</u>inder] || tuned to [[NDB]]<br />
|-<br />
| ADIRS || Air Data Inertial Reference System || <br />
|-<br />
| ADIRU || Air Data Intertial Reference Unit || <br />
|-<br />
| AFCS || <u>A</u>utomatic <u>F</u>light <u>C</u>ontrol <u>S</u>ystem<br />
|-<br />
| AFDS || Auto Pilot Flight Director System || <br />
|-<br />
| AGL || [[Above Ground Level|<u>A</u>bove <u>G</u>round <u>L</u>evel]] || [http://en.wikipedia.org/wiki/Above_ground_level AGL]<br />
|-<br />
| ALS || <u>A</u>pproach <u>l</u>ighting <u>s</u>ystem<br />
|-<br />
| ALT || <u>Alt</u>itude || [[Altitude]]<br />
|-<br />
| ALT NAV || Alternate Navigation || <br />
|-<br />
| AMI || Airline Modifiable Information || <br />
|-<br />
| [[AMSL]] || <u>A</u>bove <u>m</u>ean <u>s</u>ea <u>l</u>evel<br />
|-<br />
| AoA || Angle of Attack || The angle of the (nose of the) aircraft relative to the surrounding airflow (Pitch is relative to the ground)<br />
|-<br />
| AIMS || Airplane Infromation Management System || <br />
|-<br />
| AIP || [[Aeronautical information publication|<u>A</u>eronautical <u>I</u>nformation <u>P</u>ublication]] ||<br />
|-<br />
| APP || Approach || Used for autopilots among other.<br />
|-<br />
| Apt Elev || <u>A</u>ir<u>p</u>or<u>t</u> <u>Elev</u>ation || the MSL of a central point of an airport<br />
|-<br />
| APU || [http://en.wikipedia.org/wiki/Auxiliary_power_unit Auxiliary power unit] || Primary purpose is to provide power to start the main engines<br />
|-<br />
| A/P || [[Autopilot|<u>A</u>uto<u>p</u>ilot]]<br />
|-<br />
| ARINC || Aeronautical Radio, Incorporated || <br />
|-<br />
| ASCPC || Air Supply and Cabin Pressure Controllers || <br />
|-<br />
| ASOS || [http://en.wikipedia.org/wiki/Automated_airport_weather_station <u>A</u>utomated <u>S</u>urface <u>O</u>bservation <u>S</u>ystem] || measures and broadcasts surface wheather info automatically<br />
|-<br />
| AT || <u>AT</u> (an altitude) ||<br />
|-<br />
| ATA || Actual Time of Arrival || <br />
|-<br />
| ATC || [[ATC|<u>A</u>ir <u>T</u>raffic <u>C</u>ontrol]] ||<br />
|-<br />
| ATIS || [http://en.wikipedia.org/wiki/Automatic_Terminal_Information_Service <u>A</u>utomatic <u>T</u>erminal <u>I</u>nformation <u>S</u>ervice]<br />
|-<br />
| ATM || <u>A</u>ir <u>t</u>raffic <u>m</u>anagement || Integrated management of air traffic and airspace. Can include ATC, ATS, flow management etc. through seamless collaboration with involved parties.<br />
|-<br />
| ATS || <u>A</u>ir <u>t</u>raffic <u>s</u>ervice || A generic term that can mean flight information service, alerting service, air traffic<br />
advisory service or air traffic control service.<br />
|-<br />
| ATT || <u>Att</u>itude || <br />
|-<br />
| ATZ || Aerodrome Traffic Zone || <br />
|-<br />
| A/T || <u>A</u>uto<u>t</u>hrottle || A/P Subsystem which controls the throttle<br />
|-<br />
| AWACS || <u>A</u>irborne <u>W</u>arning <u>A</u>nd <u>C</u>ontrol <u>S</u>ystem<br />
|}<br />
<br />
=== B ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| B || At or Below (constrained altitude) || <br />
|-<br />
| BC || <u>B</u>ack <u>c</u>ourse || part of [[ILS]], beacon that provides range information, like OM/MM/IM, specifies FAF for back course, a back course is non-precison since no G/S associated<br />
|-<br />
| BITE || Built-In Test Equipment || <br />
|-<br />
| BRG/DIS || Bearing and/or Distance || <br />
|-<br />
| BRT || <u>Br</u>igh<u>t</u>ness<br />
|}<br />
<br />
=== C ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| C || Centigrade || <br />
|-<br />
| CALC || Calculated || <br />
|-<br />
| CANC || Cancel || <br />
|-<br />
| CDI || <u>C</u>ourse <u>D</u>eviation <u>I</u>ndicator || part of a VOR gauge, a needle showing whether you are on course (centered) or not (left or right)<br />
|-<br />
| CDU || [[CDU|<u>C</u>ontrol <u>D</u>isplay <u>U</u>nit]]<br />
|-<br />
| CG || Center of Gravity || <br />
|-<br />
| CI || Cost Index || <br />
|-<br />
| CLB || Climb || <br />
|-<br />
| CLB DIR || Climb Direct || <br />
|-<br />
| CLR || Clear || <br />
|-<br />
| CMCF || Central Maintenance Computer Function || <br />
|-<br />
| CO DATA || Company Data || <br />
|-<br />
| COMM || Communications || <br />
|-<br />
| CON || Continuous || <br />
|-<br />
| CRS || Course || <br />
|-<br />
| CRT || Cathode Ray Tube || <br />
|-<br />
| CRZ || Cruise || <br />
|-<br />
| CRZ ALT || Cruise Altitude || <br />
|-<br />
| CRZ CG || Cruise Center of Gravity || <br />
|-<br />
| CRZ CLB || Cruise Climb || <br />
|-<br />
| CTAF || <u>C</u>ommon <u>T</u>raffic <u>A</u>dvisory <u>F</u>requency || Available at airfields with no operational control tower.<br />
|-<br />
| CTC || <u>C</u>abin <u>T</u>emperature <u>C</u>ontroller || <br />
|-<br />
| CTOT || <u>C</u>alculated <u>t</u>ake-<u>o</u>ff <u>t</u>ime ||<br />
|-<br />
| CTR || Controlled Zone || <br />
|}<br />
<br />
=== D ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| DG || <u>D</u>irectional [http://en.wikipedia.org/wiki/Gyroscope <u>G</u>yro]<br />
|-<br />
| DH || <u>D</u>ecision <u>h</u>eight || point on G/S where to decide to continue landing or missed approach, similar to MDA, for precision approaches, determined by altimeter, lowest height where an approach can be flown by instrument alone<br />
|-<br />
| DLC || Direct lift control || system for steady approaches without changing pitch, as seen on the [[L-1011-500]].<br />
|-<br />
| [[DME]] || [http://en.wikipedia.org/wiki/Distance_Measuring_Equipment <u>D</u>istance <u>m</u>easuring <u>e</u>quipment] || measures the distance (slant, not on-ground distance) to the tuned in [[VOR]]<br />
|-<br />
| DTG || <u>D</u>istance <u>t</u>o <u>g</u>o<br />
|}<br />
<br />
=== E ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| EAT || <u>E</u>stimated <u>A</u>rrival <u>T</u>ime<br />
|-<br />
| ECEF || <u>E</u>arth-<u>C</u>entred, <u>E</u>arth-<u>F</u>ixed coordinate system || Cartesian 3D coordinate system with origo at the Earth's center of mass and x axis intersecting 0°E, 0°N<br />
|-<br />
| EDT || <u>E</u>stimated <u>D</u>eparture <u>T</u>ime<br />
|-<br />
| EFATO || <u>E</u>ngine <u>f</u>ailure <u>a</u>fter <u>t</u>ake <u>o</u>ff || Usually resulting in a force-landing.<br />
|-<br />
| EFIS || <u>E</u>lectronic <u>F</u>light <u>I</u>nstrument <u>S</u>ystem || Combination of displays (PFD and MFD) with autopilot<br />
|-<br />
| EICAS || [http://en.wikipedia.org/wiki/Eicas <u>E</u>ngine <u>I</u>ndication and <u>C</u>rew <u>A</u>lerting <u>S</u>ystem]<br />
|-<br />
| EOBT || <u>E</u>stimated <u>off-</u><u>b</u>lock <u>t</u>ime || The estimated time the aircraft will start moving before departure. In essence when the aircraft starts to taxi<br />
|-<br />
| ETA || <u>E</u>stimated <u>T</u>ime of <u>A</u>rrival<br />
|-<br />
| ETOPS || <u>E</u>xtended <u>T</u>win-engine <u>O</u>perational <u>P</u>erformance <u>Standards</u> || Standard allowing twin-engined aircraft (eg, the 777 or A330) to fly long distances between potential alternate airports, eg trans-oceanic flights.<br />
|}<br />
<br />
=== F ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| FAF || <u>F</u>inal <u>a</u>pproach <u>f</u>ix<br />
|-<br />
| FD || [http://en.wikipedia.org/wiki/Flight_director_%28aviation%29 <u>F</u>light <u>d</u>irector] || horizontal and vertical bars on your PD<br />
|-<br />
| FDM || [[Flight Dynamics Model|<u>F</u>light <u>D</u>ynamics <u>M</u>odel]]<br />
|-<br />
| FL || <u>F</u>light <u>L</u>evel || [[Flight level]]<br />
|-<br />
| FLEX || [http://en.wikipedia.org/wiki/Flex_temp Flex Temp] || Performing a take-off (TOGA) at less than full power.<br />
|}<br />
<br />
=== G ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| G/S || [http://en.wikipedia.org/wiki/Glideslope <u>G</u>lide<u>s</u>lope] || provides vertical guidance during [[ILS]], UHF, always goes together with LOC, usually 3deg, usable 10NM from field<br />
|-<br />
| GA || <u>G</u>o-<u>A</u>round<br />
|-<br />
| GA || [http://en.wikipedia.org/wiki/General_aviation <u>G</u>eneral <u>A</u>viation]<br />
|-<br />
| GAR || <u>G</u>o-<u>Ar</u>ound<br />
|-<br />
| GPS || [http://en.wikipedia.org/wiki/Gps <u>G</u>lobal <u>P</u>ositioning <u>S</u>ystem] || allows a very exact measuring of location all over the world, based on satellites<br />
|}<br />
<br />
=== H ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| HDG || <u>H</u>ea<u>d</u>in<u>g</u><br />
|-<br />
| HUD || [[Head-up display|<u>H</u>ead <u>u</u>p <u>d</u>isplay]] || [http://en.wikipedia.org/wiki/Head-up_display Head up display]<br />
|-<br />
| HSI || [http://en.wikipedia.org/wiki/Horizontal_situation_indicator <u>H</u>orizontal <u>s</u>ituation <u>i</u>ndicator] <br />
|}<br />
<br />
=== I ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| IAF || <u>I</u>nstrument <u>a</u>pproach <u>p</u>late || see Approach Plate, aka. Terminal Procedures<br />
|-<br />
| IAP || <u>I</u>nitial <u>a</u>pproach <u>f</u>ix<br />
|-<br />
| IATA || [[IATA|<u>I</u>nternational <u>A</u>ir <u>T</u>ransport <u>A</u>ssociation]]<br />
|-<br />
| ICAO || [http://en.wikipedia.org/wiki/Icao <u>I</u>nternational <u>C</u>ivil <u>A</u>viation <u>O</u>rganisation]<br />
|-<br />
| [[IFR]] || [http://en.wikipedia.org/wiki/IFR <u>I</u>nstrument <u>f</u>light <u>r</u>ules] || 0-179: odd thousands, 180-359: even thousands<br />
|-<br />
| [[ILS]] || [http://en.wikipedia.org/wiki/Glideslope <u>I</u>nstrument <u>L</u>anding <u>S</u>ystem]<br />
|-<br />
| IM || <u>I</u>nner <u>m</u>arker || See [[Inner marker]]<br />
|}<br />
<br />
=== J ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| JBD || <u>J</u>et <u>b</u>last <u>d</u>eflector<br />
|}<br />
<br />
=== K ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| KIAS || <u>K</u>nots <u>I</u>ndicated <u>A</u>ir<u>s</u>peed || [[IAS]] in knots<br />
|}<br />
<br />
=== L ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| LDA || <u>L</u>ocalizer <u>d</u>irectional <u>a</u>id || similar to LOC, but offset from runway heading, the approach path is not lined up with runway<br />
|-<br />
| [[LFR]] ||Low Frequency Radio Range || see article [[LFR]]<br />
|-<br />
| LNAV || [http://en.wikipedia.org/wiki/LNAV <u>L</u>ateral <u>nav</u>igation]<br />
|-<br />
| LOC || [http://en.wikipedia.org/wiki/Localizer <u>Loc</u>alizer] || provides lateral guidance during ILS, VHF, always goes together with G/S, usable 18NM from field<br />
|-<br />
| LOC-A || || an approach plate that ends with a letter indicates that a circling approach is required<br />
|-<br />
| LTA || <u>L</u>ighter <u>t</u>han <u>A</u>ir<br />
|}<br />
<br />
=== M ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| MALSR || <u>M</u>edium-intensity <u>ALS</u> with <u>R</u>unway alignment indicator lights || a type of Runway Approach lighting<br />
|-<br />
| MAP || <u>M</u>issed <u>a</u>pproach <u>p</u>oint || touch down zone of runway<br />
|-<br />
| MCP || <u>M</u>ode <u>C</u>ontrol <u>P</u>anel || Panel that controls the autopilot<br />
|-<br />
| MDA || <u>M</u>inimum <u>d</u>escend <u>a</u>ltitude || during an approach, this specifies the minimum Altitude (MSL) before the runway is in sight and a safe landing can be made<br />
|-<br />
| MEA || <u>M</u>ean <u>e</u>nroute <u>a</u>ltitude<br />
|-<br />
| MES || Main Engine Start || See APU<br />
|-<br />
| METAR || [[METAR|<u>Met</u>eorological <u>A</u>erodrome <u>R</u>eport]] || [http://en.wikipedia.org/wiki/METAR METAR]<br />
|-<br />
| MFD || <u>M</u>ulti <u>F</u>unction <u>D</u>isplay unit, sometimes named MDU || Display that can contain all sorts of information, like map, weather and engine status. Often a backup for PFD's<br />
|-<br />
| MIRL || <u>M</u>edium-<u>i</u>ntensity <u>r</u>unway <u>l</u>ights<br />
|-<br />
| MLS || <u>M</u>icrowave <u>l</u>anding <u>s</u>ystem<br />
|-<br />
| MM || <u>M</u>iddle <u>m</u>arker || [[Middle marker]]<br />
|-<br />
| MOCA || <u>M</u>inimum <u>o</u>bstruction <u>c</u>learance <u>a</u>ltitude<br />
|-<br />
| MSA || <u>M</u>inimum <u>s</u>afe <u>a</u>ltitude || provides minimum of 1000ft clearance from obstructions and terrain<br />
|-<br />
| MSFS || <u>M</u>icro<u>s</u>oft <u>F</u>light <u>S</u>imulator || a flight simulator by Microsoft that is now discontinued<br />
|-<br />
| MSL || <u>M</u>ean <u>S</u>ea <u>L</u>evel || Standardized height figure, Altimeters show the current A/C height over MSL<br />
|-<br />
| MTOW || [http://en.wikipedia.org/wiki/Maximum_Takeoff_Weight <u>M</u>aximum <u>T</u>ake<u>o</u>ff <u>W</u>eight] ||<br />
|}<br />
<br />
=== N ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| Navaid || [http://en.wikipedia.org/wiki/Navaid Helper for navigation] || eg: [[NDB]], Fixes, [[VOR]], GPS<br />
|-<br />
| ND || [[Navigational Display|<u>N</u>avigational <u>D</u>isplay]]<br />
|-<br />
| [[NDB]] || [http://en.wikipedia.org/wiki/Non-directional_beacon <u>N</u>on <u>d</u>irectional <u>b</u>eacon] || LW, sends out Morse code of its ID, reception only reliable > 1000ft AGL<br />
|}<br />
<br />
=== O ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| OAT || <u>O</u>utside <u>a</u>ir <u>t</u>emperature || the temperature of undisturbed air, derived by correcting TAT for compressibility errors<br />
|-<br />
| OBS || <u>O</u>mni <u>b</u>earing <u>s</u>elector || part of a [[VOR]] gauge, used to rotate the course card<br />
|-<br />
| OM || <u>O</u>uter <u>m</u>arker || [[Outer marker]]<br />
|}<br />
<br />
=== P ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| PAPI || [[Precision Approach Path Indicator|<u>P</u>recision <u>A</u>pproach <u>P</u>ath <u>I</u>ndicator]] || [http://en.wikipedia.org/wiki/Precision_Approach_Path_Indicator PAPI], similar to VASI, but more precise, uses four lights<br />
|-<br />
| PD || <u>P</u>rimary <u>d</u>isplay<br />
|-<br />
| PF || <u>P</u>ilot <u>f</u>lying || the person that currently controls the airplane, can be either Captain or F/O<br />
|-<br />
| PFD || [[Primary flight display|<u>P</u>rimary <u>f</u>light <u>d</u>isplay]]<br />
|-<br />
| PFL || <u>P</u>ractice <u>f</u>orced <u>l</u>anding || Practise approach carried out to a suitable field. No landing is made.<br />
|-<br />
| PIREP || <u>Pi</u>lot <u>Rep</u>ort ||(abbreviated UA in the briefing teletype, UUA is urgent PIREP)<br />
|-<br />
| PNF || <u>P</u>ilot <u>n</u>on-<u>f</u>lying || the person who's not the PF<br />
|}<br />
<br />
=== Q ===<br />
===R===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| RAT || <u>R</u>am <u>a</u>ir <u>t</u>emperature || the raw, non-corrected temp. as measured by the temperature probe. Errors due to the Ram effect (air compressed in the probe) and the position (air may be disturbed by parts of the airplane, and also due to the effect of the air compression in front of the plane) RAT may also describe a Ram Air Turbine; a device deployed into the airstream on large aircraft to provided minimum electrical power in the event of generator-failure.<br />
|-<br />
| [[RDF]] || Radio Direction Finder || see article [[RDF]]<br />
|-<br />
| RMI || <u>R</u>adio <u>m</u>agnetic <u>i</u>ndicator<br />
|-<br />
| RNAV || A<u>r</u>ea <u>Nav</u>igation || flying by longitude/latitude points that are not radio navigation aids, GPS or IRS is usually used.<br />
|-<br />
| RTO || <u>R</u>ejected <u>t</u>ake <u>o</u>ff<br />
|-<br />
| RTOW || [http://en.wikipedia.org/wiki/Maximum_Takeoff_Weight Regulated Take Off Weight] || See Maximum Takeoff Weight MTOW<br />
|-<br />
| RVR || [http://en.wikipedia.org/wiki/Runway_visual_range <u>R</u>unway <u>V</u>isual <u>R</u>ange] || The distance over which a pilot of an aircraft on the centreline of the runway can see the runway surface markings delineating the runway or identifying its centre line<br />
|}<br />
<br />
=== S ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| SAT || <u>S</u>tatic <u>a</u>ir <u>t</u>emperature || same as OAT<br />
|-<br />
| SDF || <u>S</u>imple <u>d</u>irectional <u>f</u>acility<br />
|-<br />
| SFDS || <u>S</u>econdary <u>F</u>light <u>S</u>ystem <u>D</u>isplay||Standby EFIS in a single self contained unit, not to be mistaken with MFD<br />
|-<br />
| SFD || <u>S</u>econdary <u>F</u>light <u>D</u>isplay || Display of the SFDS<br />
|-<br />
| SID || <u>S</u>tandard <u>i</u>nstrument <u>d</u>eparture || for takeoffs, specifies the route from the runway to the first waypoint<br />
|-<br />
| STAR || [http://en.wikipedia.org/wiki/Standard_Terminal_Arrival_Route <u>S</u>tandard <u>t</u>erminal <u>a</u>rrival <u>r</u>oute] || for landings, speciefies the route from the last waypoint down to the runway<br />
|-<br />
| STOL || <u>S</u>hort <u>t</u>ake <u>o</u>ff and <u>l</u>anding<br />
|-<br />
| STOVL || <u>S</u>hort <u>t</u>ake <u>o</u>ff and <u>v</u>ertical <u>l</u>anding<br />
|}<br />
<br />
=== T ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| TACAN || [[Tactical Air Navigation|<u>Tac</u>tical <u>A</u>ir <u>N</u>avigation]] || [http://en.wikipedia.org/wiki/TACAN Tactical Air Navigation], military<br />
|-<br />
| TAF || <u>T</u>erminal <u>a</u>erodrome <u>f</u>orecast<br />
|-<br />
| TAT || <u>T</u>otal <u>a</u>ir <u>t</u>emperature || This is derived by correcting the RAT for position. Still contains an error due to the compressibility of air inside the temperature probe.<br />
|-<br />
| TCAS ||[[Traffic Collision Avoidance System|<u>T</u>raffic <u>C</u>ollision <u>A</u>voidance <u>S</u>ystem]]<br />
|-<br />
| TDZE || <u>T</u>ouch <u>d</u>own <u>z</u>one <u>e</u>levation || the MSL of the touch down point of a runway<br />
|-<br />
| THDG || <u>T</u>rue <u>H</u>ea<u>d</u>in<u>g</u><br />
|-<br />
| TODR || <u>T</u>ake <u>O</u>ff <u>D</u>istance <u>R</u>equired || <br />
|-<br />
| TOGA || <u>T</u>ake <u>O</u>ff / <u>G</u>o <u>A</u>round || Automatic single-switch operation of throttle for Take-off / Go-Around Power.<br />
|-<br />
| TOW || [http://en.wikipedia.org/wiki/Maximum_Takeoff_Weight Take Off Weight] ||<br />
|-<br />
| T&P(s) || <u>T</u>emperatures and <u>p</u>ressures || relating to engine systems.<br />
|}<br />
<br />
=== U ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| UNICOM || <u>Uni</u>versal <u>Com</u>munications || See also: CTAF<br />
|-<br />
| UTC || [http://en.wikipedia.org/wiki/UTC Coordinated Universal Time] || Not to be confused with [http://en.wikipedia.org/wiki/Greenwich_Mean_Time GMT] - Greenwich Mean Time<br />
|}<br />
<br />
=== V ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| [[V speeds]] || [[V speeds|<u>V</u>elocity speeds]] || airspeeds important or useful to the operation of aircraft<br />
|-<br />
| VASI || [http://en.wikipedia.org/wiki/VASI <u>V</u>isual <u>a</u>pproach <u>s</u>lope <u>i</u>ndicator] || an approach lighting system, typically two lights left of the runway<br />
|-<br />
| [[VFR]] || [http://en.wikipedia.org/wiki/Visual_flight_rules <u>V</u>isual <u>F</u>light <u>R</u>ules] || 0-179: odd thousands+500ft, 180-359: even thousands+500ft<br />
|-<br />
| VNAV || <u>V</u>ertical <u>nav</u>igation<br />
|-<br />
| [[VOR]] || [[VOR|<u>V</u>HF <u>O</u>mnidirectional <u>R</u>adio Range]] || [[VOR]], a type of radio navigation system<br />
|-<br />
| [[VORTAC]] || <u>VOR</u>/<u>TAC</u>AN || A co-located [[VOR]] and [[TACAN]] beacon.<br />
|-<br />
| VSI || <u>V</u>ertical <u>s</u>peed <u>i</u>ndicator<br />
|-<br />
| VTOL || <u>V</u>ertical <u>t</u>ake <u>o</u>ff and <u>l</u>anding<br />
|}<br />
<br />
=== W ===<br />
{| class="prettytable" style="width:100%;"<br />
! style="width:8em;" | Abbreviation<br />
! style="width:20em;" | Meaning(s)<br />
! Description<br />
|-<br />
| WCA || <u>W</u>ind <u>c</u>orrection <u>a</u>ngle<br />
|-<br />
| WOW || <u>W</u>eight <u>o</u>n <u>w</u>heels || A condition met when the weight of an aircraft are pushing its wheels to the ground, indicating that it is not in the air.<br />
|}<br />
<br />
=== X ===<br />
===Y===<br />
=== Z ===<br />
<br />
<br />
----<br />
==== External links ====<br />
* [http://en.wikipedia.org/wiki/List_of_aviation,_aerospace_and_aeronautical_abbreviations Wikipedia (en)]<br />
* [http://de.wikipedia.org/wiki/Abk%C3%BCrzungen/Luftfahrt Wikipedia (de)], more detailed and descriptions are english anyway ;-)<br />
<br />
[[Category:List]]<br />
[[Category:Resource]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&diff=60265FlightGear hangars2013-05-19T09:29:22Z<p>F-JYL: /* Aircraft hangars */ omega hangar url update</p>
<hr />
<div>{{cleanup}}<br />
<br />
''See [[Links]] for an overall listing of FlightGear related external websites''<br />
<br />
FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version. <br />
<br />
Be careful with external links! <br />
<br />
== Official hangars ==<br />
=== Aircraft ===<br />
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ FlightGear Official 2.10 Hangar]<br />
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]<br />
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]<br />
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)<br />
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)<br />
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)<br />
<br />
=== Liveries ===<br />
* [http://liveries.flightgear.org FlightGear Liveries]<br />
<br />
== Unofficial sites ==<br />
=== Aircraft hangars ===<br />
* [http://www.gitorious.org/fg-airbus-a332 Airbus A330-200 Series Development Git] (A330-203, A330-223, A330-243 - FGAirbus/theOmegaHangar)<br />
* [http://www.gitorious.org/fg-airbus-a333 Airbus A330-300 Series Development Git] (A330-303, A330-323, A330-343 - FGAirbus/theOmegaHangar)<br />
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].<br />
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C and 707-320C, 777-200LR).<br />
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)<br />
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)<br />
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)<br />
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)<br />
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)<br />
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)<br />
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)<br />
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)<br />
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (164+ original aircraft)<br />
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles) <br />
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)<br />
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.<br />
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)<br />
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)<br />
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)<br />
** [http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)<br />
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)<br />
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)<br />
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)<br />
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (MiG-21bis, PC-9M, PC-21, T-50, Harrier GR.1, F-35B, RAH-66)<br />
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)<br />
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)<br />
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)<br />
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)<br />
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)<br />
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]<br />
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)<br />
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)<br />
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)<br />
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]<br />
* [http://acjza-hangers.webs.com/ ACJZA's Hanger] (A310, BAe 146, C-Series)<br />
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, scenario)<br />
<br />
=== Old Hangars ===<br />
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]<br />
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002) <br />
<br />
=== Livery hangars ===<br />
* [http://berwickskins.yolasite.com/ Berwick-skins]<br />
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]<br />
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]<br />
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]<br />
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]<br />
<br />
=== Homepages, blogs, etc. ===<br />
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]<br />
* <s>[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]</s>{{dead link|2013-01}}<br />
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]<br />
* [http://helldiversquadron.wordpress.com/ Helldiver Squadron Offensive Tactical Force Homepage]<br />
* <s>[http://www.grupofgbr.com.br/ Grupo FGBR Brazilian Portal]</s>{{dead link|2013-01}}<br />
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)<br />
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)<br />
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]<br />
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)<br />
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)<br />
* [http://www.fguk.eu/ FlightGear United Kingdom] <br />
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]<br />
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}<br />
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)<br />
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle<br />
<br />
=== Other FlightGear repositories/mirrors ===<br />
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)<br />
* [http://www.flightgearplanes.com Flightgear Planes Website]<br />
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]<br />
* [http://lukeafg.com/ LukeaFG] (FlightGear tutorials and developments)<br />
<br />
== Related content ==<br />
* [[Table of models]]<br />
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]<br />
<br />
[[Category:List]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Tutorials&diff=59474Tutorials2013-04-13T05:35:32Z<p>F-JYL: small typo</p>
<hr />
<div>[[FlightGear]] offers a flexible '''tutorial''' system, entirely written in the [[Nasal]] scripting language.<br />
Aircraft that provide support for these scripted tutorials can be found in [[:Category:Interactive Tutorial Support]].<br />
<br />
== Interfacing Tutorials to web sites ==<br />
To learn more about interfacing FlightGear to web sites (without having to go through the multiplayer protocol) by making HTTP requests via Nasal, please see this tutorial: <br />
[[Howto:Making HTTP Requests from Nasal]].<br />
<br />
== Supporting Checklists ==<br />
As of V2.9.0, FlightGear can display aircraft checklists in a standardized way, under Help->Aircraft Checklists.<br />
<br />
Checklists are situated under /sim/checklists. <br />
Please see [[Aircraft Checklists]].<br />
<br />
Also see: http://flightgear.org/forums/viewtopic.php?f=3&t=18240&p=170386#p170386<br />
<br />
== Some Background Info ==<br />
<br />
The tutorial system itself was largely developed by Stuart.<br />
<br />
In recent FGDATA, the Nasal "tutorial" module has become a so called "Nasal sub module", which means that the "tutorial.nas" module now resides in its own sub folder inside [[$FG_ROOT]]/Nasal: http://gitorious.org/fg/fgdata/trees/master/Nasal/tutorial.<br />
<br />
Support for Nasal sub modules was added by ThorstenB. Modules loaded as Nasal sub modules do automatically support reloading, because they are loaded via a listener.<br />
<br />
Please see the Nasal documentation on sub modules for details: [[Nasal#Nasal sub modules]].<br />
<br />
Regarding suggested coding practices, you should check out: [[Nasal scripting language#Memory management]] and [[Nasal#Managing timers and listeners]].<br />
<br />
To learn more about translating tutorials, please see: http://flightgear.org/forums/viewtopic.php?f=42&t=16876&p=164407&hilit=tutorials#p164407<br />
<br />
== Reloading XML tutorials at runtime ==<br />
<br />
tutorial.nas module is loaded via a listener ("/nasal/tutorial/loaded").<br />
See line 28-37 of tutorial.nas in [[$FG_ROOT]]/Nasal/tutorial to see how this is done.<br />
<br />
Before you can actually reload a tutorial, you must first of all STOP it.<br />
Please see line 112-122 of tutorial.nas in [[$FG_ROOT]]/Nasal/tutorial.<br />
<br />
Once you have stopped all running tutorials, you can reload the corresponding tutorial.<br />
Please see line 477-480 of tutorial.nas in [[$FG_ROOT]]/Nasal/tutorial to see how this is done.<br />
<br />
Basically, you should be able to come up with your own "reload" function by combining the stop() and the load() functions and adding a new "reload" function to tutorial.nas:<br />
<syntaxhighlight lang="php"><br />
var reload = func(filename,slot) stopTutorial() and load(filename,slot);<br />
</syntaxhighlight><br />
<br />
Also, see line 450-463 of tutorial.nas in [[$FG_ROOT]]/Nasal/tutorial to see how the namespace is initialized.<br />
For additional information on namespace, I suggest to have a look at: [[Namespaces and Methods]]<br />
<br />
== Using tutorials ==<br />
<br />
Tutorials can be started and stopped from the "Help" [[menubar|menu]]. They are defined in XML files. Each of them has to be loaded into <tt>/sim/tutorials/</tt> under a separate <tt>tutorial[n]/</tt> branch:<br />
<syntaxhighlight lang="xml"><br />
<sim><br />
<tutorials><br />
<tutorial include="Tutorials/take-off.xml"/><br />
<tutorial include="Tutorials/landing.xml"/><br />
</tutorial><br />
</sim><br />
</syntaxhighlight><br />
<br />
Alternatively, all tutorials can be defined in a single file, with <tt><tutorial></tt> tags around each tutorial. This is then included like so:<br />
<syntaxhighlight lang="xml"><br />
<sim><br />
<tutorials include="foo-tutorials.xml"/><br />
</sim><br />
</syntaxhighlight><br />
<br />
== Structure ==<br />
A tutorial has this structure, where some of the elements are described in detail below:<br />
<br />
<syntaxhighlight lang="xml"><br />
<tutorial><br />
<name>...</name> mandatory; short identifier, also shown in the<br />
tutorial selection dialog<br />
<description>...</description> mandatory; longer description for the dialog<br />
<audio-dir>...</audio-dir> optional; defines where to load sound samples<br />
<interval>5</interval> optional; defines default loop interval in sec<br />
<timeofday>noon</timeofday> optional; defines daytime; any of "dawn",<br />
"morning", "noon", "afternoon",<br />
"evening", "dusk", "midnight", "real"<br />
<nasal><br />
... optional; initial Nasal code; see below<br />
</nasal><br />
<br />
<models><br />
... optional; scenery objects; see below<br />
</models><br />
<br />
<targets><br />
... optional; targets; see below<br />
</targets><br />
<br />
<presets><br />
... optional; initial simulator state; see below<br />
</presets><br />
<br />
<br />
<init> optional; initial settings; see below<br />
<set><br />
... optional; property settings; allowed multiple<br />
</set> times<br />
<view><br />
... optional; view settings<br />
</view><br />
<marker><br />
... optional; marker coordinates<br />
</marker><br />
<nasal><br />
... optional; Nasal code<br />
</nasal><br />
<interval>10</inteval> optional; run loop next in this many seconds<br />
</init> (default: 5); doesn't change global<br />
interval<br />
<br />
<br />
<step> mandatory; well, not really, but if there's not<br />
at least one <step>, then the whole tutorial<br />
won't do anything; see below for details<br />
<br />
<message>...</message> optional; message to be displayed/spoken when<br />
<step> is entered; allowed multiple times, in<br />
which case one is chosen at random<br />
<br />
<audio>...</audio> optional; file name of *.wav sample to be played;<br />
may be used multiple times (random)<br />
<set><br />
... optional; allowed several times<br />
</set><br />
<view><br />
... optional<br />
</view><br />
<marker><br />
... optional<br />
</marker><br />
<nasal><br />
... optional; Nasal code that is executed when the<br />
</nasal> step is entered<br />
<br />
<interval>10</inteval> optional; run loop next in this many seconds<br />
<br />
<error> optional; allowed several times<br />
<message>..</message> optional; text displayed/spoken<br />
<audio>...</audio> optional; name of *.wav sample to be played<br />
<br />
<condition><br />
... optional, but one should be there to make sense<br />
</condition> see [[$FG_ROOT]]/Docs/README.conditions<br />
<br />
<nasal><br />
... optional; Nasal code that is executed when the<br />
</nasal> error condition was fulfilled<br />
<br />
<interval>10</inteval> optional; run loop next in this many seconds<br />
</error><br />
<br />
<exit> optional; defines when to leave this <step><br />
<condition> see [[$FG_ROOT]]/Docs/README.conditions<br />
...<br />
</condition><br />
<br />
<nasal><br />
... optional; Nasal code that is executed when the<br />
</nasal> exit condition was met<br />
</exit><br />
</step><br />
<br />
<br />
<end> optional; final settings & actions; see below<br />
<message>...</message> optional; multiple times (random)<br />
<audio>...</audio> optional; multiple times (random)<br />
<set><br />
... optional<br />
</set><br />
<view><br />
... optional<br />
</view><br />
<nasal><br />
... optional<br />
</nasal><br />
</end><br />
</tutorial><br />
</syntaxhighlight><br />
<br />
After the tutorial has finished its initialization, it goes through all <steps>. For each, it outputs the <message> or <audio>, optionally sets a <marker> and/or a <view>, then it checks all <error>s and, if an <error><condition> is fulfilled, outputs the respective <error><message>. If none of the <error>s occurred, then it checks if the <exit><condition> is true, and if so, it jumps to the next <step>. Otherwise the current <step> is endlessly repeated. Finally, after all <step>s were processed, the <end> group is executed.<br />
<br />
== Elements ==<br />
=== Nasal ===<br />
Embedded Nasal code is supported on the top level, in <init> in each <step>, in a <step>'s <error> and <exit>, and in <end>. All Nasal runs in a separate namespace __tutorial, so it's possible to define a function in the <init>'s Nasal block, and to use this function in other blocks without prefix. The namespace is preloaded with some functions:<br />
<br />
<br />
next([n=1]) ... to switch n <step>s forward<br />
previous([n=1]) ... to switch n <step>s backwards<br />
<br />
say(what [, who="copilot [, delay=0]])<br />
... says 'what' with voice 'copilot' after 'delay' seconds<br />
<br />
<br />
A Nasal group looks like this:<br />
<br />
<syntaxhighlight lang="xml"><br />
<nasal><br />
<script><br />
say("Hi, I'm the pilot!", "pilot");<br />
</script><br />
<module>__tutorial</module> optional; preset with __tutorial<br />
</nasal><br />
</syntaxhighlight><br />
<br />
=== Models ===<br />
This loads models into the scenery. It can be used to place, for example, a helicopter landing pad at an airport where normally none is, so that the tutorial can train landing. The layout is the following, with <path> being relative to [[$FG_ROOT]]:<br />
<br />
<syntaxhighlight lang="xml"><br />
<models><br />
<model><br />
<path>Models/Airport/supacat_winch.ac</path> mandatory<br />
<longitude-deg>-122.4950109</longitude-deg> mandatory<br />
<latitude-deg>37.51403798</latitude-deg> mandatory<br />
<elevation-ft>51</elevation-ft> mandatory<br />
<heading-deg>2.488888979</heading-deg> optional (default: 0)<br />
<pitch-deg>0</pitch-deg> optional (default: 0)<br />
<roll-deg>0</roll-deg> optional (default: 0)<br />
</model><br />
<br />
<model><br />
... another model<br />
</model><br />
</models><br />
</syntaxhighlight><br />
<br />
The models are only removed before a new tutorial is loaded. Otherwise they remain in the scenery for the whole FlightGear session. They aren't permanently added.<br />
<br />
=== Targets ===<br />
These are simple pairs of longitude/latitude under an arbitrary name (here "hospital" and "helipad"):<br />
<br />
<syntaxhighlight lang="xml"><br />
<targets><br />
<hospital><br />
<longitude-deg>-122.4950109</longitude-deg> mandatory<br />
<latitude-deg>37.51403798</latitude-deg> mandatory<br />
</hospital><br />
<br />
<helipad><br />
...<br />
</helipad><br />
</targets><br />
</syntaxhighlight><br />
<br />
The tutorial system will for each calculate how the user's aircraft is positioned relative to the respective target, and offer the information in this structure:<br />
<br />
<syntaxhighlight lang="xml"><br />
<sim><br />
<tutorials><br />
<targets><br />
<hospital><br />
<direction-deg>12.345</direction-deg><br />
<heading-deg>33.333</heading-deg><br />
<distance-m>12404.932</distance-m><br />
<eta-min>39.2358</eta-min><br />
</hospital><br />
<br />
<helipad><br />
...<br />
</helipad><br />
</targets><br />
</tutorials><br />
</sim><br />
</syntaxhighlight><br />
<br />
Where:<br />
<syntaxhighlight lang="xml"><br />
<direction-deg> is an angle between the aircraft's velocity vector and the<br />
azimuth to the target. 0 means that the aircraft is moving<br />
right towards the target. 10 means that the target is slightly<br />
to the right, -90 means that it's exactly left, and -180 or<br />
179.9999 that it's right behind.<br />
<br />
<heading-deg> is the absolute heading that the aircraft would currently<br />
have to fly with in a straight line to reach the target<br />
<br />
<distance-m> is the distance in meters<br />
<br />
<eta-min> is the "Estimated Time of Arrival" given the aircraft's<br />
current speed towards the target. Positive times mean that<br />
the aircraft is getting nearer to the target and can arrive<br />
there in this time given the current speed. It will, of course,<br />
only arrive there, if <direction-deg> is zero. A negative<br />
number means that the aircraft moves away, or in other words:<br />
that in this number of minutes it will be away twice as far.<br />
</syntaxhighlight><br />
<br />
=== Preset ===<br />
These set the initial simulator state. All properties are optional. The last three entries are to define the position relative to the airport/runway or the longitude/latitude.<br />
<br />
<syntaxhighlight lang="xml"><br />
<presets><br />
<airport-id>KHAF</airport-id><br />
<on-ground>1</on-ground><br />
<runway>12</runway><br />
<!--<br />
<altitude-ft>122.333</altitude-ft><br />
<latitude-deg>37.555</latitude-deg><br />
<longitude-deg>1000</longitude-deg><br />
--><br />
<heading-deg>0</heading-deg><br />
<airspeed-kt>0</airspeed-kt><br />
<glideslope-deg>0</glideslope-deg><br />
<offset-azimuth>0</offset-azimuth><br />
<offset-distance>0</offset-distance><br />
</presets><br />
</syntaxhighlight><br />
<br />
=== Set ===<br />
<set> groups can be used in <init>, <step>, and <end>. They set a <property> to a given <value> or to the value that a second <property> points to. They can also reset values that were only temporarily changed for the duration of the tutorial. This is desirable for properties that are saved to the aircraft config file or to ~/.fgfs/autosave.xml.<br />
<br />
<syntaxhighlight lang="xml"><br />
<set><br />
<property>/foo/bar</property> set /foo/bar to 123<br />
<value>123</value><br />
</set><br />
<br />
<set><br />
<property>/foo/bar</property> set /foo/bar to value of /test<br />
<property>/test</property><br />
</set><br />
</syntaxhighlight><br />
<br />
=== View ===<br />
These groups can be used in <init>, <step>, and <end>. They smoothly move the view to a new view position/direction. All parameters are optional. If, for example, only <field-of-view> is set, then the view will only zoom in -- the direction and position will remain the same. This feature is meant for cockpit tutorials, where the pilot's view is directed to some switch or instrument.<br />
<br />
<syntaxhighlight lang="xml"><br />
<view><br />
<heading-offset-deg>20</heading-offset-deg> positive is left<br />
<pitch-offset-deg>-4</pitch-offset-deg> positive is up<br />
<roll-offset-deg>0</roll-offset-deg> positive is roll right<br />
<x-offset-m>0.2</x-offset-m> positive is move right<br />
<y-offset-m>0.2</y-offset-m> positive is move up<br />
<z-offset-m>0.2</z-offset-m> positive is move back<br />
<field-of-view>55</field-of-view> default: 55; smaller zooms in<br />
</view> <br />
</syntaxhighlight><br />
<br />
=== Marker ===<br />
These are supported in <init>, <step>, and <end>. They show a magenta colored circle at given position (relative to aircraft origin) in given size. See the last section for how to conveniently find the proper coordinates.<br />
<br />
<syntaxhighlight lang="xml"><br />
<marker><br />
<x-m>1.3</x-m> positive is back<br />
<y-m>0.3</y-m> positive is to the right<br />
<z-m>0.1</z-m> positive is up<br />
<scale>1.3</scale> optional; default: 1<br />
</marker><br />
</syntaxhighlight><br />
<br />
For this to work, the aircraft model needs to include the tutorial marker model in its animation xml file:<br />
<br />
<syntaxhighlight lang="xml"><br />
<PropertyList><br />
<path>lightning-f1a.ac</path><br />
<br />
<model><br />
<path>Models/Aircraft/marker.xml</path><br />
</model><br />
<br />
...<br />
</PropertyList><br />
</syntaxhighlight><br />
<br />
==== Finding marker coordinates ====<br />
If an aircraft tutorial wants to use the marker, then the aircraft animation file needs to include the marker model (see above). If this is done, then one can use the "marker-adjust" dialog to find the respective <marker> coordinates. Just type this into the "Help->Nasal Console" dialog:<br />
<br />
<syntaxhighlight lang="php"><br />
tutorial.dialog()<br />
</syntaxhighlight><br />
<br />
<br />
Or temporarily add a key binding to the *-set.xml file:<br />
<br />
<syntaxhighlight lang="xml"><br />
<key n="96"><br />
<name>Backtick</name><br />
<desc>Open marker adjust dialog</desc><br />
<binding><br />
<command>dialog-show</command><br />
<dialog-name>marker-adjust</dialog-name><br />
</binding><br />
</key><br />
</syntaxhighlight><br />
<br />
The dialog allows to move a red cross around, which has the blinking marker circle in the middle. Note that ctrl- and shift-modifiers modulate the slider movements. Ctrl makes positioning coarser, and shift finer. The [Reset] button moves the marker back to aircraft origin, the [Center] button centers the sliders, and the [Dump] button dumps the marker coordinates to the terminal, for example:<br />
<br />
<syntaxhighlight lang="xml"><br />
<marker><br />
<x-m>1.1425</x-m><br />
<y-m>0.1994</y-m><br />
<z-m>-0.0844</z-m><br />
<scale>2.0489</scale><br />
</marker><br />
</syntaxhighlight><br />
<br />
This just needs to be copied to the tutorial XML file.<br />
<br />
=== Message/audio ===<br />
Groups <step> and <end> can have one or more <message> entries, and one or more <audio> entries. If more are used of a kind, then the tutorial chooses one at random. If <audio> are available, then the contents are interpreted as file name of a *.wav sample, which is appended to the <audio-dir> path defined at the <tutorial> top level (default: "") and played by the tutorial system. Otherwise the <message> is handed over to the voice system, and synthesized to speech by the Festival speech synthesizer (if installed). In either case the chosen <message> is displayed on top of the screen. Neither <message> nor <audio> are mandatory.<br />
<br />
Because one and the same <message> string can be displayed *and* be synthesized, which can be problematic in some cases, there is a way to specify parts for either display *or* voice synthesizer: "{<display part>|<voice part}". Example:<br />
<br />
<syntaxhighlight lang="xml"><br />
<message>Press the {No1|number one} button!</message><br />
</syntaxhighlight><br />
<br />
Here, "No1" would be displayed on the screen, but "number one" would be sent to the speech synthesis system. This can also be used to add invisible but audible exclamation marks: "Press the button{|!}"<br />
<br />
=== Condition ===<br />
These are explained in detail in [[$FG_ROOT]]/Docs/README.conditions. Here's just one example:<br />
<br />
<syntaxhighlight lang="xml"><br />
<condition><br />
<less-than><br />
<property>/foo/bar</property><br />
<value>12</value><br />
</less-than><br />
</condition><br />
</syntaxhighlight><br />
<br />
This condition is true when the value of /foo/bar is less than 12, and false otherwise.<br />
<br />
[[Category:Aircraft enhancement]]<br />
[[Category:Nasal]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Aircraft_checklists&diff=59445Aircraft checklists2013-04-11T20:49:25Z<p>F-JYL: How to reload checklist</p>
<hr />
<div>[[File:Aircraft Checklists dialog.jpg|thumb|The Aircraft Checklists dialog]]<br />
As of V2.9, [[FlightGear]] can display '''aircraft checklists''' in a standardized way, under Help > Aircraft Checklists. To learn more about creating custom checklists, see [https://gitorious.org/fg/fgdata/blobs/master/Docs/README.checklists [[$FG_ROOT]]/Docs/README.checklists] and the c172p as the reference implementation. Increasingly, the [[Tutorials]] system is also extended such that it may make use of aircraft checklists. <br />
<br />
Checklists are situated under <tt>/sim/checklists</tt>. As the checklists may be quite long, it is recommended that they are put in a separate file using the following entry in the <tt>-set.xml</tt> file of the aircraft:<br />
<br />
<syntaxhighlight lang="xml"><br />
<checklists include="c172-checklists.xml"/><br />
</syntaxhighlight><br />
<br />
Each individual checklist is created under a <checklist> XML tag, with the following sub-properties:<br />
<br />
* <code><title></code> The name of the checklist<br />
* <code><page></code> One or more pages from the checklist, containing one or more of the following:<br />
** <code><item></code> A checklist item, containing<br />
*** <code><name></code> The item name, to appear on the left hand side of the checklist<br />
*** <code><value></code> One or more values, to appear on the right hand side of the checklist. Second and and subsequent <value> tags are displayed underneath each other. It is recommended that the <value> tags are kept short, to minimize the size of the displayed checklist.<br />
*** <code><condition></code> An optional [[Howto:Animate models#Conditions|condition node]] that evaluates when the checklist item is complete. Incomplete checklist items are shown in yellow, while completed items are shown in green.<br />
*** <code><marker></code> An optional marker node that is used to display a circle around a control when the user clicks a "?" button next to the item. This contains <x-m>, <y-m>, <z-m> and <scale> sub-elements and uses the [[Tutorials#Marker|tutorial marker]].<br />
<br />
For simple checklists the <page> element can be omitted and <item> entries placed directly under the <checklist>.<br />
<br />
The following example shows a simple checklists XML file:<br />
<br />
<syntaxhighlight lang="xml"><br />
<PropertyList><br />
<checklist><br />
<title>After Landing</title> <br />
<item><br />
<name>Carburetor Heat</name><br />
<value>COLD</value><br />
<condition><br />
<equals><br />
<property>/controls/anti-ice/engine[0]/carb-heat</property><br />
<value>0</value><br />
</equals><br />
</condition><br />
<marker><br />
<x-m>-0.3225</x-m><br />
<y-m>-0.0850</y-m><br />
<z-m>-0.2117</z-m><br />
<scale>2.0500</scale><br />
</marker> <br />
</item><br />
<item><br />
<name>Wing Flaps</name><br />
<value>UP</value><br />
</item><br />
</checklist><br />
<checklist><br />
<title>Getting hamburger</title><br />
<page><br />
<item><br />
...<br />
</item><br />
</page><br />
</checklist><br />
</PropertyList><br />
</syntaxhighlight><br />
<br />
See the [[Cessna 172P]] for an example of how this all fits together.<br />
<br />
==Reloading Checklists==<br />
<br />
Cut and paste this little code snippet in nasal console and excecute it :<br />
<br />
var checklist="777-200-checklists.xml";<br />
var checklist_path=sprintf("%s/%s",getprop("/sim/aircraft-dir"),checklist);<br />
var data = io.read_properties(checklist_path,"/sim/checklists");<br />
<br />
Change the first variable to the name of the file you are editing.<br />
<br />
== External link ==<br />
* [https://gitorious.org/fg/fgdata/blobs/master/Docs/README.checklists [[$FG_ROOT]]/Docs/README.checklists]<br />
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38325.html Aircraft Checklists] (mailing list)<br />
<br />
[[Category:Aircraft enhancement]]</div>F-JYLhttps://wiki.flightgear.org/w/index.php?title=Howto:Syntax_highlighting_for_Nasal&diff=59386Howto:Syntax highlighting for Nasal2013-04-06T07:03:13Z<p>F-JYL: /* gEdit */ add info for nasal.xml and xml embedded content support</p>
<hr />
<div>There's '''[[Nasal]] syntax-highlighting''' support available for some editors, which is a big advantage, as it makes Nasal coding much easier. It can often point to syntax errors and so reduce the number of tedious time-consuming and unproductive [[FlightGear]] runs.<br />
<br />
== Notepad++ ==<br />
http://dl.dropbox.com/u/1463693/nasal.xml<br />
<br />
Instructions are here: http://superuser.com/questions/62474/notepad-custom-syntax-highlighting-setting-where-to-look-for-it<br />
<br />
== jEdit ==<br />
There's a syntax highlighting mode for jEdit, programmer's text editor<br />
<br />
Included are some of Nasal's internal functions and those functions currently implemented in NasalSys.cxx<br />
To use, add the content of the catalog inside your own catalog (do NOT overwrite the file) and nasal.xml in /home/USER/.jedit/modes<br />
<br />
Restart jEdit and you can use it. Current extension is .nas, you can add your own extension and functions.<br />
This mode is heavily based on the Javascript mode.<br />
<br />
Get it here: http://www.jedit.org/<br />
<br />
==gEdit==<br />
<br />
[[File:Philosopher's nasal highlighting in gEdit.jpeg|400px|thumb|Screen shot illustrating syntax highlighting in gEdit]]<br />
<br />
'''Philosopher''' on the FlightGear Forum has created a syntax highlighter for gEdit- a popular and simple Text Editor for Mac OSX and Linux.<br />
<br />
http://theomegahangar.flymerlion.com/downloads/nasal.lang<br />
<br />
Download the ''nasal.lang'' file from the link above or from the first post of this forum topic http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265 and:<br />
<br />
If you use Mac, move it into your ''Applications/gedit/Contents/Resources/share/gtksourceview-2.0/language specs'' folder.<br />
And for linux, move it into your ''/usr/share/gtksourceview-X.0/language-specs'' folder.<br />
nasal.xml has to be moved into ''/usr/share/gedit/plugins/snippets/'' folder and edit ''/usr/share/gtksourceview-X.0/language-specs/xml.lang'' to add the embedded xml content support.<br />
<br />
== Vim ==<br />
It also makes understanding other people's code easier. One such editor is the free vim or its gui variant gvim. <br />
<br />
It's not for everyone but it's free, and testing it doesn't hurt: http://www.vim.org/. <br />
<br />
The syntax definition file comes with the FlightGear code (http://gitorious.org/fg/flightgear/blobs/next/scripts/syntax/nasal.vim). Highlighting works even for Nasal embedded in XML files (type ":set ft=nasal", where ft stands for file-type)<br />
<br />
Here's an example, which demonstrates a short code segment with three syntax errors as well as the highlighting of a matching pair of parentheses (yellow) and trailing spaces (blue x). (The leading blue dots aren't on by default. They help to spot tab crimes.)<br />
<br />
[[File:Vim-nasal-syntax-highlighting.png|400px|thumb|Screen shot illustrating syntax highlighting in Vim]]<br />
<br />
==KDE Editors==<br />
There's a highlighting definition for nasal available at '''kde-files.org''' (http://kde-files.org/content/show.php/Nasal+highlighting?content=154555)<br />
<br />
Download the file and copy it into ~/.kde4/share/apps/katepart/syntax/ (you can create the folders if they don't exist yet).<br />
<br />
Note that the syntax highlighting in KDE doesn't set colors, it just identifies structural elements, colors are defined by the '''schemas''' used by each editor, thus you get consistent highlighting between different languages.<br />
<br />
The highlighting file should work with all editors based on the katepart: KWrite, Kate, and the editor component of KDevelop.<br />
<br />
== Sublime Text 2 ==<br />
Scripts and installation instructions are here: https://github.com/freevryheid/nasal<br />
[[File:Sublime Text 2 syntax highlighting.png|400px|thumb|Sublime Text 2 syntax highlighting]]<br />
<br />
== Other editors ==<br />
Nasal being syntactically very close to other programming languages like C, Php or JavaScript, you can get some usable highlighting even without real Nasal support:<br />
<br />
* TextMate [http://flightgear.org/forums/viewtopic.php?f=30&t=12495&p=128116&hilit=syntax+nasal#p127828]<br />
* SciTe [http://flightgear.org/forums/viewtopic.php?f=30&t=9260&p=94521&hilit=syntax+nasal#p94521]<br />
<br />
== FlightGear Wiki ==<br />
A common approach in code examples on the wiki is to use php syntax highlighting beween <code>&lt;syntaxhighlight&gt;</code>:<br />
<br />
<nowiki><syntaxhighlight lang="php"><br />
# hello.nas<br />
print('Hello World!');<br />
</syntaxhighlight></nowiki><br />
<br />
Which renders into:<br />
<syntaxhighlight lang="php"><br />
# hello.nas<br />
print('Hello World!');<br />
</syntaxhighlight><br />
<br />
[[Category:Nasal howto]]<br />
<br />
== Related ==<br />
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265&p=164155#p164155<br />
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=12495<br />
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=15972<br />
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=9812</div>F-JYL