FlightGear wiki - User contributions [en]

Howto talk:Working with FlightGear models in Blender

2024-07-06T15:45:35Z

Scttgs: I concur.

I agree that this can be deleted. [[User:Scttgs|xDraconian]] ([[User talk:Scttgs|talk]]) 15:45, 6 July 2024 (UTC)

Transponder

2024-04-22T02:28:51Z

Scttgs: /* Conspicuous and Not-Conspicuous codes - also called discrete and non-discrete */

'''Transponders''' are radio beacons which make [[aircraft]] more identifiable on [[ATC]] displays and systems and by other aircrafts. Modern transponders support transmitting additional data such as an identification ('squawk') code and aircraft altitude. See more at {{wikipedia|Transponder (aeronautics)}}.

== Id Codes ==
e.g.

* 'squawk code' 7000 is set and used VFR flight in Europe, and while in the US 1200 in used fir the same VFR.
* IFR aircraft's will have an 'attributed code' by the ATC services at Delivery Clearance time, typically at startup time. The code is ATC selected in a range of "yet not used code", range attributed regionally.

* NATO and other Military aircraft's 'sharing' the civil airspace use several code from a conventional table, like ''0300, or 0400 - NATO - CAOC 9 Exercises (activated by NOTAM)'' and ''3500 - NATO - Aircraft receiving a service from AEW aircraft''
* An aircraft becoming unable to use the voice Radio, will select the special code 7600.
* An aircraft experiencing an emergency (technical, medical) will select the special code 7700.

While some code are use the same worldwide, like the emergency code, some other codes have a different regional meaning, like the special code '0000'

* in UK, by convention, the code '0000' will be autoselected by some transponder to auto report a transponder malfunction; it is not allowed the pilots to select it by themselves.
* n Europe, in is not used any more and the use have become forbidden. It was used at the start age of transponding (in mode A) to say 'no ORCAM code inserted yet'). The use is today severely forbidden.
* In US, it is a bit more confusing:
* - it is used for some Military interception;
* - it is used by the "En route Control ARTCC" for aircraft's in cruise in their controlled airspace when ... their are no more non attributed / in current use ORCAM codes.
* - The Dep. of Transportation and the FAA have started to advocate, from 1918, the abandon of it's use going toward to prohibition of its use.

See the Wikipedia page for many more examples.

ref. https://en.wikipedia.org/wiki/List_of_transponder_codes

Codes are composes by a sequence of 4 digits of 8 possible values [ 0 ][ 0 ][ 0 ][ 0 ] to [ 7 ][ 7 ][ 7 ][ 7 ]

Codes defines 7 specifically or :

* 1 aircraft and 1 aircraft only ;
* 1 situation.

== Conspicuous and Not-Conspicuous codes - also called discrete and non-discrete ==
Codes ending by ..00 defines "situations".

e.g.

* 7600 - unable to use the Radio Voice Comms - "Communications failure"
* 7700 - Emergency (technical / Medical)

Theses codes do not define 1 aircraft only.

Codes ending by numbers (0 to 7) identifies 1 and only 1 aircraft.

* they are attributed by the ATC, usually via radio at the clearance departure
* they can be changed along the flight to accommodate management needs.

The codes identifying 1 and only 1 aircraft are called discrete or conspicuous.

The codes defining situations are called non-discrete or not-conspicuous.

This also why Transponder Codes are called Conspicuity Codes.

ref https://skybrary.aero/articles/discrete-and-non-discrete-ssr-codes

== ORCAM method (for attribution of squawk codes) ==
Their are way more aircraft's to manage than available squawk codes.

To solve the problem the ORCAM method is used.

ORCAM stands for Originating Regional Code Attribution Method.

Every region, airspace, airport, service like Militaries, etc. will see attributed a range of codes.

When the aircraft leave the controlled zone and enter the next one, if, emphasising "if", the used code collide with another currently in use in the vicinity, the ATC will ask to recycle the code to a new (not used) one.

ORCAM is a method and not a "table",

although the method keep out of its management a subset of fix codes which one are ... a table.

e.g.

Note that the following table is valid for UK only and US or Europe will present some variations

https://www.flightradars.eu/squawkcodes.html#top

== Modes A, B, C, S ==
detailed illustrated explanation ref. https://skybrary.aero/articles/transponder

or also

https://pilotinstitute.com/transponder-modes-explained/<nowiki/>{{hatnote|For a thorough description, see {{wikipedia|Aviation transponder interrogation modes}}.}}

Needs always evolves and technology merely adapt to the change. The Transponder Modes are the reflex of the evolution of theses needs.

=== Mode A ===
from 2nd WW era, when aircraft was flying back and closing to the base, it was hard to say if they was Friends Or Enemy (FOE). To avoid unwanted activation from the DCA's, pilots was activating a convention code switching ON/OFF a set of buttons to define an identity code.

After the WW, this has come back to civil aviation, but the mode was really basic and more identification features was wanted.

=== Mode B ===
have been an evolution of the mode A, but due some quirks it has been quick abandoned for mode C

=== Mode C ===
added report of the aircraft altitude.

These report altitude was read after calibration, which has led to problems and have been update to non calibrated altitude in mode S.

Why ?

Imagine an Aircraft in final approach, the definition of an incorrect altimetric pressure may lead to "hit" the ground before the RWY or hot the RWY to late and trigger a RWY excursion.

Other situation of bust of altitude (lost of vertical separation) also have happened (although more rarely).

Mode C altitude report is by 100 ft

=== Mode S. ===
Why not MODE D, E, F ... ?

Mode S have been a game changer.

In Mode C their was too many aircraft sending information at the same time. The Radio Frequency was congested, many time, life and death information become missing as the result of the chaos of all the transponder "speaking at the same time".

In Mode S, transponder are quite and shushing unless "interrogated" by the surveillance system.

Well, almost shush. The surveillance system need to know to whom direct the interrogation. For this all transponder still continue to emit repeatedly a very very short ID called the squitter.

The surveillance system keep a table of all the squitters for management.

The frequency being not any more congested, interrogated transponders have the possibility to send more extensive informations.

The mode S have itself 2 ways, ELS and EHS as ELementary Surveillance and EnHanced Surveillance

The former send altitude (before calibration) speed, direction, ... and few more Aircraft and Flight parameters.

The later one send also the "selected" altitude in the Autopilot, which allow the ATC to detect early misunderstandings and prevent possible level bust before they happen.

ref.: https://skybrary.aero/articles/mode-s

Mode S altitude report is by 10 ft, again, read before calibration !

To do this the transponder needs an altitude source. In real-life this can be a separate box called an encoder, or may be derived for FMC / ADIRU sources. It's important to note this altitude is referenced to standard pressure (29.92 inHg / 1013 Hpa), and not corrected for actual barometric pressure in the local environment.

Additional support for military modes is possible if anyone wishes to add it.

== Transponder "in the flying deck / cockpit" ==
Bare in mind that 1 transponder is always different from another transponder.

* Older aircraft may still have old transponder not Mode S capable;
* Several manufacturers
* Boeing ≠ Airbus
* ...

Some Transponder have a knob with position labelled "ALTITUDE" which does not mean the transponder is activating the mode S. The mode C also have a report of altitude. (see above).

The usual modes encountered in RL for the transponder are :

* Off - ( switched off / no power)
* Test - (maintenance)
* Stand-by - (powered on but not sending out informations except the squitter - see above)
* Ground - (send out SQUAWK CODE only - some airport, by rule - expect code 2000 for ground taxiing aircraft's)
* Altitude - (in mode C, sending out altitude information - in mode S, sending out more information)

== TA and TA/RA - Traffic Alert / Resolution Advisory ==
On some transponder, TA/RA functions might be switched on separately.

They <big>need</big> the '''mode S''' in order to work !

A frequent myth is the mode S and the TA/RA must only be activated on air.

Nothing is more wrong.

Airport where the visibility is traditionally not good and foggy, like Paris Orly LFPO, Milano Linate LIML, Bimingham EGBB, among others, other require the departing aircraft to activate the mode S and the TA from the gate/stand, before push !

TA on ground have a special mode with a different sensitivity adapted to detect closing taxiing aircraft's. It has many time be a matter of sever accidents with fatalities.

e.g.

Flight SCANDINAVIA 686 (Scandinanvian Airlines McDonnel Douglas MD-87) and a private Cessna Citation, making 118 victims. https://en.wikipedia.org/wiki/Linate_Airport_disaster

Paris Orly is "that much so foggy" that it is where have been invented to first "Turbo Clear" the first and fog systems for airports, 1963. The whole world have bought them and used them before the first ATT (Atterrissages Tout Temps) , "Landing With Any Weather", the precursor of the Instrument Landing Systems. https://www.aeroport-paris-orly.com/systemes-anti-brouillard

The myth roots itself in the fact that the rules changes by airports and situations. One discovering the rule enforced in one airport might tend to believe the whole world do the same...

Usually, the airport administration information pages in the airport charts brief clearly about the rules enforced in "that" very airport.

On ground

Mode S + Traffic Alert might be required to be used

Airborn

Mode S + Traffic Alert + Resolution Advisory is as much as possible expected

"Old" aircraft using frequently the controlled airspace are demanded to upgrade their transponder.

== Mode IDENT ==
Transponder have a separate function called IDENT and callable by the press on a button.

This actually is not a "mode" like Mode A, C or S.

It should never be pressed unless required by the ATC providing service.

It "must" not be activated by Squawk code changing ! (Frequent error)

IDENT allow to the ATC to spot in a flash an aircraft amongst many and its purpose it solely to help in case of loss of conspicuity.

Squawk codes changes at quite a good rate. If at every time the squawk code is recycled, the IDENT is activated and the BLIP (aircraft on the ATC screen) start to blink, then when the ATC demand to someone to press IDENT, the help will be void because drawn in many other IDENT...

QED.

== Configuration in FlightGear ==
Transponder support was overhauled in May 2013; earlier versions (2.10 and prior) have different support and are not documented here. Updating an aircraft to use the new config is straightforward. Key transponder properties (altitude, ident and transmitted-id) are now sent via the MP protocols for use in ATC clients.

The default altimeter can act as an altitude encoder; in its configuration, set either or both of the following boolean flags:

* encode-mode-c
* encode-mode-s

The transponder has various config properties:

* '''minimum-supply-volts''': required DV volts for operations, defaults to 8.0 ''(old '''bus-volts''' is now deprecated)''
* '''encoder-path''': defaults to '/instruments/altimeter', but can be changed to any other location. The transponder looks for child properties 'mode-c-alt-ft' and 'mode-s-alt-ft' at this path for altitude data.
* '''kt70-compatibility''': boolean, default to false. Set this to enable legacy compatibility with the old KT-70 C++ instrument. Do not use in new/updated aircraft!
* '''mode''': this is 0 for Mode-A, 1 for Mode-C and 2 for Mode-S. Other modes can be added, ask on the [[Mailing list|devel list]]!

=== Run-time properties ===
* '''altitude''': gives the transmitted altitude in feet (or -9999 for invalid)
* '''altitude-valid''': indicates if altitude value is valid data or not
* '''id-code''': allows the id-code to be read and set
* '''serviceable''': can be set to control the instrument serviceability
* '''transmitted-id''': gives the value being transmitted, including over the network via MP

==== Input properties ====
These live under <tt>/inputs</tt>.
* '''knob-mode''': sets the transponder operating mode. This corresponds to the KT-70 knob positions for convenience, but the actual modes should work for any transponder instrument. Knob modes are documented below
* '''ident-btn''': can be set to place the transponder in ident mode for 18 seconds. Note this property is not spring-loaded, i.e you must manually reset it to false
* '''digit[0]-[4]''': properties allow the id code individual digits to be read and set

In KT-70 compatibility mode, additional properties are read and set, to preserve legacy aircraft. Do not use these properties in new aircraft.

==== Knob/Functional Modes ====
* 0 - off
* 1 - standby, basically the same as off for the C++ code (3D instrument would power up the display, presumably)
* 2 - test, again the C++ largely ignores this since the test configuration of real-world instruments varies. In particular the unit does *not* set altitude or transmitted-id to any test values, you should do that in your own logic. (Maybe we should allow the test values to be defined int he config section?)
* 3 - Ground mode, responds to altitude interrogation but does not broadcast an ID. This would typically be used while taxiing prior to takeoff.
* 4 - On, normal operation but altitude transmission is inhibited
* 5 - Alt, same as on but altitude is broadcast if transponder was configured in Mode-S or Mode-C

=== Generic transponder ===
Below are all available property that you can set for your instrumentation.xml file :

<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<mode type="int">1</mode> 
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
<auto-ground>...</auto-ground> 
<airspeed-path>...</airspeed-path>
<mach-path>...</mach-path>
</transponder>
</syntaxhighlight>Please note that ''<bus-volts>'' is now '''deprecated'''. Use ''<minimum-supply-volts>'' instead.
The following is a copy of a comment in instrument source, explaining the use of Mode-S related properties
<
// Mode-S transponders (configured with mode = 2) can transmit a ground bit to
// indicate ground operation. If auto-ground is not defined, the ground bit is
// switched manually by setting the transponder knob to GND. If auto-ground is
// defined, the transponder simulates automatic switching of the ground bit
// using the value of the property defined in auto-ground.
//
// For a squat switch, use "/gear/gear/wow". For automatic switching based on
// airspeed, use a property rule to make a new boolean property that indicates,
// for example, airspeed < 80, and reference your new property in auto-ground.
//
// Note that Mode-A and Mode-C transponders do not transmit a ground bit, even
// if the transponder knob is set to the GND position.
//
// Mode-S transponders also transmit indicated airspeed and Mach number. The
// default sources are "/instrumentation/airspeed-indicator/indicated-speed-kt"
// and ".../indicated-mach", but this can be changed by setting "airspeed-path"
// and "mach-path" properties respectively as shown above.

==Related content==
===Wiki articles===
*[[Howto:Develop an aircraft transponder in Nasal]] – Most probably obsolete
*[[FLARM]]
*[[Multiplayer protocol]] – The IDs 1501-1503 are earmarked for transmitting transponder properties
*[[OpenRadar: Transponder]]
*[[Traffic alert and collision avoidance system]]

===Forum topics===
*[https://forum.flightgear.org/viewtopic.php?f=4&t=31492 Transponder properties over MP] (January-June 2017)
*[https://forum.flightgear.org/viewtopic.php?f=75&t=19826 Transponder over network] (April-December 2018)
*[https://forum.flightgear.org/viewtopic.php?f=4&t=6395 Transponder] (November 2009-December 2010)

===Developer mailing list===
*[https://sourceforge.net/p/flightgear/mailman/message/30785263/ <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Improve tranponder instrument] (Apr 2009)
*[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1388915221.2195.15.camel%40duter.localdomain/#msg31810053 <nowiki>[</nowiki>Flightgear-devel<nowiki>]</nowiki> Transponder Ident not transmitted via MP Protocol?] (Jan-Feb 2014)

===Source code===
*{{flightgear source|src/Instrumentation/transponder.hxx}}
*{{flightgear source|src/Instrumentation/transponder.cxx}}

[[Category:Aircraft enhancement]]
[[Category:Aircraft instruments]]

Keyboard shortcuts

2023-04-28T06:20:44Z

Scttgs: Add Toggle Auto-coordination

Cheat sheet for using the most common '''keyboard shortcuts'''.

{{note|As keyboard bindings can differ from aircraft to aircraft, some of these shortcuts may be different than showed below}}
{{tip|If you so wish you can also [[Howto:Reassign keyboard bindings|customize keyboard bindings]]}}

== Keyboard bindings ==
{| class="vatop"
|width="500" |
=== General ===
{| class="wikitable sortable"
|-
! Key combination
! Action
|-
| {{key press|/}}
| Show [[property browser]]
|-
| {{key press|?}}
| Show current aircraft specific help
|-
| {{key press|:}}
| vi-like [[multikey commands]]
|-
| {{key press|,}}
| Apply left brakes
|-
| {{key press|.}}
| Apply right brakes
|-
| {{key press|Shift|M}}
| Show map
|-
| {{key press|Ctrl|C}}
| Toggle [[Howto: Make a clickable panel|clickable panel hotspots]]
|-
| {{key press|Esc}}
| Quit FlightGear
|-
| {{key press|H}}
| Cycle through [[HUD]] styles
|-
| {{key press|Shift|H}}
| Cycle through [[HUD]] brightnesses
|-
| {{key press|F3}}
| Print screen
|-
| {{key press|F10}}
| Toggle [[menu]]bar visibility
|-
| {{key press|F11}}
| Open [[autopilot]] dialog
|-
| {{key press|F12}}
| Open radio settings dialog
|-
| {{key press|P}}
| Pause/continue sim
|-
| {{key press|Shift|P}}
| Toggle [[2D panel]]
|-
| {{key press|Shift|Esc}}
| Reset FlightGear
|-
| {{key press|Shift|F1}}
| Load flight
|-
| {{key press|Shift|F2}}
| Save flight
|-
| {{key press|Shift|F5}}
| Scroll 2D panel down
|-
| {{key press|Shift|F6}}
| Scroll 2D panel up
|-
| {{key press|Shift|F7}}
| Scroll 2D panel left
|-
| {{key press|Shift|F8}}
| Scroll 2D panel right
|-
| {{key press|Shift|F10}}
| Toggle fullscreen
|}

=== View ===
{| class="wikitable sortable"
|-
! Key combination
! Action
|-
| {{key press|Ctrl|X}}
| Reset zoom to default
|-
| {{key press|V}}
| Next view
|-
| {{key press|Shift|V}}
| Previous view
|-
| {{key press|X}}
| Zoom in
|-
| {{key press|Shift|X}}
| Zoom out
|-
| {{key press|Z}}
| Increase visibility
|-
| {{key press|Shift|Z}}
| Decrease visibility
|-
| {{key press|Ctrl|R}}
| Instant replay
|}
|width="500"|
=== Flying ===
{| class="wikitable sortable"
|-
! Key combination
! Action
|-
| {{key press|}}} {{key press|}}} {{key press|}}} {{key press|s}}
| Start a propeller engine ("}" x3 to set magneto, then hold "s" to start)
|-
| {{key press|/}}
| Show [[property browser]]
|-
| {{key press|B}}
| Apply all brakes
|-
| {{key press|Shift|B}}
| Toggle parking brake(s)
|-
| {{key press|G}}
| Gear up
|-
| {{key press|Shift|G}}
| Gear down
|-
| {{key press|J}}
| Spoilers/air brake down
|-
| {{key press|K}}
| Spoilers/air brake up
|-
| {{key press|[}}
| Flaps up
|-
| {{key press|]}}
| Flaps down
|-
| {{key press|Alt|2}}
| Toggle Auto-coordination
|}

=== Autopilot ===
{| class="wikitable sortable"
|-
! Key combination
! Action
|-
| {{key press|Ctrl|A}}
| Altitude lock
|-
| {{key press|Ctrl|H}}
| Heading lock
|-
| {{key press|Ctrl|G}}
| Glideslope lock
|-
| {{key press|Ctrl|N}}
| NAV1 lock
|-
| {{key press|Ctrl|P}}
| Pitch hold
|-
| {{key press|Ctrl|S}}
| Autothrottle
|-
| {{key press|Ctrl|T}}
| Terrain lock
|-
| {{key press|Ctrl|W}}
| Wing level
|-
| {{key press|F6}}
| Heading lock
|}
|}

== See also ==
* [[Bindings]]
* [[Howto:Reassign keyboard bindings]]

[[Category:FlightGear keyboard]]

Busiest World Airports Custom Scenery

2021-01-20T03:28:29Z

Scttgs: Created page with "{{Project |name = Busiest World Airports Custom Scenery |description = Produce fresh scenery for the world's busiest airports |start-date = 2021-Jan |current-status = Active |..."

{{Project
|name = Busiest World Airports Custom Scenery
|description = Produce fresh scenery for the world's busiest airports
|start-date = 2021-Jan
|current-status = Active
|developers = Scott Giese

|objective-body =
Produce high quality airport scenery leveraging the best known practices.

|background-body =
Data Sources:
* Airport Layout: X-Plane Gateway
* Demographic Data: SRTMGL1.003, LiDAR
* Land Cover Data: NLCD, CLC, OpenStreetMap
* River & Stream Data: OpenStreetMap
* Buildings, Roads, Bridges: osm2city based on OpenStreetMap
* Obstruction Data: FAA DOF

|status-body =
'''Hartsfield-Jackson Atlanta International Airport''' [KATL]: {{ongoing}} {{progressbar|30}}
* Terrain: {{ongoing}}
* Scenery: {{ongoing}}
* Obstacles: {{not done}}
* osm2city: {{not done}}
* Custom Scenery Release: {{not done}}
* TerraSync Release: {{not done}}
* Version: {{not done}}
 

|category = Custom scenery
}}

FlightGear Newsletter January 2021

2021-01-09T05:27:48Z

Scttgs: Newsletter creation, automatic preload from here

{{User:Skybike/Template:Newsletter-header-translate|2021-01}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==





== In the hangar ==









== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2021 01]]

OpenGL

2020-12-04T17:18:23Z

Scttgs: status update

{{See also|FlightGear and OpenGL ES}}

'''OpenGL''' ('''Open G'''raphics '''L'''ibrary) is a graphics API used by [[FlightGear]]. It was developed by Silicon Graphics and first released in 1992.

Currently FlightGear requires OpenGL 1.2, but more likely 2.0, and recommends 2.1 or above.

== Status ==
Last updated: 11/2020

We’re actively going to switch to Core profile, on next, in the coming months: at least that is James' big goal for 2021 development, personally.

Maybe not getting as far as [[Vulkan Scene Graph|Vulkan/VSG]] (it would be nice but a lot more work….) but certainly getting our use of the OSG API as modern as possible, and getting the shaders into a OpenGL 4.x variant. (Eg, if MoltenGL can host us, that would be good for macOS…)

James would expect as a result of that, we would require OpenGL 4.1 or 4.2 on next: we could do 3.3 at a push but why bother? Apple supports 4.2 [1] and everyone else can update their drivers. Writing clean shaders will be so much easier if we can rely on 4.2 features as a baseline.

That would imply 2020.3 is the last OpenGL 2.x / non-shader release, but James also suspects on plenty of lower-spec machines, using OpenGL 4 and shaders will give us *better* FPS than our current fixed-function code. Given lower-spec machines have Intel graphics and the Intel drivers are terrible bad at fixed-function.<ref>https://sourceforge.net/p/flightgear/mailman/message/37146847/</ref>

Scott has been working on preparing to make the switch to OpenGL Core Profile <ref>https://sourceforge.net/p/flightgear/mailman/message/37147065/</ref>:
* Compile OSG with Core - {{Done}}
* Disable (a.k.a hack) SG/FG [[FlightGear_and_OpenGL_ES#Affected_features_and_sources|features requiring compatibility profile]] {{Done}}
* Review GLSL shaders to identify where changes are required - {{Done}}
* Refactor GLSL shaders {{Progressbar|90}}

== Related content ==
* [[Resources#General OpenGL Resources|General OpenGL Resources]]
* [[Graphics drivers configuration]]
* [[Graphics Card Profiles]]

== External links ==
* [http://www.opengl.org/ Official website]
* http://www.sgi.com/products/software/opengl/overview.html
* http://en.wikibooks.org/wiki/Opengl

==References ==
{{Appendix}}

[[Category:Software]]
[[pt:OpenGL]]

OpenGL

2020-12-04T17:16:52Z

Scttgs: status update

{{See also|FlightGear and OpenGL ES}}

'''OpenGL''' ('''Open G'''raphics '''L'''ibrary) is a graphics API used by [[FlightGear]]. It was developed by Silicon Graphics and first released in 1992.

Currently FlightGear requires OpenGL 1.2, but more likely 2.0, and recommends 2.1 or above.

== Status ==
Last updated: 11/2020

We’re actively going to switch to Core profile, on next, in the coming months: at least that is James' big goal for 2021 development, personally.

Maybe not getting as far as [[Vulkan Scene Graph|Vulkan/VSG]] (it would be nice but a lot more work….) but certainly getting our use of the OSG API as modern as possible, and getting the shaders into a OpenGL 4.x variant. (Eg, if MoltenGL can host us, that would be good for macOS…)

James would expect as a result of that, we would require OpenGL 4.1 or 4.2 on next: we could do 3.3 at a push but why bother? Apple supports 4.2 [1] and everyone else can update their drivers. Writing clean shaders will be so much easier if we can rely on 4.2 features as a baseline.

That would imply 2020.3 is the last OpenGL 2.x / non-shader release, but James also suspects on plenty of lower-spec machines, using OpenGL 4 and shaders will give us *better* FPS than our current fixed-function code. Given lower-spec machines have Intel graphics and the Intel drivers are terrible bad at fixed-function.<ref>https://sourceforge.net/p/flightgear/mailman/message/37146847/</ref>

Scott has been working on preparing to make the switch to OpenGL Core Profile <ref>https://sourceforge.net/p/flightgear/mailman/message/37147065/</ref>:
* Compile OSG with Core - {{Done}}
* Disable (a.k.a hack) SG/FG [[FlightGear_and_OpenGL_ES#Affected_features_and_sources|features requiring compatibility profile]] {{Progressbar|70}}
* Review GLSL shaders to identify where changes are required - {{Progressbar|100}}
* Refactor GLSL shaders {{Progressbar|90}}

== Related content ==
* [[Resources#General OpenGL Resources|General OpenGL Resources]]
* [[Graphics drivers configuration]]
* [[Graphics Card Profiles]]

== External links ==
* [http://www.opengl.org/ Official website]
* http://www.sgi.com/products/software/opengl/overview.html
* http://en.wikibooks.org/wiki/Opengl

==References ==
{{Appendix}}

[[Category:Software]]
[[pt:OpenGL]]

OpenGL

2020-11-30T22:25:21Z

Scttgs: update progress

{{See also|FlightGear and OpenGL ES}}

'''OpenGL''' ('''Open G'''raphics '''L'''ibrary) is a graphics API used by [[FlightGear]]. It was developed by Silicon Graphics and first released in 1992.

Currently FlightGear requires OpenGL 1.2, but more likely 2.0, and recommends 2.1 or above.

== Status ==
Last updated: 11/2020

We’re actively going to switch to Core profile, on next, in the coming months: at least that is James' big goal for 2021 development, personally.

Maybe not getting as far as [[Vulkan Scene Graph|Vulkan/VSG]] (it would be nice but a lot more work….) but certainly getting our use of the OSG API as modern as possible, and getting the shaders into a OpenGL 4.x variant. (Eg, if MoltenGL can host us, that would be good for macOS…)

James would expect as a result of that, we would require OpenGL 4.1 or 4.2 on next: we could do 3.3 at a push but why bother? Apple supports 4.2 [1] and everyone else can update their drivers. Writing clean shaders will be so much easier if we can rely on 4.2 features as a baseline.

That would imply 2020.3 is the last OpenGL 2.x / non-shader release, but James also suspects on plenty of lower-spec machines, using OpenGL 4 and shaders will give us *better* FPS than our current fixed-function code. Given lower-spec machines have Intel graphics and the Intel drivers are terrible bad at fixed-function.<ref>https://sourceforge.net/p/flightgear/mailman/message/37146847/</ref>

Scott has been working on preparing to make the switch to OpenGL Core Profile <ref>https://sourceforge.net/p/flightgear/mailman/message/37147065/</ref>:
* Compile OSG with Core - {{Done}}
* Disable (a.k.a hack) SG/FG features requiring compatibility profile {{Progressbar|70}}
* Review GLSL shaders to identify where changes are required - {{Progressbar|100}}
* Refactor GLSL shaders {{Progressbar|80}}

== Related content ==
* [[Resources#General OpenGL Resources|General OpenGL Resources]]
* [[Graphics drivers configuration]]
* [[Graphics Card Profiles]]

== External links ==
* [http://www.opengl.org/ Official website]
* http://www.sgi.com/products/software/opengl/overview.html
* http://en.wikibooks.org/wiki/Opengl

==References ==
{{Appendix}}

[[Category:Software]]
[[pt:OpenGL]]

FlightGear Newsletter November 2020

2020-11-19T04:50:32Z

Scttgs: Created preloaded page

{{User:Skybike/Template:Newsletter-header-translate|2020-11}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==





== In the hangar ==












== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the important development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Scenery corner ==














== Community news ==







=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [http://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
Flightgear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flightsims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==

=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====


If you want to participate in the screenshot contest , you can submit your candidate to {{forum link|title=this|f=19|t= }}. Be sure to see the first post for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}

[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2020 11]]

[[de:FlightGear Newsletter {{#time: F Y | 2020-11 | de }}]]

Talk:2020 LTS airport announcement and Iceland intro draft

2020-10-28T23:32:25Z

Scttgs: Artwork Names

Artwork Names:
Rainbow (“Regnbogi”)
The Jet Nest (“Þotuhreiður”)
[[User:Scttgs|xDraconian]] ([[User talk:Scttgs|talk]]) 19:32, 28 October 2020 (EDT)

Howto talk:Work with AC3D files in Blender

2020-07-17T17:50:41Z

Scttgs: Why is 2.83 LTS not supported?

Blender 2.83 LTS is declared to not be supported. What is the issue? I'm using Blender 2.90 successfully.

Enhancement requests

2020-07-06T04:34:21Z

2020-06-21T04:37:33Z

Scttgs: Scttgs uploaded a new version of File:N00-N10-LC100m-SRTMGL3.png

=={{int:filedesc}}==
{{Information
|description={{en|1=N00-N10 lat}}
|date=2020-06-06
|source={{own}}
|author=[[User:Scttgs|Scttgs]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Scenery]]

World Scenery 3.0 roadmap

2020-06-14T03:36:47Z

Scttgs:

{{stub}}
{{Scenery Core Development}}
{{See also|TerraGear roadmap}}
{{Project
|name = World Scenery 3.0
|description = New world-wide scenery
|start-date = 2019-Sep
|current-status = Active
|developers = Scott Giese Richard Harrison Stuart Buchanan

|motivation-body =
{{Main article|Virtual Planet Builder}}
{{FGCquote
|Virtual Planet Builder (VPB) is OSG's terrain-database-building tool.
It loads GIS elevation data for a
region, combines it with imagery and produces a spatially-balanced
quadtree tiled database that can be navigated simply by loading the
top-level file. All of the LOD Ranges are pre-configured and the
DatabasePager automatically loads and unloads different segments of
terrain without any supporting userspace code required. VPB can build
terrain models ranging from a small area to the entire planet. These
databases can be fluidly navigated at 60fps from outer space down to
ground level with no interruptions. The terrain models are built of
regular grid arrays with optional edge-skirts to conceal any cracks
caused by adjacent LOD differences. 
|{{cite web |url=http://alphapixel.com/wp-content/uploads/2015/04/OpenSceneGraph-OSG-Virtual-Planet-Builder-VPB-OSGDEM.pdf
|title=<nowiki>OpenScenGraph's Virtual Planet Builder/OSGDEM</nowiki>
|publisher=<nowiki>AlphaPixel, LLC</nowiki>
}}
}}

|objective-body =
Produce high-quality scenery using the best-known practices.

TerraGear becomes obsolete in favor of VPB.

OpenGL 3.3 Core Profile: WS3.0 will require us to eliminate the usage of the fixed-function pipeline. 
Shader-based Rendering: All of the terrain renderings will be done via GLSL shaders. 
OSG Core: OpenSceneGraph will require targeting of the OpenGL Core Profile.

WS3.0 will continue to cooperate with osm2city.

Easy upgrade: Airport layouts will be generated in real-time. Apt.dat will continue to be the primary source for airport layouts.
Airports will be draped over the terrain. This eliminates the need to cut airport layouts into the underlying terrain.

|background-body =
=== Data Sources ===

:;SRTMGL3.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL3.003/
:;SRTMGL1.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL1.003/
:;Global Land Cover:: https://lcviewer.vito.be/
:;Natural Earth:: https://www.naturalearthdata.com/

|status-body =
Proof of Concept {{progressbar|100}}
* VPB {{done}}
* osgOcean {{done}}
* osgVegetation {{done}}
* Generate terrain for Hawaii {{done}}
* Hack Hawaii VPB into FG {{done}}
 

OSG {{progressbar|70}}
* Core Profile: {{done}}
* GLVND Support: {{done}}
* glTF Plugin Support: {{ongoing}}
 

{{gallery
| title = Standard-Fidelity
| align = right
| N00-N10-LC100m-SRTMGL3.png | N00-N45 lat
| Africa-LC100m-SRTMGL3.png | Africa Land Coverage
| Africa-Natural.png | Natural Earth
}}
=== Standard-Fidelity - 90m SRTMGL3 - 100m Global Land Cover ===

Virtual Planet Builder {{progressbar|20}}
* Procure Demographic Data: SRTMGL3.003 {{ongoing}}
** Northern: {{progressbar|50}}
** Southern: {{progressbar|0}}
* Process through VPB {{ongoing}}
** Northern: {{progressbar|50}}
** Southern: {{progressbar|0}}
 

=== High-Fidelity - 30m SRTMGL1 - Best Available Land Cover ===

Virtual Planet Builder {{progressbar|20}}
* Procure Demographic Data: SRTMGL1.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
 

|gallery-body =
}}

For the experimental runtime generated mesh/landclassing engine - which may become WS3.0 - see [[Experimental terrain engine]].

[[Category:Development projects‎]]
[[Category:Scenery]]

File:N00-N10-LC100m-SRTMGL3.png

2020-06-14T03:32:20Z

Scttgs: Scttgs uploaded a new version of File:N00-N10-LC100m-SRTMGL3.png

File:Africa-Natural.png

2020-06-14T03:30:53Z

2020-06-10T04:09:46Z

Scttgs:

{{stub}}
{{Scenery Core Development}}
{{See also|TerraGear roadmap}}
{{Project
|name = World Scenery 3.0
|description = New world-wide scenery
|start-date = 2019-Sep
|current-status = Active
|developers = Scott Giese Richard Harrison Stuart Buchanan

|motivation-body =
{{Main article|Virtual Planet Builder}}
{{FGCquote
|Virtual Planet Builder (VPB) is OSG's terrain-database-building tool.
It loads GIS elevation data for a
region, combines it with imagery and produces a spatially-balanced
quadtree tiled database that can be navigated simply by loading the
top-level file. All of the LOD Ranges are pre-configured and the
DatabasePager automatically loads and unloads different segments of
terrain without any supporting userspace code required. VPB can build
terrain models ranging from a small area to the entire planet. These
databases can be fluidly navigated at 60fps from outer space down to
ground level with no interruptions. The terrain models are built of
regular grid arrays with optional edge-skirts to conceal any cracks
caused by adjacent LOD differences. 
|{{cite web |url=http://alphapixel.com/wp-content/uploads/2015/04/OpenSceneGraph-OSG-Virtual-Planet-Builder-VPB-OSGDEM.pdf
|title=<nowiki>OpenScenGraph's Virtual Planet Builder/OSGDEM</nowiki>
|publisher=<nowiki>AlphaPixel, LLC</nowiki>
}}
}}

|objective-body =
Produce high-quality scenery using the best-known practices.

TerraGear becomes obsolete in favor of VPB.

OpenGL 3.3 Core Profile: WS3.0 will require us to eliminate the usage of the fixed-function pipeline. 
Shader-based Rendering: All of the terrain renderings will be done via GLSL shaders. 
OSG Core: OpenSceneGraph will require targeting of the OpenGL Core Profile.

WS3.0 will continue to cooperate with osm2city.

Easy upgrade: Airport layouts will be generated in real-time. Apt.dat will continue to be the primary source for airport layouts.
Airports will be draped over the terrain. This eliminates the need to cut airport layouts into the underlying terrain.

|background-body =
=== Data Sources ===

:;SRTMGL3.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL3.003/
:;SRTMGL1.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL1.003/
:;Global Land Cover:: https://lcviewer.vito.be/
:;Natural Earth:: https://www.naturalearthdata.com/

|status-body =
Proof of Concept {{progressbar|100}}
* VPB {{done}}
* osgOcean {{done}}
* osgVegetation {{done}}
* Generate terrain for Hawaii {{done}}
* Hack Hawaii VPB into FG {{done}}
 

OSG {{progressbar|70}}
* Core Profile: {{done}}
* GLVND Support: {{done}}
* glTF Plugin Support: {{ongoing}}
 

{{gallery
| title = Standard-Fidelity
| align = right
| N00-N10-LC100m-SRTMGL3.png | N00-N30 lat
| Africa-LC100m-SRTMGL3.png | Africa Land Coverage
| Africa-Natural.png | Africa Natural Earth
}}
=== Standard-Fidelity - 90m SRTMGL3 - 100m Global Land Cover ===

Virtual Planet Builder {{progressbar|30}}
* Procure Demographic Data: SRTMGL3.003 {{ongoing}}
** Northern: {{progressbar|30}}
** Southern: {{progressbar|0}}
* Process through VPB {{ongoing}}
** Northern: {{progressbar|30}}
** Southern: {{progressbar|0}}
 

=== High-Fidelity - 30m SRTMGL1 - Best Available Land Cover ===

Virtual Planet Builder {{progressbar|20}}
* Procure Demographic Data: SRTMGL1.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
 

|gallery-body =
}}

For the experimental runtime generated mesh/landclassing engine - which may become WS3.0 - see [[Experimental terrain engine]].

[[Category:Development projects‎]]
[[Category:Scenery]]