FlightGear wiki - User contributions [en]

Category:Concepts

2022-03-30T14:43:41Z

Gordon: wording

These screen shots did not actually exist in the software at the time of creation, but were modified in an image editing software to illustrate feature suggestions.

[[Category:Screenshots]]

Category:Concepts

2022-03-29T02:12:05Z

Gordon: wording

These screen shots did not actually exist in the software at the time of uploading, but were modified in an image editing software to illustrate feature suggestions.

[[Category:Screenshots]]

File:FlightGear manually specified fuel levels concept.png

2022-03-29T02:10:03Z

Gordon: Category:Screenshots, Category:Concepts

== Summary ==
{{File information
|Description = I created this concept back in 2016, but never happened to share it, until I randomly stumbled upon it again.
|Source = FlightGear; modified by [[User:Gordon]] in 2016.
|Date = 2016
|Author = FlightGear, [[User:Gordon]]
}}

=={{int:license-header}}==
{{GPL}}
[[Category:Screenshots]]
[[Category:Concepts]]

File:FlightGear manually specified fuel levels concept.png

2022-03-29T02:09:39Z

Gordon: /* Summary */ fill

File:FlightGear manually specified fuel levels concept.png

2022-03-29T02:09:16Z

Gordon: == Summary == {{File information |Description = I created this concept back in 2016, but never happened to share it, until I randomly stumbled upon it again. |Source = aargucag.png |Date = 2016 |Author = FlightGear, User:Gordon }} =={{int:license-header}}== {{GPL}}

== Summary ==
{{File information
|Description = I created this concept back in 2016, but never happened to share it, until I randomly stumbled upon it again.
|Source = aargucag.png
|Date = 2016
|Author = FlightGear, [[User:Gordon]]
}}

=={{int:license-header}}==
{{GPL}}

File:Boeing 707 engine thrust meter close-up view.png

2022-03-29T02:03:15Z

Gordon: Removing :Category:Concepts: this screenshot is not a concept. Category was added accidentially.

=={{int:filedesc}}==
{{Information
|description={{en|1=Close-up view of [[Boeing 707]] engine thrust meter (N<sub>2</sub>). It is suggested to vectorize the markers on the meters so they remain sharp at a close-up view, which would be closer to the real-world Boeing 707.}}
|date=2018
|source=Source unknown. Downloaded in 2018.
|author=FlightGear, Marc Kraus
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
{{GPL}}

[[Category:Boeing 707 cockpit detail screenshots]]

File:Boeing 707 engine thrust meter close-up view.png

2022-03-29T02:02:29Z

Gordon: Category:Concepts

File:FGRun window shortcut concept.png

2022-03-29T02:01:55Z

Gordon: :Category:Concepts

=={{int:filedesc}}==
{{Information
|description={{en|1=I am fully aware [[FGRun]] is deprecated. This is just for historical reference, since I can not find the source. Whichever image hoster this was uploaded to appears to have shut down.

Source file name: tdxc8je2.png}}
|date=2015
|source=Downloaded from unknown location in 2017.
|author=FlightGear
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
{{GPL}}

[[Category:FGRun screenshots]]
[[Category:Concepts]]

Category:Concepts

2022-03-29T02:01:32Z

Gordon: Created page with "These screen shots did not actually exist in the game at the time of uploading, but were modified in an image editing software to illustrate feature suggestions. Category:S..."

These screen shots did not actually exist in the game at the time of uploading, but were modified in an image editing software to illustrate feature suggestions.

[[Category:Screenshots]]

File:FlightGear window transparency slider concept.png

2022-03-29T01:59:47Z

Gordon: Category:Screenshots, Category:Concepts

File:FlightGear window transparency slider concept.png

2022-03-29T01:57:03Z

Gordon: /* Summary */ source

File:FlightGear window transparency slider concept.png

2022-03-29T01:56:46Z

Gordon: == Summary == {{File information |Description = I created this concept back in 2016, but never happened to share it, until I randomly stumbled upon it again. |Source = cve9rw8s.png |Date = 2016 |Author = FlightGear, User:Gordon }} =={{int:license-header}}== {{GPL}}

== Summary ==
{{File information
|Description = I created this concept back in 2016, but never happened to share it, until I randomly stumbled upon it again.
|Source = cve9rw8s.png
|Date = 2016
|Author = FlightGear, [[User:Gordon]]
}}

=={{int:license-header}}==
{{GPL}}

File:FGRun window shortcut concept.png

2022-03-28T21:54:31Z

Gordon: Uploaded a work by FlightGear from Downloaded from unknown location in 2017. with UploadWizard

File:Boeing 707 cabin seats 59ajoxr7.png

2022-03-28T21:11:58Z

Gordon: Gordon moved page File:Boeing 707 cabin seats 59ajoxr7.png to File:Boeing 707 cabin seats as of 2016.png: Added year to title.

#REDIRECT [[File:Boeing 707 cabin seats as of 2016.png]]

File:Boeing 707 cabin seats as of 2016.png

2022-03-28T21:11:58Z

Gordon: Gordon moved page File:Boeing 707 cabin seats 59ajoxr7.png to File:Boeing 707 cabin seats as of 2016.png: Added year to title.

=={{int:filedesc}}==
{{Information
|description={{en|1=Incomplete seat models of the Boeing 707 cabin as of 2016.}}
|date=2016
|source=FlightGear [[Boeing 707]] cabin
|author=FlightGear Marc Kraus
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
{{GPL}}

[[Category:Boeing 707 screenshots]]

File:Boeing 707 cabin seats as of 2016.png

2022-03-28T21:05:53Z

Gordon: Uploaded a work by FlightGear Marc Kraus from FlightGear Boeing 707 cabin with UploadWizard

User talk:Erik

2022-03-28T19:10:19Z

Gordon: /* Upload wizard */ 2 responses

== Upload wizard ==

Hi Erik,

I noticed that you didn't use the [[Special:UploadWizard|upload wizard]] when uploading some files recently. Any specific reason for that, or was it by accident? Using the wizard ensures all the fields (description, categories, license) are complete, which your recent files now lack (e.g., [[:File:Pc7mkx.jpg]]).

Thanks!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:11, 28 February 2022 (UTC)

: It's because the wiki user interface is really counter intuitive. At times I really hate it.
: I'm still not sure this is the correct way tot respond.
: {{unsigned|11:44, 26 March 2022‎|Erik}}

:: Hi Erik,
:: If you write "I really hate it", does that refer to the new upload wizard, or the wiki in general?
:: I was only wondering how you reached the "old" legcacy upload form, as the new UploadWizard is meant to make the upload process easier (and possibly a bit slower, but that's because it forces you to fill in some essential details that were often missing). I see you've managed to find it for your latest uploads, but it'd still help if you could tell me what exact steps you used to upload files through the old form. I'd like to move people away from the legacy form and thought I had moved all links to the new form, but apparently not.
:: Talk pages are indeed a bit of a hassle on wikis, but you did the correct thing to respond to this message! Note that you can "sign" your messages on talk pages with your name and the data/time, by typing four tildes (<code><nowiki>~~~~</nowiki></code>).
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 07:37, 28 March 2022 (UTC)
::: This is a civil and sincere response to criticism. Bravo! [[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 19:10, 28 March 2022 (UTC)

:: Erik, how is it different from other wikis? [[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 19:10, 28 March 2022 (UTC)

File:Boeing 707 engine thrust meter close-up view.png

2022-03-28T15:16:03Z

Gordon: description

File:Boeing 707 engine thrust meter close-up view.png

2022-03-28T15:13:57Z

Gordon: Gordon uploaded a new version of File:Boeing 707 engine thrust meter close-up view.png

=={{int:filedesc}}==
{{Information
|description={{en|1=Close-up view of [[Boeing 707]] engine thrust meter (N<sub>2</sub>)}}
|date=2018
|source=Source unknown. Downloaded in 2018.
|author=FlightGear, Marc Kraus
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
{{GPL}}

[[Category:Boeing 707 cockpit detail screenshots]]

File:Boeing 707 engine thrust meter close-up view.png

2022-03-28T14:57:49Z

Gordon: Gordon moved page File:Qjioqyb2(2).png to File:Boeing 707 engine thrust meter close-up view.png: more descriptive file name

File:Boeing 707 engine thrust meter close-up view.png

2022-03-28T14:56:49Z

Gordon: Uploaded a work by FlightGear, Marc Kraus from Source unknown. Downloaded in 2018. with UploadWizard

MediaWiki talk:Noarticletext

2022-03-28T14:44:20Z

Gordon: Created page with "I suggest slightly greying the background of the notice, as shown in the sandbox (Special:PermanentLink/134854), so the viewer sees on first glance that it is a notice box..."

I suggest slightly greying the background of the notice, as shown in the sandbox ([[Special:PermanentLink/134854]]), so the viewer sees on first glance that it is a notice box and not page content. ––[[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 14:44, 28 March 2022 (UTC)

FlightGear wiki:Sandbox

2022-03-28T14:39:45Z

Gordon: Suggestion for MediaWiki:Noarticletext

== Suggestion for [[MediaWiki:Noarticletext]] ==
<div class=noarticletext style="background-color:#eee; padding:1em;">
There is currently no text in this page.
You can [[Special:Search/{{PAGENAME}}|search for this page title]] in other pages,
<span class="plainlinks">[{{fullurl:{{#Special:Log}}|page={{FULLPAGENAMEE}}}} search the related logs],
or [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this page]</span>.

{{#switch: {{FULLPAGENAME}}
| Enter your new article name here =
{{Editnotices/Page/Enter your new article name here}}
| Wikipedia talk:Articles for creation/Enter your new article name here =
{{Editnotices/Page/Wikipedia talk:Articles for creation/Enter your new article name here}}
| #default =
{{#switch: {{lc: {{SUBJECTSPACE}}#{{SUBPAGENAME}} }}
| user#skin.js
| user#skin.css = {{skin-file disambig}}
| #default =


{{#ifexist: {{FULLPAGENAME}})
| <div class="searchdidyoumean">Did you mean: [[{{FULLPAGENAME}})|{{FULLPAGENAME}}<em>)</em>]]</div>
}}{{#ifeq: {{NAMESPACE}} | User talk
| '''No messages''' have been posted for this user yet.
| '''The FlightGear wiki does not have {{#switch: {{NAMESPACE}}
| {{ns:0}} = an article
| {{TALKSPACE}} = a [[{{ns:Help}}:Talk page|talk page]]
| {{ns:Category}} = a [[{{ns:Project}}:Category|category]]
| {{ns:Help}} = a [[{{ns:Help}}:Contents|help]] page
| {{ns:Portal}} = a [[{{ns:Project}}:Portal|portal]]
| {{ns:Template}} = a [[{{ns:Project}}:Template messages|template]]
| {{ns:User}} = a [[{{ns:Project}}:User page|user page]]
| {{ns:Project}} = a [[{{ns:Project}}:Project namespace|project page]]
| #default = a {{NAMESPACE}} page
}} with this exact name.''' {{#ifeq: {{PAGENAME}} | {{SUBPAGENAME}}
| {{#switch: {{NAMESPACE}}
| {{ns:0}} = Please [[{{ns:Special}}:Search/{{PAGENAME}}|search for ''{{PAGENAME}}'' in the wiki]] to check for alternative titles or spellings.
| {{ns:Category}} = Please browse the [[Special:Categories|existing categories]] to check if the category is covered under another name.
| {{ns:Help}} = Please browse the [[{{ns:Help}}:Contents|existing help pages]] to check if the help topic is covered under another name.
| {{ns:Portal}} = Please browse the [[{{ns:Portal}}:Browse|existing portals]] to check for similar topics.
| {{ns:Template}} = Please browse the [[:Category:Templats|existing templates]] to check if the standardized message is available under another name.
| {{ns:User}} = In general, this page should be created and edited by [[{{ns:User}}:{{PAGENAME}}]]. If in doubt, please verify that "{{PAGENAME}}" [{{fullurl:Special:ListUsers|username={{urlencode:{{PAGENAME}}}}&limit=1}} '''exists'''].
}}
| Before creating this page, please see [[{{ns:Project}}:Subpages]].
}}
}}
{{#ifeq:{{{nopermission}}}|yes||* '''[{{fullurl:{{FULLPAGENAME}}|action=edit}} {{
#switch: {{NAMESPACE}}
| User talk = Post a message to ''{{PAGENAME}}''
| #default = Start the ''{{FULLPAGENAME}}'' {{#if:{{NAMESPACE}}|page|article}}
}}]'''
}}{{#switch: {{NAMESPACE}}
| User talk =
| #default =
* [[{{ns:Special}}:Search/{{#ifeq:{{NAMESPACE}}|{{ns:0}}||{{NAMESPACE}}:}}{{PAGENAME}} |Search for "''{{#ifeq:{{NAMESPACE}}|{{ns:0}}||{{NAMESPACE}}:}}{{PAGENAME}}''"]] in existing {{#if:{{NAMESPACE}}|pages|articles}}{{#ifeq:{{NAMESPACE}}|{{ns:0}}||  of namespace {{NAMESPACE}}}}.
* [[{{ns:Special}}:WhatLinksHere/{{FULLPAGENAME}}|Look for pages within the wiki that link to this title]].
}}
<div id="noarticletext_technical">
----

'''Other reasons this message may be displayed:'''
* If {{#switch: {{NAMESPACE}}
| {{ns:File}} = an image
| a page
}} was recently created here, it may not yet be visible because of a delay in updating the database; wait a few minutes and try the [{{fullurl:{{FULLPAGENAME}}|action=purge}} purge] function.
* Titles on the wiki are '''case sensitive''' except for the first character; please check alternative capitalizations and consider adding a [[Help:Tutorial#Redirects|redirect]] here to the correct title.
* If the page has been deleted, check the '''[{{fullurl:Special:Log/delete|page={{FULLPAGENAMEE}}}} deletion log]'''.
</div>


}}
}}

</div>

Dornier Do X

2022-03-13T03:56:21Z

Gordon: Category:Aircraft with cabin view

{{:{{PAGENAME}}/info}}
The '''Dornier Do X''' was the largest, heaviest, and most powerful [[:Category:Flying boats|flying boat]] in the world when it was produced by the Dornier company of Germany in 1929.
Only three were built.

== Aircraft help ==
===Keypad===

{| class="keytable"
! Key !! Function
|-
||{{Key press|Shift|B}}||Cast Anchor (down)
|-
||{{Key press|b}}||Hoist Anchor (up)
|-
|
----
|
----
|-
||{{Key press|s}}||Start engine by engine
|-
||{{Key press|Ctrl|S}}||Stop engine by engine
|-
||{{Key press|PageUp↑}}||Increase speed of locked engines
|-
||{{Key press|PageDown↓}}||Decrease speed of locked engines
|-
||{{Key press|,}}||Increase speed left locked engines
|-
||{{Key press|Shift|;}}||Decrease speed left locked engines
|-
||{{Key press|.}}||Increase speed right locked engines
|-
||{{Key press|:}}||Decrease speed right locked engines
|-
||{{Key press|m}}||Increase Mixtures
|-
||{{Key press|Shift|M}}||Decrease Mixtures
|-
|
----
|
----
|-
||{{Key press|l}}||Interior Lights on/off
|-
||{{Key press|c}}||Interior/Exterior View
|-
||{{Key press|equals}}||Open DO X Engineer Menu
|-
||{{Key press|>}}||Switch Pilot/Radio View
|}

===Engine control between Pilot and Engineer===
In the Middle Panel between the pilot and copilot seat you see 12 lamps. 6 left for the larboard engines. 6 right for the starboard engines. The two instruments show you the average rpm of all locked engines.

{|
|-
|Red||style="background-color: red;"|→||engine off
|-
|Yellow||style="background-color: yellow;"|→||engine is running but not locked to the two little throttle gears of the pilot. Only the engineer has the control for this engine in that moment. The clutch lever to lock and unlock those engines you will find in the Engineer Cabin.
|-
|Green||style="background-color: green;"|→||pilot hase full control over this engine.
|}

===Navigation with RDF and NDB===
*Switch view between Pilot and Radio Navigation Officer with {{Key press|Ctrl|Shift|R}}.
*In the Radio Cabin you will find a RDF-panel. First you have to set a NDB, ILS or VOR/DME -frequency in range.
*Switch on the Instrument with the little knob "''AN/AUS''".
*Fit on the headset and turn the "''DREHWINKEL-SCHEIBE''" to find the loudest volume of the beacon-signal you have set.
*If you have found the max. volume, click the pencil below the RDF-panel.

===Cockpit===
This is a description of the Do X cockpit:

[[File:Do X cockpit.png|800px]]

=== Performance and weight===
{| class="prettytable"
!Empty weight:
| 28,250 kg (62,280 lb)
|-
!Max. takeoff weight:
| 56,000 kg (123,460 lb)
|}
{| class="prettytable"
!Maximum speed:
|211 km/h (131 mph)
|-
!Cruise speed:
|175 km/h (109 mph)
|-
!Range:
|1,700 km (1,056 mi)
|-
!Service ceiling:
|3200 m (10498 ft)
|}
==Special features==
===Dual control===
{|
|[[File:Dualcontrolready.png|link=Dual control]]
|</br></br>{{cquote|[[DO-X|Dornier Do X]], phenomenal experience, pilot and radio operator working on interactive dual coordination for navigation.|{{Usr|Aepcam}} Jan 31, 2016 in [[Dual control]]}}
|}
{{Main article|Dual control}}

===Livery selection dialog===
The Dornier Do X has a [[livery selection dialog]] with 5 different liveries:
*Abtl. Entwicklung (Department for development)
*D1929
*Default
*IABBN - The last build: {{wikipedia|Dornier Do X#Further models|Do X3 "''Alessandro Guidoni''"}} for Italy
*oGalego - O Galego Itinerante - "''Star of Vigo''"

=== Interior light ===
Interior light can be switched on/off in the menubar ({{Key press|F10}}) or individually in the ''"navigation cabin view"''. The switches are named:<br>
'''Innenbeleuchtung → Interior Light'''
{| class="prettytable"
!Name {{de}}
|Führer||Kommandant||Maschinenzentrale||Funkraum||Hilfsmachine
|-
!Place {{en}}
|[[#Cockpit|Cockpit]]||Navigation cabin||[[#Engine control between Pilot and Engineer|Engineer cabin]]||[[#Navigation with RDF and NDB|Radio cabin]]||Help engine cabin
|}

===Help engine===
In the "''Help engine cabin view''" you can switch with a lever between:
{| class="prettytable"
!{{de}} !!{{en}}
|-
|Pressluft||Compressed air
|-
|Generator an||Generator on
|-
|Aus || Off
|}

==Media==
{{#ev:youtube|7LbYQKysXys}}

==Related content==
*[[Dual control]]
*[[:Category:Flying boats]]
*[[Dornier Museum Friedrichshafen]]

==External Links==
*[https://sketchfab.com/models/480eff9cea88495ba83bd32aa26eabde Sketchfab] 3D Preview
*[[Wikipedia:Dornier Do X]]

{{Dornier}}
[[de:Dornier Do X]]
[[Category:Aircraft with cabin view]]

User:Gordon/missions

2022-03-13T03:46:54Z

Gordon: Created page with "I discovered the following in a text file dated June 16, 2016. As of 2022, some of the text is difficult to understand to me, since I wrote it using some strange unmemorable a..."

I discovered the following in a text file dated June 16, 2016. As of 2022, some of the text is difficult to understand to me, since I wrote it using some strange unmemorable abbreviations, and back then, I did not bother with organizing and timestamping notes. Now, I know it is important.

I might change it into a readable list of missions which could include emergency landings, glides, flying a path with low fuel, flying with limited thrust (in resemblance to British European Airways Flight 548), and low visibility.

For anyone interested, I am sharing this text:

<pre>
FG Missions:

Done: Fly2EGLL almostNoFuel Then >>Kegworth >>Cottbus ||OutPwr+AirFUel|| >>EDLG >>EDDK

CHC British38 Rwy
Land A330
Done: Ditch A320
-What is PackFLow
-Kosovo
-FG Try Metroliner
-B]]G[[[[
-QNH
-2yt fgA320 crazy bounce
-Fyg
-ATIS
-EBBR
-abBRIV
-FG preview Crashes
-2 7forums: avoid windows to minimize, if I am moving one around.
-FG Ask How long does igonring last?
-FG 777 landing lights not seperately
-Skyboat
-AP1 AP2üpp
-Prozedere
-Skinny
-mmetabolist
-Bitte, Samsung! Bitte speichere Bluetooth-Dateien im BT-Ordner und NICHT in den Downloads!!!
AirFueling with
EGLL2EDDP2EDDK with B777 >>edln>>LFPG[CHC Paris Aprt maps]>>EDDK-arrive@dawn
707+777 DitchWater Night+Day
707: London2EDDV: UnexpectedFuelOut - EMERGENCY
707:
A330: FuelOut glideLanding
SRC:AirTrain
SRC: Catfight
Fishfight
guirre
spfreload
2013 T-Online id_63540076

SRC:FMS
SRC:CDI
707 CruiseFlt A/P with Instrumental Failure
SRC:ELT PLane + LYR Badman
Marcher 2de
Vertical: "sandra3000cassie" "Cooking video 1"
Chc Bigben
SphAsma - Eifel Twr + A/T accelerate + almost catastrphoe + Fly2EDDk

playlist - hope-MeMyselfMesteo - Firefly - Candy - Konichiwa - HledensMeMyslf - OLWIKncs - WildEyesBassanova [src:Bossanova] - badman
SRC: MESTRO
SRC:Mesteo
SRC:0x80030001
src: MTP Sucks

watch: schulabreccer

Src/Chc did 707cockpit really have an ALT METER?
Src: "ALT METER"

WhatIsEdkkEdnn
ACF DL ATCpie
Partyshakr Lyr
WhatRwy Asiana214? + Date 6.June Fr?
-Fly MD-83+Crusader EDDK-EGLL [Mach Speed!]

FGFeature: RteManager Knows Depatrure Airport
Src:CDU Nav
-2fg armlßehéhe hinten verstellen
-2FG Chat Times,GPositionS[src],HDG,SPD,V/S[src],ALT@Posttime + saveChatLogs
-WKI Gleitpfad
-2iView: revert random
-BetterFG: TimeWarp 0.5 (no integer) + Set in Time dialogue
-Avianca Flt Attn
src: 777 HUD
Chc: https://www.youtube.com/watch?v=VTsMEWgqv8M https://www.youtube.com/watch?v=k9T1SrX_2Tk https://www.youtube.com/watch?v=56zm16I8xhM https://www.youtube.com/watch?v=eQYnDGpsrdQ https://www.youtube.com/watch?v=3PE_EVMyXCs
</pre>

Walk view

2022-03-04T22:07:26Z

Gordon: short introduction

{{stub}}
'''Walk view''' allows the player to walk within and/or outside an aircraft. For example, this can be used to look after (imaginary) passengers while the plane is cruising on autopilot or [[dual_control|controlled by another pilot]], and to take a walk outside a parked aircraft.

== Updates ==
{{See also|Skydiving}}

Marius_A has started extending Stuart's [[Tutorials]] system to also support DFaber's Walker:

{{#ev:youtube|dU7ikBZOjgk}}

Learn more at: [[FlightGear Missions and Adventures]]...

== Easy walk ==
This is the most easy walk mode: you just walk at the same level (compared to the plane) and you will not fall if you get outside the plane.
=== walk.nas ===
<syntaxhighlight lang="nasal">
# view nodes and offsets --------------------------------------------
var zNoseNode = props.globals.getNode("sim/view/config/y-offset-m", 1);
var xViewNode = props.globals.getNode("sim/current-view/z-offset-m", 1);
var yViewNode = props.globals.getNode("sim/current-view/x-offset-m", 1);
var hViewNode = props.globals.getNode("sim/current-view/heading-offset-deg", 1);

var walk_about = func(wa_distance) {
var i = getprop("sim/current-view/view-number");
if (i == view.indexof("Pilot View") or i == view.indexof("Model View") or i == view.indexof("View 8")) {
var wa_heading_rad = hViewNode.getValue() * 0.01745329252;
var new_x_position = xViewNode.getValue() - (math.cos(wa_heading_rad) * wa_distance);
var new_y_position = yViewNode.getValue() - (math.sin(wa_heading_rad) * wa_distance);
xViewNode.setValue(new_x_position);
yViewNode.setValue(new_y_position);
}
}
</syntaxhighlight>
=== -set.xml ===
<syntaxhighlight lang="xml">
<input>
<keyboard>
<key n="119">
<name>w</name>
<desc>Walk forward toward view</desc>
<repeatable>true</repeatable>
<binding>
<command>nasal</command>
<script>walk.walk_about(0.1)</script>
</binding>
</key>
<key n="87">
<name>W</name>
<desc>Walk backward from view</desc>
<repeatable>true</repeatable>
<binding>
<command>nasal</command>
<script>walk.walk_about(-0.1)</script>
</binding>
</key>
</keyboard>
</input>
</syntaxhighlight>
== Advanced walk with jump and parachute ==
{{Out of date}}

This advanced mode is way more complicated than the easy walk (see above). With this mode you can jump out of the plane and land with a parachute.
=== walk.nas ===
''See the [[Pilatus PC-6 Porter‎]]'s <tt>PC-6/Nasal/walk.nas</tt>''

=== -set.xml ===
<syntaxhighlight lang="xml">
<walker>
<outside type="bool">false</outside>
<walking type="bool">false</walking>
<speed type="double">0.000006</speed>
<latitude-deg type="double">0.0</latitude-deg>
<longitude-deg type="double">0.0</longitude-deg>
<altitude-at-exit-ft type="double">0.0</altitude-at-exit-ft>
<altitude-ft type="double">0.0</altitude-ft>
<heading-deg type="double">0.0</heading-deg>
<pitch-deg type="double">0.0</pitch-deg>
<roll-deg type="double">0.0</roll-deg>
<internal>
<x-offset-m type="double">4.3</x-offset-m>
<y-offset-m type="double">0.0</y-offset-m>
<z-offset-m type="double">0.0</z-offset-m>
<heading-deg type="double">0.0</heading-deg>
</internal>
<keep-inside-offset-x type="double">0.0</keep-inside-offset-x>
<keep-inside-offset-y type="double">0.0</keep-inside-offset-y>
<keep-inside-offset-z type="double">0.0</keep-inside-offset-z>
<keep-pitch-offset-deg type="double">0.0</keep-pitch-offset-deg>
<key-triggers>
<forward type="double">0</forward>
<outside-toggle type="bool">0</outside-toggle>
<slide type="double">0</slide>
</key-triggers>
<parachute-opened-altitude-ft type="double">0</parachute-opened-altitude-ft>
<parachute-opened-sec type="double">0</parachute-opened-sec>
<starting-trajectory-lat type="double">0</starting-trajectory-lat>
<starting-trajectory-lon type="double">0</starting-trajectory-lon>
<time-of-exit-sec type="double">0</time-of-exit-sec>
</walker>

<input>
<keyboard>
<key n="111">
<name>o</name>
<desc>Toggle walker outside/inside</desc>
<repeatable>false</repeatable>
<binding>
<command>property-toggle</command>
<property>sim/walker/key-triggers/outside-toggle</property>
</binding>
</key>
<key n="119">
<name>w</name>
<desc>Walk forward</desc>
<repeatable>false</repeatable>
<binding n="0">
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>1</value>
</binding>
<binding n="1">
<command>property-assign</command>
<property>sim/walker/speed</property>
<value>0.000006</value>
</binding>
<mod-up>
<binding n="0">
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>0</value>
</binding>
<binding n="1">
<command>property-assign</command>
<property>sim/walker/speed</property>
<value>0.000006</value>
</binding>
</mod-up>
</key>
<key n="87">
<name>W</name>
<desc>Run forward</desc>
<repeatable>false</repeatable>
<binding n="0">
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>1</value>
</binding>
<binding n="1">
<command>property-assign</command>
<property>sim/walker/speed</property>
<value>0.000018</value>
</binding>
<mod-up>
<binding n="0">
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>0</value>
</binding>
<binding n="1">
<command>property-assign</command>
<property>sim/walker/speed</property>
<value>0.000006</value>
</binding>
</mod-up>
</key>
<key n="115">
<name>s</name>
<desc>Walk backward</desc>
<repeatable>false</repeatable>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>-1</value>
</binding>
<mod-up>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/forward</property>
<value>0</value>
</binding>
</mod-up>
</key>
<key n="97">
<name>a</name>
<desc>Slide left</desc>
<repeatable>false</repeatable>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>-1</value>
</binding>
<mod-up>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>0</value>
</binding>
</mod-up>
</key>
<key n="65">
<name>A</name>
<desc>Slide left2, override default assignment</desc>
<repeatable>false</repeatable>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>-1</value>
</binding>
<mod-up>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>0</value>
</binding>
</mod-up>
</key>
<key n="100">
<name>d</name>
<desc>Slide right</desc>
<repeatable>false</repeatable>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>1</value>
</binding>
<mod-up>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>0</value>
</binding>
</mod-up>
</key>
<key n="68">
<name>D</name>
<desc>Slide right2</desc>
<repeatable>false</repeatable>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>1</value>
</binding>
<mod-up>
<binding>
<command>property-assign</command>
<property>sim/walker/key-triggers/slide</property>
<value>0</value>
</binding>
</mod-up>
</key>
<key n="114">
<name>r</name>
<desc>open parachute</desc>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>walk.open_chute()</script>
</binding>
</key>
</keyboard>
</input>
</syntaxhighlight>

== Adding a walker pilot or co-pilot <ref>Human [http://cms.flightgear-de.net/index.php/engoben/91-comdiffen/112-humanen]</ref> ==

To add the Walker to your Aircraft replace the <PropertyList> Entry at the top of your -set file with this:
<syntaxhighlight lang="xml">
<PropertyList include="Aircraft/Generic/Human/Include/walker-include.xml">
</syntaxhighlight>
This includes all Properties for the Walker, Key Bindings and a Menubar Entry. The Keys "a", "A" and "s" have their normal Binding when not in Walk View or Walker Orbit View.

To have a custom Exit Point add the following Properties to the <model> section in your Aircraft's -set file:
<map>
<default_exit>
<x-offset-m type ="float">1</x-offset-m>
<y-offset-m type ="float">3</y-offset-m>
</default_exit>
</map>

This specifies where the Walker Model appears.

=== Creating a pilot/copilot ===

First, position the Walker Model (walker.xml) below the seat with it's origin (feet) on the Cockpit floor. Then start FlightGear and edit the pose in the Walker animation dialog. When this is done, export the animation and copy the file to a subfolder of the aircraft. This file is referenced in the -set files pilot Properties via "include".

Note: Once the pose is done, the walker.xml entry in the Model file has to be replaced with either pilot.xml or copilot.xml!

The following properties control the appearance of the pilot and co-pilot. They are located in the /sim/model/ section of the -set file:
<syntaxhighlight lang="xml">
<crew>
<pilot n="0">
<pose include = "Include/ju52_pilot.xml"></pose>
<gender>0</gender>
<character>0</character>
<outfit>2</outfit>
</pilot>
<pilot n="1">
<pose include = "Include/ju52_pilot.xml"></pose>
<gender>1</gender>
<character>0</character>
<outfit>0</outfit>
</pilot>
</crew>
</syntaxhighlight>

here is an example with one pilot and 2 passengers "npc0" and "npc1" (non player character):
In your Aircraft's -set file:
<syntaxhighlight lang="xml">
<crew>
<pilot n="0">
<pose include = "Include/ju52_pilot.xml"></pose>
<gender>0</gender>
<character>0</character>
<outfit>2</outfit>
</pilot>
</crew>
<npc n="0">
<pose include = "Include/ju52_pilot.xml"></pose>
<gender>0</gender>
<character>1</character>
<outfit>0</outfit>
<hair>2</hair>
</npc>
<npc n="1">
<pose include = "Include/walker_sit.xml"></pose>
<gender>0</gender>
<character>0</character>
<outfit>0</outfit>
<headgear>1</headgear>
<eyewear>0</eyewear>
<mask>0</mask>
<hair>1</hair>
<toolr>1</toolr>
</npc>
</syntaxhighlight>

and in the aircraft's Model/??????.xml file:
<syntaxhighlight lang="xml">

<model>
<name>pilot</name>
<path>Aircraft/Generic/Human/Models/pilot.xml</path>
<name>pilot</name>
<nopreview/>
<offsets>
<x-m>-7.0384</x-m>
<y-m>-0.4858</y-m>
<z-m>1.5</z-m>
</offsets>
</model>


<model>
<name>npc0</name>
<path>Aircraft/Generic/Human/Models/npc0.xml</path>
<nopreview/>
<offsets>
<x-m>-7.0384</x-m>
<y-m>0.45</y-m>
<z-m>1.5</z-m>
</offsets>
</model>


<model>
<name>npc1</name>
<path>Aircraft/Generic/Human/Models/npc1.xml</path>
<nopreview/>
<offsets>
<heading-deg>90</heading-deg>
<x-m>-3.2</x-m>
<y-m>0.65</y-m>
<z-m>0.90</z-m>
</offsets>
</model>
</syntaxhighlight>

=== Custom movements ===
Basic Head Movements can be done by including this in the nasal section:

<pilot-movment>
<file>Aircraft/Generic/Human/Nasal/pilot-movment.nas</file>
<script>
var head_x = "sim/model/crew/pilot[0]/pose/position/limb[2]/x-deg";
var head_y = "sim/model/crew/pilot[0]/pose/position/limb[2]/y-deg";
var head_z = "sim/model/crew/pilot[0]/pose/position/limb[2]/z-deg";
</script>
</pilot-movment>

<copilot-movment>
<file>Aircraft/Generic/Human/Nasal/pilot-movment.nas</file>
<script>
var head_x = "sim/model/crew/pilot[1]/pose/position/limb[2]/x-deg";
var head_y = "sim/model/crew/pilot[1]/pose/position/limb[2]/y-deg";
var head_z = "sim/model/crew/pilot[1]/pose/position/limb[2]/z-deg";
</script>
</copilot-movment>

=== currently(Sept.2016) valid values for the properties ===

character:
0
1
2

eyewear:
0 no eyewear,
1 sunglasses

gender:
0 male,
1 female,
2 invisible :-)

hair:
0 no hair,
1 hairstyle 1,
2 hairstyle 2,

headgear:
1 headset,
2 big hat,
3 helmet,

mask:
0 no mask,
1 oxygen mask,

outfit:
0,
1,
2,
3,
4,

=== screenshots of walker characters, outfits and hand gestures===
http://www.23hq.com/laserman/album/24944281

== WalkView: Another option for internal walk views ==

Another option is to use the WalkView module available in Aircraft/Generic/WalkView/ (in FlightGear 2.2.0 or later).
The module supports aircraft internal views that can move around based on a description of the reachable spaces.

Load the WalkView module and the configuration from the -set file. The example below is from [[Nordstern]] and makes the view named "Walk View" into a walk view. See also [[Zeppelin NT]] and [[Short Empire]] for more examples.

<syntaxhighlight lang="xml">

<sim>
...
<view n="103">
<name>Walk View</name>
<internal>true</internal>
<config>

<from-model type="bool">true</from-model>
<from-model-idx type="int">0</from-model-idx>
<x-offset-m type="double"> 0.00 </x-offset-m>
<y-offset-m type="double"> -7.50 </y-offset-m>
<z-offset-m type="double"> 51.00 </z-offset-m>
<heading-offset-deg type="double"> 0.0 </heading-offset-deg>
<pitch-offset-deg type="double"> 0.0 </pitch-offset-deg>
<default-field-of-view-deg type="double"> 65 </default-field-of-view-deg>
</config>
</view>
...
</sim>


<nasal>
<walkview>
<file>Aircraft/Generic/WalkView/walkview.nas</file>
<script>
# The keel walk-way is a long narrow path running in the fore-aft direction.
# Additionally there is a path to the side engine cars.
var keelConstraint =
walkview.makeUnionConstraint(
[
walkview.makePolylinePath(
[
[ 10.0, 0.0, -6.3],
[ 15.0, 0.0, -7.2],
[ 20.0, 0.0, -7.8],
[ 25.0, 0.0, -8.2],
[ 30.0, 0.0, -8.6],
[ 35.0, 0.0, -8.8],
[ 40.0, 0.0, -9.0],
[ 50.0, 0.0, -9.1],
[ 65.0, 0.0, -9.1],
[ 70.0, 0.0, -8.8],
[ 80.0, 0.0, -8.5],
[ 90.0, 0.0, -7.9],
[ 95.0, 0.0, -7.4],
[100.0, 0.0, -6.9],
[105.0, 0.0, -6.2],
[110.0, 0.0, -5.4],
],
0.20),
walkview.makePolylinePath(
[
[ 59.75, -4.90, -7.79],
[ 59.75, -1.70, -9.05],
[ 59.75, 1.70, -9.05],
[ 59.75, 4.90, -7.79],
],
0.20)
]);
# Create the walker for the named view and the given movement restrictions.
var rigger_walker = walkview.Walker.new("Walk View",
keelConstraint);
</script>
</walkview>
...
</nasal>


<input>
<keyboard include="Aircraft/Generic/WalkView/walk-view-keys.xml">
...
</keyboard>
...
</input>
</syntaxhighlight>

== References ==
<references/>

== Related content ==
=== Wiki articles ===
* [[Ramp Marshall]]

=== Source code ===
* {{fgdata source|path=Aircraft/Generic/WalkView}}
* {{fgdata source|path=Aircraft/Generic/Human}}

[[es:Walk View]]

[[Category:Aircraft enhancement]]
[[Category:Nasal]]

Bombardier CRJ700 series

2022-03-04T21:53:10Z

Gordon: walk view mention

{{:{{PAGENAME}}/info}}
[[File:CRJ700-cockpit-night.jpg|The cockpit at night, demonstrating night lighting capabilities|thumb|350px|right]]
[[File:CRJ700-cabin-night.jpg|The interior cabin, also at night|thumb|350px|right]]

The '''Bombardier CRJ700 series''' is a family of 70- to 100- seat regional jet airliners manufactured by Bombardier Aerospace. Its primary competition is the Embraer E-jet series. The family consists of the Bombardier CRJ700, CRJ900, and CRJ1000. The CRJ700 series was developed from the [[Bombardier CRJ-200LR|Bombardier CRJ200]], and remains one of the most popular regional airliner series in the world.

It belongs to the few aircraft for FlightGear that feature a ''[[walk view]]''.

=Variants=

* CRJ700 - the original CRJ700
* CRJ700ER - extended range version
* CRJ700LR - long-range version
* CRJ900 - the first stretch of the airframe
* CRJ900ER - extended range version
* CRJ900LR - long-range version
* CRJ1000 - the final stretch of the airframe
* CRJ1000 EuroLite - low-range/low-cost version targeted at European operators
* CRJ1000ER - extended range version

=Aircraft help=

HTML documentation is included in the Docs/ folder.

==Key commands==

{| class="keytable"
! Key
! Function
|-
! colspan="2" | Speedbrakes/spoilers
|-
| {{key press|Ctrl|B}}
| Cycle speedbrake setting
|-
| {{key press|j}}
| Decrease ground lift dump setting
|-
| {{key press|k}}
| Increase ground lift dump setting
|-
! colspan="2"|Engines
|-
| {{key press|Ctrl|Del}}
| Arm/disarm thrust reversers
|-
| {{key press|Del}}
| Toggle thrust reversers
|-
! colspan="2" | Autopilot
|-
| {{key press|Ctrl|A}}
| Toggle autopilot altitude mode
|-
| {{key press|Ctrl|F}}
|Engage/disengage autopilot
|-
| {{key press|Ctrl|G}}
| Toggle autopilot approach mode
|-
| {{key press|Ctrl|H}}
| Toggle autopilot heading mode
|-
| {{key press|Ctrl|N}}
| Toggle autopilot NAV mode
|-
| {{key press|Ctrl|P}}
| Set autopilot basic pitch mode
|-
| {{key press|Ctrl|W}}
| Set autopilot basic heading/roll mode
|-
| {{key press|F6}}
| Cycle NAV source
|-
! colspan="2" | Tiller/Nose gear steering
|-
| {{key press|q}}
| Steer tiller left
|-
| {{key press|Shift|Q}}
| Set tiller to full left
|-
| {{key press|w}}
| Center tiller
|-
| {{key press|Shift|W}}
| Pop up tiller dialog
|-
| {{key press|e}}
| Steer tiller right
|-
| {{key press|Shift|E}}
| Set tiller to full right
|-
! colspan="2" | Walk view
|-
| {{key press|r}}
| Walk forward toward view
|-
| {{key press|Shift|R}}
| Run forward toward view
|-
| {{key press|f}}
| Walk backwards from view
|-
| {{key press|y}}
| View point down
|-
| {{key press|Y}}
| View point up
|}

==Simplified procedures==
===Startup===
[[File:Start-123.png|thumb|right|CRJ700 Startup (1,2,3)]]
#Battery switch ... on
#APU start/stop switch ... on
#Bleed air source ... automatic
#Fuel Pumps ... enable
#Engine 1 thrust lever ... idle
#Engine 1 start sequence ... initiated
#Engine 2 thrust lever ... idle
#Engine 2 start sequence ... initiated
#Engine 1 electric generator ... on
#Engine 2 electric generator ... on
#APU start/stop switch ... off

===Takeoff===
#Flaps/slats ... 8 or 20
#Landing lights ... on
#Engine thrust modes ... TO/GA

===Climb and cruise===
#Engine thrust modes ... climb
Nominal cruise speed Mach 0.78 (0.80 for CRJ900)

===Approach and landing===
Remain below 250 knots below 10,000 feet at all times
#Thrust reversers ... armed
#Obey speed limits for flaps and gear extension
#Flaps/slats on final ... 45

===Shutdown===
#Parking break ... set
#External power ... select
#Engine thrust levers ... shutoff
#Engine 1 electric generator ... off
#Engine 2 electric generator ... off

=Downloading=

The latest version is always available on the official FlightGear aircraft download page and will be committed regularly to [[FGAddon]].

The latest development version at GitHub can also be downloaded [https://github.com/d-jsb/CRJ700-family/archive/master.zip here].

=Aircraft of the Week/Month=

The CRJ700 was reviewed by Thorsten R as part of the "Aircraft of the Week/Month" feature on the FlightGear Forums.

====Model====

The 3d cockpit of the CRJ-700 is very detailed and contains not only functionality on the main panel but also on the central console and an overhead panel. However, as often seen, the cockpit surfaces not covered by instrumentation are very simply textured by a monochromatic grey color - a more natural texture resembling a real material with some wear and tear could add a lot here.

[http://www.phy.duke.edu/~trenk/pics/crj700-cockpit.jpg View image]

There is a lot of functionality in the cockpit - a startup procedure using the APU is supported as well as a full set of external lights and no-smoking and seat belt signs for the passengers. A nice touch of the model is that it also contains an interior view of the cabin in which the signs can be observed. Switches and knobs are usually animated, and the clickspots are placed fairly intuitively. The MFD's all have various selectable functions.

The exterior model of the aircraft is also very nicely done, contains good animations and shows all the light switch settings in the cockpit faithfully. An option to switch livery exists as well.

[http://www.phy.duke.edu/~trenk/pics/crj700-model.jpg View image]

====Flight characteristics====

The FDM of the CRJ-700 is quite plausible for an airliner of its size. I haven't really tested the behaviour at the edge of the performance envelope, but during normal operations, the plane behaves well and reaches basic performance characteristics. All in all, the plane is an airliner (albeit a small one) - it turns slowly, it does not descent rapidly without picking up a lot of excess speed and all maneuvers need to be planned well in advance. Having said that, it's actually fun to fly.

I found the AP nicely tuned and able to fly turns, climb or dive at all altitudes without oscillations or weird behaviour. Unfortunately, the support for AP modes involving navaids is not as good: While I could home in on a VOR station, the AP seems to be tracking the station rather than the chosen radial, i.e. the angle under which I approached the station kept changing. Also, I was unable to intercept an ILS glideslope automatically. However, the plane can be operated well in IFR conditions just using the instruments to display the navaid signals and the heading and altitude modes of the AP to control the plane.

====My personal wishlist====

Fixing the AP to a more consistent behaviour with navaids would be high on my priority list - there are currently very few airliners with a well-tuned AP capable of tracking navaids. Some more natural texturing in the cockpit would also be nice. I realize that the CRJ-700 is a fairly recent addition to the aircraft repository of Flightgear - but I like where the model is going very much.

====Things to experience====

Try flying at night - the CRJ-700 has one of the best light concepts I've ever seen. The instrument lights are very beautifully done and can be dimmed at need, the cabin lights likewise, and all lighting is visible both from internal and external views.

''Editor's note: The autopilot VOR-LOC/ILS holds have been fixed as of CRJ700 v1.0.2.''

=Development status/Issues/Todo=
==Key features==
* Startup and shutdown procedures
* Mostly complete cockpit
* Realistic autopilot
* Functional flight management system (FMS), advisory-only vertical navigation system (VNAV), and control display unit (CDU)
* Emergency procedures with ram air turbine (RAT) and auxiliary power unit (APU)
* Small library of tutorials
* Cockpit, cabin, and exterior model lightmaps
* Reflection shader on the engines
* Developed aircraft systems
* Tiller steering system

==Todo==
For rating information, see [[Formalizing Aircraft Status]].
===FDM (current rating 3)===
* Make something a little more refined than my [[YASim]] solution (any [[JSBSim]] masters?)
===Exterior (current rating 4)===
* Add minor elements like antennas, ram air turbine, improve gear bay texturing and geometry
* More liveries!
===Flight deck (current rating 4)===
* Improve texturing
* Model circuit breakers
===Systems (current rating 3)===
* Add more pages to EICAS

== Development (section added May 2015) ==
D-JSB et al. work on the CRJ700 family.

=== Status without any particular order ===
==== done ====
* Some bugfixes (e.g. MFD wind indicator, nav pointers, MFD symbols)
* Removed 2D panel which depended on Boing 737-300
* More views (cabin windows, gear)
* OHP switches / switchlights (gimmick: implemented the light test button)
* Details of auto pilot panel behaviour like push function of CRS and HDG
* Modified slats/flaps indicator on EICAS
* APU details on EICAS
* EICAS pages for doors
* Simulation of hydraulic system
* EICAS pages for hydraulic system
* Extend failures dialog (hydraulics)
* Re-implement the electrical system (AC and DC).
* Add cargo doors to model
* Add APU door to model

==== In progress / testing ====
* Update of documentation

==== Planed ====
* Canvas implementation of glas cockpit

== Canvas implementation (planed) ==
[[CRJ 700 family canvas ]]

=External links=
* [http://en.wikipedia.org/wiki/Bombardier_CRJ700_series Bombardier CRJ700 series at Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?t=11863 Development thread at the FlightGear Forums]
* [http://www.smartcockpit.com/data/...700.../HGS_00_Pilots_Guide_CRJ_00.pdf GHS Pilots Guide CRJ]
* [http://aligero.us/files/FMS%204200.pdf FMS 4200 Intro]
* [http://www.4shared.com/get/Q_rDeIsz/Collins_FMS-4200_Flight_Manage.html FMS-4200 Manual]
* [https://360.schnurstracks.de/panoramafotografie/cockpit/cockpit-panorama-bombardier.html?initvars.internlink=1 360° cockpit photo]

{{Template:Bombardier}}
[[Category: Aircraft with cabin view]]

Bombardier CRJ700 series

2022-03-04T21:39:23Z

Gordon: +Category: Aircraft with cabin view

{{:{{PAGENAME}}/info}}
[[File:CRJ700-cockpit-night.jpg|The cockpit at night, demonstrating night lighting capabilities|thumb|350px|right]]
[[File:CRJ700-cabin-night.jpg|The interior cabin, also at night|thumb|350px|right]]

The '''Bombardier CRJ700 series''' is a family of 70- to 100- seat regional jet airliners manufactured by Bombardier Aerospace. Its primary competition is the Embraer E-jet series. The family consists of the Bombardier CRJ700, CRJ900, and CRJ1000. The CRJ700 series was developed from the [[Bombardier CRJ-200LR|Bombardier CRJ200]], and remains one of the most popular regional airliner series in the world.

=Variants=

* CRJ700 - the original CRJ700
* CRJ700ER - extended range version
* CRJ700LR - long-range version
* CRJ900 - the first stretch of the airframe
* CRJ900ER - extended range version
* CRJ900LR - long-range version
* CRJ1000 - the final stretch of the airframe
* CRJ1000 EuroLite - low-range/low-cost version targeted at European operators
* CRJ1000ER - extended range version

=Aircraft help=

HTML documentation is included in the Docs/ folder.

==Key commands==

{| class="keytable"
! Key
! Function
|-
! colspan="2" | Speedbrakes/spoilers
|-
| {{key press|Ctrl|B}}
| Cycle speedbrake setting
|-
| {{key press|j}}
| Decrease ground lift dump setting
|-
| {{key press|k}}
| Increase ground lift dump setting
|-
! colspan="2"|Engines
|-
| {{key press|Ctrl|Del}}
| Arm/disarm thrust reversers
|-
| {{key press|Del}}
| Toggle thrust reversers
|-
! colspan="2" | Autopilot
|-
| {{key press|Ctrl|A}}
| Toggle autopilot altitude mode
|-
| {{key press|Ctrl|F}}
|Engage/disengage autopilot
|-
| {{key press|Ctrl|G}}
| Toggle autopilot approach mode
|-
| {{key press|Ctrl|H}}
| Toggle autopilot heading mode
|-
| {{key press|Ctrl|N}}
| Toggle autopilot NAV mode
|-
| {{key press|Ctrl|P}}
| Set autopilot basic pitch mode
|-
| {{key press|Ctrl|W}}
| Set autopilot basic heading/roll mode
|-
| {{key press|F6}}
| Cycle NAV source
|-
! colspan="2" | Tiller/Nose gear steering
|-
| {{key press|q}}
| Steer tiller left
|-
| {{key press|Shift|Q}}
| Set tiller to full left
|-
| {{key press|w}}
| Center tiller
|-
| {{key press|Shift|W}}
| Pop up tiller dialog
|-
| {{key press|e}}
| Steer tiller right
|-
| {{key press|Shift|E}}
| Set tiller to full right
|-
! colspan="2" | Walk view
|-
| {{key press|r}}
| Walk forward toward view
|-
| {{key press|Shift|R}}
| Run forward toward view
|-
| {{key press|f}}
| Walk backwards from view
|-
| {{key press|y}}
| View point down
|-
| {{key press|Y}}
| View point up
|}

==Simplified procedures==
===Startup===
[[File:Start-123.png|thumb|right|CRJ700 Startup (1,2,3)]]
#Battery switch ... on
#APU start/stop switch ... on
#Bleed air source ... automatic
#Fuel Pumps ... enable
#Engine 1 thrust lever ... idle
#Engine 1 start sequence ... initiated
#Engine 2 thrust lever ... idle
#Engine 2 start sequence ... initiated
#Engine 1 electric generator ... on
#Engine 2 electric generator ... on
#APU start/stop switch ... off

===Takeoff===
#Flaps/slats ... 8 or 20
#Landing lights ... on
#Engine thrust modes ... TO/GA

===Climb and cruise===
#Engine thrust modes ... climb
Nominal cruise speed Mach 0.78 (0.80 for CRJ900)

===Approach and landing===
Remain below 250 knots below 10,000 feet at all times
#Thrust reversers ... armed
#Obey speed limits for flaps and gear extension
#Flaps/slats on final ... 45

===Shutdown===
#Parking break ... set
#External power ... select
#Engine thrust levers ... shutoff
#Engine 1 electric generator ... off
#Engine 2 electric generator ... off

=Downloading=

The latest version is always available on the official FlightGear aircraft download page and will be committed regularly to [[FGAddon]].

The latest development version at GitHub can also be downloaded [https://github.com/d-jsb/CRJ700-family/archive/master.zip here].

=Aircraft of the Week/Month=

The CRJ700 was reviewed by Thorsten R as part of the "Aircraft of the Week/Month" feature on the FlightGear Forums.

====Model====

The 3d cockpit of the CRJ-700 is very detailed and contains not only functionality on the main panel but also on the central console and an overhead panel. However, as often seen, the cockpit surfaces not covered by instrumentation are very simply textured by a monochromatic grey color - a more natural texture resembling a real material with some wear and tear could add a lot here.

[http://www.phy.duke.edu/~trenk/pics/crj700-cockpit.jpg View image]

There is a lot of functionality in the cockpit - a startup procedure using the APU is supported as well as a full set of external lights and no-smoking and seat belt signs for the passengers. A nice touch of the model is that it also contains an interior view of the cabin in which the signs can be observed. Switches and knobs are usually animated, and the clickspots are placed fairly intuitively. The MFD's all have various selectable functions.

The exterior model of the aircraft is also very nicely done, contains good animations and shows all the light switch settings in the cockpit faithfully. An option to switch livery exists as well.

[http://www.phy.duke.edu/~trenk/pics/crj700-model.jpg View image]

====Flight characteristics====

The FDM of the CRJ-700 is quite plausible for an airliner of its size. I haven't really tested the behaviour at the edge of the performance envelope, but during normal operations, the plane behaves well and reaches basic performance characteristics. All in all, the plane is an airliner (albeit a small one) - it turns slowly, it does not descent rapidly without picking up a lot of excess speed and all maneuvers need to be planned well in advance. Having said that, it's actually fun to fly.

I found the AP nicely tuned and able to fly turns, climb or dive at all altitudes without oscillations or weird behaviour. Unfortunately, the support for AP modes involving navaids is not as good: While I could home in on a VOR station, the AP seems to be tracking the station rather than the chosen radial, i.e. the angle under which I approached the station kept changing. Also, I was unable to intercept an ILS glideslope automatically. However, the plane can be operated well in IFR conditions just using the instruments to display the navaid signals and the heading and altitude modes of the AP to control the plane.

====My personal wishlist====

Fixing the AP to a more consistent behaviour with navaids would be high on my priority list - there are currently very few airliners with a well-tuned AP capable of tracking navaids. Some more natural texturing in the cockpit would also be nice. I realize that the CRJ-700 is a fairly recent addition to the aircraft repository of Flightgear - but I like where the model is going very much.

====Things to experience====

Try flying at night - the CRJ-700 has one of the best light concepts I've ever seen. The instrument lights are very beautifully done and can be dimmed at need, the cabin lights likewise, and all lighting is visible both from internal and external views.

''Editor's note: The autopilot VOR-LOC/ILS holds have been fixed as of CRJ700 v1.0.2.''

=Development status/Issues/Todo=
==Key features==
* Startup and shutdown procedures
* Mostly complete cockpit
* Realistic autopilot
* Functional flight management system (FMS), advisory-only vertical navigation system (VNAV), and control display unit (CDU)
* Emergency procedures with ram air turbine (RAT) and auxiliary power unit (APU)
* Small library of tutorials
* Cockpit, cabin, and exterior model lightmaps
* Reflection shader on the engines
* Developed aircraft systems
* Tiller steering system

==Todo==
For rating information, see [[Formalizing Aircraft Status]].
===FDM (current rating 3)===
* Make something a little more refined than my [[YASim]] solution (any [[JSBSim]] masters?)
===Exterior (current rating 4)===
* Add minor elements like antennas, ram air turbine, improve gear bay texturing and geometry
* More liveries!
===Flight deck (current rating 4)===
* Improve texturing
* Model circuit breakers
===Systems (current rating 3)===
* Add more pages to EICAS

== Development (section added May 2015) ==
D-JSB et al. work on the CRJ700 family.

=== Status without any particular order ===
==== done ====
* Some bugfixes (e.g. MFD wind indicator, nav pointers, MFD symbols)
* Removed 2D panel which depended on Boing 737-300
* More views (cabin windows, gear)
* OHP switches / switchlights (gimmick: implemented the light test button)
* Details of auto pilot panel behaviour like push function of CRS and HDG
* Modified slats/flaps indicator on EICAS
* APU details on EICAS
* EICAS pages for doors
* Simulation of hydraulic system
* EICAS pages for hydraulic system
* Extend failures dialog (hydraulics)
* Re-implement the electrical system (AC and DC).
* Add cargo doors to model
* Add APU door to model

==== In progress / testing ====
* Update of documentation

==== Planed ====
* Canvas implementation of glas cockpit

== Canvas implementation (planed) ==
[[CRJ 700 family canvas ]]

=External links=
* [http://en.wikipedia.org/wiki/Bombardier_CRJ700_series Bombardier CRJ700 series at Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?t=11863 Development thread at the FlightGear Forums]
* [http://www.smartcockpit.com/data/...700.../HGS_00_Pilots_Guide_CRJ_00.pdf GHS Pilots Guide CRJ]
* [http://aligero.us/files/FMS%204200.pdf FMS 4200 Intro]
* [http://www.4shared.com/get/Q_rDeIsz/Collins_FMS-4200_Flight_Manage.html FMS-4200 Manual]
* [https://360.schnurstracks.de/panoramafotografie/cockpit/cockpit-panorama-bombardier.html?initvars.internlink=1 360° cockpit photo]

{{Template:Bombardier}}
[[Category: Aircraft with cabin view]]

User:Gordon/notes

2022-03-04T21:03:17Z

Gordon: /* Features that could be useful */ realistic cabin

On this page, I will be sharing notes and observations I made while playing FlightGear, as I find them. These may include flaws that have already been fixed, since some of the notes I found are from several years ago, and I am admittedly somewhat hesitant to update due to the risk of something that worked well so far being broken, which is an experience I frequently had with other software like web browsers.

* A water aircraft does not block sunlight. The sun's reflection is still visible on the water surface in the shadow area of the aircraft. Tested with [[Dornier Do X]].
* Perhaps the map should show coordinates at the mouse pointer's position.
* It could be useful if the flight data was recorded locally in real-time (like a real FDR), so that if the simulation crashes, the flight path is not lost.
* The instruments of some planes like the [[Boeing 707]] used raster graphics last time I checked. With vector graphics (if technically possible), they would appear sharper on high-resolution displays and while zoomed in.
* The Boeing 707 is unable to glide for long distances after engine failure due to the stall as a result of the wings being frozen from the cold temperatures at high altitudes. May or may not be intentional.

== Features that could be useful ==
These are not essential to simulation, but could add some convenience and fun:
* Ability to search for properties
* Ability to log console commands to a text file.
* YSflight has a "wingman" feature where other computer-controlled aircraft fly in formation. Something similar has been implemented with the [[Boeing 707-TT]].
* The ability to lock the camera in place (like in YSflight and Super Mario 64)
* The ability to see multiple perspectives simultaneously in separate windows, like cockpit view and cabin view simultaneously.
* Realistic cabin view models, like [http://www.dh-aircraft.co.uk/news/files/2fca08a971937b0878c77f36169d8455-82.html this Comet 4C] and [http://www.nmusafvirtualtour.com/media/062/B-36J%20Engineer.html Convair B-36 (360-degree view, link dead as of 2022)].

Boeing 707-420

2022-03-04T20:54:59Z

Gordon: :Category:Aircraft with cabin view

{{:{{PAGENAME}}/info}}
[[File:Boeing707 1.png|thumb|270px|707-420/430 "City of Friedrichshafen"]]

[[Image:Tutorialready.png|link=Tutorials]]
[[Image:Checklistready.png|link=Aircraft Checklists]]
[[Image:Routemanagerready.png|link=Route Manager]]
[[Image:Airrefuelingready.png|link=Air Refueling Ready]]
[[Image:Rembrandtready.png|link=Rembrandt]]

The '''[[Boeing]] 707-420/430''' were versions of the [[Boeing 707-320|707-320]] with Rolls-Royce Conway 508 turbofans. First appearing in 1960, 37 examples were delivered to BOAC, Lufthansa, Air India, El Al and Varig through November 1963.

This [[FlightGear]] model includes versions dating from 1959 to the late 1970s. Feel the difference between the older Rolls-Royce Conway 508 turbofans engines and the later JT4 engines simply by changing liveries.

== Variants ==
* 707-420/430: Passenger airliners capable of seating 147 passengers.
* 707-TT ('''T'''anker '''T'''ransport): An Italian tanker variant. Can be used for [[Howto:Aerial refueling|air-to-air refueling]].
* EC-137D: An AWACS variant that later evolved into the [[E-3 Sentry]].

== Aircraft help ==
The 707-420/430 has a detailed built-in tutorial in German, English, Czech, Portugues and Spanish. You can help translate the tutorial into other languages by visiting our {{github source|user=D-MKF1|repo=707|text=page on github}}.

[[File:Cockpit1.png|thumb|270px|707-420/430 "Chanson de Roland" panel]]

=== Cheat sheet ===
{| class="keytable"
!Key
!Function
|-
|{{Key press|Delete}}
|Deploy reverse thrust.
|-
|{{Key press|Shift}} + {{Key press|B}}
|Set or unset the parking brake.
|-
|{{Key press|Control}} + {{Key press|B}}
|Deploy the speedbrakes.
|-
|{{Key press|G}}
|Raise the landing gear.
|-
|{{Key press|Shift}} + {{Key press|G}}
|Lower the landing gear.
|-
|{{Key press|]}}
|Lower the leading and trailing edge flaps.
|-
|{{Key press|[}}
|Raise the leading and trailing edge flaps.
|-
|{{Key press|y}}
|Hide or show the cockpit yokes.
|-
|{{Key press|<}}
|Toggle between pilot and engineer views.
|-
|{{Key press|F9}}
|Open the fuel and weight controls.
|-
|{{Key press|F11}}
|Focus or unfocus the view on the autopilot controls.
|}

== Usability ==

The aircraft's philosophy is based on the WYSIWYG concept. Everything you see on the panels is clickable - and works.

The light effects in the cockpit are made with extra attention to detail, with the aim of giving the user the most realistic experience possible. The hope is that the pilot to feel as if they are actually in the plane itself.

On the other hand, the 707-420/430 is also focused on usability for new users. For example, the generic autopilot dialog has been retained, and an autostart function is available. Tutorials are available in several languages. All this is done with the aim of making things easy for first-time users while also allowing them to learn and have fun.

[[File:Cockpit2.png|thumb|270px|Looking to starboard from the captain's seat]]

== Compatibility ==
The 707-420/430 has been tested on several platforms, including GNU/Linux, Windows XP to Windows 10 and Mac OS X from FlightGear 2.10 to 2016.2 and GIT, and has passed all tests with flying colors. Over 15 users have helped test the aircraft throughout its evolution.
[[File:EngineerPanel.png|thumb|270px|The 707-420/430 engineering panel]]
Additionally, members of the beta testing team have visited the German Technical Museum in Munich and verified the model's accuracy.
[[File:Radiostack.png|thumb|270px|The 707-430 radio stack, radar, and throttle quadrant]]

== Get certified ==
It has been estimated that the 707 certification takes about 400 hours of flight time. We will grant 707 Knight Sky Class Certification to those pilots who reach 400 hours. Additionally, we will be giving away a 707 "City of Friedrischafen" custom set of wings, diploma, and avatar.
[[File:Refuelling707TT-EC137D.jpg|thumb|270px|A 707-TT refueling an EC-137D]]
The aircraft has been fully tested and certified. Now it's your turn. '''Be a part of the legend.'''

[[File:707Certification.png|Get Certication Boeing 707-420/430]]

== Thanks to... ==
* Innis Cunningham and all the developers who have contributed to FlightGear
=== Test pilots ===
* D-3m
* D-AHGM

=== Technical systems assistance ===
* D-LEON
=== Custom autopilot integration ===
* buster
=== Bug smashers ===
* D-STHO
* D-ABBA

{{boeing}}
{{air-to-air refueling}}

[[Category:Rembrandt aircraft]]
[[Category:Aircraft with cabin view]]

[[de:Boeing 707-420]]
[[Category:Red Griffin ATC compatible aircraft]]

Airbus A340-600

2022-03-04T20:53:27Z

Gordon: :Category:Aircraft with cabin view

{{:{{PAGENAME}}/info}}

The '''Airbus A340-600''', made by [[:Category:Airbus|Airbus]] Industries, is the longest [[:Category:Civilian aircraft|civil]] [[:Category:Airliners|airliner]] in world, until the [[Boeing 747-8i]]. It was was added to [[FlightGear]] by Liam Gathercole, starting in early November 2009.

You can follow it's progress and download the latest development version here: http://forum.flightgear.org/viewtopic.php?f=4&t=11894

Designed as an early generation [[Boeing 747|747]] replacement, the A340-600 caries up to 380 passengers in a three-class cabin layout (or 419 in a 2-class layout), with a range of over 7,500 nautical miles (13,900 km). It provides similar passenger capacity to a 747 but with 25% more cargo volume, and at lower trip and seat costs. First flight of the A340-600 was made on 23 April 2001. Virgin Atlantic began commercial services in August 2002. The A340-600 is more than 10 m longer than a basic [[Airbus A340|-300]], making it the longest airliner currently in production; more than four metres longer than the [[Boeing 747-400]] and 2.3m longer than the [[Airbus A380|A380]]. The Airbus A340-600 will continue to hold the record for being the worlds longest commercial aircraft until the first Boeing 747-8 Intercontinental is in service.

== Development status/Issues/Todo ==
=== Key Features ===
* Multiple liveries
* Reflection shaders
* External equipment models
* Internal cabin sound effects
* Autostart feature
* Good lights system
* Wings Flex with turbulence/lift
* 3D Cockpit
* Autopilot
* Animations

=== To-do ===
* Some cockpit development

== Related content ==
* [[Airbus A340]]

{{Airbus}}
[[Category:Aircraft with cabin view]]

[[fr:Airbus A340-600]]

Category:Aircraft with cabin view

2022-03-04T20:52:34Z

Gordon: Created page with "This category lists aircraft that have cabin view implemented."

This category lists aircraft that have cabin view implemented.

Dual control

2022-03-04T20:50:17Z

Gordon: picture too large

{{Affected by HLA}}
[[File:Dualcontrolready.png]]

'''Dual Control''' is a system for [[FlightGear]] that adds basic support for shared control of an [[aircraft]] over the FlightGear [[Multiplayer Howto|multiplayer network]].

'''Note:''' [[FlightGear 1.9.0]] or later is needed to use Dual Control.

== Aircraft ==

Currently there are a small number of aircraft with dual control support:
* [[Airbus A320 Family]], pilot and co-pilot (<tt>A3xx-xx1</tt>, <tt>A320-copilot</tt>). Available from {{gitorious source|proj=airbus-aircraft|repo=a320|text=Gitorious project page}}. Be sure to rename the aircraft directory to "A320-family" after checking out/downloading.
* [[Airbus A340-600]], pilot and co-pilot (<tt>A340-600</tt>, <tt>A346-copilot</tt>). Available in FlightGear 2.0 or later, Latest beta versions available on the forum.
* [[Blackburn Buccaneer]], pilot and systems officer (<tt>buccaneer</tt>, <tt>buccaneer-obs</tt>). Available in FlightGear 1.9.0 or later.
* [[Boeing 747-400]], pilot flying and pilot monitoring (<tt>747-400</tt>, <tt>747-400-fo</tt>). Available in FlightGear/Git.
* c172p Skyhawk, pilot and copilot (<tt>c172p-pilot</tt> and <tt>c172p-copilot</tt>). Based on David Megginson's [[Cessna C172|c172p]] single control aircraft. Available from [http://www.gidenstam.org/FlightGear/DualControl/Aircraft the dual-control aircraft hangar]. The tar.gz archive for the aircraft should be extracted in [[$FG_ROOT]]/Aircraft/.
* Cessna [[Cessna 182S|C182s and c182t]] Skylane
*[[Bombardier CRJ700]] (all variants), pilot and first officer (<tt>CRJ700</tt>, et al and <tt>CRJ700-firstofficer</tt>). Copilot can control aircraft using joystick and keyboard shortcuts but not toggle any switches. Available in FlightGear 2.0.0 or later.
*[[Dornier Do X]], phenomenal experience, pilot and radio operator working on interactive dual coordination for navigation. Available from [http://marc-kraus.de The Lake of Constance]
*[[fr/Douglas DC-3-C47]], pilot and copilot <u>can control aircraft</u>, and passenger 1 to 4 (<tt>dc-3</tt>, <tt>dc-3-copilot</tt>, <tt>dc-3-psg1</tt>, <tt>dc-3-psg2</tt>, <tt>dc-3-psg3</tt>, <tt>dc-3-psg4</tt>). Available in GIT.
*[[Embraer E-jets Family]], pilot and co-pilot (<tt>Embraer-17X</tt>, <tt>Embraer-17X-Copilot</tt>), Avaliable from http://theomegahangar.flymerlion.org
*[[Grumman F-14 Tomcat]], pilot and RIO (<tt>f-14b</tt>, <tt>f-14b-bs</tt>). Available in FlightGear 2.0.0 or later.
*[[Lockheed Constellation]], pilot and flight engineer, available in FGAddon since May 2017, compatible with FlightGear 3.0 and later.
*[[Hughes OH-6 Cayuse]], pilot and co-pilot (<tt>OH-6</tt>, <tt>OH-6-cp</tt>). Available on [[Hughes OH-6 Cayuse|the wiki page]].
*[[ASK-13 sailplane|Schleicher ASK-13 glider]], pilot and passenger (<tt>ask13</tt>, <tt>ask13-passenger</tt>). Available in FlightGear/Git.
*[[Submarine Scout]], pilot and observer (<tt>Submarine_Scout</tt>, <tt>Submarine_Scout-observer</tt>). Available in FlightGear 1.9.0 or later.
*[[Storch|Fieseler Fi 156 Storch]], pilot and passenger (<tt>Fi-156-de</tt>, <tt>Fi-156-passenger</tt>). Available in FlightGear 2.0.0 or later.
*[[Zeppelin NT]], pilot and copilot (<tt>ZLT-NT</tt>, <tt>ZLT-NT-copilot</tt>). Available in FlightGear 1.9.0 or later.

To connect the pilot and copilot selects each other in the Copilot dialog (FlightGear 2.0.0 or later) or set properties as explained in the usage instructions below.

Dual control enables a pilot and copilot to jointly fly the aircraft over the FlightGear multiplayer network. Depending on the aircraft the pilot and copilot have shared control over primary flight controls, throttle, mixture and so on. Exactly which controls are shared varies between the aircraft but usually include elevator trim, flaps, brakes, cockpit switches, the radio stack and some instrument settings. The copilot usually has a subset of the full instrumentation (also depending on the aircraft), usually including airspeed, altimeter, VSI, HSI, turn coordinator, engine RPM and the radio stack. Typically Nav/Comm 1 and the first VOR indicator is best controlled by the pilot, while Nav/Comm 2 and the corresponding VOR indicator is faster for the copilot.

[[File:ZLT-NT-dual.jpg|800px|thumb|center|Side-by-side presentation of the Zeppelin NT pilot's (left) and copilot's (right) views.]]

==Usage instruction==
The system consists of two "aircraft":

The pilot uses a special variant of the c172p, <tt>c172p-pilot</tt>. The pilot needs to specify the callsign of the copilot (other copilots will be ignored).
For the Zeppelin NT the aircraft names are <tt>ZLT-NT</tt> and <tt>ZLT-NT-copilot</tt>, respectively.

In the current version the pilot and copilot can select each other in their Co/Pilot selection dialogs available from the "Zeppelin NT/c172p-dual-control"->"MP-(Co)Pilot" menus.

Alternatively the relevant properties can be set from the command line or via the property browser.

'''Pilot usage example:'''
fgfs --aircraft=c172p-pilot --prop:/sim/remote/pilot-callsign="someone"

The copilot uses a special "aircraft", c172p-copilot, which piggybacks on the designated pilot and captures the local control inputs. A current limitation is that only the cockpit views are jitter free. There is also a noticeable delay between control inputs and effect, since they are passed via the the multiplayer protocol. The severity of this delay depend on round trip time and some other factors - the delay seems significantly longer than the round trip time itself which is due to buffering in the MP protocol receiver. That said, I have flown successfully as copilot in a setup with 100-120ms round trip time between both pilot and server and copilot and server (total delay >500ms). Landing is a bit exciting in that case, however.

'''Copilot usage example:'''
fgfs --aircraft=c172p-copilot --prop:/sim/remote/pilot-callsign="anybody"
Note: External views are jitter prone for the copilot.

==Developer information==
{{Caution|
{{FGCquote
|1= Normally the only Nasal available will be loaded from the model xml. The -set is effectively a placeholder for an invisible craft as you'll be sitting inside someone else's MP aircraft. The normal -set file isn't loaded at all. All properties need to be transmitted over MP, so if /instrumentation/cdu/serviceable is missing it'll need to be sent. It's a really strange concept that all of the normal stuff isn't where it usually is. It took me a while to figure out this for the F-14 RIO which I think is done in the same way
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=282765#p282765
| title = <nowiki>Re: Dual control for Boeing 777</nowiki>
| author = <nowiki>Richard</nowiki>
| date = Apr 17th, 2016
| added = Apr 17th, 2016
| script_version = 0.25
}}
}}

{{FGCquote
|1= it's roughly like this.
The nasal modules in f-14b-bs-set.xml are loaded and do the work of connecting the RIO to the pilot's aircraft. However the mp-network cannot be loaded until the model is loaded (can't remember exactly why, but it has to be done this way).
So the approach to take is to ensure that you use /sim/multiplay/generic/float or /sim/multiplay/generic/int (0..19 of each) to share the important properties over mp. This is the easiest way. If you look at the F-14 you'll see that a whole heap of animations and gauges are connected to the multiplay properties, because these will work either when flying or as an MP aircraft. If you don't want to change the animations then a nasal module inside the co-pilot to copy the multiplay/generic into the right place will work. See backseat instruments for an example of how this is done.
It gets more difficult if you need to transmit more than the permitted amount of parameters (40). Then you either have to start packing using bits, or use one of the string parameters to share the rest. Using the string parameters (as in the F-14 and the F-15) is quite inefficient and it is something that I'm working on fixing so that we have much better interaction between the front and back seats - but the first thing I'll do is to get the key properties transmitted using ints or floats, and then do the rest probably using the Emesary multiplayer bridge that I'm working on.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=282793#p282793
| title = <nowiki>Re: Dual control for Boeing 777</nowiki>
| author = <nowiki>Richard</nowiki>
| date = Apr 17th, 2016
| added = Apr 17th, 2016
| script_version = 0.25
}}
}}

}}

The main part of the Dual Control system is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality. See the link below for some more information.

==External links==

*[http://www.gidenstam.org/FlightGear/DualControl The main page for the Dual Control system.] Check here for the latest information.

[[es:Control dual]]
[[pt:Controle duplo]]
[[Category:Dual control aircraft| ]]
[[Category:FlightGear feature]]
[[Category:Multiplayer]]

Category:Articles containing Instant-Cquotes

2022-03-04T19:25:57Z

Gordon: __HIDDENCAT__ – housekeping / maintenance category

__HIDDENCAT__
{{en|Category with articles containing [[FlightGear wiki:Instant-Cquotes|Instant-Cquotes]]. The category is automatically added to pages using the {{tl|FGCquote}} template. ''See also [[:Category:Articles containing extensive quoting]].''}}

[[Category:Wiki maintenance]]

User:Gordon/notes

2022-03-04T14:28:45Z

Gordon: /* Features that could be useful */ missing word

User:Gordon/notes

2022-03-04T14:02:30Z

Gordon: + 2

On this page, I will be sharing notes and observations I made while playing FlightGear, as I find them. These may include flaws that have already been fixed, since some of the notes I found are from several years ago, and I am admittedly somewhat hesitant to update due to the risk of something that worked well so far being broken, which is an experience I frequently had with other software like web browsers.

* A water aircraft does not block sunlight. The sun's reflection is still visible on the water surface in the shadow area of the aircraft. Tested with [[Dornier Do X]].
* Perhaps the map should show coordinates at the mouse pointer's position.
* It could be useful if the flight data was recorded locally in real-time (like a real FDR), so that if the simulation crashes, the flight path is not lost.
* The instruments of some planes like the [[Boeing 707]] used raster graphics last time I checked. With vector graphics (if technically possible), they would appear sharper on high-resolution displays and while zoomed in.
* The Boeing 707 is unable to glide for long distances after engine failure due to the stall as a result of the wings being frozen from the cold temperatures at high altitudes. May or may not be intentional.

== Features that could be useful ==
These are not essential to simulation, but could add some convenience and fun:
* Ability to search for properties
* Ability to log console commands to a text file.
* YSflight has a "wingman" feature where other computer-controlled aircraft fly in formation. Something similar has been implemented with the [[Boeing 707-TT]].
* The ability to lock the camera in place (like YSflight and Super Mario 64)
* The ability to see multiple perspectives simultaneously in separate windows, like cockpit view and cabin view simultaneously.

User:Gordon/notes

2022-03-04T04:12:48Z

Gordon: expanded

User:Gordon/notes

2022-03-04T04:02:28Z

Gordon: added more

On this page, I will be sharing notes and observations I made while playing FlightGear, as I find them. These may include flaws that have already been fixed, since some of the notes I found are from several years ago.

* A water aircraft does not block sunlight. The sun's reflection is still visible on the water surface in the shadow area of the aircraft. Tested with [[Dornier Do X]].
* Perhaps the map should show coordinates at the mouse pointer's position.
* It could be useful if the flight data was recorded locally in real-time (like a real FDR), so that if the simulation crashes, the flight path is not lost.
* The instruments of some planes like the [[Boeing 707]] used raster graphics last time I checked. With vector graphics (if technically possible), they would appear sharper on high-resolution displays and while zoomed in.
* The Boeing 707 is unable to glide for long distances after engine failure due to the stall as a result of the wings being frozen from the cold temperatures at high altitudes.

User:Gordon/notes

2022-03-04T03:52:50Z

Gordon: Created page with "On this page, I will be sharing notes and observations I made while playing FlightGear, as I find them. These may include flaws that have already been fixed, since some of the..."

On this page, I will be sharing notes and observations I made while playing FlightGear, as I find them. These may include flaws that have already been fixed, since some of the notes I found are from several years ago.

* A water aircraft does not block sunlight. The sun's reflection is still visible on the water surface in the shadow area of the aircraft. Tested with [[Dornier Do X]].
* Perhaps the map should show coordinates at the mouse pointer's position.

Boeing EC-137D

2022-02-18T21:03:59Z

Gordon: Redirected page to Boeing 707-420#Variants

#REDIRECT [[Boeing_707-420#Variants]]

FlightGear wiki:Village pump

2022-02-18T20:53:58Z

Gordon: /* Backup and shutdown plan */ plural

__NEWSECTIONLINK__
{{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]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.

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.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

:: Hm, I cannot reproduce that here. Did it happen at a specific page? Can you try to reproduce it and provide a recipe?
::[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

:: Good one, done!
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Basic question sub page/sandbox ==

Hi,
New to the wiki here and hoping to contribute in some small way. I don't see any instructions (or menu options) on how to crate a sub page or sandbox in order to start drafting an article. I'll also aim to update the wiki on how to crate a sub page as it might help others with the same question.
Many thanks
[[User:Volador|Volador]] ([[User talk:Volador|talk]]) 08:33, 7 April 2021 (UTC)

== MediaWiki updated to 1.35.3 ==
We have updated MediaWiki to its latest version 1.35.3 today. Although we've tested the update, chances are that we've missed certain scenarios. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:45, 23 July 2021 (UTC)

== Backup and shutdown plan ==

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.

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)

: Hi Gorden and welcome!
: 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].
: Does that give you enough reassurance to contribute?
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:25, 14 February 2022 (UTC)

:: 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)

FlightGear wiki:Village pump

2022-02-18T20:48:32Z

Gordon: /* Backup and shutdown plan */ thanks

__NEWSECTIONLINK__
{{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]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.

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.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

:: Hm, I cannot reproduce that here. Did it happen at a specific page? Can you try to reproduce it and provide a recipe?
::[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

:: Good one, done!
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Basic question sub page/sandbox ==

Hi,
New to the wiki here and hoping to contribute in some small way. I don't see any instructions (or menu options) on how to crate a sub page or sandbox in order to start drafting an article. I'll also aim to update the wiki on how to crate a sub page as it might help others with the same question.
Many thanks
[[User:Volador|Volador]] ([[User talk:Volador|talk]]) 08:33, 7 April 2021 (UTC)

== MediaWiki updated to 1.35.3 ==
We have updated MediaWiki to its latest version 1.35.3 today. Although we've tested the update, chances are that we've missed certain scenarios. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:45, 23 July 2021 (UTC)

== Backup and shutdown plan ==

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.

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)

: Hi Gorden and welcome!
: 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].
: Does that give you enough reassurance to contribute?
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:25, 14 February 2022 (UTC)

:: Yes, sounds good. Thanks much. As a side note, the Internet Archive saves pages' lastest revision but not the full history. It just serves as additional surface backup. [[User:Gordon|Gordon]] ([[User talk:Gordon|talk]]) 20:48, 18 February 2022 (UTC)

FlightGear wiki:Village pump

2022-02-13T13:14:05Z

Gordon: /* Backup and shutdown plan */ punctuation

FlightGear wiki:Village pump

2022-02-13T13:13:19Z

Gordon: /* Backup and shutdown plan */ new section

__NEWSECTIONLINK__
{{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]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.

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.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

:: Hm, I cannot reproduce that here. Did it happen at a specific page? Can you try to reproduce it and provide a recipe?
::[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

:: Good one, done!
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Basic question sub page/sandbox ==

Hi,
New to the wiki here and hoping to contribute in some small way. I don't see any instructions (or menu options) on how to crate a sub page or sandbox in order to start drafting an article. I'll also aim to update the wiki on how to crate a sub page as it might help others with the same question.
Many thanks
[[User:Volador|Volador]] ([[User talk:Volador|talk]]) 08:33, 7 April 2021 (UTC)

== MediaWiki updated to 1.35.3 ==
We have updated MediaWiki to its latest version 1.35.3 today. Although we've tested the update, chances are that we've missed certain scenarios. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:45, 23 July 2021 (UTC)

== Backup and shutdown plan ==

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.

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)

FlightGear wiki:Village pump

2022-02-13T13:07:46Z

Gordon: __NEWSECTIONLINK__