https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Gijs&feedformat=atomFlightGear wiki - User contributions [en]2024-03-28T13:00:25ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Preset_Properties&diff=139565Preset Properties2024-03-25T16:12:00Z<p>Gijs: Fix vor-id</p>
<hr />
<div>{{stub}}<br />
{{See also|Fixing Presets}}<br />
{{Startup}}<br />
<br />
[[FlightGear]] currently uses these properties to set up the [[aircraft]]'s initial situation :<br />
<br />
'''/sim/presets/airport-id''' - The ICAO identifier for an airport waypoint, such as "KJFK" or "EGLL". See also the runway property. An airport identifier takes precedence over vor-id , ndb-id , or fix , but is overridden by latitude-deg and longitude-deg .<br />
<br />
'''/sim/presets/airspeed-kt'''<br />
<br />
'''/sim/presets/altitude-ft''' - If this property has a value greater than -9990, then FlightGear will use it to set the initial altitude MSL, unless the glideslope-deg property is also set.<br />
<br />
'''/sim/presets/carrier'''<br />
<br />
'''/sim/presets/fix''' - The identifier for a fix or intersection of some kind. All other waypoints take precedence over a fix. This property should be renamed to fix-id .<br />
<br />
'''/sim/presets/heading-deg''' - The aircraft's initial heading in degrees. FlightGear may also use this property to select a default runway in some situations.<br />
<br />
'''/sim/presets/latitude-deg''' - If an explicit longitude and latitude are supplied, FlightGear will use that; otherwise, it will look for an airport-id , vor-id , ndb-id , fix , and then finally default to KSFO if nothing else is available.<br />
<br />
'''/sim/presets/longitude-deg''' - See latitude-deg.<br />
<br />
'''/sim/presets/mach'''<br />
<br />
'''/sim/presets/ndb-id''' - The identifier for an NDB waypoint, such as "OW" or "YSH". An NDB takes precedence over fix.<br />
<br />
'''/sim/presets/onground''' - True if the aircraft should start on the ground, false otherwise.<br />
<br />
'''/sim/presets/parkpos'''<br />
<br />
'''/sim/presets/pitch-deg'''<br />
<br />
'''/sim/presets/roll-deg'''<br />
<br />
'''/sim/presets/runway''' - The name of a runway, such as "22" or "11R", for an onground start or an initial approach path. This property makes sense only with the airport-id property. <br />
<br />
'''/sim/presets/speed-down-fps'''<br />
<br />
'''/sim/presets/speed-east-fps'''<br />
<br />
'''/sim/presets/speed-north-fps'''<br />
<br />
'''/sim/presets/speed-set'''<br />
<br />
'''/sim/presets/trim'''<br />
<br />
'''/sim/presets/uBody-fps'''<br />
<br />
'''/sim/presets/vBody-fps'''<br />
<br />
'''/sim/presets/vor-id''' - The identifier for a VOR waypoint, such as "YOW" or "ART". A VOR takes precedence over ndb-id and fix .<br />
<br />
'''/sim/presets/wBody-fps'''</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump&diff=139564FlightGear wiki:Village pump2024-03-25T15:01:38Z<p>Gijs: /* Forum registration problem */</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}<br />
{{shortcut|FGW:VP}}<br />
<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 <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.<br />
<br />
Old discussions 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 />
__TOC__<br />
<br />
== MediaWiki updated to 1.39.6 ==<br />
<br />
We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)<br />
<br />
== Embedded YouTube videos broken ==<br />
<br />
It seems that the [[mw:Extension:EmbedVideo|EmbedVideo extension]] was removed at some point. Consequently, pages such as [[Howto:Creating FlightGear Promo Videos]] are broken. At present, the best replacements seems to be [[mw:Extension:EmbedVideo_(fork)|a fork]] and [[mw:Extension:YouTube|Extension:YouTube]].<br />
<br />
—'''''[[User:Red Leader|<span style="color:red">Red Leader</span>]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 19:21, 30 January 2024 (UTC)<br />
<br />
: Hi,<br />
: Thanks for the report. It was introduced by today's update, but should be fixed now.<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:21, 30 January 2024 (UTC)<br />
<br />
:: Confirmed, thanks. And I’d completely forgotten about {{[[Template:Wikipedia|wikipedia]]}}. 😅<br />
:: '''''[[User:Red Leader|<span style="color:red">Red Leader</span>]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 21:57, 30 January 2024 (UTC)<br />
<br />
== Forum registration problem ==<br />
<br />
Hello,<br />
I would like to register on the forum, but I tried several times without success. I sent an email to the administrator some time ago, but it seems to have been lost. I don't know what to do, is there somebody here who could help? Please tell me if you need additional information.<br />
Thanks very much in advance. [[User:Kestrel|Kestrel]] ([[User talk:Kestrel|talk]]) 13:14, 25 March 2024 (UTC)<br />
<br />
: Hi,<br />
: That's unfortunate! You can find my email address at https://forum.flightgear.org/contact.php Please try again if you've done that before, I'll actively monitor the address for any incoming messages, and let me know if you don't get a reply.<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:01, 25 March 2024 (UTC) (forum admin)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Portal:Developer&diff=139523Portal:Developer2024-03-18T15:31:38Z<p>Gijs: Remove some outdated info</p>
<hr />
<div>{{Main page/Header<br />
|title=Welcome to the developer portal<br />
|introduction=Please visit [http://forum.flightgear.org our forum] if you cannot find what you're looking for.<br />
|rightbox=<br />
<!-------------------------------------------------------------<br />
Portal overview<br />
--------------------------------------------------------------><br />
|rightcolumn1= </div><br />
<span style="font-size:105%; font-weight:bold">[[FlightGear and Git|Development repository status]]</span><br /><br />
<center style="padding-top:.9em;">{{GitStatus}}</center><br />
<br />
|rightcolumn2= </div><br />
<span style="font-size:105%; font-weight:bold">Getting started</span><br /><br />
<span style="font-style:italic;"><br />
[[How the FlightGear project works]] <br/><br />
[[Howto: Understand the FlightGear development process|The development process]] · [[Release plan]]<br/><br />
[[Building FlightGear]] · [[FlightGear and Git|Git]] · [[FlightGear Build Server|Build server]]<br/><br />
[[Property tree]] · [[File formats]] · [[Tools of the Trade]] · {{tickets|Bug tracker}}</span><br />
<br />
|rightcolumn3= </div><br />
<span style="font-size:105%; font-weight:bold">Feeds</span><br /><br />
<span style="font-style:italic;"><br />
[https://forum.flightgear.org/feed.php Forum posts]<br/><br />
[http://wiki.flightgear.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom Wiki changes]<br/><br />
[https://sourceforge.net/p/flightgear/codetickets/feed.rss Bugs]<br/><br />
{{repo link<br />
| site = sf<br />
| repo = fgdata<br />
| view = rss<br />
| text = FGData RSS feed<br />
}}<br/><br />
{{repo link<br />
| site = sf<br />
| repo = flightgear<br />
| view = rss<br />
| text = FlightGear RSS feed<br />
}}<br/><br />
{{repo link<br />
| site = sf<br />
| repo = simgear<br />
| view = rss<br />
| text = SimGear RSS feed<br />
}}<br />
</span><br />
<br />
|rightcolumn4= </div><br />
<span style="font-size:105%; font-weight:bold">General</span><br /><br />
<span style="font-style:italic;"><br />
[[Long Term Goals|Long term goals]] · [[:Category:Popular Community Requests|Popular Ideas]] · [[Virtual FSweekend Hackathon 2021]]<br/><br />
[[Improving Glider Realism|Improving glider realism]] / [[Improving Helicopter Realism|helicopter realism]]<br/><br />
[[Howto:Set up a multiplayer server|Setting up a multiplayer server]] · [[FlightGear Expo Checklist|Expo checklist]]</span><br />
<br />
|rightcolumn5= [[File:Portal aircraft.png|40px]]</div><br />
<span style="font-size:105%; font-weight:bold">[[Portal:Developer/Aircraft|Aircraft]]</span><br /><br />
<span style="font-style:italic;"><br />
[[Howto:Troubleshooting Aircraft Performance Issues]]·<br />
[[Howto: Make an aircraft|Making an aircraft]] · [[Flight Dynamics Model|Flight dynamics model]]<br/><br />
[[Howto: 3D Aircraft Models|3D aircraft models]] · [[Howto: Edit a livery|Liveries]] · [[:Category:Aircraft resources|Resources]]<br/><br />
[[Soaring instrumentation sdk]] · [[Creating instruments for FG|Creating instruments]] · [[System dependent instruments|System dependent instruments]]<br/><br />
[[Howto: Design an autopilot|Designing an autopilot]]</span><br />
<br />
|rightcolumn6= [[File:Nuvola apps kaboodle.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Animations</span><br /><br />
<span style="font-style:italic;"><br />
[[Howto: Animate models|Animate models]] · [[Howto: Illuminate faces|Illuminate objects]]<br/><br />
[[Howto: Animate gear scissors|Gear scissors]] ([[Howto: Animate gear scissors using the tracking animation|with tracking animation]])<br/><br />
[[Howto: Make a clickable panel|Clickable panels]] · [[Knob / slider animation]]</span><br />
<br />
|rightcolumn7= [[File:Portal developer.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Core</span><br /><br />
<span style="font-style:italic;"><br />
[[:Category:FlightGear Core developers|List of Core Developers]] · [[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] <br/><br />
[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Nasal/CppBind|Adding scripting bindings]]<br/><br />
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]]<br/><br />
[[Built-in Profiler]] · [[Howto:Extend Nasal]] · [[Howto:Using Ada in FlightGear]]<br/><br />
[[Howto:Use Property Tree Objects]] · [[Code cleanup]] <br/><br />
[[FlightGear-Points of Interest]] · [[Request for comments]] <br/><br />
[[OpenSceneGraph]] · [[Rendering system improvements]] · [http://build.flightgear.org:8080 Jenkins build page] · {{tickets|Bug tracker}}</span><br />
<br />
|rightcolumn8= [[File:Portal scenery.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">[[Portal:Developer/Scenery|Scenery]]</span><br /><br />
<span style="font-style:italic;"><br />
[[Procedural Texturing]]<br/><br />
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]]<br/><br />
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]]<br/><br />
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]]<br/><br />
[[AI Traffic]] · [[Howto:Improve scenery in your area, or area of interest|Quick links: Improve your area - where & how to improve something you see]]</span><br />
<br />
|rightcolumn9= [[File:Nasallogo3.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">[[Nasal|Scripting]]</span><br /><br />
<span style="font-style:italic;"><br />
[[Nasal FAQ|Frequently asked questions]] · [[Howto:Write simple scripts in Nasal|Writing simple scripts]] <br /><br />
[[Nasal for C++ programmers]] · [[Nasal Variables|Variables and their types]] <br /><br />
[[Nasal Conditionals|Conditionals]] · [[Nasal Loops|Loops]] · [[Nasal Operators|Operators]] · [[Nasal Console|In-sim console]]</span><br />
<br />
|rightcolumn10= [[File:Animation Icon.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Effects and shaders</span><br /><br />
<span style="font-style:italic;"><br />
[[Shaders]] · [[Project Rembrandt]]<br/><br />
[[Howto:Shader Programming in FlightGear|Shader programming in FlightGear]]<br/><br />
[[Shader Coding - Best Practices|Best Practices]] · [[GLSL Shader Programming Resources|GLSL resources]]</span><br />
<br />
<!-------------------------------------------------------------<br />
Main sections<br />
--------------------------------------------------------------><br />
|sections=<br />
<br />
{{Main page/Leftbox|title=Put a piece of yourself into FlightGear!<br />
|contents=In FlightGear, "development" is [[Howto:Understand the FlightGear development process|anything that improves the project]]. So, it's not just code-related [[Howto:Start core development|core development]]. There's also [[Portal:Developer/Scenery|scenery development]], [[Portal:Developer/Aircraft|aircraft development]] and all the stuff you can see in the column here on the right. If you want an extended overview, check out the [[Volunteer]] page.<br />
<br />
Actually that's not all you can contribute. There's also documentation, with the [[FlightGear Manual]]... and this wiki of course! To contribute to the wiki, head off to the [[Portal:Wiki|Wiki Portal]]. There's a lot to do there too.<br />
<br />
If you want to get in touch with other developers, register an account at the [http://forum.flightgear.org/viewforum.php?f=18 forum], and for core development subscribe to the [[mailing list]] too and consider visiting the {{tickets|Bug tracker}}.<br />
<br />
Remember: we might call it volunteering, but what should drive you is [[How the FlightGear project works|the fun of doing something]].<br />
}}<br />
<br />
{{Main page/Leftbox|title=For core developers<br />
|contents=<br />
Visit [[:Category:Core development projects]] to see a list of currently ongoing projects!<br />
See [[:Category:Developer Plans]] to see a list of developer plans for the upcoming release.<br />
See [[request for comments]] for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress (admittedly a little outdated meanwhile). Also see the [http://build.flightgear.org:8080 Jenkins build page] and the {{tickets|Bug tracker}}.<br />
}}<br />
<br />
{{Main page/Leftbox|title=Coding Help Needed! (Updated 06/2020)<br />
|contents=<br />
* {{Progressbar|20}} [[Deboosting FlightGear|Replacing boost]]<br />
* {{Pending}} [[World Scenery 3.0 roadmap]] <br />
* {{Pending}} [[Reset & re-init]] <br />
* {{Pending}} [[Canvas Development]] - discusses possible future Canvas additions<br />
}}<br />
<br />
}}<br />
<br />
[[Category:Portals]]<br />
<br />
[[ca:Portal:Desenvolupador]]<br />
[[de:Portal:Entiwcklung]]<br />
[[es:Portal:Desarrollo]]<br />
[[fr:Portal:Développeur]]<br />
[[it:Portal:Sviluppo]]<br />
[[pl:Portal:Developer]]<br />
[[sr:Portal:Razvoj]]<br />
[[zh:Portal:Developer]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:Package_Management&diff=139522Template:Package Management2024-03-18T11:13:23Z<p>Gijs: Remove non-existing pages</p>
<hr />
<div>{{sidebar<br />
| name = Package Management<br />
| title = Package management<br />
| contentstyle= text-align: left;<br />
<br />
| content1 = Background<br />
* [[Aircraft rating system]]<br />
* [[Simplifying Aircraft Deployment]]<br />
| content2 = Implementation<br />
* [[Catalog metadata]]<br />
* [[Hangar catalog]]<br />
* [[FlightGear Package Manager]]<br />
| content3 = Front Ends<br />
* [[Aircraft Center]] (Nasal/Canvas-'''runtime''')<br />
* [[Integrated Qt5 Launcher]] (hard-coded '''startup''')<br />
* [[Phi]] (browser-based '''runtime''')<br />
| content4 = Related efforts<br />
* [[Reset & re-init]]<br />
* [[FlightGear Headless]]<br />
* [[Initializing Nasal early]]<br />
* [[FGCanvas]]<br />
}}<noinclude><br />
[[Category:Navigation templates]]<br />
[[Category:Undocumented templates]]<br />
</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=De_Havilland_DH.106_Comet&diff=139205De Havilland DH.106 Comet2024-02-27T17:16:52Z<p>Gijs: Links</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''de Havilland DH.106 "Comet"''' was the world's first commercial jet airliner. Developed and manufactured by [[:Category:De Havilland|de Havilland]] at its Hatfield Aerodrome in Hertfordshire, United Kingdom, the Comet 1 prototype first flew in 1949. It featured an aerodynamically clean design with four de Havilland Ghost turbojet engines buried in the wing roots, a pressurised cabin, and large square windows. For the era, it offered a relatively quiet, comfortable passenger cabin and was commercially promising at its debut in 1952<ref>{{wikipedia|de Havilland Comet}}</ref>. The [[FGAddon]] Comet is based on the Comet Model 4.<br />
<br />
== Specifications (Comet 4)<ref>https://aeropedia.com.au/content/dehavilland-dh-106-comet</ref> ==<br />
<br />
{| class="wikitable"<br />
|Max Take-Off Wt. || 162,000 lbs<br />
|-<br />
|Max Landing Wt. || <br />
|-<br />
|Empty Wt. || 75,424 lbs<br />
|-<br />
|Max payload || 20,286 lbs<br />
|-<br />
|Maximum Speed || <br />
|-<br />
|Normal Cruising Speed || 450 kts<br />
|-<br />
|Vfe (max flaps speed) || <br />
|-<br />
|Approach Speed || 124 kts<br />
|-<br />
|Landing Speed || <br />
|-<br />
|Stall Speed || <br />
|-<br />
|Service Ceiling || 42,000 feet <br/> 13000 m<br />
|-<br />
|Range || 4,000 nm<br />
|-<br />
|Landing Distance || <br />
|-<br />
|Take-off Distance || <br />
|}<br />
<br />
== Basic procedures ==<br />
<br />
== Gallery ==<br />
{{Gallery<br />
|DH106_instruments.png |<br />
|DH106_AirFrance.png|<br />
}}<br />
<br />
{{Appendix}}</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Airbus_A330&diff=139164Airbus A3302024-02-24T09:57:20Z<p>Gijs: Reverted edits by Enjoyer (talk) to last revision by Nish4t</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
<br />
This is an accurate, and complex recreation of the Airbus A330. This simulation of this majestic jet includes fully functional PFDs, realistic fly-by-wire technology and a pretty nice & detailed cockpit. <br />
<br />
== Airbus_A330 Overview ==<br />
<br />
Includes:<br />
* A330-203 (GE)<br />
* A330-223 (PW)<br />
* A330-243 (RR)<br />
* A330-223F (PW)<br />
* A330-243F (RR)<br />
* A330-303 (GE)<br />
* A330-323 (PW)<br />
* A330-343 (RR)<br />
* Voyager KC2/KC3 (A330-243 RR)<br />
* KC-30A (A330 MRTT) (A330-203 GE)<br />
* <br />
* <br />
* <br />
* <br />
<br />
See the right InfoBox for the Repository, or Download. <u>Remember to rename the aircraft's folder to "IDG-A33X"</u>.<br />
<br />
Solely, the KC2, KC3 and KC30A are damage comapatiable by OPRF standards and are the most advanced aerial refueling tankers currently available in FG.<br />
<br />
== The Team ==<br />
* FDM: Josh Davidson (Octal450)<br />
* Systems: Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)<br />
* Cockpit: Thorsten Herrmann (TH-555), Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)<br />
* Instruments: Josh Davidson (Octal450), Jonanthan Redpath (legoboyvdlp)<br />
<br />
== Livery Packs ==<br />
None.<br />
<br />
But there are plenty in flightgear's discord server if you want and some are also scattered in some renowned repositories over GitHub.<br />
<br />
[[Discord]]<br />
<br />
You can click here to join and then go to #livery_dev for more.<br />
<br />
== Credits ==<br />
Thank you to the following people for their contributions to this project!<br />
* Necolatis: Nasal Help, Canvas Help, MFD System<br />
* pinto: Nasal Help, JSBsim Help<br />
* Richard Harrison: Canvas Help, JSBsim Help<br />
* omega95: Some 3D Models<br />
* artix: Airbus Canvas Nav Display<br />
* Various others: Liveries, Some Code, Some 3D Models, Some Textures.<br />
<br />
== Aircraft help ==<br />
{| class="keytable"<br />
! Key !! Function<br />
|-<br />
| {{key press|1}}<br />
| Show Captains View<br />
|-<br />
| {{key press|2}}<br />
| Show First Officers View<br />
|-<br />
| {{key press|3}}<br />
| Show Overhead View<br />
|-<br />
| {{key press|4}}<br />
| Show Forward Pedestal View<br />
|-<br />
| {{key press|5}}<br />
| Show Aft Pedestal View<br />
|-<br />
| {{key press|6}}<br />
| Show FCU Panel View<br />
|-<br />
| {{key press|F1}}<br />
| Disengage/Decrease Reverse Thrust<br />
|-<br />
| {{key press|F2}}<br />
| Engage/Increase Reverse Thrust<br />
|-<br />
| {{key press|DEL}}<br />
| Toggle Thrust Reversers<br />
|-<br />
| {{key press|E}}<br />
| Set Idle Thrust<br />
|-<br />
| {{key press|F}}<br />
| Set TOGA Thrust<br />
|-<br />
| {{key press|CTRL|B}}<br />
| Cycle Spoilers<br />
|-<br />
| {{key press|Shift|B}}<br />
| Toggle Parking Brake<br />
|-<br />
| {{key press|CTRL|D}}<br />
| Disconnect Autothrottle<br />
|-<br />
| {{key press|Shift|D}}<br />
| Disconnect Autopilot<br />
|-<br />
| {{key press|CTRL|F}}<br />
| Set MCT/FLX Thrust<br />
|-<br />
| {{key press|Shift|F}}<br />
| Set CL Thrust<br />
|}<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:Forum_link&diff=139159Template:Forum link2024-02-23T08:20:04Z<p>Gijs: Add template data</p>
<hr />
<div><span class="plainlinks"><!--<br />
-->{{#if: {{{onlyicon|}}}<br />
| [[{{#if: {{{size|}}}<br />
| File:FlightGear_logo.png<br />
| File:FlightGear icon 15px.png<br />
}}<!--<br />
-->| {{{size|15px}}}<!--<br />
-->| {{#if: {{{title|{{{text|}}}}}}<br />
| {{#if: {{{title|}}}<br />
| {{#switch: {{{type|view}}}<br />
| view = <!--<br />
- -->{{#if: {{{p|}}}<br />
| {{LangSwitch<br />
| de = '{{{title}}}' Post im FlightGear-Forum.<br />
| en = '{{{title}}}' post on the FlightGear forum.<br />
}}<br />
| {{#if: {{{t|}}}<br />
| {{LangSwitch<br />
| de = '{{{title}}}' Thema des FlightGear-Forums.<br />
| en = '{{{title}}}' topic on the FlightGear forum.<br />
}}<br />
| {{LangSwitch<br />
| de = '{{{title}}}' Unterforum des FlightGear-Forums.<br />
| en = '{{{title}}}' subforum of the FlightGear forum.<br />
}}<br />
}}<br />
}}<br />
| member = <!--<br />
-->{{#if: {{{u|}}}<br />
| {{LangSwitch<br />
| de = Der FlightGear-Forum Benutzer '{{{title}}}'.<br />
| en = The FlightGear forum user '{{{title}}}'.<br />
}}<br />
| {{LangSwitch<br />
| de = Die Mitgliederliste des Forums.<br />
| en = The FlightGear forum listing.<br />
}}<br />
}}<br />
| search = <!--<br />
-->{{#if: {{{t|}}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear topic search for '{{{keywords}}}'.<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear topic search page.<br />
}}<br />
}}<br />
| {{#if: {{{f|}}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear subforum search for '{{{keywords}}}'.<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear subforum search page.<br />
}}<br />
}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear forum search for '{{{keywords}}}'.<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear forum search page.<br />
}}<br />
}}<br />
}}<br />
}}<br />
}}<br />
| {{{text}}}<br />
}}<br />
| {{LangSwitch<br />
| de = Dies ist ein Link zum FlightGear-Forum.<br />
| en = This is a link to the FlightGear forum.<br />
| fr = Ceci est un lien vers le forum FlightGear.<br />
}}<br />
}}<!--<br />
-->| link={{forum url<br />
| type = {{{type|view}}}<br />
| f{{#if:{{{f|}}}||NULL}} = {{{f}}}<br />
| t{{#if:{{{t|}}}||NULL}} = {{{t}}}<br />
| p{{#if:{{{p|}}}||NULL}} = {{{p}}}<br />
| u{{#if:{{{u|}}}||NULL}} = {{{u}}}<br />
| anchor{{#if:{{{anchor|}}}||NULL}} = {{{anchor}}}<br />
| hilit{{#if:{{{hilit|}}}||NULL}} = {{{hilit}}}<br />
| keywords{{#if:{{{keywords|}}}||NULL}} = {{{keywords}}}<br />
}}<!--<br />
-->]]<br />
| [{{forum url<br />
| type = {{{type|view}}}<br />
| f{{#if:{{{f|}}}||NULL}} = {{{f}}}<br />
| t{{#if:{{{t|}}}||NULL}} = {{{t}}}<br />
| p{{#if:{{{p|}}}||NULL}} = {{{p}}}<br />
| u{{#if:{{{u|}}}||NULL}} = {{{u}}}<br />
| anchor{{#if:{{{anchor|}}}||NULL}} = {{{anchor}}}<br />
| hilit{{#if:{{{hilit|}}}||NULL}} = {{{hilit}}}<br />
| keywords{{#if:{{{keywords|}}}||NULL}} = {{{keywords}}}<br />
}} <!--<br />
-->{{#if: {{{title|{{{text|}}}}}}<br />
| {{#if: {{{title|}}}<br />
| {{#switch: {{{type|view}}}<br />
| view = <!--<br />
-->{{#if: {{{p|}}}<br />
| {{LangSwitch<br />
| de = ''{{{title}}}'' Post im Forum<br />
| en = ''{{{title}}}'' post on the forum<br />
}}<br />
| {{#if: {{{t|}}}<br />
| {{LangSwitch<br />
| de = ''{{{title}}}'' Thema des Forums<br />
| en = ''{{{title}}}'' topic on the forum<br />
}}<br />
| {{LangSwitch<br />
| de = ''{{{title}}}'' Unterforum<br />
| en = ''{{{title}}}'' subforum<br />
}}<br />
}}<br />
}}<br />
| member = <!--<br />
-->{{#if: {{{u|}}}<br />
| {{LangSwitch<br />
| de = der Forum Benutzer ''{{{title}}}''<br />
| en = the forum user ''{{{title}}}''<br />
}}<br />
| {{LangSwitch<br />
| de = Die Mitgliederliste des Forums<br />
| en = the forum member listing''<br />
}}<br />
}}<br />
| search = <!--<br />
-->{{#if: {{{t|}}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear topic search for '{{{keywords}}}'<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear topic search page<br />
}}<br />
}}<br />
| {{#if: {{{f|}}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear subforum search for '{{{keywords}}}'<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear subforum search page<br />
}}<br />
}}<br />
| {{#if: {{{keywords|}}}<br />
| {{LangSwitch<br />
| en = FlightGear forum search for '{{{keywords}}}'<br />
}}<br />
| {{LangSwitch<br />
| en = FlightGear forum search page<br />
}}<br />
}}<br />
}}<br />
}}<br />
}}<br />
| {{{text}}}<br />
}}<br />
}}<!--<br />
-->]</span><!--<br />
-->{{#if: {{{noicon|}}}<br />
|<br />
| &#32;[[{{#if: {{{size|}}}<br />
| File:FlightGear_logo.png<br />
| File:FlightGear icon 15px.png<br />
}}<!--<br />
-->| {{{size|15px}}}<!--<br />
-->| {{LangSwitch<br />
| de = Dies ist ein Link zum FlightGear-Forum.<br />
| en = This is a link to the FlightGear forum.<br />
| fr = Ceci est un lien vers le forum FlightGear.<br />
}}<!--<br />
-->| link={{project infrastructure|forum|link=no}}<!--<br />
-->]]<br />
}}<br />
}}<noinclude><br />
{{Informative template|1=<br />
== Goal ==<br />
This template is used to create MediaWiki links - either via text or the icon - to subforums, topics and posts on the FlightGear forum.<br />
<br />
__TOC__<br />
== Usage ==<br />
<br />
{{obr}}'''forum link'''<br />
{{!}} ''title'' =<br />
{{!}} ''text'' =<br />
{{!}} ''type'' =<br />
{{!}} ''f'' =<br />
{{!}} ''t'' =<br />
{{!}} ''p'' =<br />
{{!}} ''anchor'' =<br />
{{!}} ''hilit'' =<br />
{{!}} ''u'' =<br />
{{!}} ''keywords'' =<br />
{{!}} ''noicon'' =<br />
{{!}} ''onlyicon'' =<br />
{{!}} ''size'' =<br />
{{cbr}}<br />
<br />
; title: Topic title (optional). This will be italicised and used to build the link text.<br />
<br />
; text: The link text (optional). This is an alternative to the {{param|title}} parameter and, if supplied, will be used for the link text.<br />
<br />
; type: The forum interface type that can be one of:<br />
<br />
:; view: The default value. This is used for URLs to posts, topics, and posts, via phpBB's <code>viewforum.php</code> or <code>viewtopic.php</code>.<br />
<br />
:; member: For URLs of a user on the forum, via phpBB's <code>memberlist.php</code>. This value will cause the {{param|f}}, {{param|t}}, {{param|p}}, {{param|anchor}}, and {{param|hilit}} parameters to be ignored.<br />
<br />
:; search: For URLs performing forum searches, via phpBB's <code>search.php</code>. This value will cause the {{param|p}}, {{param|anchor}}, and {{param|hilit}} parameters to be ignored.<br />
<br />
; f: Forum number (optional). Used with the {{param|type}} values of {{param||view}} and {{param||search}}.<br />
<br />
; t: Topic number (optional). Used with the {{param|type}} values of {{param||view}} and {{param||search}}.<br />
<br />
; p: Post number (optional). Used with the {{param|type}} value of {{param||view}}.<br />
<br />
; anchor: HTML anchor, used for jumping to posts (optional). Used with the {{param|type}} value of {{param||view}}.<br />
<br />
; hilit: Words on the forum posts to be highlighted (optional). Words should be separated by the plus character "+". Used with the {{param|type}} value of {{param||view}}.<br />
<br />
; u: User number (optional). Used with the {{param|type}} value of {{param||member}}.<br />
<br />
; keywords: The keywords to perform a forum search with (optional). Words should be separated by the plus character "+". Used with the {{param|type}} value of {{param||search}}.<br />
<br />
; noicon: If true, the little FlightGear icon ([[File:FlightGear icon 15px.png]]) will not be shown.<br />
<br />
; onlyicon: If true, only the little FlightGear icon ([[File:FlightGear icon 15px.png]]) will be shown.<br />
<br />
; size: The icon size (optional). This should be a valid MediaWiki image size value, e.g. {{param||32px}}.<br />
<br />
== Technical details ==<br />
<br />
This template uses the {{tl|forum url}} template to construct the URI part of the link. That template then uses the {{tl|project infrastructure}} template to provide the protocol and domain name part of the URI.<br />
<br />
== Examples ==<br />
<br />
=== No arguments ===<br />
<br />
{{obr}}forum link{{cbr}}<br />
<br />
{{forum link}}<br />
<br />
=== View mode ===<br />
<br />
==== A subforum (The FlightGear project) ====<br />
<br />
{{obr}}forum link{{!}}f=42{{cbr}}<br />
<br />
{{forum link|f=42}}<br />
<br />
{{obr}}forum link{{!}}title=The FlightGear project{{!}}f=42{{cbr}}<br />
<br />
{{forum link|title=The FlightGear project|f=42}}<br />
<br />
{{obr}}forum link{{!}}text=The FlightGear project{{!}}f=42{{cbr}}<br />
<br />
{{forum link|text=The FlightGear project|f=42}}<br />
<br />
{{obr}}forum link{{!}}title=The FlightGear project{{!}}f=42{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=The FlightGear project|f=42|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=The FlightGear project{{!}}f=42{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=The FlightGear project|f=42|onlyicon=yes}}<br />
<br />
==== A topic (FlightGear Newsletter) ====<br />
<br />
{{obr}}forum link{{!}}t=7794{{cbr}}<br />
<br />
{{forum link|t=7794}}<br />
<br />
{{obr}}forum link{{!}}title=FlightGear Newsletter{{!}}t=7794{{cbr}}<br />
<br />
{{forum link|title=FlightGear Newsletter|t=7794}}<br />
<br />
{{obr}}forum link{{!}}text=FlightGear Newsletter{{!}}t=7794{{cbr}}<br />
<br />
{{forum link|text=FlightGear Newsletter|t=7794}}<br />
<br />
{{obr}}forum link{{!}}title=FlightGear Newsletter{{!}}t=7794{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=FlightGear Newsletter|t=7794|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=FlightGear Newsletter{{!}}t=7794{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=FlightGear Newsletter|t=7794|onlyicon=yes}}<br />
<br />
==== A post (Re: Marking topics as "solved") ====<br />
<br />
{{obr}}forum link{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333}}<br />
<br />
{{obr}}forum link{{!}}text=Re: Marking topics as "solved"{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|text=Re: Marking topics as "solved"|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|onlyicon=yes}}<br />
<br />
==== Subforum, topic and post ====<br />
<br />
{{note|The {{param|f}} and {{param|t}} parameters are redundant in this URL.}}<br />
<br />
{{obr}}forum link{{!}}f=8{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|f=8|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}f=8{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|f=8|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}text=Re: Marking topics as "solved"{{!}}f=8{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|text=Re: Marking topics as "solved"|f=8|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}f=8{{!}}t=10805{{!}}p=111333{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|f=8|t=10805|p=111333|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}f=8{{!}}t=10805{{!}}p=111333{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|f=8|t=10805|p=111333|onlyicon=yes}}<br />
<br />
==== Topic and post ====<br />
<br />
{{note|The {{param|t}} parameter is redundant in this URL.}}<br />
<br />
{{obr}}forum link{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}text=Re: Marking topics as "solved"{{!}}t=10805{{!}}p=111333{{cbr}}<br />
<br />
{{forum link|text=Re: Marking topics as "solved"|t=10805|p=111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}p=111333{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|p=111333|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}p=111333{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|p=111333|onlyicon=yes}}<br />
<br />
==== Anchoring ====<br />
<br />
{{obr}}forum link{{!}}t=10805{{!}}anchor=p111333{{cbr}}<br />
<br />
{{forum link|t=10805|anchor=p111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}anchor=p111333{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|anchor=p111333}}<br />
<br />
{{obr}}forum link{{!}}text=Re: Marking topics as "solved"{{!}}t=10805{{!}}anchor=p111333{{cbr}}<br />
<br />
{{forum link|text=Re: Marking topics as "solved"|t=10805|anchor=p111333}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}anchor=p111333{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|anchor=p111333|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}t=10805{{!}}anchor=p111333{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|t=10805|anchor=p111333|onlyicon=yes}}<br />
<br />
==== Highlighting ====<br />
<br />
{{obr}}forum link{{!}}t=10805{{!}}hilit=board+index{{cbr}}<br />
<br />
{{forum link|t=10805|hilit=board+index}}<br />
<br />
{{obr}}forum link{{!}}title=board index{{!}}t=10805{{!}}hilit=board+index{{cbr}}<br />
<br />
{{forum link|title=board index|t=10805|hilit=board+index}}<br />
<br />
{{obr}}forum link{{!}}text=board index{{!}}t=10805{{!}}hilit=board+index{{cbr}}<br />
<br />
{{forum link|text=board index|t=10805|hilit=board+index}}<br />
<br />
{{obr}}forum link{{!}}title=board index{{!}}t=10805{{!}}hilit=board+index{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=board index|t=10805|hilit=board+index|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=board index{{!}}t=10805{{!}}hilit=board+index{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=board index|t=10805|hilit=board+index|onlyicon=yes}}<br />
<br />
===== Highlight a post =====<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}hilit=contains+a+problem{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|hilit=contains+a+problem}}<br />
<br />
=== Member mode ===<br />
<br />
==== Member listing ====<br />
<br />
{{obr}}forum link{{!}}type=member{{cbr}}<br />
<br />
{{forum link|type=member}}<br />
<br />
{{obr}}forum link{{!}}title=Forum member listing{{!}}type=member{{cbr}}<br />
<br />
{{forum link|title=Forum member listing|type=member}}<br />
<br />
{{obr}}forum link{{!}}text=Forum member listing{{!}}type=member{{cbr}}<br />
<br />
{{forum link|text=Forum member listing|type=member}}<br />
<br />
{{obr}}forum link{{!}}title=Forum member listing{{!}}type=member{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Forum member listing|type=member|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Forum member listing{{!}}type=member{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Forum member listing|type=member|onlyicon=yes}}<br />
<br />
==== Specific member ====<br />
<br />
{{obr}}forum link{{!}}type=member{{!}}u=2{{cbr}}<br />
<br />
{{forum link|type=member|u=2}}<br />
<br />
{{obr}}forum link{{!}}title=curt{{!}}type=member{{!}}u=2{{cbr}}<br />
<br />
{{forum link|title=curt|type=member|u=2}}<br />
<br />
{{obr}}forum link{{!}}text=curt{{!}}type=member{{!}}u=2{{cbr}}<br />
<br />
{{forum link|text=curt|type=member|u=2}}<br />
<br />
{{obr}}forum link{{!}}title=curt{{!}}type=member{{!}}u=2{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=curt|type=member|u=2|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=curt{{!}}type=member{{!}}u=2{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=curt|type=member|u=2|onlyicon=yes}}<br />
<br />
=== Search mode ===<br />
<br />
==== Search page ====<br />
<br />
{{obr}}forum link{{!}}type=search{{cbr}}<br />
<br />
{{forum link|type=search}}<br />
<br />
{{obr}}forum link{{!}}title=Search page{{!}}type=search{{cbr}}<br />
<br />
{{forum link|title=Search page|type=search}}<br />
<br />
{{obr}}forum link{{!}}text=Search page{{!}}type=search{{cbr}}<br />
<br />
{{forum link|text=Search page|type=search}}<br />
<br />
{{obr}}forum link{{!}}title=Search page{{!}}type=search{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Search page|type=search|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Search page{{!}}type=search{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Search page|type=search|onlyicon=yes}}<br />
<br />
==== Search everything ====<br />
<br />
{{obr}}forum link{{!}}type=search{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|type=search|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}text=Amphibious Cessna{{!}}type=search{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|text=Amphibious Cessna|type=search|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}keywords=c172p+floats{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|keywords=c172p+floats|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}keywords=c172p+floats{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|keywords=c172p+floats|onlyicon=yes}}<br />
<br />
==== Search a subforum ====<br />
<br />
{{obr}}forum link{{!}}type=search{{!}}f=4{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|type=search|f=4|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}f=4{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|f=4|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}text=Amphibious Cessna{{!}}type=search{{!}}f=4{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|text=Amphibious Cessna|type=search|f=4|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}f=4{{!}}keywords=c172p+floats{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|f=4|keywords=c172p+floats|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}f=4{{!}}keywords=c172p+floats{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|f=4|keywords=c172p+floats|onlyicon=yes}}<br />
<br />
==== Search a topic ====<br />
<br />
{{obr}}forum link{{!}}type=search{{!}}t=25157{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|type=search|t=25157|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}t=25157{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|t=25157|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}text=Amphibious Cessna{{!}}type=search{{!}}t=25157{{!}}keywords=c172p+floats{{cbr}}<br />
<br />
{{forum link|text=Amphibious Cessna|type=search|t=25157|keywords=c172p+floats}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}t=25157{{!}}keywords=c172p+floats{{!}}noicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|t=25157|keywords=c172p+floats|noicon=yes}}<br />
<br />
{{obr}}forum link{{!}}title=Amphibious Cessna{{!}}type=search{{!}}t=25157{{!}}keywords=c172p+floats{{!}}onlyicon=yes{{cbr}}<br />
<br />
{{forum link|title=Amphibious Cessna|type=search|t=25157|keywords=c172p+floats|onlyicon=yes}}<br />
<br />
=== Different icon sizes ===<br />
<br />
==== Text and icon ====<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}size=15px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|size=15px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}size=32px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|size=32px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}size=64px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|size=64px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}size=200px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|size=200px}}<br />
<br />
==== Icon only ====<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}onlyicon=yes{{!}}size=15px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|onlyicon=yes|size=15px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}onlyicon=yes{{!}}size=32px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|onlyicon=yes|size=32px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}onlyicon=yes{{!}}size=64px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|onlyicon=yes|size=64px}}<br />
<br />
{{obr}}forum link{{!}}title=Re: Marking topics as "solved"{{!}}p=111333{{!}}onlyicon=yes{{!}}size=200px{{cbr}}<br />
<br />
{{forum link|title=Re: Marking topics as "solved"|p=111333|onlyicon=yes|size=200px}}<br />
<br />
== Related templates ==<br />
<br />
* {{tl|forum}}<br />
* {{tl|project infrastructure}}<br />
* {{tl|forum url}}<br />
<br />
}}<br />
<br />
<templatedata><br />
{<br />
"params": {<br />
"onlyicon": {<br />
"description": "If true, only the little FlightGear icon will be shown.",<br />
"type": "boolean"<br />
},<br />
"size": {<br />
"label": "Icon size",<br />
"description": "This should be a valid MediaWiki image size value, e.g. 32px.",<br />
"type": "unknown"<br />
},<br />
"title": {<br />
"label": "Topic title",<br />
"description": "This will be italicised and used to build the link text.",<br />
"type": "string"<br />
},<br />
"text": {<br />
"label": "Link text",<br />
"description": "This is an alternative to the title parameter and, if supplied, will be used for the link text.",<br />
"type": "string"<br />
},<br />
"type": {<br />
"label": "Type",<br />
"description": "The forum interface type.",<br />
"type": "string",<br />
"suggestedvalues": [<br />
"view",<br />
"member",<br />
"search"<br />
],<br />
"default": "view"<br />
},<br />
"p": {<br />
"label": "Post id",<br />
"description": "Used with the type value of view.",<br />
"type": "number"<br />
},<br />
"t": {<br />
"label": "Topic id",<br />
"description": "Used with the type values of view and search.",<br />
"type": "number"<br />
},<br />
"u": {<br />
"label": "User id",<br />
"description": "Used with the type value of member.",<br />
"type": "number"<br />
},<br />
"keywords": {<br />
"label": "Keywords",<br />
"description": "The keywords to perform a forum search with (optional). Words should be separated by the plus character \"+\". Used with the type value of search.",<br />
"type": "string"<br />
},<br />
"f": {<br />
"label": "Forum id",<br />
"description": "Used with the type values of view and search.",<br />
"type": "number"<br />
},<br />
"anchor": {<br />
"label": "Anchor",<br />
"description": "Used for jumping to posts (optional). Used with the type value of view."<br />
},<br />
"hilit": {<br />
"description": "Words on the forum posts to be highlighted (optional). Words should be separated by the plus character \"+\". Used with the type value of view."<br />
},<br />
"noicon": {<br />
"description": "If true, the little FlightGear icon will not be shown.",<br />
"type": "boolean"<br />
}<br />
},<br />
"description": "This template is used to create MediaWiki links - either via text or the icon - to subforums, topics and posts on the FlightGear forum.",<br />
"paramOrder": [<br />
"title",<br />
"text",<br />
"type",<br />
"f",<br />
"t",<br />
"p",<br />
"u",<br />
"anchor",<br />
"hilit",<br />
"keywords",<br />
"noicon",<br />
"onlyicon",<br />
"size"<br />
]<br />
}<br />
</templatedata><br />
<br />
[[Category:Link templates]]</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2023-10&diff=139136Category:Screenshot of the month/2023-102024-02-18T12:24:56Z<p>Gijs: Created page with "See {{forum link|title=Submit your screenshot for the SOTM of October 2023|t=41745}} and {{forum link|title=Voting for the SOTM of October 2023|t=41775}}. Category:Screenshot of the month"</p>
<hr />
<div>See {{forum link|title=Submit your screenshot for the SOTM of October 2023|t=41745}} and {{forum link|title=Voting for the SOTM of October 2023|t=41775}}.<br />
<br />
[[Category:Screenshot of the month]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Piper_PA-18_over_lake_Coeur_d%27Alene.png&diff=139134File:Piper PA-18 over lake Coeur d'Alene.png2024-02-18T10:45:22Z<p>Gijs: Uploaded a work by {{forum link|title=Cyber_Gamer|type=member|u=28418}} from {{forum link|p=415544|title=Submit your screenshot for the SOTM of October 2023}} with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Cruisin' over lake Coeur d'Alene east of Spokane with the PA-18.}}<br />
|date=2023-10-24<br />
|source={{forum link|p=415544|title=Submit your screenshot for the SOTM of October 2023}}<br />
|author={{forum link|title=Cyber_Gamer|type=member|u=28418}}<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month/2023-10]]<br />
[[Category:Piper PA-18 Super Cub screenshots]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Grumman_F-14_Tomcat_Weapons_Operations&diff=139045Grumman F-14 Tomcat Weapons Operations2024-01-30T21:23:03Z<p>Gijs: /* Dual Control */ preferably use Template:Wikipedia, to differentiate it from an internal wiki link</p>
<hr />
<div>This page explains how to operate weapons and the related radar modes for the [[Grumman_F-14_Tomcat|Grumman F-14 Tomcat]].<br />
<br />
<br />
== Version Warning ==<br />
{{Note|<br />
Be aware that the documentation in this page refers to the development version of the F-14, which is maintained in a [https://github.com/Zaretto/fg-aircraft GitHub repository]. Some features might therefore not be available, if you use the less frequently updated version from [[FGAddon|FGAddon]].<br />
}}<br />
<br />
The development of the weapons and radar in the F-14 are related to [https://discord.gg/MBWnqHC4 Operation Red Flag], the premier military aviation organization for the flight simulator FlightGear!<br />
<br />
== Weapons Operation ==<br />
NB: Especially for gunning you might want to set SAS Roll to off to prevent the plane from oscillating when using aggressive stick input.<br />
<br />
NB: In some new versions of FlightGear, the {{Key press|w}} key is replaced by the {{Key press|m}} key to select weapons.<br />
<br />
===M61A1 Vulcan (gun)===<br />
*At startup, the ammunition store is filled with 675 round. There is an option on the '''Fuel and Stores''' dialog in the '''Tomcat Controls''' Menu to allow the gun to be reloaded<br />
*Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available {{Key press|:}}{{Key press|A}}{{Key press|H}}{{Key press|a}}. Having the HUD in this mode is not mandatory however when the HUD is in the right mode the guidance symbology will assist with target identification and aiming.<br />
*Select Gun mode with the Stick Weapon Mode Selector ({{Key press|w}}). A pipper, the G symbol with a number showing approximately the remaining rounds x 100 and a closure rate scale are displayed in the HUD. The closure rate scale is active only if a target has been locked ({{Key press|y}}) by the radar with TWS AUTO mode (diamond on the HUD).<br />
*Switch Master Arm on cycle with {{Key press|CTRL-w}}, the X on the G symbol means Master Arm off or in training mode.<br />
* Press {{Key press|e}} to fire the gun.<br />
<br />
===AIM-9M Sidewinders===<br />
*Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD light" has 4 sidewinders, "FAD", "FAD heavy" and "Bombcat" have 2 of them.<br />
*Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available ({{Key press|:}}{{Key press|A}}{{Key press|H}}{{Key press|a}}).<br />
* Select "SW" mode with the Stick Weapon Mode Selector ({{Key press|w}}).<br />
*Switch to the RIO view ({{Key press|Ctrl|v}}).<br />
*Select pylons 1 and 8, down position, on the Armament panel, on RIO's left console. A shortcut toggles these two switches so you can select or deselect all AIM-9 in one keyboard stroke ({{Key press|Ctrl|m}}) without leaving pilot's view. If you have 4 sidewinders, then after shooting the first 2 you need to toggle the pylons 1 and 8 into the up position.<br />
*Switch back to the pilot's view ({{Key press|Ctrl|v}}).<br />
* Switch Master Arm on, you hear the search signal of the seeker head, a low volume buzz sound.<br />
*Now prior to be fired, the AIM-9 must have a lock on a target. Multiplayers, AI aircraft, and AI tankers can be locked (radar lock with {{Key press|y}}). The minimal lock distance is 10 NM, the target must be approximately inside a 80° cone centred on datum line. When locked, the signal buzz volume becomes louder and the 2 red "LOCK" lights at the top of the canopy frame are lit. For best results try to shoot ({{Key press|e}}) at a 3 to 6 NM range and with the target centred on the aircraft velocity vector (when the 2 red "SHOOT" lights at the top of the canopy frame are lit). The missile will explode at the smaller distance possible. However if this distance is above 70 meters, it will continue its trajectory without guidance.<br />
<br />
===AIM-7 Sparrow and AIM-54 Phoenix===<br />
*Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD" has 2 Sparrows and 4 Phoenix, "FAD light" has 4 Sparrows, "FAD heavy" has 6 Phoenix.<br />
*Select A/A Mode, master arm etc. as with Sidewinders.<br />
*Select "SP-PH" mode with the Stick Weapon Mode Selector ({{Key press|w}}).<br />
*Set the appropriate pylons into the up position: 3, 4, 5, 6 for the pylons below the belly, 1 and 8 under the wing in up position for "FAD" (2 Sparrows, the 2 Sidewinders are selected in the down position of 1/8.<br />
*Obtain a radar lock by using {{Key press|y}} the the next target and {{Key press|Ctrl|y}} the the previous target.<br />
*Launching the missiles is the same as for the Sidewinders, but there is no growling sound and the max shooting range are larger: up to 30+ nm for the {{Wikipedia|AIM-7_Sparrow}} and 100+ nm for the {{Wikipedia|AIM-54_Phoenix}}.<br />
<br />
===Bombs===<br />
NB: only CCIP mode is implemented - and only dumb low-drag unguided bombs - and only single release.<br />
*Select the right weapons' set using the menu: Tomcat Controls > Fuel and Stores: "Bombcat" has 4 Mk83 bombs.<br />
*Master arm on<br />
*Select A/G Mode<br />
*Select "Off" mode with the Stick Weapon Mode Selector (yes, off - you will still be able to pull the trigger in A/G mode).<br />
*Set the appropriate pylons into the up position: 3, 4, 5, 6.<br />
*No need for locking with the radar. There is a CCIP in the HUD.<br />
*Set wing sweep to manual and 55 deg.<br />
*Make sure you are high above terrain (e.g. 10000 ft) and initiate a steep dive to 40 degs. Deploy speed brakes in order not to get too fast. Make sure wings are levelled, otherwise the bomb will not hit even though the pipper is on the target (there is currently no vertical bomb fall line implemented in the HUD).<br />
*Release the bomb when the target is within the circle around the bottom of the HUD and before you reach 2000 ft above ground.<br />
<br />
Find out what is working for you - it is not that simple.<br />
<br />
<br />
==Radar Scan Modes==<br />
===Key Bindings===<br />
{{Key press|y}}: Next target<br />
<br />
{{Key press|Shift|y}}: Cycle azimuth field width<br />
<br />
{{Key press|Shift|u}}: Undesignate (very useful for PAL mode)<br />
<br />
{{Key press|i}}: Tilt radar up<br />
<br />
{{Key press|Shift|i}}: Tilt radar down<br />
<br />
{{Key press|Shift|d}}: Cycle number of bars<br />
<br />
{{Key press|Ctrl|n}}: Cycle radar scan modes<br />
<br />
{{Key press|d}}: Pilot Auto Lockon mode (PAL) [click {{Key press|Ctrl|n}} to exit]<br />
<br />
{{Key press|r}}: Single Target Track mode (STT)<br />
<br />
{{Key press|Shift|e}} and {{Key press|r}}: Radar range when not in PAL mode.<br />
<br />
{{Key press|q}}: Radar standby<br />
<br />
===Modes===<br />
Use {{Key press|Ctrl|n}} to cycle between radar scan modes (alternatively press the corresponding buttons on the RIO's front console).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Mode !! Notes<br />
|-<br />
| '''PD SEARCH''' || Has the longest RCS sensitivity of the modes. Will only show targets that has above/below a certain closure-rate. Notchable. Will not show targets altitude or heading.<br />
|-<br />
| '''RWS''' || Medium RCS sensitivity. Notchable.<br />
|-<br />
| '''P SEARCH''' || Basically a ground/sea radar. Cannot be notched.<br />
|-<br />
| '''PAL''' || Scans the area around the HUD, fixed at 10nm range. Automatically enters STT for anything it sees. Note that when in this mode, none of the RIO mode push buttons will lit up.<br />
|-<br />
| '''P STT''' || Single target track. Cannot be notched, wont produce closure-rate output.<br />
|-<br />
| '''PD STT''' || Single target track. Can be notched.<br />
|-<br />
| '''TWS MAN''' || Once a target has been scanned twice within some seconds, groundtrack (headings) is displayed on TID. Only has 2 options for bars/az combinations. Has the shortest RCS sensitivity of the modes. Notchable.<br />
|-<br />
| '''TWS AUTO''' || Is disabled / does not work.<br />
|} <br />
<br />
==== Missile Notes ====<br />
<br />
* AIM-7 needs STT mode.<br />
<br />
* AIM-9 needs STT mode or TWS mode with something selected. Or radar in standby, then it will lock onto whatever is at bore.<br />
<br />
* AIM-54 need either STT or TWS with something selected (in which case it will go active immediately with reduced range).<br />
<br />
====How to Notch====<br />
Notching means flying manoeuvrers to make an aircraft less detectable on radar/evade it. It is sometimes called beaming.<br />
<br />
If you are flying against an F-14, keep the F-14 on your 3 or 9 o'clock and make sure that seen from the F-14 point of view that he will see terrain behind you.<br />
<br />
====Datalink====<br />
<br />
Aircraft on datalink that are inside the radar field will be shown on TID (even if the radar is standby). The backseater needs to take care to enter the datalink channel at the top of the right panel (IFF is taken care of by the pilot at the top of the pilot's right panel).<br />
<br />
====Misc====<br />
<br />
RWS/TWS MAN/PDSearch/PSearch will able to show 19 targets, MP or not. TWS can show groundtrack on max 10 of them.<br />
<br />
Radar elevation, commanded and actual, is shown on gauge left of DDD display. It is in relation to horizon in all modes except PAL.<br />
<br />
Each mode remembers its own bars and az settings. So if you switch to 1 bar in RWS, and then switch to PD SEARCH it might have 8 bars, when you switch back to RWS you will have 1 bar again. Radar antennae elevation/azimuth is shared between modes though.<br />
<br />
====Moving Radar Azimuth Field Left and Right====<br />
<br />
There are no key bindings for moving the radar azimuth field left and right when not 120. To use this, enable it from FG joystick dialog.<br />
<br />
====Dual Control====<br />
<br />
When connecting as a Radar Intercept Officer (RIO aka. {{wikipedia|weapon systems officer|WSO}}), the pilot will no longer be able to control the radar - it is all done from the dual control RIO MP seat. The RIO is able to control the station switches.<br />
<br />
Make sure that you as a RIO do not switch modes and stuff too fast, allow for a short moment for each change you make to propagate to the pilot.<br />
<br />
If the RIO selects something and it fails pilot screen will show selection handover fails, the pilot could try to press y to repeat the handover and if successful, and then ask RIO to cycle modes if RIO had commanded STT, to make the pilots radar try to enter STT again.<br />
<br />
==Related Information==<br />
{{#ev:youtube|ibHrZyAQ1C4|||A tutorial video explaining how to fire the F-14B's missiles.|frame}}</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump&diff=139044FlightGear wiki:Village pump2024-01-30T21:21:34Z<p>Gijs: /* Embedded YouTube videos broken */ fixed</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}<br />
{{shortcut|FGW:VP}}<br />
<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 <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.<br />
<br />
Old discussions 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 />
__TOC__<br />
<br />
== MediaWiki updated to 1.39.6 ==<br />
<br />
We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)<br />
<br />
== Embedded YouTube videos broken ==<br />
<br />
It seems that the [[mw:Extension:EmbedVideo|EmbedVideo extension]] was removed at some point. Consequently, pages such as [[Howto:Creating FlightGear Promo Videos]] are broken. At present, the best replacements seems to be [[mw:Extension:EmbedVideo_(fork)|a fork]] and [[mw:Extension:YouTube|Extension:YouTube]].<br />
<br />
—'''''[[User:Red Leader|<span style="color:red">Red Leader</span>]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 19:21, 30 January 2024 (UTC)<br />
<br />
: Hi,<br />
: Thanks for the report. It was introduced by today's update, but should be fixed now.<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:21, 30 January 2024 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=MediaWiki:Sidebar&diff=139039MediaWiki:Sidebar2024-01-30T15:29:05Z<p>Gijs: Update links</p>
<hr />
<div>* navigation<br />
** mainpage|mainpage-description<br />
<!--** portal-url|portal--><br />
** recentchanges-url|recentchanges<br />
** FlightGear wiki:Village pump|Village pump<br />
** Help:Contents|Help<br />
* Portals<br />
** Portal:User|User<br />
** Portal:Developer|Developer<br />
<!--<br />
** Portal:Cockpit Building / Embedded<br />
** Portal:Unmanned Aerial Vehicles<br />
--><br />
** Portal:Wiki|Wiki<br />
* FlightGear<br />
** https://www.flightgear.org/|Website<br />
** https://forum.flightgear.org/|Forum<br />
** Mailing lists|Mailing&nbsp;lists<br />
** https://sourceforge.net/p/flightgear/codetickets/|Bug&nbsp;tracker<br />
** https://sourceforge.net/p/flightgear/_list/git|Source<br />
** https://scenery.flightgear.org/|Scenery<br />
** https://liveries.flightgear.org/|Liveries<br />
** http://build.flightgear.org:8080/|Build&nbsp;server<br />
<!--* SEARCH--><br />
* TOOLBOX<br />
* LANGUAGES</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear&diff=139037FlightGear2024-01-30T13:47:36Z<p>Gijs: Wiki link to LaRCsim</p>
<hr />
<div>{{Infobox Software<br />
|title = FlightGear Flight Simulator<br />
|logo = FlightGear logo.png<br />
|logosize = 200px<br />
|image = Boeing 777-200ER cockpit.jpg<br />
|alt = The cockpit of the [[Boeing 777-200ER]]<br />
|developedby = FlightGear developers & contributors<br />
|initialrelease = July 17, 1997<br />
|latestrelease = {{current release|full}} ({{#time: j F Y |{{current release|fulldate}}}})<br />
|writtenin = C/C++/Nasal<br />
|os = Windows, macOS, Linux, and FreeBSD<ref>{{cite web|url=http://www.flightgear.org/download/main-program/|title=http://www.flightgear.org/download/main-program/|accessdate=February 15, 2015}}</ref><br />
|platform = Cross-platform<br />
|developmentstatus = Active (1996-present)<br />
|type = Flight simulator<br />
|license = [[GNU General Public License]]<br />
|website = http://www.flightgear.org/<br />
}}<br />
[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]<br />
'''FlightGear Flight Simulator''' (often shortened to '''FlightGear''' or '''FGFS''') is a sophisticated, free, and completely open-source flight simulator framework, created by volunteers. FlightGear is released under the terms of the [[GNU General Public License]]. FlightGear is mostly written in the C and C++ programming languages.<br />
<br />
Increasingly detailed and realistic versions of FlightGear have been released every year since the project was started in 1996.<br />
<br />
The latest public release is available as a free download at [http://www.flightgear.org/download/ flightgear.org/download/], with easy to install packages for a variety of operating systems including Microsoft Windows, Mac OS X, and Linux.<br />
<br />
== History ==<br />
{{main article|FlightGear History}}<br />
<br />
FlightGear development started with an online proposal in 1996, using custom 3D graphics code. Development of an [[OpenGL]] based version was spearheaded by Curtis Olson starting in 1997. Many people have contributed to the project in the years since its inception.<br />
<br />
FlightGear incorporated other open-source resources, including the [[LaRCsim]] flight model from NASA, and freely available elevation data. The first working binaries, using OpenGL for 3D graphic code, came out in 1997. Enthusiastic development of newer versions for several years resulted in progressively more stable and advanced versions. By 2001, the team was releasing new beta versions regularly, and by 2005, the maturity of software lead to more widespread reviews, and increased popularity. 2007 marked a formal transition out of beta development with the release of version 1.0.0, ten years after FlightGear's first release in 1997.<br />
<br />
[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]<br />
<br />
In 2008, version 1.9.0 of FlightGear included a major change from [[PLIB]] to [[OSG]], which caused the temporarily loss of some features like 3D clouds and shadows, while newly added features, such as particles, imparted another degree of realism to the simulation. <br />
<br />
== Software ==<br />
<br />
The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.<br />
<br />
This customizability of FlightGear is illustrated by the wide range of aircraft models that are available in FlightGear, from [[:Category:Gliders|glider]]s to [[Helicopter]]s, and from [[:Category:Airliners|airliners]] to [[Military aircraft|fighter jets]]. These aircraft models have been contributed by many different people.<br />
<br />
The FlightGear aircraft in general use one of two main flight data models [[JSBSim]] and [[YAsim]]. Currently only one terrain engine is used, TerraGear. Weather effects include 3D clouds, lighting effects, and time of day.<br />
<br />
=== Flight Dynamics Models ===<br />
[[Flight Dynamics Models]] (FDM) are how the flight for an aircraft is simulated in the program. FlightGear uses a variety of internally written and imported flight model projects. Any aircraft must be programmed to use one of these models. Currently FlightGear is the only flight graphical flight simulator all the FDM are used for, and UIUC and YASim were developed specifically for FlightGear. <br />
<br />
Early version used a FDM based on [[LaRCsim]] by NASA, which was replaced with more flexible FDM. <br />
<br />
* [[JSBSim]] - the default flight dynamics model software since 2000.<br />
* [[YASim]] - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.<br />
* [[UIUC]] - developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim. Once being widely used, it is nowadays longer included in FlightGear by default.<br />
* FlightGear can also be setup to render using inputs from an external FDM source, such as from [[MATLAB]].<br />
* Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.<br />
<br />
=== FlightGear dependencies ===<br />
Unlike commercial software titles, the main output of the project is simply the release of a collection of code. To turn it into a usable program it must be compiled for a given platform. The software libraries used to create FlightGear have varied over time. The main one is [[SimGear]], which is the underlying sim engine for FlightGear. [[TerraGear]] is not a dependency, but simply a name for the default terrain data program in FlightGear. OpenAL is used for sound/audio software, including support for SDL (since 0.9.5). PLIB is used for hardware support routines, formerly used for sound support also which was taken over by OpenAL. [[OpenGL]] is used for its integrated 3D graphics routines, and other hardware acceleration (namely DirectX) is not supported. [[OpenSceneGraph]] is also integrated into FlightGear. Finally, Simple DirectMedia Layer is a software library which is used for compiling. Some of the dependencies vary depending on which platform the code is being compiled for. FlightGear users must either compile the code themselves, or find a third party to release a binary, if it is not among the ones available from the project.<br />
<br />
== Hardware ==<br />
Hardware needed for FlightGear is narrowed to machines that support [[OpenGL]] and 3D hardware acceleration, with NVIDIA hardware having better support. Early versions had support for 3dfx cards, though this dropped as hardware requirements increased.<br />
<br />
[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]<br />
== Add-ons and customization ==<br />
There are programs that are either integrated into FlightGear (dependencies) or perform a function with it. Some of these are included in the release of FlightGear for a specific platform but made by the project, while others are independently distributed but are hosted by the FlightGear project. <br />
<br />
One major additional software is the actual interface for launching an executable of FlightGear. For most of its early life FlightGear was only run through [[command line]] interfaces. However, [[FlightGear Launch Control]] has been included since 0.9.3 in 2003. ''[[KFreeFlight]]'' is a launcher/front-end for KDE. ''FGTools'' is an alternative windows launcher front-end. ''FGKicker'' is a GTK+ based front-end.<br />
<br />
Other significant programs include editors and projects for terrain data. ''[[Atlas]]'' is a chart/map support for FlightGear; ''[[Kelpie Flight Planner]]'' is a Java based flight planner for FlightGear. Finally, ''[[WorldEditor]]'' is an editor for airport runways and taxiways.<br />
<br />
=== Aircraft ===<br />
{{Main article|Table of models}}<br />
<br />
FlightGear started out with an aircraft included in NASA's LaRCsim, a Navion, which was replaced by a Cessna 172 by 2000. UIUC as well as JSBsim development brought several more aircraft with them, as did the development of YASim which have since become the main FDM used in FG. Over 400 aircraft in more than 900 unique liveries, are available for version 2.12, although only a few are included in the base package.<br />
<br />
[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]<br />
<br />
=== Scenery ===<br />
{{Main article|Scenery}}<br />
FlightGears [[world scenery]] project contains elevation and landclass data of the enitre world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].<br />
<br />
=== Networking and multi-display ===<br />
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Multiplayer Howto|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.<br />
<br />
Several instances of FlightGear can be synchronized to allow for a multi-monitor environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.<br />
<br />
== FlightGear code vs. binaries ==<br />
Unlike most commercial software, the project release dates only apply to a release of code, not an executable program. To create a runnable program the code must be compiled, which requires several specific libraries, including some general ones and, in some cases some platform specific ones. However, since this too difficult for most mainstream users, other contributors will work to make binaries available for a specific platform and operating system. These packages vary in their stability, performance, dependencies, and how up to date they are with the code base. For example, some older binaries work on Mac OS 9 but newer releases require specific Mac OS X versions.<br />
<br />
For example, by late 2012 the latest code release was 2.10 (pre-release) and 2.8.0 (final). Binaries are generally available for the last final code release on all major platforms. [http://www.flightgear.org/download/main-program/ Click here to proceed to the flightgear binaries download page]<br />
<br />
Binaries for other platforms such as IRIX are no longer supported, although pre-1.0 releases may work and can be found in the [[FlightGear Git|git source code repositories]].<br />
<br />
==Applications and usages==<br />
{{Main article|Professional and educational FlightGear users}}<br />
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.<br />
<br />
== Reviews ==<br />
{{Main article|FlightGear Reviews}}<br />
<br />
== External links ==<br />
{{Main article|Links}}<br />
* {{Wikipedia|FlightGear}}<br />
* [http://www.flightgear.org Official website]<br />
* {{forum link|text=Forum}}<br />
* [https://sourceforge.net/p/flightgear/codetickets/ Bug tracker]<br />
* [http://www.flightgear.org/proposal-3.0.1 Original FlightGear Proposal]<br />
<br />
{{Appendix}}<br />
<br />
[[Category:FlightGear]]<br />
<br />
[[ca:FlightGear]]<br />
[[de:FlightGear]]<br />
[[es:FlightGear]]<br />
[[fr:FlightGear]]<br />
[[it:FlightGear]]<br />
[[nl:FlightGear]]<br />
[[pl:FlightGear]]<br />
[[pt:FlightGear]]<br />
[[pt-br:FlightGear]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump&diff=139035FlightGear wiki:Village pump2024-01-30T09:31:36Z<p>Gijs: /* MediaWiki updated to 1.39.6 */ new section</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}<br />
{{shortcut|FGW:VP}}<br />
<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 <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.<br />
<br />
Old discussions 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 />
__TOC__<br />
<br />
== MediaWiki updated to 1.39.6 ==<br />
<br />
We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump&diff=139034FlightGear wiki:Village pump2024-01-30T09:29:47Z<p>Gijs: Move to archive</p>
<hr />
<div>__NEWSECTIONLINK__<br />
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}<br />
{{shortcut|FGW:VP}}<br />
<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 <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.<br />
<br />
Old discussions 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 />
__TOC__</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_wiki:Village_pump/Archive_2022&diff=139033FlightGear wiki:Village pump/Archive 20222024-01-30T09:29:08Z<p>Gijs: 2022 content of FlightGear wiki:Village pump</p>
<hr />
<div>{{talk archive}}<br />
<br />
== Backup and shutdown plan ==<br />
<br />
Hello. In the past, I have contributed to sites such as Yahoo Answers, which disappointingly ended up shutting down with little notice after operating seemingly well for a long time, i.e. over a decade.<br />
<br />
In the unlikely case that this wiki ends up shutting down at some point in future, I would like to ask whether the wiki has a backup plan. Since text compresses efficiently, will a compressed archive of users' contributions be released? And how long in advance would there be a warning? [[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 13:13, 13 February 2022 (UTC)<br />
<br />
: Hi Gorden and welcome!<br />
: Yes, we make regular backups. There is no intention to shutdown the wiki at any point and as we are not a commercial project, we have absolutely no reason to withhold any data that you've contributed. I could imagine that at some point the contents of the wiki may be moved to a different platform (who knows what'll be available in years from now), but definitely not deleted. Note that the wiki is also occasionally archived to the [http://web.archive.org/web/*/wiki.flightgear.org* Internet Archive].<br />
: Does that give you enough reassurance to contribute?<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:25, 14 February 2022 (UTC)<br />
<br />
:: Yes, sounds good. Thanks much. As a side note, the Internet Archive saves pages' lastest revisions but not their full history. It just serves as additional surface backup. [[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 20:48, 18 February 2022 (UTC)<br />
<br />
== 2022 Newsletters forward/backward links are broken ==<br />
<br />
Recently the chain of newsletters for 2022 appears to have been broken. There was a February newsletter and a April newsletter, but no March newsletter, and the Feb and Mar newsletters did not link to each other.<br />
<br />
In the last day or so, [[User:Aepcam]] has created a March newsletter. But the links are still not working. For example both the March and April newsletters have "Create next Edition >" links that would create a new May newsletter.<br />
<br />
See:<br />
<br />
* [[FlightGear_Newsletter_February_2022]]<br />
* [[FlightGear_Newsletter_March_2022]]<br />
* [[FlightGear_Newsletter_April_2022]]<br />
<br />
Could someone who knows how these things work, take a look?<br />
<br />
Thanks.<br />
<br />
[[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 20:16, 18 April 2022 (UTC)<br />
<br />
: Hi,<br />
: This looks to me as if it's still working like it used to? "Please help us write the coming edition" links to the April newsletter (which is being written now) and "Create next edition" links to May, which is the next edition after that. Or did you mean something else?<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:04, 19 April 2022 (UTC)<br />
<br />
:: The problem i was seeing has been fixed by this change (i think by you?): https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_March_2022&diff=134988&oldid=134976<br />
<br />
:: Thanks.<br />
<br />
:: [[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 10:16, 19 April 2022 (UTC)<br />
<br />
::: Ah ok, good to know. That was an easy fix :-)<br />
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:35, 19 April 2022 (UTC)<br />
<br />
== Favicon not showing ==<br />
<br />
I've just noticed that the favicon, set up back in [[FlightGear wiki:Village pump/Archive 2021#MediaWiki updated to 1.35.1]] is no longer showing. Does <code>$wgFavicon</code> need to be re-added to the <code>LocalSettings.php</code> file? Cheers!<br />
<br />
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:22, 5 July 2022 (UTC)<br />
<br />
: Should be fixed now. Thanks for notifying!<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:32, 5 July 2022 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Cessna_208B_Caravan_sunrise_over_Caribbean_with_HDR.jpg&diff=138979File:Cessna 208B Caravan sunrise over Caribbean with HDR.jpg2024-01-17T09:10:49Z<p>Gijs: Typo</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Enjoying the early morning in the Caribbean with the [[Cessna 208 Caravan|Cessna 208B Caravan]] - [[HDR]].}}<br />
|date=2023-12-15<br />
|source={{forum link|p=417359|title=Submit your screenshot for the SOTM of december 2023}}<br />
|author= {{forum link|title=Cyber_Gamer|type=member|u=28418}}<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Cessna aircraft screenshots]]<br />
[[Category:Compositor screenshots]]<br />
[[Category:Screenshot of the month/2023-12]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Cessna_208B_Caravan_sunrise_over_Caribbean_with_HDR.jpg&diff=138972File:Cessna 208B Caravan sunrise over Caribbean with HDR.jpg2024-01-15T14:40:59Z<p>Gijs: Add info, license and categories</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Enjoying the early morning in the Caribbean with the [[Cessna 208 Caravan|Cessna 208B Caravan]] - [[HDR]].}}<br />
|date=2023-12-15<br />
|source={{forum link|p=417359|title=Submit your screenshot for the SOTM of december 2023}}<br />
|author= {{forum link|title=Cyber_Gamer|type=member|u=28418}}<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Cessna aircraft screenshots]]<br />
[[Category:Compositor screenshot]]<br />
[[Category:Screenshot of the month/2023-12]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2023-12&diff=138971Category:Screenshot of the month/2023-122024-01-15T14:39:22Z<p>Gijs: Created page with "See {{forum link|title=Submit your screenshot for the SOTM of december 2023|t=41879}} and {{forum link|title=Voting for the SOTM of december 2023|t=41957}}. Category:Screen..."</p>
<hr />
<div>See {{forum link|title=Submit your screenshot for the SOTM of december 2023|t=41879}} and {{forum link|title=Voting for the SOTM of december 2023|t=41957}}.<br />
<br />
[[Category:Screenshot of the month]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Cessna_208B_Caravan_sunrise_over_Caribbean_with_HDR.jpg&diff=138969File:Cessna 208B Caravan sunrise over Caribbean with HDR.jpg2024-01-15T14:29:59Z<p>Gijs: </p>
<hr />
<div>Enjoying the early morning in the Caribbean with the [[Cessna 208B Caravan]] - HDR.</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Cygd-c140-winter.jpg&diff=138968File:Cygd-c140-winter.jpg2024-01-15T14:07:31Z<p>Gijs: Adding information, still missing proper license according to :Category:License templates</p>
<hr />
<div><br />
<br />
=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Approaching Georgian Bay (Lake Huron) in winter. Note the detail of the inland water.}}<br />
|date=2024-01-12<br />
|source={{own}}<br />
|author=[[User:David.megginson|David.megginson]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==</div>Gijshttps://wiki.flightgear.org/w/index.php?title=North_American_X-15&diff=138831North American X-152023-12-21T12:36:44Z<p>Gijs: Set hangar to FGaddon to auto-populate links</p>
<hr />
<div>{{infobox Aircraft<br />
|ready = spacetrip<br />
|image = X15.jpg<br />
|name = North American X-15<br />
|hangar = fgaddon<br />
|aircraft = X15<br />
|type = Rocket-powered aircraft<br />
|fdm = JSBSim<br />
|status =<br />
|authors = Mike Hill, Jon S. Berndt (FDM), John Check, Enrique Laso (new model)<br />
|fgname = X15, X15-new<br />
}}<br />
<br />
A famous rocket plane for [[FlightGear]]. Of the two out three surviving X-15, one is at the [[National Air and Space Museum]]<br />
<br />
[[Image:Spacetripready.png|link=FlightGear_space_program]]<br />
<br />
== Development status/Issues/Todo ==<br />
'''Outside:'''<br />
* textures are bumpy<br />
* flaps are not animated (''fixed in future release shown below'')<br />
* rudder, ailerons and pitch elevator are not animated (''fixed in future release shown below'')<br />
* cockpit windows are not transparent (''fixed in future release shown below'')<br />
* aircraft has no shadow<br />
* no aircraft light available (''actual aircraft did not have external lights'')<br />
* there is no stream behind the rocket engine visible (''fixed in future release shown below'')<br />
<br />
'''3d Cockpit:'''<br />
* no 3d cockpit available (''fixed in future release shown below'')<br />
<br />
'''General:'''<br />
* engines have no sound<br />
* no hud available (''actual aircraft did not have HUD but can be activated as usual for flight test'')<br />
* aircraft has no braking parachutes (''actual aircraft did not have brake parachute'')<br />
<br />
== Ballistic high altitude flight and rendering ==<br />
<br />
FlightGear is able to render the scene for the ballistic high altitude flight the X-15 is capable of (at least on a modern graphics card), but it needs some special adjustments to do so. Assume the visibility at arc top should be 500 km:<br />
<br />
* from the menu, LOD bare range needs to be set to 500000.0<br />
* in the property browser, /sim/rendering/camera-group/zfar needs to be set to 500000.0<br />
* in the weather menu, configure visibility at high altitude to 500000.0 m<br />
* use the Atmospheric Light Scattering framework to get the correct visuals of being outside the atmosphere in the rendering menu<br />
<br />
[[File:X-15-iceland03.jpg|250px|The X-15 on the falling leg of a high-altitude ballistic trajectory above Iceland]]<br />
[[File:X-15-iceland04.jpg|250px|The X-15 on the falling leg of a high-altitude ballistic trajectory above Iceland]]<br />
[[File:X-15-iceland05.jpg|250px|The X-15 on the falling leg of a high-altitude ballistic trajectory above Iceland]]<br />
<br />
== Electrical system modelling (nasal proposal) ==<br />
<br />
The X-15 electrical and hydraulic systems are peculiar because they use a pair of hydrogen peroxide fuelled APUs to provide power to the aircraft instead of being connected to the main engine. While the mechanical power drain from those systems can be neglected for regular aircraft where most of the fuel is used for propulsion, this cannot be done for accurate computation of fuel consumption from the APU. And depletion of APU fuel can leave you without a controllable aircraft ...<br />
<br />
As hydraulics and electrical systems have many common feature, the following is only an introduction to the electrical system design.<br />
The system can be split in the following generic components (each one having its class in Nasal)<br />
* Mechanically driven generators (''hyd : pumps'')<br />
* Batteries (''hyd : accumulators'')<br />
* Transformers (that includes transformer rectifiers and inverters)<br />
* Buses (''hyd: circuit'')<br />
* Bus ties (''hyd : power transfer unit'')<br />
* Circuit breakers (''hyd : relief valve'')<br />
* Terminal loads which include<br />
- Lights<br />
- Instruments<br />
- Switches<br />
- Actuators ...<br />
<br />
The system will be updated per display cycle in order to achieve several goals :<br />
* compute the mechanical load to for the generators<br />
* drain each generator according to the tie logics between buses (achieved through a priority of connections towards buses)<br />
* compute the properties of the electrical power applied to each terminal load<br />
<br />
As it stands, the electrical system is built by instantiation of objects for each class e.g.<br />
<syntaxhighlight lang="nasal" enclose="div"><br />
var X_15_electrical = ElectricalSystem.new ();<br />
var AC_1 = ElectricalBus.new(X_15_electrical);<br />
var gen_1 = Generator.new (X_15_electrical,<br />
regulated_AC_voltage,<br />
generator_rating,<br />
AC_1, #bus<br />
40000, #low rpm<br />
25000, #cutoff rpm<br />
3); #priority on bus<br />
var AC_voltmeter_1 = Gauge.new (AC_1,<br />
0, #low value<br />
250, #hi value<br />
drop_on_shutdown, #behavior when power is lost<br />
200, #nominal voltage<br />
0.5, #relaxation time<br />
0.5, #nominal electrical consumption<br />
"/systems/electrical/voltage-1"); #displayed value<br />
</syntaxhighlight><br />
<br />
And the chain of updates (tree traversal) is as follows <br />
<syntaxhighlight lang="nasal" enclose="div"><br />
ElectricalSystem.update = func (delta_t)<br />
{<br />
var index = 0;<br />
#first we look which are the loads attached to each generator<br />
forindex (index; me.generators) me.generators[index].feed();<br />
#then external connections <br />
forindex (index; me.externals) me.externals[index].feed();<br />
#including batteries<br />
forindex (index; me.batteries) me.batteries[index].feedBus();<br />
#then we compute the load coming from each of the terminal loads<br />
forindex (index; me.terminal_loads) me.terminal_loads[index].powerDemand(delta_t);<br />
#compute the change in battery load<br />
forindex (index; me.batteries) me.batteries[index].updateCharge(delta_t);<br />
#compute the mechanical power demand for each of the generators<br />
forindex (index; me.generators) me.generators[index].computePowerConsumption(delta_t);<br />
#reset all cyclic elements<br />
forindex (index; me.buses) me.buses[index].resetForCycle();<br />
forindex (index; me.terminal_loads) me.terminal_loads[index].resetForCycle();<br />
}<br />
</syntaxhighlight><br />
<br />
Due to the number of function calls and the genericity of the approach it may be interesting in the future to include this models in the C++ code, even though current benchmarks do no seem to show a noticeable drop in frame rate<br />
<br />
{{North American}}<br />
<br />
[[Category:Experimental aircraft]]<br />
[[Category:Hypersonic aircraft]]<br />
[[Category:Parasite aircraft]]<br />
[[Category:Rocket-powered aircraft]]<br />
[[Category:Spaceplanes]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Building_using_CMake_-_Windows&diff=138822Building using CMake - Windows2023-12-19T09:51:23Z<p>Gijs: Update MSVC and fix minor typos</p>
<hr />
<div>{{Main article|Building FlightGear}}<br />
This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 10 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.<br />
<br />
As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.<br />
<br />
== Required software ==<br />
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.<br />
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2022] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 12/19/2023, the latest version of the compiler is "MSVC v143 - VS 2022 C++ x64/86 build tools".<br />
* [https://www.qt.io/download-open-source/ Qt5] for the [[Integrated Qt5 Launcher]]. Download the online installer, and choose the version matching your toolchain of Visual Studio e.g. "Qt 5.15.2 --> MSVC 2019 64-bit". Any version past 5.9 will be fine; latest 5.x recommended. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling.<br />
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!<br />
<br />
== Obtaining source ==<br />
{{Main article|FlightGear and Git}}<br />
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).<br />
Using an organized directory (see below) will help significantly.<br />
<br />
The commands to run are:<br />
<br />
{{code|git clone https://git.code.sf.net/p/flightgear/simgear simgear}}<br />
<br />
{{code|git clone https://git.code.sf.net/p/flightgear/flightgear flightgear}}<br />
<br />
{{code|git clone https://git.code.sf.net/p/flightgear/fgdata fgdata}}<br />
<br />
{{code|git clone https://git.code.sf.net/p/flightgear/windows-3rd-party windows-3rd-party}}<br />
<br />
{{code|git clone -b fgfs-osg-36-1 https://github.com/zakalawe/osg.git osg}}<br />
<br />
{{caution| Cloning fgdata from SourceForge often fails. Therefore, we suggest you use a GitLab mirror repository. Instead of<br />
<br />
{{code|git clone https://git.code.sf.net/p/flightgear/fgdata fgdata}} <br />
<br />
call:<br />
<br />
{{code|git clone https://gitlab.com/flightgear/fgdata.git fgdata}}<br />
<br />
and after downloaded all data:<br />
<br />
<syntaxhighlight lang="bash"><br />
cd fgdata<br />
git checkout next<br />
git remote set-url origin https://git.code.sf.net/p/flightgear/fgdata<br />
git pull<br />
</syntaxhighlight><br />
}}<br />
<br />
After downloading these, I would suggest assembling a folder structure as below:<br />
<br />
== Directory Tree ==<br />
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.<br />
<br />
<br />
Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.<br />
<br />
<tt><br />
: FlightGearBuild / </tt> (Main root directory) <tt><br />
:: fgdata / </tt> (FlightGear data files) <tt><br />
:: flightgear / </tt> (FlightGear sources) <tt><br />
:: install / </tt> (Directory where you will install the built binaries to) <tt><br />
::: launch.bat / </tt> (launch script if desired, see below) <tt><br />
:: osg / </tt> (OSG sources) <tt><br />
:: simgear / </tt> (SimGear sources) <tt><br />
:: windows-3rd-party /<br />
:: build.bat / </tt> (build script, see below) <tt><br />
:: update.bat / </tt> (update script, see below)<br />
<br />
== Building ==<br />
=== Scripted Compilation ===<br />
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.<br />
<br />
{{collapsible script<br />
| type = Windows batch file<br />
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG<br />
| lang = batch<br />
| script =<br />
SET PATH=%PATH%;%ProgramFiles%\CMake\bin<br />
SET QT5SDK64=C:\Qt\5.15.2\msvc2019_64<br />
SET CMAKE_TOOLCHAIN="Visual Studio 17 2022"<br />
SET ROOT_DIR=C:\path\to\FlightGearBuild<br />
<br />
md osg-build<br />
md simgear-build<br />
md flightgear-build<br />
<br />
cd %ROOT_DIR%\osg-build<br />
<br />
cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^<br />
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^<br />
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^<br />
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^<br />
-DWIN32_USE_MP:BOOL=ON ^<br />
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install<br />
cmake --build . --config RelWithDebInfo --target INSTALL<br />
<br />
cd %ROOT_DIR%\simgear-build<br />
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^<br />
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^<br />
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install<br />
cmake --build . --config RelWithDebInfo --target INSTALL<br />
<br />
cd %ROOT_DIR%\flightgear-build<br />
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^<br />
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^<br />
-DCMAKE_PREFIX_PATH=%QT5SDK64% ^<br />
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON<br />
<br />
cmake --build . --config RelWithDebInfo --target INSTALL<br />
<br />
pause<br />
| show = 1<br />
}}<br />
<br />
Before starting to use the script, you need to edit the top few lines of the script. You will have to:<br />
<br />
1. Set the path to your CMake installation.<br />
<br />
2. Ensure that the path to your QT SDK is correct for your version of MSVC.<br />
<br />
3. Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 15 2017" for MSVC 2017.<br />
<br />
4. Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)<br />
<br />
==== Post-compilation: Launching FlightGear ====<br />
'''In the debugger:'''<br />
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG. <br />
<br />
To launch FlightGear from Visual Studio, you can follow the following steps:<br />
The first time only:<br />
# Make sure you set your build type to RelWithDebInfo in the top bar.<br />
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.<br />
# Press the green arrow (Local Windows Debugger) to start up FlightGear. <br />
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.<br />
<br />
Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!<br />
<br />
'''As a standard .exe:'''<br />
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).<br />
<br />
Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.<br />
This launch script should work, put into your /install/bin/ folder:<br />
{{collapsible script<br />
| type = Windows batch file<br />
| title = The <code>launch.bat</code> script for launching flightgear<br />
| lang = batch<br />
| script =<br />
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%<br />
fgfs.exe --launcher<br />
| show = 1<br />
}}<br />
<br />
Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.<br />
<br />
=== Updating ===<br />
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.<br />
<br />
{{collapsible script<br />
| type = Windows batch file<br />
| title = The <code>update.bat</code> script for updating repositories<br />
| lang = batch<br />
| script =<br />
SET ROOT_DIR=C:\path\to\FlightGearBuild<br />
<br />
cd %ROOT_DIR%\osg<br />
git pull<br />
<br />
cd %ROOT_DIR%\fgdata<br />
git pull<br />
<br />
cd %ROOT_DIR%\flightgear<br />
git pull<br />
<br />
cd %ROOT_DIR%\simgear<br />
git pull<br />
<br />
cd %ROOT_DIR%\windows-3rd-party<br />
git pull<br />
<br />
pause<br />
| show = 1<br />
}}<br />
<br />
=== Changing the Configuration ===<br />
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.<br />
<br />
In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.<br />
<br />
{{building}}<br />
[[fr:compiler flightear avec CMake - Windows]]<br />
[[Category:Windows specific]]<br />
[[Category:Hackathon Materials]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=User_talk:Macenal&diff=138820User talk:Macenal2023-12-18T09:41:51Z<p>Gijs: /* Internal wiki links */ new section</p>
<hr />
<div>{{Template:Welcome to the wiki|realName=|name=Macenal}}<br />
<br />
-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 22:33, 29 May 2023 (UTC)<br />
<br />
== Internal wiki links ==<br />
<br />
Hi,<br />
<br />
Thank you for your continuous contributions to the FlightGear wiki! Just one minor request: please use internal wiki links when referring to wiki articles. See the change I've made to [https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter&type=revision&diff=138819&oldid=138802 your newsletter edits here]. You can read more about the proper use of internal links at [[Help:Formatting#Links to other wiki pages]].<br />
<br />
Thanks! And please do let me know if you have any questions about editing the wiki!<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:41, 18 December 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter&diff=138819FlightGear Newsletter2023-12-18T09:38:34Z<p>Gijs: /* Archive */ use internal wiki link</p>
<hr />
<div>[[File:magagazine.png|right]]<br />
<br />
The '''FlightGear Newsletter''' is intended to provide a collection of the latest developments from the worldwide [[FlightGear]] community. With so much development ongoing, it's almost impossible for anyone to keep up. The newsletter was started in July 2009, and is presented on a monthly basis. It is a collaborative effort that is created, edited and distributed via the [[FlightGear Wiki]], and all FlightGear users, contributors and developers are invited to contribute.<br />
<br />
=== Archive ===<br />
{| class="prettytable"<br />
! align="left" | 2023<br />
! align="left" | 2022<br />
! align="left" | 2021<br />
! align="left" | 2020<br />
! align="left" | 2019<br />
! align="left" | 2018<br />
! align="left" | 2017<br />
! align="left" | 2016<br />
! align="left" | 2015<br />
! align="left" | 2014<br />
! align="left" | 2013<br />
! align="left" | 2012<br />
! align="left" | 2011<br />
! align="left" | 2010<br />
! align="left" | 2009<br />
|-<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2023|January]]<br />
* [[FlightGear Newsletter February 2023|February]]<br />
* [[FlightGear Newsletter March 2023|March]]<br />
* [[FlightGear Newsletter April 2023|April]]<br />
* [[FlightGear Newsletter May 2023|May]]<br />
* [[FlightGear Newsletter June 2023|June]]<br />
* [[FlightGear Newsletter July 2023|July]]<br />
* [[FlightGear Newsletter August 2023|August]]<br />
* [[FlightGear Newsletter September 2023|September]]<br />
* [[FlightGear_Newsletter October 2023|October]<br />
* [[FlightGear_Newsletter November 2023|November]<br />
* [[FlightGear_Newsletter December 2023|December]<br />
''(currently being written)''<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2022|January]]<br />
* [[FlightGear Newsletter February 2022|February]]<br />
* [[FlightGear Newsletter March 2022|March]]<br />
* [[FlightGear Newsletter April 2022|April]]<br />
* [[FlightGear Newsletter May 2022|May]] <br />
* June<br />
* [[FlightGear Newsletter July 2022|July]]<br />
* [[FlightGear Newsletter August 2022|August]]<br />
* [[FlightGear Newsletter September 2022|September]]<br />
* October<br />
* [[FlightGear Newsletter November 2022|November]]<br />
* [[FlightGear Newsletter December 2022|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2021|January]]<br />
* [[FlightGear Newsletter February 2021|February]]<br />
* [[FlightGear Newsletter March 2021|March]]<br />
* [[FlightGear Newsletter April 2021|April]]<br />
* [[FlightGear Newsletter May 2021|May]] <br />
* [[FlightGear Newsletter June 2021|June]]<br />
* [[FlightGear Newsletter July 2021|July]] <br />
* [[FlightGear Newsletter August 2021|August]] <br />
* [[FlightGear Newsletter September 2021|September]] <br />
* [[FlightGear Newsletter October 2021|October]] <br />
* [[FlightGear Newsletter November 2021|November]] <br />
* [[FlightGear Newsletter December 2021|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2020|January]]<br />
* [[FlightGear Newsletter February 2020|February]]<br />
* [[FlightGear Newsletter March 2020|March]]<br />
* [[FlightGear Newsletter April 2020|April]] <br />
* [[FlightGear Newsletter May 2020|May]] <br />
* [[FlightGear Newsletter June 2020|June]]<br />
* [[FlightGear Newsletter July 2020|July]]<br />
* [[FlightGear Newsletter August 2020|August]]<br />
* [[FlightGear Newsletter September 2020|September]]<br />
* [[FlightGear Newsletter October 2020|October]]<br />
* [[FlightGear Newsletter November 2020|November]]<br />
* [[FlightGear Newsletter December 2020|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2019|January]]<br />
* [[FlightGear Newsletter February 2019|February]]<br />
* [[FlightGear Newsletter March 2019|March]]<br />
* [[FlightGear Newsletter April 2019|April]]<br />
* [[FlightGear Newsletter May 2019|May]]<br />
* [[FlightGear Newsletter June 2019|June]]<br />
* [[FlightGear Newsletter July 2019|July]]<br />
* [[FlightGear Newsletter August 2019|August]]<br />
* [[FlightGear Newsletter September 2019|September]]<br />
* [[FlightGear Newsletter October 2019|October]]<br />
* [[FlightGear Newsletter November 2019|November]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2018|January]]<br />
* [[FlightGear Newsletter February 2018|February]]<br />
* [[FlightGear Newsletter March 2018|March]]<br />
* [[FlightGear Newsletter April 2018|April]]<br />
* [[FlightGear Newsletter May 2018|May]]<br />
* [[FlightGear Newsletter June 2018|June]]<br />
* [[FlightGear Newsletter July 2018|July]]<br />
* [[FlightGear Newsletter August 2018|August]]<br />
* [[FlightGear Newsletter September 2018|September]]<br />
* [[FlightGear Newsletter October 2018|October]]<br />
* [[FlightGear Newsletter November 2018|November]]<br />
* [[FlightGear Newsletter December 2018|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2017|January]]<br />
* [[FlightGear Newsletter February 2017|February]]<br />
* [[FlightGear Newsletter March 2017|March]]<br />
* [[FlightGear Newsletter April 2017|April]]<br />
* [[FlightGear Newsletter May 2017|May]]<br />
* [[FlightGear Newsletter June 2017|June]]<br />
* [[FlightGear Newsletter July 2017|July]]<br />
* [[FlightGear Newsletter August 2017|August]]<br />
* [[FlightGear Newsletter September 2017|September]]<br />
* [[FlightGear Newsletter October 2017|October]]<br />
* [[FlightGear Newsletter November 2017|November]]<br />
* [[FlightGear Newsletter December 2017|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2016|January]]<br />
* [[FlightGear Newsletter February 2016|February]]<br />
* [[FlightGear Newsletter March 2016|March]]<br />
* [[FlightGear Newsletter April 2016|April]]<br />
* [[FlightGear Newsletter May 2016|May]]<br />
* [[FlightGear Newsletter June 2016|June]]<br />
* [[FlightGear Newsletter July 2016|July]]<br />
* [[FlightGear Newsletter August 2016|August]]<br />
* [[FlightGear Newsletter September 2016|September]]<br />
* [[FlightGear Newsletter October 2016|October]]<br />
* [[FlightGear Newsletter November 2016|November]]<br />
* [[FlightGear Newsletter December 2016|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2015|January]]<br />
* [[FlightGear Newsletter February 2015|February]]<br />
* [[FlightGear Newsletter March 2015|March]]<br />
* [[FlightGear Newsletter April 2015|April]]<br />
* [[FlightGear Newsletter May 2015|May]]<br />
* [[FlightGear Newsletter June 2015|June]]<br />
* [[FlightGear Newsletter July 2015|July]]<br />
* [[FlightGear Newsletter August 2015|August]]<br />
* [[FlightGear Newsletter September 2015|September]]<br />
* [[FlightGear Newsletter October 2015|October]]<br />
* [[FlightGear Newsletter November 2015|November]]<br />
* [[FlightGear Newsletter December 2015|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2014|January]] <br />
* [[FlightGear Newsletter February 2014|February]]<br />
* [[FlightGear Newsletter March 2014|March]]<br />
* [[FlightGear Newsletter April 2014|April]]<br />
* [[FlightGear Newsletter May 2014|May]]<br />
* [[FlightGear Newsletter June 2014|June]]<br />
* [[FlightGear Newsletter July 2014|July]]<br />
* [[FlightGear Newsletter August 2014|August]]<br />
* [[FlightGear Newsletter September 2014|September]]<br />
* [[FlightGear Newsletter October 2014|October]]<br />
* [[FlightGear Newsletter November 2014|November]]<br />
* [[FlightGear Newsletter December 2014|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2013|January]]<br />
* [[FlightGear Newsletter February 2013|February]]<br />
* [[FlightGear Newsletter March 2013|March]]<br />
* [[FlightGear Newsletter April 2013|April]]<br />
* [[FlightGear Newsletter May 2013|May]] <br />
* [[FlightGear Newsletter June 2013|June]]<br />
* [[FlightGear Newsletter July 2013|July]]<br />
* [[FlightGear Newsletter August 2013|August]]<br />
* [[FlightGear Newsletter September 2013|September]]<br />
* [[FlightGear Newsletter October 2013|October]]<br />
* [[FlightGear Newsletter November 2013|November]]<br />
* [[FlightGear Newsletter December 2013|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2012|January]]<br />
* [[FlightGear Newsletter February 2012|February]]<br />
* [[FlightGear Newsletter March 2012|March]]<br />
* [[FlightGear Newsletter April 2012|April]]<br />
* [[FlightGear Newsletter May 2012|May]]<br />
* [[FlightGear Newsletter June 2012|June]]<br />
* [[FlightGear Newsletter July 2012|July]]<br />
* [[FlightGear Newsletter August 2012|August]]<br />
* [[FlightGear Newsletter September 2012|September]]<br />
* [[FlightGear Newsletter October 2012|October]]<br />
* [[FlightGear Newsletter November 2012|November]]<br />
* [[FlightGear Newsletter December 2012|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2011|January]]<br />
* [[FlightGear Newsletter February 2011|February]]<br />
* [[FlightGear Newsletter March 2011|March]]<br />
* [[FlightGear Newsletter April 2011|April]]<br />
* [[FlightGear Newsletter May 2011|May]]<br />
* [[FlightGear Newsletter June 2011|June]]<br />
* [[FlightGear Newsletter July 2011|July]] <br />
* [[FlightGear Newsletter August 2011|August]]<br />
* [[FlightGear Newsletter September 2011|September]]<br />
* [[FlightGear Newsletter October 2011|October]]<br />
* [[FlightGear Newsletter November 2011|November]]<br />
* [[FlightGear Newsletter December 2011|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2010|January]]<br />
* [[FlightGear Newsletter February 2010|February]]<br />
* [[FlightGear Newsletter March 2010|March]]<br />
* [[FlightGear Newsletter April 2010|April]]<br />
* [[FlightGear Newsletter May 2010|May]]<br />
* [[FlightGear Newsletter June 2010|June]]<br />
* [[FlightGear Newsletter July 2010|July]]<br />
* [[FlightGear Newsletter August 2010|August]]<br />
* [[FlightGear Newsletter September 2010|September]]<br />
* [[FlightGear Newsletter October 2010|October]]<br />
* [[FlightGear Newsletter November 2010|November]]<br />
* [[FlightGear Newsletter December 2010|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter July 2009|July]]<br />
* [[FlightGear Newsletter August 2009|August]]<br />
* [[FlightGear Newsletter September 2009|September]]<br />
* [[FlightGear Newsletter October 2009|October]]<br />
* [[FlightGear Newsletter November 2009|November]]<br />
* [[FlightGear Newsletter December 2009|December]]<br />
|}<br />
<br />
Some newsletter editions have been translated in other languages:<br />
* [[File:De.gif|16px|link=:De:FlightGear Newsletter]] [[:De:FlightGear Newsletter|Deutsch]]<br />
* [[File:Es.gif|16px|link=:Es:FlightGear Newsletter]] [[:Es:FlightGear Newsletter|Español]]<br />
* [[File:Fr.gif|16px|link=:Fr:FlightGear Newsletter]] [[:Fr:FlightGear Newsletter|Français]]<br />
<br />
=== You are invited to contribute! ===<br />
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. The FlightGear Newsletter is a community-driven newsletter, which means that it is created and edited by people like ''you''. You don't need to be a long-time FlightGear user (or even a developer) to contribute to the newsletter. <br />
<br />
In fact, helping write the monthly FlightGear newsletter is an excellent way for getting started contributing to the FlightGear community very quickly and very easily. <br />
<br />
Even if you don't have to add anything yourself, just reviewing and improving additions by others is also highly appreciated, as are efforts to help translate newsletters or add screen shots (e.g. taken from the forum or mailing lists) to the newsletter. Screen shots can be uploaded at [[Special:Upload]].<br />
<br />
Everyone with a wiki account (free to [[Special:UserLogin|register]]) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.<br />
<br />
A simple template providing a basic structure for each upcoming newsletter can be taken from [[Talk:Next newsletter]]. This template can be copied/pasted into each new newsletter to help users getting started providing contents.<br />
<br />
The draft for the upcoming newsletter can always be found at [[Next newsletter]].<br />
<br />
If English is not your native language, please don't be concerned about contributing to the newsletter, you can always easily ask fellow FlightGear users to review or proof-read your changes. Also, one of the easiest ways to get started is simply copying/pasting text from forum or mailing list discussions, such as announcements (e.g., new aircraft, new scenery, etc.).<br />
<br />
Another neat option to get started is adding links to FlightGear-related YouTube videos. For this, we have a dedicated section in each newsletter: "[[FlightGear Newsletter {{#time: F Y | last month }}#FlightGear on YouTube|FlightGear on YouTube]]."<br />
<br />
If you want to embed a video, please see {{mediawiki|Extension:EmbedVideo#Usage}}<br />
<br />
If you are looking for other ways to get involved, please see [[Volunteer]].<br />
<br />
[[Category:FlightGear Newsletter| ]]<br />
[[Category:Community|Newsletter]]<br />
[[Category:Lists|Newsletter]]<br />
<br />
[[de:FlightGear Newsletter]]<br />
[[es:FlightGear Newsletter]]<br />
[[fr:FlightGear Newsletter]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2023-11&diff=138716Category:Screenshot of the month/2023-112023-11-28T09:42:23Z<p>Gijs: Created page with "See {{forum link|title=Submit your screenshot for the SOTM of november 2023|t=41794}} and {{forum link|title=Voting for the SOTM of november 2023|t=41841}}. Category:Screen..."</p>
<hr />
<div>See {{forum link|title=Submit your screenshot for the SOTM of november 2023|t=41794}} and {{forum link|title=Voting for the SOTM of november 2023|t=41841}}.<br />
<br />
[[Category:Screenshot of the month]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Morning_at_Mount_Fuji_with_the_amazing_Douglas_DC-3_-_HDR_-_PBR.jpg&diff=138715File:Morning at Mount Fuji with the amazing Douglas DC-3 - HDR - PBR.jpg2023-11-28T09:40:07Z<p>Gijs: Uploaded a work by {{forum link|text=Cyber_Gamer|type=member|u=28418}} from {{forum link|p=416346|title=Submit your screenshot for the SOTM of november 2023}} with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Morning at Mount Fuji with the amazing [[Douglas DC-3]] featuring [[HDR]] and [[PBR]]}}<br />
|date=2023-11-16<br />
|source={{forum link|p=416346|title=Submit your screenshot for the SOTM of november 2023}}<br />
|author={{forum link|text=Cyber_Gamer|type=member|u=28418}}<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month/2023-11]]<br />
[[Category:Douglas DC-3 screenshots]]<br />
[[Category:Compositor screenshots]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Aerotow_Everywhere_Add-on&diff=138463Aerotow Everywhere Add-on2023-10-10T09:45:38Z<p>Gijs: Correct header levels and typo</p>
<hr />
<div>{{Infobox Software<br />
| title = Aerotow Everywhere Add-on<br />
| logo = <br />
| image = Aerotow add-on 1.png<br />
| alt = Aerotow Everywhere Addo-on - the tow plane taxis in front of the glider.<br />
| developedby = Roman Ludwicki (PlayeRom, SP-ROM)<br />
| initialrelease = August 14th, 2022<br />
| latestrelease = 1.8.5, Sep 8th, 2023<br />
| writtenin = Nasal<br />
| developmentstatus = Stable (2023)<br />
| type = Addon<br />
| license = [[GNU General Public License]] v3<br />
| website = https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere<br />
}}<br />
<br />
This is an add-on designed to include an AI aircraft that will be able to tow a glider. The main idea is to be able to do this at any airport and with any glider. Technically, this add-on adds the aerotow-dragger AI scenario dynamically, so you won't have to create XML with the scenario manually anymore.<br />
<br />
== Installation ==<br />
<br />
{{warning|This add-on is working only on version 2020.4 (dev/night).}}<br />
<br />
This add-on creates a flight plan in real-time based on the airport you are at. Unfortunately this causes a problem which you will have to solve manually by following the instructions below.<br />
Namely, the flight plan for AI aircraft, by default, must be stored in the <code>[[$FG_ROOT]]/AI/FlightPlans/</code> directory. But for security reasons, Nasal scripts cannot save files to that directory, but can save e.g. to <code>[[$FG_HOME]]/Export/</code>. Therefore, the run-time created flight plan will just be saved to <code>[[$FG_HOME]]/Export/Addons/org.flightgear.addons.Aerotow/AI/FlightPlans/</code>. The problem is that FlightGear does not know that it is supposed to look for the flight plan file in this location as well, so you have to tell it manually by using the <code>--data</code> [[Command_line_options|command line option]].<br />
<br />
<code>[[$FG_HOME]]</code> is the FlightGear home path. It differs depending on the operating system.<br />
Under Linux/macOS <code>[[$FG_HOME]]</code> is <code>/home/{username}/.fgfs/</code>.<br />
Under Windows <code>[[$FG_HOME]]</code> is <code>C:\Users\{username}\AppData\Roaming\flightgear.org\</code>.<br />
Where <code>{username}</code> is the name of the user logged into the operating system.<br />
<br />
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere/releases Download "Aerotow Everywhere" add-on] and unzip it.<br />
# In Launcher go to "Add-ons" tab. Click "Add" button by "Add-on Module folders" section and select folder with unzipped "Aerotow Everywhere" add-on directory (or add command line options: <code>--addon=path</code>), and click "Fly!". After loading the simulator, a <code>$FG_HOME/Export/Addons/org.flightgear.addons.Aerotow</code> directory should be created.<br />
# Close FlightGear for now.<br />
# In the file explorer of your operating system, find the directory <code>$FG_HOME/Export/Addons/org.flightgear.addons.Aerotow</code>. This path must be added by the <code>--data</code> command line option, so it will be treated as an additional FGData directory. In Launcher go to "Settings" tab and in "Additionnal Setting" type for example on the Linux system: <code>--data=/home/{username}/.fgfs/Export/Addons/org.flightgear.addons.Aerotow</code> or on the Windows: <code>--data=C:\Users\{username}\AppData\Roaming\flightgear.org\Export\Addons\org.flightgear.addons.Aerotow</code>.<br />
# Run simulator again, now everything should be working.<br />
<br />
== How to start? ==<br />
<br />
Start FlightGear at any airport with your aircraft as a glider, such as ASK 21.<br />
<br />
From the top menu, select "Aerotow Everywhere" -> "Call for Piper J3 Cub aircraft", "Robin DR400", "Cessna 182" or "Douglas C-47". (Yes, you can choose from many aircrafts). The AI aircraft will appear to your right and align to the centerline of the runway in front of you. At this time you should hook up to the aircraft, most often by pressing the {{key press|Ctrl|o}} key (check help of your glider). The AI aircraft will begin to accelerate and take off.<br />
<br />
You can also take off in the bush. Then the tow plane will position itself in front of you (glider's course), so what heading you have is important. If you move away from the runway threshold further than 100 m, then the take-off of the tow plane will be as in the bush, i.e. according to the glider heading and not the runway.<br />
<br />
== How does the AI tow aircraft fly by default? ==<br />
<br />
[[File:Aerotow add-on 1.png|thumb|Aerotow Everywhere Addo-on - the tow plane taxis in front of the glider.]]<br />
<br />
The tow plane always takes off in front of your runway and flies along the runway for 5 km, then turns back and flies downwind for 6 km, then turns back again and flies another 6 km. During this flight it is constantly gaining altitude. Then, after having flown the entire given route, it lands at the airport from which it took off or when start in the bush turns in an unknown direction and flies at a constant altitude. If the aircraft lands at the airport, the scenario starts again, i.e. the aircraft respawn to take-off again.<br />
<br />
You can disconnect from the aircraft at any time, most often by pressing the {{key press|o}} key (check help of your glider).<br />
<br />
Default route:<br />
^ - airport with heading direction to north<br />
1 - 1st waypoint<br />
2 - 2nd waypoint, etc.<br />
<br />
2 . . 1 5<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. . .<br />
. ^ .<br />
. .<br />
. .<br />
3 . . . . 4<br />
<br />
== Menu of add-on ==<br />
<br />
This add-on add a new item to main menu named "Aerotow Everywhere" with following items:<br />
<br />
# <code>Aerotow Route</code> - display the dialog for change aerotow route.<br />
# <code>Towrope Configuration</code> - display the dialog for change towrope parameters.<br />
# <code>Call for Piper J3 Cub aircraft</code> - load AI tow sceneraio with Piper J3 Cub.<br />
# <code>Call for Robin DR400 aircraft</code> - load AI tow sceneraio with Robin DR400. This aircraft has better performance and can take you higher then Piper Cub.<br />
# <code>Call for Cessna 182 aircraft</code> - load AI tow sceneraio with Cessna 182. This aircraft has little bit better performance than Robin.<br />
# <code>Call for Douglas C-47 aircraft</code> - load AI tow sceneraio with Douglas C-47.<br />
# <code>Disable tow aircraft</code> - unload AI tow sceneraio.<br />
# <code>Add thermal</code> - display the dialog for configuring and adding thermal.<br />
# <code>Help</code> - display help dialog.<br />
# <code>About</code> - display about dialog with add-on information.<br />
<br />
== Aerotow Route == <br />
<br />
You can change the AI aircraft's default route, for this go to menu "Aerotow Everywhere" -> "Aerotow Route".<br />
<br />
=== Aerotow aircraft ===<br />
<br />
On the top of the "Aerotow Route" dialog you have selector to change aircraft type. It's only for calculate performance and display how the altitude will change.<br />
<br />
=== Max alt (AGL) ===<br />
<br />
Here you can set limit of AGL altitude. 0 means without limits - the plane will always increase its altitude during its flight. AGL is always in terms of the place you are starting from.<br />
<br />
=== Route ===<br />
<br />
Next you have initial heading, distance and altitude change. "Initial heading" depend of the runway where you are located. The aircraft will always take-off along the runway, a distance of 100 m, where it will gain 20 ft in altitude above the terrain. These parameters you cannot change unless you change the airport/runway.<br />
<br />
Next you can see a table with fields where you can change values. Each row represents a single waypoint of flight plan of AI aircraft. For each waypoint you have following columns:<br />
<br />
# <code>Heading change (deg)</code> - information on how the heading of the aircraft should change in relation to the previous one. A value of <code>0</code> means no change, so continue with the same heading. And e.g. <code>-90</code> means a left turn of 90 degrees, <code>60</code> means a right turn of 60 degrees, etc.<br />
# <code>Distance (m)</code> - distance in meters from the previous waypoint to the present one.<br />
# <code>Alt change (AGL ft)</code> - information on how much the altitude on this leg of the route will increase (in feet above ground.) This information depend of selected airplane. AGL is always in terms of the place you are starting from (not the waypoint place).<br />
<br />
If you enter a value less than or equal to <code>0</code> for <code>Distance (m)</code> field this means that here the route is end and the next rows will not be included to the flight plan.<br />
<br />
You have a maximum of 10 waypoints to use, hope that's enough.<br />
<br />
On the below of the dialog you can see a total amount of distance (in meters) and total altitude in feet above ground level.<br />
<br />
=== Buttons ===<br />
<br />
# <code>OK</code> - close the route dialog.<br />
# <code>Default</code> - set default waypoints (your changes will be lost.)<br />
<br />
== Adding thermals ==<br />
<br />
An additional feature of this add-on is the possibility of placing the thermals just in front of the glider. To do this, go to menu "Aerotow Everywhere" -> "Add thermal" where you can configure the following parameters:<br />
<br />
# <code>Distance</code> - the distance in metres at which the thermals will be placed in front of the gliders.<br />
# <code>Strength</code> - thermal strength in feet per second.<br />
# <code>Diameter</code> - diameter of thermal in feet.<br />
# <code>Height</code> - height of thermal in feet above mean sea level.<br />
<br />
Click <code>Add thermal</code> button for add the thermal.<br />
<br />
Many thanks to the FG forum user "wlbragg" for proposing and presenting a solution to this feature.<br />
<br />
== Limitations ==<br />
<br />
# This add-on doesn't check if there are any obstacles in the AI aircraft's path, e.g. terrain, buildings, power lines, etc. Keep this in mind when choosing an airport or planning your route.<br />
# Minimum FlightGear version: 2020.4.0 (dev/nightly). Because only nightly version is able to search for flight plans in additional FGData folders added by <code>--data</code> command line option.<br />
<br />
== Troubleshooting ==<br />
<br />
=== When I select "Aerotow Everywhere" -> "Call for Piper J3 Cub aircraft" or other plane from menu, I see "Let's fly!" message but nothing happened. The tow plane does not appear. ===<br />
<br />
Probably you didn't include the <code>--data</code> command line option with the path where FlightGear should look for additional flight plan files for AI. Unfortunately, the simulator does not inform us that there was a problem with finding the flight plan file, so everything looks like it should work but does not.<br />
<br />
For fix it, in the file explorer of your operating system, find the directory <code>[[$FG_HOME]]/Export/Addons/org.flightgear.addons.Aerotow</code>. This path must be added by the <code>--data</code> command line option, so it will be treated as an additional FGData directory where FlightGear will find the flight plan. In Launcher go to "Settings" tab and in "Additionnal Setting" type (on the Linux system):<br />
<br />
--data=/home/{username}/.fgfs/Export/Addons/org.flightgear.addons.Aerotow<br />
<br />
or on the Windows:<br />
<br />
--data=C:\Users\{username}\AppData\Roaming\flightgear.org\Export\Addons\org.flightgear.addons.Aerotow<br />
<br />
Run simulator again, now everything should be working.<br />
<br />
== What is the difference with "Drag robot"? ==<br />
<br />
Some gliders have a "Drag robot" function implemented, which basically, you could say, does the same thing, tows our glider. "Drag robot" uses the trick of positioning the model of the plane. The "drag robot" always spins semicircles in a random way from left to right.<br />
<br />
This add-on can be independent of the glider and available to anyone where "Drag robot" is unavailable. This add-on applies a flight plan AI scenario for an AI aircraft which means that the aircraft "really flies" using flight dynamics (we have rotating propeller, adjusting the landing gear, etc.) You can also set the route in which the plane should fly. In addition, we have the sound of the AI aircraft engine.<br />
<br />
"Drag robot" has "Advanced Configuration" dialog to adjust plane parameters, what is not available in Aerotow Everywhere Add-on.<br />
<br />
[[Category:FlightGear addons]]<br />
[[Category:Nasal software]]<br />
[[Category:Glider tugs]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:Current_release&diff=138395Template:Current release2023-09-19T07:33:43Z<p>Gijs: Leave unknown next release date empty</p>
<hr />
<div><includeonly>{{#switch: {{{1|}}}<br />
| cr = 2020.3<br />
| crd = 6 November 2020<br />
| nr = 2020.4<br />
| nrd = <!-- {{days from now|2050|1|1}} --><!-- uncomment if date is known --><br />
<br />
| full = 2020.3.18<br />
| fulldate = 21 March 2023<br />
<br />
| #default = {{error|No argument given|current release}}<br />
}}</includeonly><noinclude><br />
{{Informative template|1=<br />
== Goal ==<br />
This template is used internally by {{tl|GitStatus}} to display:<br />
# the current release<br />
# the release date of the current release<br />
# the next release<br />
# the number of days until the next release. Leave empty or comment if unknown<br />
# the full version of the newest release and its release date<br />
<br />
This template should be updated with every new release, including bugfix releases.<br />
<br />
== Usage ==<br />
{{obr}}'''current release'''{{!}}data{{cbr}}<br />
<br />
; data : Dictates what data is returned. This parameter is mandatory. Value may be one of:<br />
:*'''cr''': Current release<br />
:*'''crd''': Release date of current release<br />
:*'''nr''': Next release<br />
:*'''nrd''': Days until the next release<br />
<br />
== Examples ==<br />
{{obr}}current release{{!}}cr{{cbr}}<br />
{{current release|cr}}<br />
<br />
== Related template ==<br />
* {{tl|GitStatus}}<br />
<br />
== See also ==<br />
* [[Release plan]]<br />
<br />
}}<br />
<br />
[[Category:Git templates]]<br />
</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:GitStatus&diff=138394Template:GitStatus2023-09-19T07:32:14Z<p>Gijs: Hide next release date if unknown</p>
<hr />
<div>{| cellspacing="5" width="100%"<br />
| align="center" | {{LangSwitch<br />
| en = <!-- English --><br />
'''Current release:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|en}})<br>'''Next release:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} from now)|}}<br>See [[release plan]] for details.<br />
| de = <!-- German --><br />
'''Aktuelle Version:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|de}})<br>'''Nächste Version:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} ab jetzt)|}}<br>Siehe [[release plan|Release-Plan]] für weitere Einzelheiten.<br />
| nl = <!-- Dutch --><br />
'''Huidige versie:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|nl}})<br>'''Volgende versie:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} vanaf nu)|}}<br>Zie [[release plan|vrijlating plan]] voor details.<br />
| es = <!-- Spanish --><br />
'''Lanzamiento actual:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|es}})<br>'''Próxima versión:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir de ahora)|}}<br>Ver [[release plan|plan de lanzamiento]] para más detalles.<br />
| fr = <!-- French --><br />
'''Version actuelle:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|fr}})<br>'''Prochaine publication:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} à partir de maintenant)|}}<br>Voir [[release plan|plan de libération]] pour les détails.<br />
| pt = <!-- Portuguese --><br />
'''A versão atual:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|pt}})<br>'''Próximo lançamento:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir de agora)|}}<br>Ver [[release plan|plano de lançamento]] para mais detalhes.<br />
| ru = <!-- Russian --><br />
'''Текущий релиз:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|ru}})<br>'''Следующий релиз:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} с этого момента)|}}<br>См [[release plan|план выпуска]] Подробности<br />
| pl = <!-- Polish --><br />
'''Aktualna wersja:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|pl}})<br>'''Następnie zwolnić:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} od teraz)|}}<br>Zobacz szczegóły [[release plan|planu zwalniania]]<br />
| sr = <!-- Serbian --><br />
'''Тренутно издање:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|sr}})<br>'''Следеће издање:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} од сада)|}}<br>Погледајте [[release plan|релеасе план]] за детаље<br />
| sl = <!-- Slovenian --><br />
'''Trenutni javnost:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|sl}})<br>'''Naslednja objava:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} od zdaj)|}}<br>Glej [[release plan|načrt javnost]] podrobnosti<br />
| ca = <!-- Catalan --><br />
'''Versió actual:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|ca}})<br>'''Següent versió:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir d'ara)|}}<br>Veure [[release plan|pla de llançament]] per a més detalls<br />
| ja = <!-- Japanese --><br />
'''現在のリリース:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|ja}})<br>'''次のリリース:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} 今から)|}}<br>詳細については、[[release plan|リリース計画]]を参照してください。<br />
| fa = <!-- Persian --><br />
<span dir="rtl">'''نسخه فعلی:''' <span class="plainlinks">[http://www.flightgear.org/download/ {{Current release|full}}]</span> ({{#time:j M Y|{{Current release|fulldate}}|fa}})</span><br><span dir="rtl">'''نسخه بعدی:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|({{Current release|nrd}} از هم اکنون)|}}</span><br><span dir="rtl">دیدن طرح آزاد ([[release plan|اینجا]]) برای جزئیات</span><br />
}}<br />
|}<noinclude><br />
{{Informative template|1=<br />
== Goal ==<br />
This template displays information about the current release state of [[FlightGear]]. It display the current, date of that release, the next release, and the time until the next release.<br />
<br />
== Usage ==<br />
{{obr}}'''GitStatus'''{{cbr}}<br />
<br />
== See also ==<br />
* [[Release plan]]<br />
<br />
}}<br />
<br />
[[Category:Git templates]]<br />
<br />
</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:SOTM_2020-07_Late_Night_Flight_in_Finland_by_Oswald.jpg&diff=138364File:SOTM 2020-07 Late Night Flight in Finland by Oswald.jpg2023-09-14T15:32:38Z<p>Gijs: Fix category</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=SOTM 2020-07 Late Night Flight in Finland by Oswald (Cessna 337G Skymaster)}}<br />
|date=2020-07-31<br />
|source=FlightGear.org SOTM 2020-07, released under CC-BY-SA-4.0<br />
|author=X - see filename.<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Screenshot of the month/2020-07]]<br />
[[Category:Screenshots at high settings]]<br />
[[Category:Screenshots at high settings/2020]]<br />
[[Category:Screenshots at high settings/sotm]]<br />
[[Category:Screenshots of weather]]<br />
[[Category:Cessna 337 screenshots]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Category:Cessna_310_screenshots&diff=138363Category:Cessna 310 screenshots2023-09-14T15:31:30Z<p>Gijs: Add parent categories</p>
<hr />
<div>{{fg screenshot cat|the [[Cessna 310]]}}<br />
<br />
[[Category:Cessna aircraft screenshots|310]]<br />
[[Category:Aircraft screenshots by model|Cessna 310]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=User_talk:Jakkos98&diff=138353User talk:Jakkos982023-09-10T07:21:25Z<p>Gijs: Gijs moved page User talk:Jakkos to User talk:Jakkos98 without leaving a redirect: Automatically moved page while renaming the user "Jakkos" to "Jakkos98"</p>
<hr />
<div>{{Template:Welcome to the wiki|realName=Jakub Kosakowski|name=Jakkos}}<br />
<br />
-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 22:54, 9 September 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Next_newsletter&diff=138341Next newsletter2023-09-05T09:10:55Z<p>Gijs: Update</p>
<hr />
<div>#REDIRECT [[FlightGear Newsletter September 2023]]<br />
{{User:Skybike/Template:This months newsletter|date=now}}</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter&diff=138340FlightGear Newsletter2023-09-05T09:10:17Z<p>Gijs: Use internal wiki link</p>
<hr />
<div>[[File:magagazine.png|right]]<br />
<br />
The '''FlightGear Newsletter''' is intended to provide a collection of the latest developments from the worldwide [[FlightGear]] community. With so much development ongoing, it's almost impossible for anyone to keep up. The newsletter was started in July 2009, and is presented on a monthly basis. It is a collaborative effort that is created, edited and distributed via the [[FlightGear Wiki]], and all FlightGear users, contributors and developers are invited to contribute.<br />
<br />
=== Archive ===<br />
{| class="prettytable"<br />
! align="left" | 2023<br />
! align="left" | 2022<br />
! align="left" | 2021<br />
! align="left" | 2020<br />
! align="left" | 2019<br />
! align="left" | 2018<br />
! align="left" | 2017<br />
! align="left" | 2016<br />
! align="left" | 2015<br />
! align="left" | 2014<br />
! align="left" | 2013<br />
! align="left" | 2012<br />
! align="left" | 2011<br />
! align="left" | 2010<br />
! align="left" | 2009<br />
|-<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2023|January]]<br />
* [[FlightGear Newsletter February 2023|February]]<br />
* [[FlightGear Newsletter March 2023|March]]<br />
* [[FlightGear Newsletter April 2023|April]]<br />
* [[FlightGear Newsletter May 2023|May]]<br />
* [[FlightGear Newsletter June 2023|June]]<br />
* [[FlightGear Newsletter July 2023|July]]<br />
* [[FlightGear Newsletter August 2023|August]]<br />
* [[FlightGear Newsletter September 2023|September]]<br />
''(currently being written)''<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2022|January]]<br />
* [[FlightGear Newsletter February 2022|February]]<br />
* [[FlightGear Newsletter March 2022|March]]<br />
* [[FlightGear Newsletter April 2022|April]]<br />
* [[FlightGear Newsletter May 2022|May]] <br />
* June<br />
* [[FlightGear Newsletter July 2022|July]]<br />
* [[FlightGear Newsletter August 2022|August]]<br />
* [[FlightGear Newsletter September 2022|September]]<br />
* October<br />
* [[FlightGear Newsletter November 2022|November]]<br />
* [[FlightGear Newsletter December 2022|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2021|January]]<br />
* [[FlightGear Newsletter February 2021|February]]<br />
* [[FlightGear Newsletter March 2021|March]]<br />
* [[FlightGear Newsletter April 2021|April]]<br />
* [[FlightGear Newsletter May 2021|May]] <br />
* [[FlightGear Newsletter June 2021|June]]<br />
* [[FlightGear Newsletter July 2021|July]] <br />
* [[FlightGear Newsletter August 2021|August]] <br />
* [[FlightGear Newsletter September 2021|September]] <br />
* [[FlightGear Newsletter October 2021|October]] <br />
* [[FlightGear Newsletter November 2021|November]] <br />
* [[FlightGear Newsletter December 2021|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2020|January]]<br />
* [[FlightGear Newsletter February 2020|February]]<br />
* [[FlightGear Newsletter March 2020|March]]<br />
* [[FlightGear Newsletter April 2020|April]] <br />
* [[FlightGear Newsletter May 2020|May]] <br />
* [[FlightGear Newsletter June 2020|June]]<br />
* [[FlightGear Newsletter July 2020|July]]<br />
* [[FlightGear Newsletter August 2020|August]]<br />
* [[FlightGear Newsletter September 2020|September]]<br />
* [[FlightGear Newsletter October 2020|October]]<br />
* [[FlightGear Newsletter November 2020|November]]<br />
* [[FlightGear Newsletter December 2020|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2019|January]]<br />
* [[FlightGear Newsletter February 2019|February]]<br />
* [[FlightGear Newsletter March 2019|March]]<br />
* [[FlightGear Newsletter April 2019|April]]<br />
* [[FlightGear Newsletter May 2019|May]]<br />
* [[FlightGear Newsletter June 2019|June]]<br />
* [[FlightGear Newsletter July 2019|July]]<br />
* [[FlightGear Newsletter August 2019|August]]<br />
* [[FlightGear Newsletter September 2019|September]]<br />
* [[FlightGear Newsletter October 2019|October]]<br />
* [[FlightGear Newsletter November 2019|November]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2018|January]]<br />
* [[FlightGear Newsletter February 2018|February]]<br />
* [[FlightGear Newsletter March 2018|March]]<br />
* [[FlightGear Newsletter April 2018|April]]<br />
* [[FlightGear Newsletter May 2018|May]]<br />
* [[FlightGear Newsletter June 2018|June]]<br />
* [[FlightGear Newsletter July 2018|July]]<br />
* [[FlightGear Newsletter August 2018|August]]<br />
* [[FlightGear Newsletter September 2018|September]]<br />
* [[FlightGear Newsletter October 2018|October]]<br />
* [[FlightGear Newsletter November 2018|November]]<br />
* [[FlightGear Newsletter December 2018|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2017|January]]<br />
* [[FlightGear Newsletter February 2017|February]]<br />
* [[FlightGear Newsletter March 2017|March]]<br />
* [[FlightGear Newsletter April 2017|April]]<br />
* [[FlightGear Newsletter May 2017|May]]<br />
* [[FlightGear Newsletter June 2017|June]]<br />
* [[FlightGear Newsletter July 2017|July]]<br />
* [[FlightGear Newsletter August 2017|August]]<br />
* [[FlightGear Newsletter September 2017|September]]<br />
* [[FlightGear Newsletter October 2017|October]]<br />
* [[FlightGear Newsletter November 2017|November]]<br />
* [[FlightGear Newsletter December 2017|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2016|January]]<br />
* [[FlightGear Newsletter February 2016|February]]<br />
* [[FlightGear Newsletter March 2016|March]]<br />
* [[FlightGear Newsletter April 2016|April]]<br />
* [[FlightGear Newsletter May 2016|May]]<br />
* [[FlightGear Newsletter June 2016|June]]<br />
* [[FlightGear Newsletter July 2016|July]]<br />
* [[FlightGear Newsletter August 2016|August]]<br />
* [[FlightGear Newsletter September 2016|September]]<br />
* [[FlightGear Newsletter October 2016|October]]<br />
* [[FlightGear Newsletter November 2016|November]]<br />
* [[FlightGear Newsletter December 2016|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2015|January]]<br />
* [[FlightGear Newsletter February 2015|February]]<br />
* [[FlightGear Newsletter March 2015|March]]<br />
* [[FlightGear Newsletter April 2015|April]]<br />
* [[FlightGear Newsletter May 2015|May]]<br />
* [[FlightGear Newsletter June 2015|June]]<br />
* [[FlightGear Newsletter July 2015|July]]<br />
* [[FlightGear Newsletter August 2015|August]]<br />
* [[FlightGear Newsletter September 2015|September]]<br />
* [[FlightGear Newsletter October 2015|October]]<br />
* [[FlightGear Newsletter November 2015|November]]<br />
* [[FlightGear Newsletter December 2015|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2014|January]] <br />
* [[FlightGear Newsletter February 2014|February]]<br />
* [[FlightGear Newsletter March 2014|March]]<br />
* [[FlightGear Newsletter April 2014|April]]<br />
* [[FlightGear Newsletter May 2014|May]]<br />
* [[FlightGear Newsletter June 2014|June]]<br />
* [[FlightGear Newsletter July 2014|July]]<br />
* [[FlightGear Newsletter August 2014|August]]<br />
* [[FlightGear Newsletter September 2014|September]]<br />
* [[FlightGear Newsletter October 2014|October]]<br />
* [[FlightGear Newsletter November 2014|November]]<br />
* [[FlightGear Newsletter December 2014|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2013|January]]<br />
* [[FlightGear Newsletter February 2013|February]]<br />
* [[FlightGear Newsletter March 2013|March]]<br />
* [[FlightGear Newsletter April 2013|April]]<br />
* [[FlightGear Newsletter May 2013|May]] <br />
* [[FlightGear Newsletter June 2013|June]]<br />
* [[FlightGear Newsletter July 2013|July]]<br />
* [[FlightGear Newsletter August 2013|August]]<br />
* [[FlightGear Newsletter September 2013|September]]<br />
* [[FlightGear Newsletter October 2013|October]]<br />
* [[FlightGear Newsletter November 2013|November]]<br />
* [[FlightGear Newsletter December 2013|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2012|January]]<br />
* [[FlightGear Newsletter February 2012|February]]<br />
* [[FlightGear Newsletter March 2012|March]]<br />
* [[FlightGear Newsletter April 2012|April]]<br />
* [[FlightGear Newsletter May 2012|May]]<br />
* [[FlightGear Newsletter June 2012|June]]<br />
* [[FlightGear Newsletter July 2012|July]]<br />
* [[FlightGear Newsletter August 2012|August]]<br />
* [[FlightGear Newsletter September 2012|September]]<br />
* [[FlightGear Newsletter October 2012|October]]<br />
* [[FlightGear Newsletter November 2012|November]]<br />
* [[FlightGear Newsletter December 2012|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2011|January]]<br />
* [[FlightGear Newsletter February 2011|February]]<br />
* [[FlightGear Newsletter March 2011|March]]<br />
* [[FlightGear Newsletter April 2011|April]]<br />
* [[FlightGear Newsletter May 2011|May]]<br />
* [[FlightGear Newsletter June 2011|June]]<br />
* [[FlightGear Newsletter July 2011|July]] <br />
* [[FlightGear Newsletter August 2011|August]]<br />
* [[FlightGear Newsletter September 2011|September]]<br />
* [[FlightGear Newsletter October 2011|October]]<br />
* [[FlightGear Newsletter November 2011|November]]<br />
* [[FlightGear Newsletter December 2011|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2010|January]]<br />
* [[FlightGear Newsletter February 2010|February]]<br />
* [[FlightGear Newsletter March 2010|March]]<br />
* [[FlightGear Newsletter April 2010|April]]<br />
* [[FlightGear Newsletter May 2010|May]]<br />
* [[FlightGear Newsletter June 2010|June]]<br />
* [[FlightGear Newsletter July 2010|July]]<br />
* [[FlightGear Newsletter August 2010|August]]<br />
* [[FlightGear Newsletter September 2010|September]]<br />
* [[FlightGear Newsletter October 2010|October]]<br />
* [[FlightGear Newsletter November 2010|November]]<br />
* [[FlightGear Newsletter December 2010|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter July 2009|July]]<br />
* [[FlightGear Newsletter August 2009|August]]<br />
* [[FlightGear Newsletter September 2009|September]]<br />
* [[FlightGear Newsletter October 2009|October]]<br />
* [[FlightGear Newsletter November 2009|November]]<br />
* [[FlightGear Newsletter December 2009|December]]<br />
|}<br />
<br />
Some newsletter editions have been translated in other languages:<br />
* [[File:De.gif|16px|link=:De:FlightGear Newsletter]] [[:De:FlightGear Newsletter|Deutsch]]<br />
* [[File:Es.gif|16px|link=:Es:FlightGear Newsletter]] [[:Es:FlightGear Newsletter|Español]]<br />
* [[File:Fr.gif|16px|link=:Fr:FlightGear Newsletter]] [[:Fr:FlightGear Newsletter|Français]]<br />
<br />
=== You are invited to contribute! ===<br />
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. The FlightGear Newsletter is a community-driven newsletter, which means that it is created and edited by people like ''you''. You don't need to be a long-time FlightGear user (or even a developer) to contribute to the newsletter. <br />
<br />
In fact, helping write the monthly FlightGear newsletter is an excellent way for getting started contributing to the FlightGear community very quickly and very easily. <br />
<br />
Even if you don't have to add anything yourself, just reviewing and improving additions by others is also highly appreciated, as are efforts to help translate newsletters or add screen shots (e.g. taken from the forum or mailing lists) to the newsletter. Screen shots can be uploaded at [[Special:Upload]].<br />
<br />
Everyone with a wiki account (free to [[Special:UserLogin|register]]) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.<br />
<br />
A simple template providing a basic structure for each upcoming newsletter can be taken from [[Talk:Next newsletter]]. This template can be copied/pasted into each new newsletter to help users getting started providing contents.<br />
<br />
The draft for the upcoming newsletter can always be found at [[Next newsletter]].<br />
<br />
If English is not your native language, please don't be concerned about contributing to the newsletter, you can always easily ask fellow FlightGear users to review or proof-read your changes. Also, one of the easiest ways to get started is simply copying/pasting text from forum or mailing list discussions, such as announcements (e.g., new aircraft, new scenery, etc.).<br />
<br />
Another neat option to get started is adding links to FlightGear-related YouTube videos. For this, we have a dedicated section in each newsletter: "[[FlightGear Newsletter {{#time: F Y | last month }}#FlightGear on YouTube|FlightGear on YouTube]]."<br />
<br />
If you want to embed a video, please see {{mediawiki|Extension:EmbedVideo#Usage}}<br />
<br />
If you are looking for other ways to get involved, please see [[Volunteer]].<br />
<br />
[[Category:FlightGear Newsletter| ]]<br />
[[Category:Community|Newsletter]]<br />
[[Category:Lists|Newsletter]]<br />
<br />
[[de:FlightGear Newsletter]]<br />
[[es:FlightGear Newsletter]]<br />
[[fr:FlightGear Newsletter]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Talk:SimGear&diff=138339Talk:SimGear2023-09-05T08:42:28Z<p>Gijs: SimGear website is still available</p>
<hr />
<div>=== Simgear.org is dead/taken? ===<br />
I have just checked this page within the scope of translating FAQ page to Russian - and it seems that current content of simgear.org has nothing to do with the project. Has someone else acquired this domain? Is there an up-to-date website somewhere still?<br />
[[User:Dot sent|Dot sent]] ([[User talk:Dot sent|talk]]) 18:02, 3 February 2018 (EST)<br />
<br />
: As of today there is nothing under simgear.org. I just created an edit where I link to the git repo directly plus an archived version of simgear.org. Bless the Internet Archive (and donate if you can). [[User:Meliache|Meliache]] ([[User talk:Meliache|talk]]) 01:26, 3 September 2023 (UTC)<br />
<br />
:: If I'm not mistaken, the original website is still up and running (though unmaintained) at https://simgear.sourceforge.net/. It's just the simgear.org domain that's no longer active.<br />
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 08:42, 5 September 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=User_talk:Mukesh&diff=138284User talk:Mukesh2023-08-31T14:03:54Z<p>Gijs: /* Asking for support */ new section</p>
<hr />
<div>{{Template:Welcome to the wiki|realName=|name=Mukesh}}<br />
<br />
-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 09:23, 17 June 2023 (UTC)<br />
<br />
== Asking for support ==<br />
<br />
Hi!<br />
<br />
Just a quick message regarding your recent question at [[User:New user message]] (I think you created that article by accident?). The wiki is primarily a documentation service and not really the best place to ask for (tailored) help. Our forum is much more suited for that and also more active: {{forum url}}.<br />
<br />
Cheers,<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 14:03, 31 August 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=User_talk:Nish4t&diff=138198User talk:Nish4t2023-08-21T15:31:19Z<p>Gijs: /* File names */ new section</p>
<hr />
<div>{{Template:Welcome to the wiki|realName=|name=Nish4t}}<br />
<br />
-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 07:49, 11 January 2023 (UTC)<br />
<br />
== File names ==<br />
<br />
Hi and welcome to the FlightGear wiki!<br />
<br />
It's great to see you adding and editing pages. There is just one minor request that I would like to make: please carefully consider the file name when uploading images. A name like [[:File:Fgfs-20230421114742.png]] is very generic, making it harder to find your image. A better name could be "File:Tupolev Tu-144 cockpit.png" or something along that line.<br />
<br />
Thanks!<br />
<br />
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:31, 21 August 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter&diff=138148FlightGear Newsletter2023-08-14T08:43:26Z<p>Gijs: /* Archive */ use internal wiki link</p>
<hr />
<div>[[File:magagazine.png|right]]<br />
<br />
The '''FlightGear Newsletter''' is intended to provide a collection of the latest developments from the worldwide [[FlightGear]] community. With so much development ongoing, it's almost impossible for anyone to keep up. The newsletter was started in July 2009, and is presented on a monthly basis. It is a collaborative effort that is created, edited and distributed via the [[FlightGear Wiki]], and all FlightGear users, contributors and developers are invited to contribute.<br />
<br />
=== Archive ===<br />
{| class="prettytable"<br />
! align="left" | 2023<br />
! align="left" | 2022<br />
! align="left" | 2021<br />
! align="left" | 2020<br />
! align="left" | 2019<br />
! align="left" | 2018<br />
! align="left" | 2017<br />
! align="left" | 2016<br />
! align="left" | 2015<br />
! align="left" | 2014<br />
! align="left" | 2013<br />
! align="left" | 2012<br />
! align="left" | 2011<br />
! align="left" | 2010<br />
! align="left" | 2009<br />
|-<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2023|January]]<br />
* [[FlightGear Newsletter February 2023|February]]<br />
* [[FlightGear Newsletter March 2023|March]]<br />
* [[FlightGear Newsletter April 2023|April]]<br />
* [[FlightGear Newsletter May 2023|May]]<br />
* [[FlightGear Newsletter June 2023|June]]<br />
* [[FlightGear Newsletter July 2023|July]]<br />
* [[FlightGear Newsletter August 2023|August]]<br />
''(currently being written)''<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2022|January]]<br />
* [[FlightGear Newsletter February 2022|February]]<br />
* [[FlightGear Newsletter March 2022|March]]<br />
* [[FlightGear Newsletter April 2022|April]]<br />
* [[FlightGear Newsletter May 2022|May]] <br />
* June<br />
* [[FlightGear Newsletter July 2022|July]]<br />
* [[FlightGear Newsletter August 2022|August]]<br />
* [[FlightGear Newsletter September 2022|September]]<br />
* October<br />
* [[FlightGear Newsletter November 2022|November]]<br />
* [[FlightGear Newsletter December 2022|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2021|January]]<br />
* [[FlightGear Newsletter February 2021|February]]<br />
* [[FlightGear Newsletter March 2021|March]]<br />
* [[FlightGear Newsletter April 2021|April]]<br />
* [[FlightGear Newsletter May 2021|May]] <br />
* [[FlightGear Newsletter June 2021|June]]<br />
* [[FlightGear Newsletter July 2021|July]] <br />
* [[FlightGear Newsletter August 2021|August]] <br />
* [[FlightGear Newsletter September 2021|September]] <br />
* [[FlightGear Newsletter October 2021|October]] <br />
* [[FlightGear Newsletter November 2021|November]] <br />
* [[FlightGear Newsletter December 2021|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2020|January]]<br />
* [[FlightGear Newsletter February 2020|February]]<br />
* [[FlightGear Newsletter March 2020|March]]<br />
* [[FlightGear Newsletter April 2020|April]] <br />
* [[FlightGear Newsletter May 2020|May]] <br />
* [[FlightGear Newsletter June 2020|June]]<br />
* [[FlightGear Newsletter July 2020|July]]<br />
* [[FlightGear Newsletter August 2020|August]]<br />
* [[FlightGear Newsletter September 2020|September]]<br />
* [[FlightGear Newsletter October 2020|October]]<br />
* [[FlightGear Newsletter November 2020|November]]<br />
* [[FlightGear Newsletter December 2020|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2019|January]]<br />
* [[FlightGear Newsletter February 2019|February]]<br />
* [[FlightGear Newsletter March 2019|March]]<br />
* [[FlightGear Newsletter April 2019|April]]<br />
* [[FlightGear Newsletter May 2019|May]]<br />
* [[FlightGear Newsletter June 2019|June]]<br />
* [[FlightGear Newsletter July 2019|July]]<br />
* [[FlightGear Newsletter August 2019|August]]<br />
* [[FlightGear Newsletter September 2019|September]]<br />
* [[FlightGear Newsletter October 2019|October]]<br />
* [[FlightGear Newsletter November 2019|November]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2018|January]]<br />
* [[FlightGear Newsletter February 2018|February]]<br />
* [[FlightGear Newsletter March 2018|March]]<br />
* [[FlightGear Newsletter April 2018|April]]<br />
* [[FlightGear Newsletter May 2018|May]]<br />
* [[FlightGear Newsletter June 2018|June]]<br />
* [[FlightGear Newsletter July 2018|July]]<br />
* [[FlightGear Newsletter August 2018|August]]<br />
* [[FlightGear Newsletter September 2018|September]]<br />
* [[FlightGear Newsletter October 2018|October]]<br />
* [[FlightGear Newsletter November 2018|November]]<br />
* [[FlightGear Newsletter December 2018|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2017|January]]<br />
* [[FlightGear Newsletter February 2017|February]]<br />
* [[FlightGear Newsletter March 2017|March]]<br />
* [[FlightGear Newsletter April 2017|April]]<br />
* [[FlightGear Newsletter May 2017|May]]<br />
* [[FlightGear Newsletter June 2017|June]]<br />
* [[FlightGear Newsletter July 2017|July]]<br />
* [[FlightGear Newsletter August 2017|August]]<br />
* [[FlightGear Newsletter September 2017|September]]<br />
* [[FlightGear Newsletter October 2017|October]]<br />
* [[FlightGear Newsletter November 2017|November]]<br />
* [[FlightGear Newsletter December 2017|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2016|January]]<br />
* [[FlightGear Newsletter February 2016|February]]<br />
* [[FlightGear Newsletter March 2016|March]]<br />
* [[FlightGear Newsletter April 2016|April]]<br />
* [[FlightGear Newsletter May 2016|May]]<br />
* [[FlightGear Newsletter June 2016|June]]<br />
* [[FlightGear Newsletter July 2016|July]]<br />
* [[FlightGear Newsletter August 2016|August]]<br />
* [[FlightGear Newsletter September 2016|September]]<br />
* [[FlightGear Newsletter October 2016|October]]<br />
* [[FlightGear Newsletter November 2016|November]]<br />
* [[FlightGear Newsletter December 2016|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2015|January]]<br />
* [[FlightGear Newsletter February 2015|February]]<br />
* [[FlightGear Newsletter March 2015|March]]<br />
* [[FlightGear Newsletter April 2015|April]]<br />
* [[FlightGear Newsletter May 2015|May]]<br />
* [[FlightGear Newsletter June 2015|June]]<br />
* [[FlightGear Newsletter July 2015|July]]<br />
* [[FlightGear Newsletter August 2015|August]]<br />
* [[FlightGear Newsletter September 2015|September]]<br />
* [[FlightGear Newsletter October 2015|October]]<br />
* [[FlightGear Newsletter November 2015|November]]<br />
* [[FlightGear Newsletter December 2015|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2014|January]] <br />
* [[FlightGear Newsletter February 2014|February]]<br />
* [[FlightGear Newsletter March 2014|March]]<br />
* [[FlightGear Newsletter April 2014|April]]<br />
* [[FlightGear Newsletter May 2014|May]]<br />
* [[FlightGear Newsletter June 2014|June]]<br />
* [[FlightGear Newsletter July 2014|July]]<br />
* [[FlightGear Newsletter August 2014|August]]<br />
* [[FlightGear Newsletter September 2014|September]]<br />
* [[FlightGear Newsletter October 2014|October]]<br />
* [[FlightGear Newsletter November 2014|November]]<br />
* [[FlightGear Newsletter December 2014|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2013|January]]<br />
* [[FlightGear Newsletter February 2013|February]]<br />
* [[FlightGear Newsletter March 2013|March]]<br />
* [[FlightGear Newsletter April 2013|April]]<br />
* [[FlightGear Newsletter May 2013|May]] <br />
* [[FlightGear Newsletter June 2013|June]]<br />
* [[FlightGear Newsletter July 2013|July]]<br />
* [[FlightGear Newsletter August 2013|August]]<br />
* [[FlightGear Newsletter September 2013|September]]<br />
* [[FlightGear Newsletter October 2013|October]]<br />
* [[FlightGear Newsletter November 2013|November]]<br />
* [[FlightGear Newsletter December 2013|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2012|January]]<br />
* [[FlightGear Newsletter February 2012|February]]<br />
* [[FlightGear Newsletter March 2012|March]]<br />
* [[FlightGear Newsletter April 2012|April]]<br />
* [[FlightGear Newsletter May 2012|May]]<br />
* [[FlightGear Newsletter June 2012|June]]<br />
* [[FlightGear Newsletter July 2012|July]]<br />
* [[FlightGear Newsletter August 2012|August]]<br />
* [[FlightGear Newsletter September 2012|September]]<br />
* [[FlightGear Newsletter October 2012|October]]<br />
* [[FlightGear Newsletter November 2012|November]]<br />
* [[FlightGear Newsletter December 2012|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2011|January]]<br />
* [[FlightGear Newsletter February 2011|February]]<br />
* [[FlightGear Newsletter March 2011|March]]<br />
* [[FlightGear Newsletter April 2011|April]]<br />
* [[FlightGear Newsletter May 2011|May]]<br />
* [[FlightGear Newsletter June 2011|June]]<br />
* [[FlightGear Newsletter July 2011|July]] <br />
* [[FlightGear Newsletter August 2011|August]]<br />
* [[FlightGear Newsletter September 2011|September]]<br />
* [[FlightGear Newsletter October 2011|October]]<br />
* [[FlightGear Newsletter November 2011|November]]<br />
* [[FlightGear Newsletter December 2011|December]] <br />
| valign="top" |<br />
* [[FlightGear Newsletter January 2010|January]]<br />
* [[FlightGear Newsletter February 2010|February]]<br />
* [[FlightGear Newsletter March 2010|March]]<br />
* [[FlightGear Newsletter April 2010|April]]<br />
* [[FlightGear Newsletter May 2010|May]]<br />
* [[FlightGear Newsletter June 2010|June]]<br />
* [[FlightGear Newsletter July 2010|July]]<br />
* [[FlightGear Newsletter August 2010|August]]<br />
* [[FlightGear Newsletter September 2010|September]]<br />
* [[FlightGear Newsletter October 2010|October]]<br />
* [[FlightGear Newsletter November 2010|November]]<br />
* [[FlightGear Newsletter December 2010|December]]<br />
| valign="top" |<br />
* [[FlightGear Newsletter July 2009|July]]<br />
* [[FlightGear Newsletter August 2009|August]]<br />
* [[FlightGear Newsletter September 2009|September]]<br />
* [[FlightGear Newsletter October 2009|October]]<br />
* [[FlightGear Newsletter November 2009|November]]<br />
* [[FlightGear Newsletter December 2009|December]]<br />
|}<br />
<br />
Some newsletter editions have been translated in other languages:<br />
* [[File:De.gif|16px|link=:De:FlightGear Newsletter]] [[:De:FlightGear Newsletter|Deutsch]]<br />
* [[File:Es.gif|16px|link=:Es:FlightGear Newsletter]] [[:Es:FlightGear Newsletter|Español]]<br />
* [[File:Fr.gif|16px|link=:Fr:FlightGear Newsletter]] [[:Fr:FlightGear Newsletter|Français]]<br />
<br />
=== You are invited to contribute! ===<br />
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. The FlightGear Newsletter is a community-driven newsletter, which means that it is created and edited by people like ''you''. You don't need to be a long-time FlightGear user (or even a developer) to contribute to the newsletter. <br />
<br />
In fact, helping write the monthly FlightGear newsletter is an excellent way for getting started contributing to the FlightGear community very quickly and very easily. <br />
<br />
Even if you don't have to add anything yourself, just reviewing and improving additions by others is also highly appreciated, as are efforts to help translate newsletters or add screen shots (e.g. taken from the forum or mailing lists) to the newsletter. Screen shots can be uploaded at [[Special:Upload]].<br />
<br />
Everyone with a wiki account (free to [[Special:UserLogin|register]]) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.<br />
<br />
A simple template providing a basic structure for each upcoming newsletter can be taken from [[Talk:Next newsletter]]. This template can be copied/pasted into each new newsletter to help users getting started providing contents.<br />
<br />
The draft for the upcoming newsletter can always be found at [[Next newsletter]].<br />
<br />
If English is not your native language, please don't be concerned about contributing to the newsletter, you can always easily ask fellow FlightGear users to review or proof-read your changes. Also, one of the easiest ways to get started is simply copying/pasting text from forum or mailing list discussions, such as announcements (e.g., new aircraft, new scenery, etc.).<br />
<br />
Another neat option to get started is adding links to FlightGear-related YouTube videos. For this, we have a dedicated section in each newsletter: "[[FlightGear Newsletter {{#time: F Y | last month }}#FlightGear on YouTube|FlightGear on YouTube]]."<br />
<br />
If you want to embed a video, please see {{mediawiki|Extension:EmbedVideo#Usage}}<br />
<br />
If you are looking for other ways to get involved, please see [[Volunteer]].<br />
<br />
[[Category:FlightGear Newsletter| ]]<br />
[[Category:Community|Newsletter]]<br />
[[Category:Lists|Newsletter]]<br />
<br />
[[de:FlightGear Newsletter]]<br />
[[es:FlightGear Newsletter]]<br />
[[fr:FlightGear Newsletter]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2023-08&diff=138121Template:POTM/2023-082023-08-09T09:34:02Z<p>Gijs: Gijs moved page Template:POTM/2023-08 to Template:POTM/2023-07</p>
<hr />
<div>#REDIRECT [[Template:POTM/2023-07]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2023-07&diff=138120Template:POTM/2023-072023-08-09T09:34:02Z<p>Gijs: Gijs moved page Template:POTM/2023-08 to Template:POTM/2023-07</p>
<hr />
<div>{{POTM<br />
| image = Boeing E-3 Sentry in North Italy with PBR and HDR.jpg<br />
| description = '''[[Boeing E-3 Sentry]]''' in North Italy with [[HDR Pipeline|HDR]] (PBR)..<br />
| article = Boeing E-3 Sentry<br />
}}<noinclude>[[Category:Picture of the month 2023]]</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:POTM/2023-07&diff=138119Template:POTM/2023-072023-08-09T09:33:37Z<p>Gijs: Created page with "{{POTM | image = Boeing E-3 Sentry in North Italy with PBR and HDR.jpg | description = '''Boeing E-3 Sentry''' in North Italy with HDR (PBR).. | art..."</p>
<hr />
<div>{{POTM<br />
| image = Boeing E-3 Sentry in North Italy with PBR and HDR.jpg<br />
| description = '''[[Boeing E-3 Sentry]]''' in North Italy with [[HDR Pipeline|HDR]] (PBR)..<br />
| article = Boeing E-3 Sentry<br />
}}<noinclude>[[Category:Picture of the month 2023]]</noinclude></div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Boeing_E-3_Sentry_in_North_Italy_with_PBR_and_HDR.jpg&diff=138118File:Boeing E-3 Sentry in North Italy with PBR and HDR.jpg2023-08-09T09:32:29Z<p>Gijs: Uploaded a work by User:Necolatis from {{forum url|t=41506}} with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=[[Boeing E-3 Sentry]] in North Italy with [[HDR Pipeline|HDR]] (PBR).}}<br />
|date=2023-06-16 19:48:23<br />
|source={{forum url|t=41506}}<br />
|author=[[User:Necolatis]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Boeing aircraft screenshots]]<br />
[[Category:Screenshots of AWACS aircraft]]<br />
[[Category:Compositor screenshots]]<br />
[[Category:Screenshot of the month/2023-07]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Category:Screenshot_of_the_month/2023-07&diff=138117Category:Screenshot of the month/2023-072023-08-09T09:32:19Z<p>Gijs: Created page with "Category:Screenshot of the month"</p>
<hr />
<div>[[Category:Screenshot of the month]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Antonov_An-225_Space_Shuttle_transport&diff=138081Antonov An-225 Space Shuttle transport2023-08-07T08:23:20Z<p>Gijs: /* Related content */ remove reference to deleted article</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
{{WIP}}<br />
{{for|the An-225 in the official [[FGAddon]] aircraft repository|Antonov An-225 Mriya}}<br />
<br />
[[File:Spacetripready.png]]<br />
<br />
The '''Antonov An-225 ''Mriya''''' (NATO reporting name: '''Cossack''') is a transport aircraft with six turbofan engines. It first flew in the 1980s and was developed from the smaller four-engined [[Antonov An-124]].<br />
<br />
The Antonov An-225 is the longest and heaviest airplane ever built. Is part of the [[FlightGear Space Program]] with assigned cargo missions for you around the Space Program Airport Network. See [[FlightGear space program missions|mission list]]<br />
<br />
== Development status/Issues/Todo ==<br />
'''Outside:'''<br />
* Complete model. Outstanding gear animation with steering of 16 tail wheels<br />
* ToDo: cargo and crew doors, interior for cargo room <br />
<br />
'''Cockpit:'''<br />
* 3d cockpit is available<br />
<br />
'''General:'''<br />
* Shuttle doors should be closed before take off, payload for Shuttle is set. ILS landing is now working for this aircraft. Navigation Lights are on the middle switch, instrument lights on the right one, both on the panel with the 3 switches. 7 steps of flaps, 4 steps of slats, 4 steps of spoilers, landing speed is about 150 kt.<br />
<br />
'''New Version:'''<br />
<br />
The new version of the Antonov An-225 has now 2 models to transport, reverser, a complete navigation system and sounds.<br />
<br />
http://github.com/HerbyW/AN-225-Mrija<br />
<br />
[[File:225ready.png|thumb|An-225 SpaceShuttle Transport ready.]]<br />
== Variants ==<br />
<br />
* AN-225 Tank transport<br />
* AN-225 SpaceShuttle transport<br />
<br />
All variants are included in the main model. User can change the variant easily in runtime just by a switch in the cockpit panel.<br />
== Aircraft help ==<br />
[[File:An225b.png|thumb|Antonov An-225 Mriya Badge]]<br />
<br />
<br />
=== Cheat sheet ===<br />
{| class="keytable"<br />
!Key<br />
!Function<br />
|-<br />
| {{Key press|&lt;}} || Toggle between pilot/engineer view <br />
|-<br />
|{{Key press|Shift}} + {{Key press|B}}<br />
|Set or unset the parking brake.<br />
|-<br />
|{{Key press|j}}<br />
|Retract the spoilers.<br />
|-<br />
|{{Key press|k}}<br />
|Extend the spoilers.<br />
|-<br />
|{{Key press|K}}<br />
|Toggle trajectory markers.<br />
|-<br />
|{{Key press|G}}<br />
|Raise the landing gear.<br />
|-<br />
|{{Key press|Shift}} + {{Key press|G}}<br />
|Lower the landing gear.<br />
|-<br />
|{{Key press|]}}<br />
|Lower flaps.<br />
|-<br />
|{{Key press|[}}<br />
|Raise flaps.<br />
|-<br />
|{{Key press|f}}<br />
|Lower slats.<br />
|-<br />
|{{Key press|d}}<br />
|Raise slats.<br />
|-<br />
|{{Key press|h}}<br />
|Hide or show the HUD.<br />
|-<br />
|{{Key press|U}}<br />
|Update drop view position.<br />
|-<br />
|{{Key press|F2}}<br />
|Activate and deactivate the reverser.<br />
|-<br />
|{{Key press|F11}}<br />
|Open autopilot dialog.<br />
|-<br />
|{{Key press|:}}{{Key press|D}}{{Key press|f}} <br />
|Open payload and fuel dialog. Case sensitive.<br />
|}<br />
<br />
== Compatibility ==<br />
The AN-225 is been developing and tested on several platforms, including GNU/Linux, Windows XP, Windows 7, and Mac OS X with FlightGear 3.2 3.4 and GIT.<br />
<br />
== Thanks to... ==<br />
* Lee Elliot<br />
=== Test pilots ===<br />
3m, D-Leon, Michatov, Ph-Cor<br />
=== Technical systems assistance ===<br />
HerbyW<br />
=== Custom Propulsion integration ===<br />
HerbyW<br />
<br />
== Related content ==<br />
* [[FlightGear space program missions]]<br />
* [[Space Shuttle (FG Space Program)]]<br />
* [[Antonov An-22A]]<br />
* [[Antonov An-12BK]]<br />
* [[Shuttle Landing Facility]]<br />
<br />
{{Antonov}}<br />
<br />
[[Category:Community|Space Program]]<br />
[[Category:Red Griffin ATC compatible aircraft]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Talk:FGAddon&diff=137953Talk:FGAddon2023-07-28T09:09:27Z<p>Gijs: /* Launcher? */</p>
<hr />
<div>__TOC__<br />
== Templates instead of explicit URLs ==<br />
: ''Moved here from [[FlightGear wiki:Village pump#Repository link templates]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=88830#Repository_link_templates perm]).''<br />
<br />
The [[FGAddon]] article could greatly benefit from being reviewed with a focus on getting rid of/generalizing explicit URLs (or even git instructions) in favor of using templates that encapsulate any URL/git specifics, so that things can be more easily updated in the future. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 03:01, 20 September 2015 (EDT)<br />
<br />
: Is there a listing or category page for such templates? I haven't found where these are collected, and cannot find the relevant template. The SF URLs are very diverse in this article, e.g.:<br />
<br />
<syntaxhighlight lang="bash"><br />
svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<br />
svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DaSH<br />
svn+ssh://<username>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<aircraft><br />
https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<br />
https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DaSH<br />
https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<aircraft><br />
https://sourceforge.net/u/<username>/profile/<br />
https://sourceforge.net/u/<username>/code-fkdr1/ci/master/tree/<br />
ssh://<username>@git.code.sf.net/u/<username>/code-<aircraft><br />
https://sourceforge.net/u/<username>/code-<aircraft>/ci/master/tree<br />
ssh://<username>@git.code.sf.net/u/<username>/code-ornithopter<br />
https://sourceforge.net/u/<username>/code-ornithopter/ci/master/tree/<br />
ssh://<username>@git.code.sf.net/u/<username_leader>/code-ornithopter<br />
</syntaxhighlight><br />
<br />
: Some of these URLs are highly specific to the very detailed and reqired instructions on the page. The parts in angular brackets <> should be presented in these brackets on the page to indicate that the reader replaces it with the relevant value. So these are not followable URLs anyway. And can templates be used in the <nowiki><syntaxhighlight></nowiki> tags? Note that none of these are for the SF web interface, for which all the templates I've seen so far are for.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:58, 27 October 2015 (EDT)<br />
<br />
:: The idea can be seen at [http://wiki.flightgear.org/Template:Git_clone] - i.e. originally, we were hoping to grow a library of templates that can be parameterized, not just in terms of "actions" (clone, update/pull, push etc), but also in front-end terms - e.g. by adding screen shots for different front-ends and dynamically showing the matching UI front-end (or shell instructions). ::: The whole thing was inspired by the discussion at [[Talk:Development Workflow]]. For instance, for NetBeans: [[File:Netbeans-staying-up2date.png|thumb|git pull via NetBeans]]<br />
:: --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:05, 27 October 2015 (EDT)<br />
<br />
::: In an abstract way, I can see how this would be useful. In a concrete way - i.e. the fine details of how this should be implemented - I cannot see this yet. I need some time to think about it. The main issue is that the exact commands to type, which are essential and without which the article cannot function, are very much specific to the prompt UI of svn, git, and git-svn. Each GUI does this differently, packaging a number of the commands into one menu entry or button. I think for this task that the GUI diversity is insane, and we cannot provide full coverage, and that the major focus of the article should be the command line.<br />
<br />
::: For URL templates, some of these may have a slight advantage. However look at history - of the Gitoriuos to SF transition. If we had had Gitorious templates, these and there surrounding instructions would be hopelessly out of date and nothing could be done in the template to fix it. The fixing action would be to search for all instances in the wiki and replace, and this would be the same amount of work with or without the template. The other situation where a template would be useful is if the SF url changes. However this might require a template change and search+fix all instances anyway. Also the SF urls are pretty much fixed in stone and very unlikely to change. So template+template usage costs may be higher than pure command+url usage. From a pure cost analysis perspective, I'm not convinced of the benefit yet.<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:22, 28 October 2015 (EDT)<br />
<br />
<br />
::: Let me add, that for that long list of specific SF URLs above, that 0% of these are covered by the current {{tl|repo link}} template.<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:55, 28 October 2015 (EDT)<br />
<br />
== History of the fgdata split ==<br />
<br />
Hooray, I would prefer not to have the following changes:<br />
* http://wiki.flightgear.org/index.php?title=FGAddon&diff=98220&oldid=98157<br />
* http://wiki.flightgear.org/index.php?title=FGAddon&diff=98222&oldid=98221<br />
* http://wiki.flightgear.org/index.php?title=FGAddon&diff=98223&oldid=98222<br />
Firstly, any mention of FGMEMBERS is irrelevant to FGAddon. Ok, they wish to [https://forum.flightgear.org/viewtopic.php?f=85&t=29559&start=15#p284835 slaughter] FGAddon, but that has zero business in this article. Secondly a lot of the introduced text is a repetition of what is already there. Look at your text where you are quoting my statements about Gijs, and then look at the next paragraph that says "A first splitting attempt was organised by Gijs de Rooy and announced on October 18, 2011". I didn't mention Cedric, but he is listed in the reference at the bottom of the page. But the quote is an almost perfect doubling up of the text - the quote origin is essentially quoting from here, and that is now coming back. As for Curt's quote, this is justifying why SourceForge was used, in the context of FGMEMBERS attacks. I think my original sentence "Other parts of the FlightGear infrastructure were already hosted by SourceForge, making the move a natural one." is sufficient and a positive outlook on the subject, as it is and should be seen. This history section is about presenting the facts. The excessive justifications demanded from the FlightGear community by FGMEMBERS does not in any way belong in here! All of the facts are from long before [http://thread.gmane.org/gmane.games.flightgear.devel/78933/focus=78940 FGMEMBERS came into existence].<br />
<br />
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:22, 14 May 2016 (EDT)<br />
<br />
<br />
You are free to review/edit and revert the corresponding additions, like I said, they were not intended to stay "as is". However, the history section is currently incomplete anyway, and that "fgmembers" ended up in it, is merely because I took '''your''' quote ;-) The current forum debate illustrates that it does make sense to mention that we've had other attempts, and that they failed. Anyway, feel free to revert. I just think that the history section could have the potential to explain things that people ask about on the forum - even without mentioning fgmembers specifically.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 09:38, 14 May 2016 (EDT)<br />
<br />
: It's already all there. For example:<br />
<br />
:* '''Original:''' A first splitting attempt was organised by Gijs de Rooy and announced on October 18, 2011[9]. Each aircraft was placed in its own Git repository and all aircraft linked back to fgdata using a Git submodule approach. However this attempt failed and was abandoned. From this date until the end of 2014, the design of the fgdata split was discussed on the development mailing list and summarised in the FlightGear Git: splitting fgdata wiki article. In the planning stages, the repositories were known as fgdata-old splitting into FGData (a.k.a. fgdata-new) and FGAddon (a.k.a. flightgear-aircraft and fgaircraft). After half a decade of planning, it was decided that the best solution for FlightGear aircraft development would be a single centralized Subversion repository. This would facilitate community management and maintenance of the aircraft while at the same time providing modularity and smaller downloads and smaller local repository sizes. <br />
<br />
:* '''New addition:''' Back in Oct 2011, the group decided to go with the git submodule approach, as lead by Gijs. However Gijs found a number of fatal issues with the approach, the exact same issues are actually currently found in the FGMEMBERS aircraft repositories, and there were enough voices on the list to stop with the git submodules and to search for an alternative, that ended up being SVN. Cedric was obviously not happy after spending so much effort on creating the full git submodule system with one repository per aircraft[7] - a system identical to the FGMEMBERS aircraft repositories.[8]<br />
<br />
: Cedric is the first name in reference 9, so apart from the mention of FGMEMBERS, the two pieces of text say exactly the same thing. This is not coincidence ;) A duplication is confusing, and the second piece of text is just one of many regurgitations of the history that FGMEMBERS proponents repetitively and incessantly ask for (to somehow try to [https://forum.flightgear.org/viewtopic.php?f=85&t=29559&start=15#p284835 slaughter FGAddon]). For the second addition:<br />
<br />
:* The short summary is that we already were maintaining a well established presence on sourceforge. So after quite a bit of discussion, we decided to consolidate there. In addition, we had a perpetual complaint that the fgdata git repository was far too big for most people to initially download (1Gb+). Thus we split off most of the aircraft (expecting unbounded future growth potential) into an svn repository called fgaddon. Sourceforge supports both git and svn repositories. This puts a dependency on a central svn server for our fgaddon aircraft repository, but lightens the weight for anyone wanting to checkout a copy of everything (you don't need a copy of the entire development history, and a copy of every version ever created of every aircraft if you just want to have the latest versions.) Plus svn allows checking out subtrees (without needing the whole repository) so this can also serve as a potential JIT single aircraft service provider. Of course there are always multiple ways to solve every problem and of course every engineering decision has trade offs. Github is a nice provider, no doubt.[10]<br />
<br />
: This too is repetitive and long. For example sentence 1 is covered by "Other parts of the FlightGear infrastructure were already hosted by SourceForge...". Sentence 3 is the early text "...the fgdata repository mushroomed...". The lightening the weight might be useful, but as a few words at the point where the split is first mentioned. I'll revert, but see if there are a few small things that can be added without this having to look like an attempt to justify the right for FGAddon to exist. And I'll try to keep this light, as needed for a 20 year summary of all the FlightGear asset history.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:32, 14 May 2016 (EDT)<br />
<br />
== Request for “Contributing” section ==<br />
<br />
The page deals with using, and then with developing aircraft. But there is a very important middle-ground: people who like to fly this for a bit and then that for a bit, find issues and want to report those issues and possibly have a simple patch worth a couple of lines to fix it. Such people (like me) are not really interested in setting up development branches nor getting commit access. They just need:<br />
<br />
# A documented, '''on this page''' and the sourceforge project page, and reasonably simple way to report those issues that is preferably:<br />
## Consistent across all the aircraft. I.e. it shouldn't be this email for one aircraft, that forum thread for second and another github repo for third. If that is the status quo and can't be improved on, at least there should be one place where the correct way for each aircraft could be found: not all aircraft have wiki pages, not all have README, etc.<br />
## With public record. Bug tracker is best, but forum or mailing list are fine as long as it does not depend on one maintainer who might have gone MIA without anyone noticing.<br />
# Similarly documented best practice how to prepare and send patches to maximise the chance that the repository maintainers will accept and merge them.<br />
<br />
Would anybody please be able to add that info before the [[http://wiki.flightgear.org/FGAddon#Aircraft_development Aircraft development]] section? Or at least give me hint where to find such information so I could copy it over here?<br />
<br />
Thanks<br />
<br />
<small>Note: This is, for me, benefit of the FGMEMBERS—it is clear that the appropriate channel is the github issue tracker for each aircraft. However I worked in many settings and don't mind the particulars. Whatever works for the core team is fine be it a mailing list, forum or whatever kind of tracker. It just needs to be obvious and in case of FGAddon (and to large extent FlightGear itself too) it never was to me.</small><br />
<br />
—[[User:JanHudec|JanHudec]] ([[User talk:JanHudec|talk]]) 10:03, 26 July 2016 (EDT)<br />
<br />
: This is a fair point - I'll add some information about the FlightGear tracker - https://sourceforge.net/p/flightgear/codetickets/?source=navbar - for posting patches, files, etc.<br />
<br />
: Note though that this is complex because of how the FGAddon repository is used. A large number (likely >75%) of aircraft are managed and developed in external 3rd party hangars. That is why the most important point is to contact the original author ([[FGAddon#Contact the original aircraft authors]]). For example the [[:Category:Helijah hangar|Helijah hangar]] consists of 275+ actively maintained aircraft in [[FGAddon]]. For these it is best to directly contact Emmanuel rather than use the tracker. The same goes with many other aircraft - simply contact the original author. Anyway, you'll be told if you use that FG tracker for an actively maintained aircraft to go to the original source.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:33, 26 July 2016 (EDT)<br />
<br />
:: It would be great if the maintainers could be, gradually, persuaded to use a common tracker. It would make it easier for others to contribute. But obviously it's not gonna change overnight (I guess that's big part of the reason FGMEMBERS don't work). Documenting the status quo is an important first step. Thank you.<br />
<br />
:: —[[User:JanHudec|JanHudec]] ([[User talk:JanHudec|talk]]) 10:44, 26 July 2016 (EDT)<br />
<br />
::: It also depends on the motivation of the original authors. Again for example take a look at the Helijah hangar: http://helijah.free.fr/flightgear/hangar.htm. For Emmanuel, it is a lot of work to actively follow a tracker for 275+ aircraft. A simple email or post on his dedicated forum - http://embaranger.free.fr/ - is more efficient for him, and is his preferred way of working. I am specifically redesigning the {{tl|infobox aircraft}} template to help direct potential contributors to the correct original source.<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:00, 26 July 2016 (EDT)<br />
<br />
:::: That's great too. Unfortunately of the 275+ aircraft (to continue that example), the [[:Category:Helijah hangar]] only has 22…<br />
:::: Also, good tracker, when properly configured, is easy to follow: when the component (aircraft) is correctly filled in, it should send notification to the respective maintainer and it should provide the maintainer an overview of outstanding issue in the components (aircraft) they maintain. But I understand it's not easy to change one's habits.<br />
:::: —[[User:JanHudec|JanHudec]] ([[User talk:JanHudec|talk]]) 11:18, 26 July 2016 (EDT)<br />
<br />
::::: If you look at the recent wiki history ([[Special:RecentChanges]]), you'll see that I'm in the process of converting the 486 [[:Category:All aircraft|aircraft pages]] to the new template. This is no easy task! Have a look at the [[:Category:Unknown hangar]] at [[:Category:Aircraft by hangar]] to get an idea. Also a lot in [[:Category:FGAddon hangar]] still have to be tagged with the 'devel-hangar' parameter to categorize all those external hangars hosted within FGAddon.<br />
<br />
::::: For the tracker, you can assign an "owner", and everyone with current FGAddon access is listed (a number of authors are still to sign up, but they have effectively retired). Many authors for the external hangars in FGAddon however prefer direct contact.<br />
<br />
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:50, 26 July 2016 (EDT)<br />
<br />
== Launcher? ==<br />
<br />
Hi, i tought that the launcher also downloads from the version-tagged fgaddon tree?<br />
<br />
Should the page be revised in this regards?<br />
<br />
: Correct! For quite a while now actually... Please go ahead and update the [[FGAddon#Obtaining aircraft|Obtaining aircraft]] section.<br />
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:09, 28 July 2023 (UTC)</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Boeing_737_MAX_9_Icelandair_takeoff_roll.png&diff=137668File:Boeing 737 MAX 9 Icelandair takeoff roll.png2023-05-11T08:35:32Z<p>Gijs: Fix category</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Ready to roll}}<br />
|date=2023-05-10<br />
|source=Discord<br />
|author=SP Ntx<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Boeing 737 screenshots]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Fgfs-20230307234618.png&diff=137667File:Fgfs-20230307234618.png2023-05-11T08:33:52Z<p>Gijs: Gijs moved page File:Fgfs-20230307234618.png to File:Boeing 737 MAX 9 Icelandair takeoff roll.png: More descriptive title</p>
<hr />
<div>#REDIRECT [[File:Boeing 737 MAX 9 Icelandair takeoff roll.png]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=File:Boeing_737_MAX_9_Icelandair_takeoff_roll.png&diff=137666File:Boeing 737 MAX 9 Icelandair takeoff roll.png2023-05-11T08:33:51Z<p>Gijs: Gijs moved page File:Fgfs-20230307234618.png to File:Boeing 737 MAX 9 Icelandair takeoff roll.png: More descriptive title</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Ready to roll}}<br />
|date=2023-05-10<br />
|source=Discord<br />
|author=SP Ntx<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{cc-by-sa-4.0}}<br />
<br />
[[Category:Max for takeoff]]</div>Gijshttps://wiki.flightgear.org/w/index.php?title=Template:Boeing&diff=137664Template:Boeing2023-05-10T08:49:24Z<p>Gijs: Add Boeing 737 MAX</p>
<hr />
<div>{{Navbox<br />
| name = Boeing<br />
| title = {{LangSwitch<br />
| de = [[:Category:Boeing|Boeing]] Flugzeuge<br />
| en = [[:Category:Boeing|Boeing]] aircraft<br />
| fr = Aéronefs [[:Category:Boeing|Boeing]]<br />
| zh = [[:Category:Boeing|波音]]飞机<br />
}}<br />
| listclass = hlist<br />
<br />
| group1 = {{LangSwitch<br />
| de = Ziviles Flugzeuge<br />
| en = Civilian aircraft<br />
| fr = Aéronefs civil<br />
| zh = 民用飞机<br />
}}<br />
| list1 =<br />
* {{LangSwitch<br />
| de = [[:de:Boeing 314|314]]<br />
| en = [[Boeing 314|314]]<br />
}}<br />
* {{LangSwitch<br />
| de = [[Boeing 707|707]] ([[Boeing 707-320|-320C]]/[[Boeing 707-320|-3J9C]]/[[Boeing 707-338|-338]]/[[Boeing 707-400|-400]]/[[:de:Boeing 707-420|-420]])<br />
| en = [[Boeing 707|707]] ([[Boeing 707-320|-320C]]/[[Boeing 707-320|-3J9C]]/[[Boeing 707-338|-338]]/[[Boeing 707-400|-400]]/[[Boeing 707-420|-420]])<br />
| pt = [[:pt:Boeing 707|707]] ([[Boeing 707-320|-320C]]/[[Boeing 707-320|-3J9C]]/[[Boeing 707-338|-338]]/[[:pt:Boeing 707-400|-400]]/[[Boeing 707-420|-420]])<br />
}}<br />
* {{LangSwitch<br />
| de = [[:de:Boeing 717|717]]<br />
| en = [[Boeing 717|717]]<br />
}}<br />
* {{LangSwitch<br />
| de = [[:de:Boeing 727|727]] ([[727-200|-200]]/[[:de:Boeing 727-230|-230]])<br />
| en = [[Boeing 727|727]] ([[727-200|-200]]/[[Boeing 727-230|-230]])<br />
}}<br />
* {{LangSwitch<br />
| de = [[Boeing 737|737]] ([[:de:Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737-400|-400]]/[[Boeing 737-500|-500]]/[[Boeing 737NG|NG]]/[[Boeing 737 MAX|MAX]])<br />
| en = [[Boeing 737|737]] ([[Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[Boeing 737-400|-400]]/[[Boeing 737-500|-500]]/[[Boeing 737NG|NG]]/[[Boeing 737 MAX|MAX]])<br />
| fr = [[Boeing 737|737]] ([[Boeing 737-100|-100]]/[[Boeing 737-300|-300]]/[[:fr:Boeing 737-400|-400]]/[[Boeing 737-500|-500]]/[[Boeing 737NG|NG]]/[[Boeing 737 MAX|MAX]])<br />
}}<br />
* {{LangSwitch<br />
| de = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[:de:Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])<br />
| en = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])<br />
| nl = [[Boeing 747|747]] ([[Boeing 747-100|-100]]/[[Boeing 747-200|-200]]/[[:nl:Boeing 747-400|-400]]/[[Boeing 747-8i|-8]])<br />
}}<br />
* [[Boeing 757-200|757-200]]<br />
* [[Boeing 767-300|767-300]]<br />
* {{LangSwitch<br />
| en = [[Boeing 777|777]] ([[Boeing 777-200|-200]]/[[Boeing 777-200LR|-200LR]]/[[Boeing 777-300|-300]]/[[Boeing_777-F|-F]])<br />
| fr = [[:fr:Boeing 777|777]] ([[Boeing 777-200|-200]]/[[Boeing 777-200LR|-200LR]]/[[Boeing 777-300|-300]]/[[Boeing_777-F|-F]])<br />
}}<br />
* [[Boeing 787-8 Dreamliner|787-8]]<br />
<br />
| group2 = {{LangSwitch<br />
| de = Militärisches Flugzeuge<br />
| en = Military aircraft<br />
| fr = Aéronefs militaire<br />
| zh = 军用飞机<br />
}}<br />
| list2 =<br />
* {{LangSwitch<br />
| de = [[:de:Douglas A-4 Skyhawk|A-4]]<br />
| en = [[Douglas A-4 Skyhawk|A-4]]<br />
}}<br />
* {{LangSwitch<br />
| en = [[Boeing-Stearman Model 75|PT-17]]<br />
| es = [[:es:Boeing-Stearman Model 75|PT-17]]<br />
}}<br />
* [[Boeing B-17 Flying Fortress|B-17]]<br />
* {{LangSwitch<br />
| en = [[Boeing B-29 Superfortress|B-29]]<br />
| fr = [[:fr:Boeing B-29 Superfortress|B-29]]<br />
}}<br />
* [[Boeing B-52|B-52]]<br />
* [[C-17]]([[C-17 Globemaster III]]/[[C-17 Globemaster III (FGMEMBERS)]])<br />
* [[Boeing 757-200|C-32A]]<br />
* [[Boeing 757-200|C-32B]]<br />
* [[Boeing E-3 Sentry|E-3]]<br />
* {{LangSwitch<br />
| en = [[McDonnell Douglas F-15 Eagle|F-15]]<br />
| fr = [[:fr:McDonnell Douglas F-15 Eagle|F-15]]<br />
}}<br />
* [[Boeing KC-135E|KC-135E]]<br />
<br />
| group3 = {{LangSwitch<br />
| de = Hubschrauber<br />
| en = Helicopters<br />
| fr = Hélicoptères<br />
| zh = 直升机<br />
}}<br />
| list3 =<br />
* [[AH-64 Apache|AH-64]]<br />
* [[CH-47 Chinook Helicopter|CH-47]]<br />
* [[Boeing-Sikorsky RAH-66 Comanche|RAH-66]]<br />
* [[Bell Boeing V-22 Osprey|V-22]]<br />
}}<includeonly>{{main other|[[Category:Boeing]]}}</includeonly><noinclude><br />
{{Informative template|1=<br />
__NOTOC__<br />
== Goal ==<br />
This navigation template links together aircraft manufactured by Boeing.<br />
<br />
Adding this template to a page in the article namespace will automatically add [[:Category:Boeing]] to that page.<br />
<br />
== Usage ==<br />
Put this line before the categories and the language links at the bottom of the article.<br />
<br />
{{obr}}'''Boeing'''{{cbr}}<br />
<br />
}}<br />
<br />
[[Category:Manufacturer navigation templates]]<br />
</noinclude></div>Gijs