FlightGear wiki - User contributions [en]

FlightGear Newsletter December 2025

2025-12-10T09:14:20Z

Avionyx: spacing

{{User:Skybike/Template:Newsletter-header-translate|2025-12}}
{{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.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==



== Related Software tools and projects ==
=== Julia photoscenery generator GUI ===
==== Photoscenery-GUI ====
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal "LIBERA ET TESSELA"]]

A major update has been released for the Photoscenery GUI, introducing significant accessibility enhancements.

The key addition is full Internationalization (i18n) support, which makes the tool more accessible to a global audience. Users can now switch between languages instantly using new flag icons located in the control panel.

What’s New:

Multi-language Support:
The interface now supports multiple languages, including: English, Italian, French, German, Spanish, Portuguese, Chinese (Simplified), Japanese, Korean, Arabic (with full Right-to-Left layout support), and Russian.

UI Improvements:
A new language switcher with flag icons has been implemented. Layout and font sizes have been optimized for better readability across different languages. Spacing in the control panel has been improved for a cleaner interface.

This update is now available in the main branch on GitHub https://github.com/abassign/Photoscenery-GUI.git. Users are encouraged to test the new features and provide feedback regarding any translation errors or suggestions for additional language support.

For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&t=39066&start=420

=== Re-Introducing the Rain Vector Editor Addon ===
This tool has been around for a while, to reintroduce it there is a short video in the forum link below demonstrating its simple use. Use it to get the exact splash-x, y and z vectors that best look like rain on any specific window. Use that data to code dynamic control over the look of rain on windows and windscreens when introducing wind, prop blast and aircraft velocity through the air.

{{#ev:youtube|EyRiW5aZeX0|480px||FG Rain Vector Editor Add-on}}

To explore the Rain Vector Editor project and its assets, you can directly access its repository here:

https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/RainVectorEditor/

We encourage everyone to check it out and contribute feedback!

https://forum.flightgear.org/viewtopic.php?f=14&t=43932&sid=20078e01f815391532dbded0a512a825&start=45#p436889

== In the hangar ==


======

=== Augusta Westland AW109 "Grand New" ===
[[File:aw109ext2.png|400px|thumb|AW109 External shot 1]]Version 1.0 of the AW109 has been released by the team at FGUK.
[[File:109int3.png|thumb|400x400px|AW109 Internal shot]]
[[File:aw109ext1.png|400px|thumb|right|AW109 External View - HEMS configuration]]This initial release includes a new model with latest fuselage and shader effects, a functional cockpit and basic HDR compatibility.

The FDM, in YASim, is entirely bespoke and tuned to give realistic performance across the flight envelope. V3 of the FGUK heli-autopilot is also included (help available via the in sim documentation)

There are various configuration options selectable either manually or via the liveries (15+ included) to cover HEMS, SAR, Law Enforcement, Passenger and Military equipment levels and loadouts, with a functioning winch operator available in configurations with an appropriate winch.

Details, downloads and discussion/updates are available directly [https://forum.fguk.me/discussion/987/augusta-westland-aw109-grand-new-now-available#latest here at the FGUK forum]

[[File:aw109ext4.png|400x400px|thumb|AW109 "Grand New" external shot - Sunset ]]

=== <big>Boeing 727 </big> ===
Progress on the new Boeing 727 is continuing, with the virtual cockpit being further 3D modelled and the SP-150 autopilot being developed.

=== <big>Boeing 777</big> ===
A few people have gathered to collaborate on the Boeing 777. They have taken development to a new [https://gitlab.com/sidi762/flightgear-777 gitlab repository], and will backport stable releases to FGaddon. Currently Jean-Yves Lebleu is improving the LNAV/VNAV implementation on the 777. Naviat is working on a new 3D model that will eventually replace the current 3D model and Octal450 will be creating a [[JSBSim]] FDE to replace the old YASim.

Isaak has made quite some progress on the hydraulics system that will soon be merged into the stable release. As this is close to finished, below are some pointers of what is possible. Checklists are currently in the working. The hydraulics system operates as close as currently possible to the Boeing 777 FCOM. A few items are still missing because they require a better electric and air system or a fault simulation. They are on a longer term todo list for when these systems are impro

These features are implemented:

* There is a new item in the "Aircraft settings" dialog: you can enable realistic hydraulic fluid depletion (due to leaks and wear). This requires the "Store fuel and hydraulic fluid level between sessions" option to be enabled as well. Hydraulic fluid will deplete at a very slow rate, based on which systems and pumps are operating. Isaak will finetune the consumption rate a bit further. The goal is to require a refill of (some) hydraulic fluid every 2 weeks of operation, to add some extra workload to the preflight checks. If a fluid reservoir runs below standpipe level or completely empty, the corresponding pumps will fail and possibly overheat if running without fluid. The hydraulic fluid levels can be checked and refilled via the ground services dialog.
* Hydraulics synoptics screen on the MFD (lower EICAS) is fully functional. It is selectable with the "Hyd" button on the EFIS control panel.
* Hydraulic pumps and valves operate as per FCOM: they require hydraulic fluid in the correct reservoir (at or below standpipe level, depending on the pump), a correct power source...
* If a hydraulic pump or system fails, the corresponding system will fail too: flaps will not extend, brakes might fail if the brake accumulator runs empty as well...
* It has become extremely important to turn on and off the hydraulic pumps in the right order: fluid transfer between the center and right system is implemented (via the brake system) so you can overfill or deplete one of the systems when you enable/disable the right hydraulic pumps at the wrong time. Follow the checklists to prevent this: always turn on the right hydraulic system before powering the others, and only switch it off after the center pumps have been switched off.
* Both the normal and alternate/reserve brake systems are implemented. The brake accumulator can power the brakes if it is pressurised enough. If it pressurises the parking brake, it will slowly lose pressure over time. After about 10 hours, the parking brake will release (even though the "Parking Brake Set" will remain active on the EICAS display), so for longer times of unpowered parking: use wheel chocks to prevent an unwanted trip with the aircraft. The brake accumulator is powerful enough to bring the aircraft to a complete stop when landing without hydraulic systems.
* The EICAS will throw errors when pumps and/or systems are depressurised.

There are some good Youtube videos that can help you understand the Boeing 777 hydraulics systems:

* [https://www.youtube.com/watch?v=DEoniYv6GOI This series] provides a good basic understanding of normal and non-normal hydraulic systems and procedures.
* [https://www.youtube.com/watch?v=P_izKDUc-GY This series] provides a deeper insight in the Boeing 777 brake system.

The hydraulics system is currently still in a separate branch, but will be merged into "master" soon.

=== <big>McDonnell Douglas MD-80</big> ===
The MD-80 now has a new pedestal with all the missing controls modelled. Most of them are already hooked up to the aircraft systems with exceptions to pressurization control.

{{#ev:youtube|IKOa8NUofw8}}




== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 05]]

FlightGear Newsletter December 2025

2025-12-10T09:12:02Z

Avionyx: spacing

{{User:Skybike/Template:Newsletter-header-translate|2025-12}}
{{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.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==



== Related Software tools and projects ==
=== Julia photoscenery generator GUI ===
==== Photoscenery-GUI ====
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal "LIBERA ET TESSELA"]]

A major update has been released for the Photoscenery GUI, introducing significant accessibility enhancements.

The key addition is full Internationalization (i18n) support, which makes the tool more accessible to a global audience. Users can now switch between languages instantly using new flag icons located in the control panel.

What’s New:

Multi-language Support:
The interface now supports multiple languages, including: English, Italian, French, German, Spanish, Portuguese, Chinese (Simplified), Japanese, Korean, Arabic (with full Right-to-Left layout support), and Russian.

UI Improvements:
A new language switcher with flag icons has been implemented. Layout and font sizes have been optimized for better readability across different languages. Spacing in the control panel has been improved for a cleaner interface.

This update is now available in the main branch on GitHub https://github.com/abassign/Photoscenery-GUI.git. Users are encouraged to test the new features and provide feedback regarding any translation errors or suggestions for additional language support.

For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&t=39066&start=420

=== Re-Introducing the Rain Vector Editor Addon ===
This tool has been around for a while, to reintroduce it there is a short video in the forum link below demonstrating its simple use. Use it to get the exact splash-x, y and z vectors that best look like rain on any specific window. Use that data to code dynamic control over the look of rain on windows and windscreens when introducing wind, prop blast and aircraft velocity through the air.

{{#ev:youtube|EyRiW5aZeX0|480px||FG Rain Vector Editor Add-on}}

To explore the Rain Vector Editor project and its assets, you can directly access its repository here:

https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/RainVectorEditor/

We encourage everyone to check it out and contribute feedback!

https://forum.flightgear.org/viewtopic.php?f=14&t=43932&sid=20078e01f815391532dbded0a512a825&start=45#p436889

== In the hangar ==


===  Augusta Westland AW109 "Grand New" ===
[[File:aw109ext2.png|400px|thumb|left|Caption]]Version 1.0 of the AW109 has been released by the team at FGUK.
[[File:109int3.png|thumb|400x400px|AW109 Internal shot]]
[[File:aw109ext1.png|400px|thumb|right|AW109 External View - HEMS configuration]]This initial release includes a new model with latest fuselage and shader effects, a functional cockpit and basic HDR compatibility.

The FDM, in YASim, is entirely bespoke and tuned to give realistic performance across the flight envelope. V3 of the FGUK heli-autopilot is also included (help available via the in sim documentation)

There are various configuration options selectable either manually or via the liveries (15+ included) to cover HEMS, SAR, Law Enforcement, Passenger and Military equipment levels and loadouts, with a functioning winch operator available in configurations with an appropriate winch.

Details, downloads and discussion/updates are available directly [https://forum.fguk.me/discussion/987/augusta-westland-aw109-grand-new-now-available#latest here at the FGUK forum]

[[File:aw109ext4.png|400x400px|thumb|left|AW109 "Grand New" external shot - Sunset ]]

=== <big>Boeing 727 </big> ===
Progress on the new Boeing 727 is continuing, with the virtual cockpit being further 3D modelled and the SP-150 autopilot being developed.

=== <big>Boeing 777</big> ===
A few people have gathered to collaborate on the Boeing 777. They have taken development to a new [https://gitlab.com/sidi762/flightgear-777 gitlab repository], and will backport stable releases to FGaddon. Currently Jean-Yves Lebleu is improving the LNAV/VNAV implementation on the 777. Naviat is working on a new 3D model that will eventually replace the current 3D model and Octal450 will be creating a [[JSBSim]] FDE to replace the old YASim.

Isaak has made quite some progress on the hydraulics system that will soon be merged into the stable release. As this is close to finished, below are some pointers of what is possible. Checklists are currently in the working. The hydraulics system operates as close as currently possible to the Boeing 777 FCOM. A few items are still missing because they require a better electric and air system or a fault simulation. They are on a longer term todo list for when these systems are improved.

These features are implemented:

* There is a new item in the "Aircraft settings" dialog: you can enable realistic hydraulic fluid depletion (due to leaks and wear). This requires the "Store fuel and hydraulic fluid level between sessions" option to be enabled as well. Hydraulic fluid will deplete at a very slow rate, based on which systems and pumps are operating. Isaak will finetune the consumption rate a bit further. The goal is to require a refill of (some) hydraulic fluid every 2 weeks of operation, to add some extra workload to the preflight checks. If a fluid reservoir runs below standpipe level or completely empty, the corresponding pumps will fail and possibly overheat if running without fluid. The hydraulic fluid levels can be checked and refilled via the ground services dialog.
* Hydraulics synoptics screen on the MFD (lower EICAS) is fully functional. It is selectable with the "Hyd" button on the EFIS control panel.
* Hydraulic pumps and valves operate as per FCOM: they require hydraulic fluid in the correct reservoir (at or below standpipe level, depending on the pump), a correct power source...
* If a hydraulic pump or system fails, the corresponding system will fail too: flaps will not extend, brakes might fail if the brake accumulator runs empty as well...
* It has become extremely important to turn on and off the hydraulic pumps in the right order: fluid transfer between the center and right system is implemented (via the brake system) so you can overfill or deplete one of the systems when you enable/disable the right hydraulic pumps at the wrong time. Follow the checklists to prevent this: always turn on the right hydraulic system before powering the others, and only switch it off after the center pumps have been switched off.
* Both the normal and alternate/reserve brake systems are implemented. The brake accumulator can power the brakes if it is pressurised enough. If it pressurises the parking brake, it will slowly lose pressure over time. After about 10 hours, the parking brake will release (even though the "Parking Brake Set" will remain active on the EICAS display), so for longer times of unpowered parking: use wheel chocks to prevent an unwanted trip with the aircraft. The brake accumulator is powerful enough to bring the aircraft to a complete stop when landing without hydraulic systems.
* The EICAS will throw errors when pumps and/or systems are depressurised.

There are some good Youtube videos that can help you understand the Boeing 777 hydraulics systems:

* [https://www.youtube.com/watch?v=DEoniYv6GOI This series] provides a good basic understanding of normal and non-normal hydraulic systems and procedures.
* [https://www.youtube.com/watch?v=P_izKDUc-GY This series] provides a deeper insight in the Boeing 777 brake system.

The hydraulics system is currently still in a separate branch, but will be merged into "master" soon.

=== <big>McDonnell Douglas MD-80</big> ===
The MD-80 now has a new pedestal with all the missing controls modelled. Most of them are already hooked up to the aircraft systems with exceptions to pressurization control.

{{#ev:youtube|IKOa8NUofw8}}




== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 05]]

FlightGear Newsletter December 2025

2025-12-10T09:11:43Z

Avionyx: Addition of AW109 section

{{User:Skybike/Template:Newsletter-header-translate|2025-12}}
{{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.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==



== Related Software tools and projects ==
=== Julia photoscenery generator GUI ===
==== Photoscenery-GUI ====
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal "LIBERA ET TESSELA"]]

A major update has been released for the Photoscenery GUI, introducing significant accessibility enhancements.

The key addition is full Internationalization (i18n) support, which makes the tool more accessible to a global audience. Users can now switch between languages instantly using new flag icons located in the control panel.

What’s New:

Multi-language Support:
The interface now supports multiple languages, including: English, Italian, French, German, Spanish, Portuguese, Chinese (Simplified), Japanese, Korean, Arabic (with full Right-to-Left layout support), and Russian.

UI Improvements:
A new language switcher with flag icons has been implemented. Layout and font sizes have been optimized for better readability across different languages. Spacing in the control panel has been improved for a cleaner interface.

This update is now available in the main branch on GitHub https://github.com/abassign/Photoscenery-GUI.git. Users are encouraged to test the new features and provide feedback regarding any translation errors or suggestions for additional language support.

For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&t=39066&start=420

=== Re-Introducing the Rain Vector Editor Addon ===
This tool has been around for a while, to reintroduce it there is a short video in the forum link below demonstrating its simple use. Use it to get the exact splash-x, y and z vectors that best look like rain on any specific window. Use that data to code dynamic control over the look of rain on windows and windscreens when introducing wind, prop blast and aircraft velocity through the air.

{{#ev:youtube|EyRiW5aZeX0|480px||FG Rain Vector Editor Add-on}}

To explore the Rain Vector Editor project and its assets, you can directly access its repository here:

https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/RainVectorEditor/

We encourage everyone to check it out and contribute feedback!

https://forum.flightgear.org/viewtopic.php?f=14&t=43932&sid=20078e01f815391532dbded0a512a825&start=45#p436889

== In the hangar ==


===  Augusta Westland AW109 "Grand New" ===
[[File:aw109ext2.png|400px|thumb|left|Caption]]Version 1.0 of the AW109 has been released by the team at FGUK.
[[File:109int3.png|thumb|400x400px|AW109 Internal shot]]
[[File:aw109ext1.png|400px|thumb|right|AW109 External View - HEMS configuration]]This initial release includes a new model with latest fuselage and shader effects, a functional cockpit and basic HDR compatibility.

The FDM, in YASim, is entirely bespoke and tuned to give realistic performance across the flight envelope. V3 of the FGUK heli-autopilot is also included (help available via the in sim documentation)

There are various configuration options selectable either manually or via the liveries (15+ included) to cover HEMS, SAR, Law Enforcement, Passenger and Military equipment levels and loadouts, with a functioning winch operator available in configurations with an appropriate winch.

Details, downloads and discussion/updates are available directly [https://forum.fguk.me/discussion/987/augusta-westland-aw109-grand-new-now-available#latest here at the FGUK forum]

[[File:aw109ext4.png|400x400px|thumb|left|AW109 "Grand New" external shot - Sunset ]]

=== <big>Boeing 727 </big> ===
Progress on the new Boeing 727 is continuing, with the virtual cockpit being further 3D modelled and the SP-150 autopilot being developed.

=== <big>Boeing 777</big> ===
A few people have gathered to collaborate on the Boeing 777. They have taken development to a new [https://gitlab.com/sidi762/flightgear-777 gitlab repository], and will backport stable releases to FGaddon. Currently Jean-Yves Lebleu is improving the LNAV/VNAV implementation on the 777. Naviat is working on a new 3D model that will eventually replace the current 3D model and Octal450 will be creating a [[JSBSim]] FDE to replace the old YASim.

Isaak has made quite some progress on the hydraulics system that will soon be merged into the stable release. As this is close to finished, below are some pointers of what is possible. Checklists are currently in the working. The hydraulics system operates as close as currently possible to the Boeing 777 FCOM. A few items are still missing because they require a better electric and air system or a fault simulation. They are on a longer term todo list for when these systems are improved.

These features are implemented:

* There is a new item in the "Aircraft settings" dialog: you can enable realistic hydraulic fluid depletion (due to leaks and wear). This requires the "Store fuel and hydraulic fluid level between sessions" option to be enabled as well. Hydraulic fluid will deplete at a very slow rate, based on which systems and pumps are operating. Isaak will finetune the consumption rate a bit further. The goal is to require a refill of (some) hydraulic fluid every 2 weeks of operation, to add some extra workload to the preflight checks. If a fluid reservoir runs below standpipe level or completely empty, the corresponding pumps will fail and possibly overheat if running without fluid. The hydraulic fluid levels can be checked and refilled via the ground services dialog.
* Hydraulics synoptics screen on the MFD (lower EICAS) is fully functional. It is selectable with the "Hyd" button on the EFIS control panel.
* Hydraulic pumps and valves operate as per FCOM: they require hydraulic fluid in the correct reservoir (at or below standpipe level, depending on the pump), a correct power source...
* If a hydraulic pump or system fails, the corresponding system will fail too: flaps will not extend, brakes might fail if the brake accumulator runs empty as well...
* It has become extremely important to turn on and off the hydraulic pumps in the right order: fluid transfer between the center and right system is implemented (via the brake system) so you can overfill or deplete one of the systems when you enable/disable the right hydraulic pumps at the wrong time. Follow the checklists to prevent this: always turn on the right hydraulic system before powering the others, and only switch it off after the center pumps have been switched off.
* Both the normal and alternate/reserve brake systems are implemented. The brake accumulator can power the brakes if it is pressurised enough. If it pressurises the parking brake, it will slowly lose pressure over time. After about 10 hours, the parking brake will release (even though the "Parking Brake Set" will remain active on the EICAS display), so for longer times of unpowered parking: use wheel chocks to prevent an unwanted trip with the aircraft. The brake accumulator is powerful enough to bring the aircraft to a complete stop when landing without hydraulic systems.
* The EICAS will throw errors when pumps and/or systems are depressurised.

There are some good Youtube videos that can help you understand the Boeing 777 hydraulics systems:

* [https://www.youtube.com/watch?v=DEoniYv6GOI This series] provides a good basic understanding of normal and non-normal hydraulic systems and procedures.
* [https://www.youtube.com/watch?v=P_izKDUc-GY This series] provides a deeper insight in the Boeing 777 brake system.

The hydraulics system is currently still in a separate branch, but will be merged into "master" soon.

=== <big>McDonnell Douglas MD-80</big> ===
The MD-80 now has a new pedestal with all the missing controls modelled. Most of them are already hooked up to the aircraft systems with exceptions to pressurization control.

{{#ev:youtube|IKOa8NUofw8}}




== Scenery corner ==




















== Community news ==









== Multiplayer events ==









== 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.

{{Appendix}}

[[Category:Changes after 2024.1]]
[[Category:FlightGear Newsletter|2025 05]]

File:Aw109ext4.png

2025-12-10T08:39:27Z

Avionyx: External shot AW109 V1

== Summary ==
External shot AW109 V1

File:Aw109ext2.png

2025-12-10T08:38:36Z

Avionyx: AW109 V1.0 External shot

== Summary ==
AW109 V1.0 External shot

File:Aw109ext1.png

2025-12-10T08:37:37Z

Avionyx: AW109 "Grand New" V.1 External

== Summary ==
AW109 "Grand New" V.1 External

File:109int3.png

2025-12-10T08:36:25Z

Avionyx: AW109 "Grand New" Interior shot - HDR Sunset

== Summary ==
AW109 "Grand New" Interior shot - HDR Sunset

Hackathon Proposal:Add movement to boats using METAR

2021-11-05T22:23:54Z

Avionyx: added video links to working examples

{| class="wikitable"
|-
| Title: || <big>{{{title|Add movement to boats using METAR plus default oscillation}}}</big> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations.
|-
| Background: || {{{background|}}}
|-
| Details: || <s>{{{details|n/a}}}</s> {{{details|n/a}}}
|-
| Required skills: || XML and possibly Nasal. This must be lightweight on processing.
|-
| Learning Opportunities: || xml animation
|-
| Notes: || Possible example here at: http://www.fguk.me/hangar/download/15-ai-scenarios/536-uss-lake-champlain - Various other ships fitted with same script not yet released but tested as working quite well.

[https://www.youtube.com/watch?v=O0sE_kH3JCM - https://www.youtube.com/watch?v=O0sE_kH3JCM]

- https://youtu.be/vwm3TtRr1tk?t=587

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Add movement to boats using METAR

2021-11-05T22:10:27Z

Avionyx: Added information to already working example which may provide what is needed or a start point.

{| class="wikitable"
|-
| Title: || <big>{{{title|Add movement to boats using METAR plus default oscillation}}}</big> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations.
|-
| Background: || {{{background|}}}
|-
| Details: || <s>{{{details|n/a}}}</s> {{{details|n/a}}}
|-
| Required skills: || XML and possibly Nasal. This must be lightweight on processing.
|-
| Learning Opportunities: || xml animation
|-
| Notes: || Possible example here at: http://www.fguk.me/hangar/download/15-ai-scenarios/536-uss-lake-champlain - Various other ships fitted with same script not yet released but tested as working quite well

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

[[Category:Hackathon 2021 Ideas]]

Ground Services

2020-12-31T16:31:21Z

Avionyx: /* Installation */

{{infobox subsystem
|image = GroundServices-Title.png
|name = Ground Services
|started = 03/2017
|description = Moving ground service vehicles at airports
|status = Under active development as of 03/2017
|maintainers = {{usr|ThomasS}}
|developers = ThomasS
|topic-fgdata = https://github.com/thomass171/GroundServices (addon)
}}

{{See also|Ground Traffic Simulation Resources}}
This article is about the '''GroundServices addon''' prototype for FlightGear. Unlike some existing ground services which are part of various aircraft, it is intended to be generic and not dependent on specific aircraft (though there will be dependencies from aircraft dimensions).

== Overview ==
{{See also|Traffic Shader}}
{{See also|Road Traffic}}

The [[addon]] currently moves ground vehicles along an airports taxiways and provides simple catering and fueling services.

It is written completely in [[Nasal]] and is derived/inspired from the existing AI subsystem and <code>tanker.nas</code> (except for the way vehicles are moving).<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=311651#p311651
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Jun 2nd, 2017
|added = Jun 2nd, 2017
|script_version = 0.40
}}</ref>

After starting FlightGear, GroundServices goes to "standby" mode, monitoring the distance of the main aircraft to the next airport. When the distance is below 3 NM (<code>main.minairportrange</code>), GroundService switches to "active" mode. It reads the corresponding <code>groundnet.xml</code> and ground vehicles are launched as defined in <code>AI/groundservices.xml</code></code>.

<code>initialcount</code> vehicles (scaled by airport size) of each type will be launched at their defined home location and move between the configured destinations (random groundnet nodes are used if nothing is configured).

When the distance to the airport exceeds 3 NM, GroundServices switches back to "standby" mode, removing all ground vehicles.

The models included are

* The standard Goldhofert pushback truck with aircraft specific animations removed
* The followme car from FG Addon
* The fuel truck from Gabriels 737-800 branch
* The catering model https://scenery.flightgear.org/app.php?c=Models&a=view&id=6620

The GUI provides the options to
* Launch an additional vehicle (select in combo box and button "Launch")
* Launch catering and fuel service for an arrived aircraft
* Visualize the groundnet (which is implemented quite inefficiently by multiple models for each length due to the lack of dynamic model scaling). The color of the groundnet lines should be yellow, but differs for some unknown reason (lighting effects?) from red to orange.
* Toggle auto movement of vehicles and auto service
* Open a canvas map which shows the location of the vehicles and service points
* Write the state of each vehicle to the logfile

== Background ==
There are already existing ground service components in FG providing Pushback, FollowMe, Ramp Marshall and Jetways (maybe even more). Integrating these with the existing AI system appears straightforward. Routes for driving vehicles on the apron could be derived from <code>groundnet.xml</code>.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=304670#p304670
|title = <nowiki> Re: Ground services ! </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Feb 1st, 2017
|added = Feb 1st, 2017
|script_version = 0.40
}}</ref>
The Nasal approach of <code>tanker.nas</code> however looks more comprehensive. Reading <code>groundnet.xml</code> from Nasal apparently isn't possible yet without doing explicit XML parsing. Though the <code>airportinfo</code> function in nasal provides parking and taxiway information, these might be derived from different sources than <code>groundnet.xml</code>.

Having the <code>groundnet.xml</code> information available in Nasal in combination with the logic in <code>tanker.nas</code> might provide a simple way for having vehicles moving on the apron.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=304670#p304670
|title = <nowiki> Re: Ground services ! </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Feb 1st, 2017
|added = Feb 1st, 2017
|script_version = 0.40
}}</ref>

== Requirements ==
{{See also|Airports with ground networks}}
GroundServices was developed and tested with FlightGear 2016.4.3, 2017.3.1 and EDDKs, EHAMs, EGLLs and EDDFs groundnet. As of release 0.3.0 it is a FlightGear addon and so requires at least FlightGear version 2017.3. There are no further known special requirements and it should also work with later FlightGear versions and airports that have a groundnet defined.

The solution is based on the airports <code>groundnet.xml</code>. So for now you just have to make sure that your airports <code>groundnet.xml</code> is reasonable, meaning parking positions are at correct location and all connected to taxiways. Look at [https://github.com/thomass171/GroundServices/releases ] https://github.com/thomass171/GroundServices/releases for releases.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=315223#p315223
|title = <nowiki> Re: Ground services ! </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Jul 28th, 2017
|added = Jul 28th, 2017
|script_version = 0.40
}}</ref>

== Current Status ==
GroundServices currently moves ground vehicles along an airports taxiways and provides simple catering and fueling services.
Its just a prototype and still might contain bugs. There is a risk of null/nil pointer incidents. Indicator for this is when all vehicles stop moving.

The catering and fueling services are composed of a catering vehicle approaching an aircraft right front door and a fuel truck approaching the left wing. The approach destinations are calculated from the aircraft position and a defined door and wing position of the aircraft. Currently the implementation only uses a rough approximation of these positions, because there seem to be only a few aircraft models out there that have door positions defined.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=315206#p315206
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Jul 28th, 2017
|added = Jul 28th, 2017
|script_version = 0.40
}}</ref>

Furthermore, there seems to be no way to get information about an AI aircraft model from the property tree currently. However, <code>jetways.nas</code> seems to find the door positions even for AI aircrafts (issue added to roadmap).

Known problems are (see also [https://github.com/thomass171/GroundServices/issues issue list]):

* Ground Services doesn't work with scenery outside FG_HOME (solved in release v0.3.0)
* Vehicles appear twisting at some nodes when turning (partly solved in release v0.3.0)

== Releases ==
The addon is available [https://github.com/thomass171/GroundServices/releases here]. It is recommended to use the latest release 0.5.0 and install the addon from the zip archive.

Changelog up to release 0.5.0

v0.2.0 (August 2017):
* Fixes the problem of vehicles having wrong elevation when they were launched before the scenery was completely loaded.
* Uses position dependant elevation for visualized ground net segments instead of airport elevation.
* Fuel truck added
* Now finds a vehicle home position even for groundnets having inconsistent headings at parking positions
* Fixes several "non-objects have no members" problems.
* Delayed launch of initial vehicles
* preparation for AI traffic integration

v0.3.0 (November 2017):
* Further fixes for correct elevation of vehicles
* Fix for airports with negative longitude (didn't work here)
* Service points and schedules are introduced. Service points let catering and fuel trucks approach aircraft.
* Canvas map shows location of vehicles, service points and main aircraft
* Vehicles have varying speed (accelerate and brake)
* The module is an addon now

v0.4.0 (April 2018):
* Adjustments for complying to new addon structure

0.5.0 (June 2018):
* Additional adjustments for complying to new addon structure. No more manual installation required.
* Vehicles move at the outline of taxiways instead of on the center line. This reduces the number of visual collisions.
* Two 737 model (Air Canada and Air France) and one Cessna Citation are launched. The Cessna will just move around the groundnet while the 737 will move to some non occupied neighbor position of the current aircraft.

== Installation ==
As of release 0.3.0 this module is an addon and as of release 0.5.0 it fully complies to the FlightGear addon infrastructure available as of 2018.2.1. It is recommended to use at least release 0.5.0 of this addon with at least FlightGear 2018.2.1.

The addon is installed just like any other addon as described in [[Addon]]. No manual steps are needed any more.

'''A video of the installation and running can be found here:'''

{{#ev:youtube | SBbus7I0oPs}}
Youtube video: Installation and running of Ground Services Addon for FlightGear

== Running ==
After starting FG with the aircraft located on an airport that has a groundnet defined (I propose using ufo on EDDK for a first attempt) the vehicles will start moving from their home point immediately. In EDDK vehicles will move near the main terminal and should be easily visible. EHAM, EDDF and EGLL are considerably larger and have no home configured. In EHAM vehicles will start from cargo position R, which is in the south west of the airport. Move ufo near there (by PHI; thats very easy) for seeing the vehicles.

If any problems occur, check FGs logfiles for nasal errors. In addition a logfile <code>FG_HOME/groundservices.log</code> is written by GroundService and can be checked for errors.

== Features ==
For having some nearby activity, two 737 models (Air Canada and Air France) will be launched after initialization (config parameter <code>delayfornearbyaircraft</code>). These will move to some non occupied neighbor position of the current aircraft and receive servicing.

== Monitoring vehicles ==
Its not easy to detect the current position of ground vehicles. Seeing them from your current view point is mere chance.

=== Phi ===
[[File:Phi-Vehicles.png|right|thumb|Ground vehicles displayed in Phi]]

An option for monitoring vehicles is the map of [[Phi]]. This however requires two patches to the file <code>Phi/topics/Map/AILayer.js</code> in <code>FG_ROOT</code>. Near line 81 the type <code>gsvehicle</code> needs to added:

<syntaxhighlight lang="js">
self.addData(self.aiPropsToGeoJson(data, [
"tanker","gsvehicle", "aircraft", "multiplayer", "carrier" ], self._map.getBounds()));
</syntaxhighlight>

and near line 139 these models need to be considered:

<syntaxhighlight lang="js">
if (type == "gsvehicle") {
callsign = child.getNode("id").getValue();
} else {
if (type == "carrier") {
...
</syntaxhighlight>

Don't forget the closing curly brace a few lines beneath (not displayed here). Reload [[Phi]] in your browser and choose "Other Traffic" in the layer selection menu.

=== Canvas Map ===
[[File:Gs mapEDDF.PNG|right|thumb|Ground Services map in EDDF]]

The map is opened by clicking the "Map" menu item in the Ground Services menu. It uses the following colored indicators for vehicles:

{| class="wikitable"
| <big style="color: rgb(0, 255, 128);">o</big> || ground vehicle
|-
| <big style="color: rgb(200,0,240);">o</big> || active service point (arrived aircraft)
|-
| <big style="color: rgb(0, 255, 255);">o</big> || current aircraft
|}

=== Model Cockpit View ===
The addon [[Model Cockpit View]] lets cycle the view point through all AI cockpits. For using it with ground service vehicles, the phrase <code>gsvehicle</code> needs to be added manually to the code (<code>main.nas</code>):

<syntaxhighlight lang="xml">
...
~ ai.getChildren("gsvehicle")
...
</syntaxhighlight>

By default, the view point will be at (0,0,0), so the view point from a ground vehicle will be exactly on the ground below the vehicle. Though this might be useful for analysis purposes, a raised view point is more interesting. See [[Model Cockpit View]] on how to change the view point.

== Configuration ==
The main configuration file is <code>AI/groundservices.xml</code>. When no home position is defined for an airport, the first (or last)
parking node will be used as home.

== Uninstall ==
Uninstallation is done by just deleting the addons directory and removing it from the addons option from the command line.

== Implementation Notes ==
The groundnet information is stored in a graph data structure.

For simplification, the coordinates are projected to a 2D xy coordinate system, where all calculations are executed (The projection currently is a too simple linear projection).

Moving of vehicles is implemented by first finding a path along the graph (<code>Graph.findPath()</code>), which is quite simple due to Edsger Dijkstras preliminary work. The vehicles will move along their defined path like a train on rails. They will allways be fixed at some specific position on some edge (class <code>GraphPosition</code>).

For accomplishing a smooth transition from one edge to the other, the graph not only allows line edges but also arc edges. So the shortest path found through the graph will be smoothed (<code>GraphUtils.createPathFromGraphPosition()</code> and <code>GraphUtils.createTransition()</code>) by truncating line edges and connecting these by arc edges. These graph edges will be added temporarily to the graph and will be removed from the graph when the vehicle reaches its destination.

Smoothing the graph path is a quite complex process with many potential combinations (eg. short edges, small angles between edges, orientation of vehicles). Optimizing this process still is a work in progress.

== Known Problems ==
Sometimes the errors

<syntaxhighlight>
NasalSys.cxx:1204:Nasal runtime error: non-objects have no members
NasalSys.cxx:1216: at /Users/thomas/Projekte/FlightGearGit/FGData/Nasal/canvas/api.nas, line 147

NasalSys.cxx:1204:Nasal runtime error: MapStructure model not found
NasalSys.cxx:1216: at /Users/thomas/Projekte/FlightGearGit/FGData/Nasal/canvas/MapStructure.nas, line 27
</syntaxhighlight>
are logged to the FG log file. The reason is unclear.

== Roadmap ==
The list of possible improvements is endless. The following are some of the ideas (without any order):
* The turning radius of vehicles at parking nodes is too small sometimes, which make vehicles turn unrealistically twisting {{pending}}
* Vehicles should accelerate instead of just switching speed. {{Progressbar|100}} {{done}}
* Vehicles shouldn't move on taxiways but on dedicated lanes. This requires either an extended version of groundnet.xml (newer versions of <code>apt.dat</code> might contain a groundnet for ground service vehicles) or some smart algorithm. In any case, a big challenge. {{pending}}
* Vehicles not using dedicated lanes (currently all) should move at the outline of taxiways which reduces the risk of collisions. {{Progressbar|100}} {{done}}
* Make a fuel and catering vehicle approach parking AI aircraft {{Progressbar|100}} {{done}}
* Vehicles should be animated, starting with a catering vehicle moving up its container. Unfortunately the current catering vehicle model doesn't allow animation.{{pending}}
* Animation of wheels. {{pending}}
* Check using <code>ai.nas</code> mentioned in [[Scripted_AI_Objects]]. {{pending}} (that's actually outdated meanwhile, [[Ground Services]] looks much more promising)
* Make it a Flightgear addon. {{Progressbar|100}} {{done}}
* Add a canvas GUI for monitoring vehicles {{Progressbar|100}} {{done}}
* Retrieve door positions from AI model like [[Howto:Animated jetways|animated jetways]] does. AI aircraft should contain a piece of nasal code that adds door information to the property tree when loaded. However, extending AI core code for saving model origin information to the property tree could still be useful, eg. for defining cockpit positions in addon [[Model Cockpit View]]. {{Progressbar|20}}
* Extend AI core code for saving departure/arrival information of AI aircrafts to the property tree. Thus arrived parking aircrafts can be detected for service more reliably. Such an extension might also be helpful for the [[Howto:Animated jetways|animated jetways]]. {{Progressbar|10}} {{pending}}
* Unify AI traffic categories for avoiding manual patches to [[Model Cockpit View]] and [[Phi]] by a Nasal registry for all kinds of AI/MP traffic, eg. <code>AI.nas</code> or <code>Traffic.nas</code>.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=6&t=30735&p=323612&hilit=mapstructure.nas#p323588
|title = <nowiki> Re: Ground services ! </nowiki>
|author = <nowiki> Hooray</nowiki>
|date = Dec 2nd, 2017
|added = Dec 2nd, 2017
|script_version = 0.40
}}</ref> {{Progressbar|10}} {{pending}}
* Extend MapStructure.nas with a kind of layer registry for avoiding copying files into FG_ROOT.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=6&t=30735&p=323612&hilit=mapstructure.nas#p323588
|title = <nowiki> Re: Ground services ! </nowiki>
|author = <nowiki> Hooray</nowiki>
|date = Dec 2nd, 2017
|added = Dec 2nd, 2017
|script_version = 0.40
}}</ref> . Latest tests show that no change to <code>MapStructure.nas</code> is required. The layer can just be added from the addon. Will be part of next release. {{Progressbar|100}} {{done}}

== Gallery ==
A followme vehicle on its way at EHAM.

[[File:GroundServices-screen-007.png]]

== References ==
{{Appendix}}

[[Category:FlightGear addons]]

FlightGear hangars

2019-04-11T06:57:12Z

Avionyx: /* Aircraft hangars */ - Updated to correct URL for FGUK following change from .eu to .me domain

Aircraft in FlightGear are often distributed from a hangar. The official FlightGear hangar is called [[FGAddon]] and it contains hundreds of aircraft at different stages of development (including aircraft from up to 20 years ago). Many aircraft are also distributed via 3rd-party hangars.

== Licensing ==

The [[FGAddon]] hangar is distributed using the GPLv2+ licensing terms - see the official [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. Third party hangars are free to license their content as they wish.

{{caution|If licensing violations are found in a 3rd party hangar - including copying images, sounds, 3D objects or any other content that cannot be legally copied, or any non-legal licensing combinations - the FlightGear developers reserve the right to remove all mentions of that hangar from the official FlightGear web infrastructure (wiki, forum, mailing lists, etc.). The advertisement of illegal content via the official infrastructure could lead to legal problems for the FlightGear developers.}}

== Official FGAddon hangar ==
The [[FGAddon|FGAddon hangar]] is the official FlightGear hangar.

=== Aircraft downloads ===
[[File:FGAddon logo.png|270px|right|link=FGAddon]]

All official release aircraft can now be individually downloaded and updated with FlightGear itself. This is a nice way to browse new aircraft and make sure your favorites are always kept up to date.

=== Aircraft development ===
The [[FGAddon]] version controlled repository contains in-development aircraft as well as aircraft tagged for FlightGear 3.4 and higher stable releases.

* {{fgaddon aircraft source|text=FGAddon Hangar}} The Subversion version controlled repository for the official FlightGear aircraft on the SourceForge infrastructure, see [[FGAddon]] for details.
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} The Gitorious archive of the official aircraft, migrated to the [https://archive.org/ Internet Archive] for archival and history preservation purposes. Aircraft were migrated to [[FGAddon]] in September 2014. For further details see the [[FlightGear Newsletter September 2014#Aircraft moved to SVN|September 2014 newsletter announcement]] and the [http://forum.flightgear.org/viewtopic.php?f=28&t=24045 announcement topic on the forum]

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Livery Database]

== Third party sites ==
=== Aircraft catalogues ===
If a hangar provides a [[hangar catalog|catalog URL]] file (catalog.xml), it can be added to the FlightGear QtLauncher to display all the aircraft of that hangar. See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.

=== Aircraft hangars ===
These are links where you can download individual planes manually.

{| class="wikitable sortable"
|-
! Hangar
! Description
! [[Hangar catalog|Catalog URL]]
|-
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar]
| With U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships and ZF free balloon and additional craft at [http://github.com/andgi?tab=repositories Anders' aircraft repositories at GitHub].
|
|-
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.
|
|-
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (& a YASim intro).
|
|-
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]
| Finished aircraft will be uploaded to FGAddon.
|
|-
| [http://www.daveshangar.org/ Dave's Hangar]
|
| [http://www.daveshangar.org/catalog.xml catalog.xml]
|-
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]
| Developing Pipistrel aircraft.
|
|-
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. 
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]
|-
| [http://fguk.me/hangar/ FlightGear UK - FGUK hangar]
| UK based group improving, mainly European, aircraft and scenery for FG. Weekly MP FlightNights. Over 60 Open Source aircraft so far. [http://www.fguk.me/forum/ Friendly community forum]
|
|-
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.
|
|-
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]
| Aermacchi MB339 Frecce Tricolori.
|
|-
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].
|
|-
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]
| Scenarios, skins, film inspired aerospace vehicles.
|
|-
| [https://github.com/HerbyW HerbyW Hanger]
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]
|-
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]
| Misc. projects.
|
|-
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]
| Spanish site.
|
|-
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
|
|-
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
|
|
|-
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]
|-
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]
| JA-37, scenario.
|
|-
| [http://marc-kraus.de/ Lake of Constance Hangar]
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.
|
|-
| [http://longfly.square7.ch Longfly's hangar]
|
|
|-
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]
|
|
|-
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]
| [[Tupolev Tu-144|Tu-144D]].
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]
|-
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]
| Blog, CRJ-200.
|
|-
| [http://opredflag.com/ Operation Red Flag Hangar]
| Flightgear Flight Sim Military Community
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]
|-
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...
|
|-
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures...
|
|-
| [http://presteshangar.wikidot.com/start Prestes Hangar]
| Many Brazilian aircraft articles.
|
|-
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]
| BN-2 Islander, Giant Marshmallow Man.
|
|-
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]
| Models & liveries.
|
|-
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
| Newest bluebird version.
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]
|-
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]
| Newer 2.0 versions.
|
|-
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]
| A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.
|
|-
| [http://vicmar.weebly.com/ VicMar]
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.
|
|-
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]
| Douglas DC-8.
|
|}

=== Old Hangars ===
* <s>[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]</s>
* <s>{{gitorious source|text=Airbus Aircraft Development Git}}</s>{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under <code>airbus-aircraft</code>)
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)
* <s>[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]</s>{{dead link|2015-09}} (Classic aircraft)
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)
* <s>[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]</s>{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)
* <s>[http://theomegahangar.flymerlion.org/ Omega Hangar]</s>{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* <s>[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]</s>{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)

=== Livery/Scenery hangars ===
* <s>[http://AAliveries.yolasite.com/ AA Liveries]</s>{{dead link|2015-01}} Another livery site
* [http://berwickskins.yolasite.com/ Berwick-skins]
* <S>[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]</s> (dead link as of 1/2/2017)
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new & updated airports 2016-10
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)

=== Other FlightGear repositories/mirrors ===
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
* <s> [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) </s> {{dead link|2018-06}}

== Related content ==
* [[Table of models]]
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]

== References ==
{{Appendix}}

[[Category:Lists]]
[[ca:Hangars de FlightGear]]
[[es:Hangares_Flightgear]]
[[fr:FlightGear hangars]]

FlightGear Newsletter January 2018

2018-01-31T14:22:59Z

Avionyx: /* Aérospatiale SA 315B Lama */

{{Newsletter-header|January 2018}}
{{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 ==



=== Docker-based scenery toolchain ===
[[File:Docker-sourceforge.png|thumb|screenshot showing sourceforge header with new docker entry]]
Torsten has recently been working on preparing and running Docker-containers for the scenery toolchain. The jenkins server responsible for maintaining the terrasync data at https://scenery.flightgear.org/jenkins/ already does some tasks within containers.

The jenkins instance itself will move into a container soon. Torsten also created a Docker image for terragear to make its usage a lot easier. The short term goal is to get all the tools required to run the scenemodels database with its web frontend, the terrasync upstream data maintenance into containers, hoping to be able to run this entire chain at any public or private cloud.

A mid term goal might be to have terragear running from Jenkins on automatically-provisioned virtual machines whenever a new scenery set needs to be rebuilt. There is still a lot to do before this becomes reality and a docker swarm or kubernetes cluster generates scenery for us regulary.

As all journeys starts with the first step, Torsten is happy to announce the public docker repository for our images and the git repository for the config files behind:

* Our official docker hub repository is at: https://hub.docker.com/u/flightgear/
* The backing Dockerfiles live at: https://sourceforge.net/p/flightgear/docker/

Anybody interested in driving this forward, willing to learn or contribute is more than welcome to do so. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36206523/
|title = <nowiki> [Flightgear-devel] Making containers fly: FlightGear scenery goes
docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 27th, 2018
|added = Jan 27th, 2018
|script_version = 0.36
}}</ref>

The Docker image is now capable of performing almost all tasks required for building scenery:
* Fetch SRTM elevation data
* Run hgtchop
* Run terrafit
* Fetch airports and stay in sync with the x-plane gateway
* Run ogr-decode against local shapefiles or perform direct queries to a postgres database

Torsten has sucessfully created the elevation data from SRTM1/3 for the entire globe and created a few random airports with this image. Currently, he is playing with integrating ogr-decode. The docker image gets automatically built, including building latest simgear & terragear from GIT. This build process runs directly at the docker hub: https://hub.docker.com/r/flightgear/terragear/builds/ (Yes: docker hub compiles simgear and terragear for us, amazing, isn't it?) Torsten hopes to be able to compile the a first chunk of scenery within the next couple of weeks.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209739/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

That means, if someone wants to generate scenery in the future they will simply be able to download the latest docker image, start it up on Docker CE and run the commands. No compilation required. Which is quite amaing, and could massively reduce the effort required to work on scenery.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209758/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Stuart Buchanan </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

In other words, Build once, run anywhere - thats what docker is made for. (caveat: anywhere means "any Linux flavor or MacOS on x86-64 architecture and eventually Windows64, too.)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209773/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

=== Oscilloscope Addon ===
[[File:Rleibner-canvas-vsd-12-2017.png|thumb|rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below).For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref>]]
rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below).
For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref>
[[File:Oscilloscope.png|thumb|rleibner's new Oscilloscope addon is working.This screenshot shows the usual c172p "magnetos checking" Channel 1 (yellow) is '''rpm''' (100 rpm / div).Channel 2 (mauve) is '''magnetos''' (1 / div).Time sweep is 200 ms / div.The idea is to share it as an addon. Mainly to have some feedback about plot2D/graph.<ref>{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=325929#p325929 |title = <nowiki> Re: Plot2D and graph helpers </nowiki> |author = <nowiki> rleibner </nowiki> |date = Jan 6th, 2018 |added = Jan 6th, 2018 |script_version = 0.36 }}</ref>]]

=== Aircraft Dialogs ===
Some of you may already know that the current tool to generate the dialogs ([[PUI]]) is going to disappear in the mid-future. After some (partially controversial) discussion, there seems now to be some support for the idea that canvas is a good tool to generate aircraft-specific dialogs in the future (as it allows to tailor the dialog closely to the plane and also, canvas being canvas, the UI can smoothly mesh with the 3d models, so you can project a canvas checklist onto a 3d model in sim for instance rather than a popup window).

Thorsten would very much like to claim to be pioneering this approach, but in fact he believes the [[Extra EA-500|Extra-500 team]] is - look at the [[Extra_EA-500/failure_dialog|failure dialog of that plane]] where you can click the components you want to fail and you see what he means!

[[File:Extra500-Failuredialog-deice.png|right|thumb|500px|Extra 500 - failure dialog - de-ice]]

Anyway, Thorsten has started to roll out a few designs of his own and try to keep the tools fairly general so that they can be re-used by others- so here's the revised version of the Shuttle propellant dialog.

[[File:Propellant dlg02.jpg|thumb|right|an example of the detail dialog which allows to set levels of fuel and oxidizer separately (and the overview dialog shows the usable propellant then, i.e. the minimum of the two) - for aircraft, this would be somewhat simpler.]]

The general idea is to use semi-transparent 'content gauges' on a background raster image to show where the tank is located and how full it currently is - double-clicking any tank will bring up a detail window which allows to set the content (here propellant and oxidier separately, this is rocket fuel...) and also shows the current tank pressures and temperatures.
The whole thing can readily be applied on top of a different raster image with a different number of tanks - you just instance and position the labels and 'gauges' you need - in fact placement is probably what's going to take longest (at least for me).
The whole thing is currently in flux <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=326789&sid=c15d338facab18fb091aa0530f5dfa0f#p326789
|title = <nowiki> Aircraft-specific dialogs </nowiki>
|author = <nowiki> Thorsten </nowiki>
|date = Jan 24th, 2018
|added = Jan 24th, 2018
|script_version = 0.36
}}</ref>
If anyone wants to follow the development or use the code, it's here:
https://sourceforge.net/p/fgspaceshuttledev/code/ci/development/tree/Nasal/canvas/canvas_dialogs.nas

=== FG1000 Updates ===
[[File:Fg1000 mfd.jpg|thumb|PUI-canvas FG1000 early prototype using PUI dialog to speed up development]]

Stuart has been doing some further work on the FG1000 implementation over the christmas break 2017. Key changes are:

# Using Richard's [[Emesary]] IPC frame to link between the MFD and underlying simulation state. This should make it easy to run the MFD on a separate FG instance, and provides a good demarkation between the individual aircraft systems and the FG1000 itself.
# Create various underlying classes to support UI features - highlighting, editing. The idea here is that one can create the UI as an SVG file, and these are used to control it. For an example of this in use, see the Airport Information page. Press the CRSR knob to create a cursor on the ICAO airport ID, then use the inside FMS knob to start editing the ID. This should make creating most of the rest of the pages far easier. See [[Canvas MFD Framework]] for details of the elements now supported.

There's still a huge number of pages to write, and the pages around route planning will likely be particular "fun", but it should be far faster now these blocks are in place.

The [[FG1000]] wiki page shows the pages that have been created so far (4 out of 28!). Stuart is pretty happy with the overall architecture now, so if anyone wants to create some of the pages they are very welcome to do so!<ref>{{cite web |url = https://sourceforge.net/p/flightgear/mailman/message/36179339/ |title = <nowiki> Re: [Flightgear-devel] FG1000 Status Update </nowiki> |author = <nowiki> Stuart Buchanan </nowiki> |date = Jan 5th, 2018 |added = Jan 5th, 2018 |script_version = 0.36 }}</ref>

You can access it from the Debug menu. All the buttons and knobs are set up, though some of them don't actually do anything!
See the Garmin website for documentation, but for a quick cheat's guide:

* Use the outer FMS knob (shift-mouse wheel on the FMS knob on the bottom right) to navigate through the page groups.
* Use the inner FMS knob (mouse wheel on the FMS knob on the bottom right) to navigate through the pages within the group.
* To moved around the page, click on the FMS knob, and then use the FMS knob to navigate around the page.
* Press ENT when any frequency is highlighted to load it into the standby frequency of the NAV/COM.

<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=326383&sid=3bf022788187248462943dc0bf1a47ba#p326383
|title = <nowiki> Re: Canvas G1000 </nowiki>
|author = <nowiki> stuart </nowiki>
|date = Jan 14th, 2018
|added = Jan 14th, 2018
|script_version = 0.36
}}</ref>

Learn more at [[FG1000]] ...

=== Airbus GPWS ===
FlightGear now provides better [[GPWS]] support for Airbus aircraft - the unit which triggers voice alerts like "''Pull up!''" and altitude callouts ''...50-40-30-20-10''. The original FlightGear GPWS implementation was made to exactly match all details of a specific real-world hardware unit. The specific unit was never intended to be installed on Airbus aircraft, hence, so far lacked the Airbus-specific warnings and callouts.

Starting with FG2018.1, the FlightGear GPWS unit was extended with optional support for Airbus callouts. The short description of how to enable the Airbus mode is: set the "category-4" configuation value in the "mk-viii" section of the aircraft's "...-set.xml" file to "1000". The long and detailed description is: read the [[GPWS#Altitude_Callouts|Wiki page]]. :-) You can also improve the realism of the unit by providing more realistic Airbus-style voice samples (.wav files).

'''So, what's different with an Airbus GPWS then?'''

While some callouts may depend on an airline's company policy, there's usually several voice alerts specific to Airbus, which are not to be heard on a Boeing aircraft.

* '''2500'''!: When landing with an Airbus, you'll hear the first GPWS altitude announcement earlier - starting with an early "''2500''" callout when descending below 2500ft.
* '''Hundred above!''': An additional "''Hundred above!''" callout is issued at 100ft above the ''selected decision height''. The decision height is the altitude where the crew needs to make their final decision whether to continue with the approach or whether they need to abort due to bad visibility. The "''Hundred above!''" callout gives an Airbus crew some extra time to make up their minds. Seconds later, the actual decision height is then announced by the "Minimums!" callout - which is also common with Boeing and many other aircraft.
* '''Retard! Retard! Retard!''': Retard? Well, yes. This is the infamous Airbus-specific callout which has caused thousands of teenagers to leave more or less funny comments and questions on YouTube Airbus cockpit videos. The "''Retard!''" callout is triggered, when an Airbus decends below 20-30ft above the runway and the thrust-levers are not yet set to idle. The callouts reminds the crew to "''Retard the thrust-levers '''now'''!''". So, why did Airbus decide to use the word "retard"? Well, since the engineers certainly didn't care about teenage YouTube comments. Instead, they needed to find a word which is short and also uniquely connected to a thrust-lever. Something like "''Pull the thrust-levers all the way back to idle now!''" would have been far to long - and also "''pull''" is already associated with the yoke/stick (remember the "''Pull up! Pull up!''" alert). "Retard" is nice and short - and certainly not connected with any other control input. So, on an Airbus, you simply "''retard the thrust-levers to idle''" just before landing the aircraft...

== New software tools and projects ==
Sidi has updated the iOS version of FGYoke and make it available on AppStore recently.
For details, check [[Yoke_for_FlightGear]]
[[File:Screenshot of FGYoke in AppStore.png|thumbnail|center|Screenshot of FGYoke in AppStore]]



== In the hangar ==




=== New aircraft ===

=== Aérospatiale SA 315B Lama ===
[[File:Lama Sunset.png|thumb|Screenshot of Lama 315B at sunset]]
[[File:Lama Overhead.png|thumb|Overhead panel for SA 315B Lama]]
The FGUK Development team are very pleased to announce the '''Aérospatiale SA 315B Lama''' for FlightGear. An incredibly accurate model with a selection of liveries, equipment loadouts and a totally custom FDM for flying by the book

More photos on the [https://www.facebook.com/FlightGearUK/ FGUK Facebook Page]

[http://www.http://fguk.eu/index.php/hangar/download/13-rotary-wing/558-aerospatiale-sa-315b-lama Download here]







== AI ==

== 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 Google+ ===
Since November 2011 there is a [https://plus.google.com/+flightgear FlightGear page on Google+]. If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

== 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 ====
FlightGear's Screenshot of the Month January 2017 is '''Flying high with the Lama''' by StuartC
[[File:SOTM-Jan18.jpg|900px|center|Flying high with the Lama - StuartC]]

If you want to participate in the screenshot contest of February 2018, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=33703 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=33703#p327123 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 edition of February 2018.

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

[[Category:FlightGear Newsletter|2018 01]]
[[Category:Changes after 2017.3]]
[[de:FlightGear Newsletter Januar 2018]]

File:Lama Sunset.png

2018-01-31T14:22:26Z

Avionyx: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Screenshot of Lama 315B at sunset}}
|date=2018-01-31
|source={{own}}
|author=[[User:Avionyx|Avionyx]]
|permission=
|other versions=
}}

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

[[Category:Aircraft]]

FlightGear Newsletter January 2018

2018-01-31T14:03:09Z

Avionyx: /* In the hangar */

{{Newsletter-header|January 2018}}
{{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 ==



=== Docker-based scenery toolchain ===
[[File:Docker-sourceforge.png|thumb|screenshot showing sourceforge header with new docker entry]]
Torsten has recently been working on preparing and running Docker-containers for the scenery toolchain. The jenkins server responsible for maintaining the terrasync data at https://scenery.flightgear.org/jenkins/ already does some tasks within containers.

The jenkins instance itself will move into a container soon. Torsten also created a Docker image for terragear to make its usage a lot easier. The short term goal is to get all the tools required to run the scenemodels database with its web frontend, the terrasync upstream data maintenance into containers, hoping to be able to run this entire chain at any public or private cloud.

A mid term goal might be to have terragear running from Jenkins on automatically-provisioned virtual machines whenever a new scenery set needs to be rebuilt. There is still a lot to do before this becomes reality and a docker swarm or kubernetes cluster generates scenery for us regulary.

As all journeys starts with the first step, Torsten is happy to announce the public docker repository for our images and the git repository for the config files behind:

* Our official docker hub repository is at: https://hub.docker.com/u/flightgear/
* The backing Dockerfiles live at: https://sourceforge.net/p/flightgear/docker/

Anybody interested in driving this forward, willing to learn or contribute is more than welcome to do so. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36206523/
|title = <nowiki> [Flightgear-devel] Making containers fly: FlightGear scenery goes
docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 27th, 2018
|added = Jan 27th, 2018
|script_version = 0.36
}}</ref>

The Docker image is now capable of performing almost all tasks required for building scenery:
* Fetch SRTM elevation data
* Run hgtchop
* Run terrafit
* Fetch airports and stay in sync with the x-plane gateway
* Run ogr-decode against local shapefiles or perform direct queries to a postgres database

Torsten has sucessfully created the elevation data from SRTM1/3 for the entire globe and created a few random airports with this image. Currently, he is playing with integrating ogr-decode. The docker image gets automatically built, including building latest simgear & terragear from GIT. This build process runs directly at the docker hub: https://hub.docker.com/r/flightgear/terragear/builds/ (Yes: docker hub compiles simgear and terragear for us, amazing, isn't it?) Torsten hopes to be able to compile the a first chunk of scenery within the next couple of weeks.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209739/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

That means, if someone wants to generate scenery in the future they will simply be able to download the latest docker image, start it up on Docker CE and run the commands. No compilation required. Which is quite amaing, and could massively reduce the effort required to work on scenery.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209758/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Stuart Buchanan </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

In other words, Build once, run anywhere - thats what docker is made for. (caveat: anywhere means "any Linux flavor or MacOS on x86-64 architecture and eventually Windows64, too.)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36209773/
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery
goes docker </nowiki>
|author = <nowiki> Torsten Dreyer </nowiki>
|date = Jan 30th, 2018
|added = Jan 30th, 2018
|script_version = 0.36
}}</ref>

=== Oscilloscope Addon ===
[[File:Rleibner-canvas-vsd-12-2017.png|thumb|rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below).For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref>]]
rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below).
For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref>
[[File:Oscilloscope.png|thumb|rleibner's new Oscilloscope addon is working.This screenshot shows the usual c172p "magnetos checking" Channel 1 (yellow) is '''rpm''' (100 rpm / div).Channel 2 (mauve) is '''magnetos''' (1 / div).Time sweep is 200 ms / div.The idea is to share it as an addon. Mainly to have some feedback about plot2D/graph.<ref>{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=325929#p325929 |title = <nowiki> Re: Plot2D and graph helpers </nowiki> |author = <nowiki> rleibner </nowiki> |date = Jan 6th, 2018 |added = Jan 6th, 2018 |script_version = 0.36 }}</ref>]]

=== Aircraft Dialogs ===
Some of you may already know that the current tool to generate the dialogs ([[PUI]]) is going to disappear in the mid-future. After some (partially controversial) discussion, there seems now to be some support for the idea that canvas is a good tool to generate aircraft-specific dialogs in the future (as it allows to tailor the dialog closely to the plane and also, canvas being canvas, the UI can smoothly mesh with the 3d models, so you can project a canvas checklist onto a 3d model in sim for instance rather than a popup window).

Thorsten would very much like to claim to be pioneering this approach, but in fact he believes the [[Extra EA-500|Extra-500 team]] is - look at the [[Extra_EA-500/failure_dialog|failure dialog of that plane]] where you can click the components you want to fail and you see what he means!

[[File:Extra500-Failuredialog-deice.png|right|thumb|500px|Extra 500 - failure dialog - de-ice]]

Anyway, Thorsten has started to roll out a few designs of his own and try to keep the tools fairly general so that they can be re-used by others- so here's the revised version of the Shuttle propellant dialog.

[[File:Propellant dlg02.jpg|thumb|right|an example of the detail dialog which allows to set levels of fuel and oxidizer separately (and the overview dialog shows the usable propellant then, i.e. the minimum of the two) - for aircraft, this would be somewhat simpler.]]

The general idea is to use semi-transparent 'content gauges' on a background raster image to show where the tank is located and how full it currently is - double-clicking any tank will bring up a detail window which allows to set the content (here propellant and oxidier separately, this is rocket fuel...) and also shows the current tank pressures and temperatures.
The whole thing can readily be applied on top of a different raster image with a different number of tanks - you just instance and position the labels and 'gauges' you need - in fact placement is probably what's going to take longest (at least for me).
The whole thing is currently in flux <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=326789&sid=c15d338facab18fb091aa0530f5dfa0f#p326789
|title = <nowiki> Aircraft-specific dialogs </nowiki>
|author = <nowiki> Thorsten </nowiki>
|date = Jan 24th, 2018
|added = Jan 24th, 2018
|script_version = 0.36
}}</ref>
If anyone wants to follow the development or use the code, it's here:
https://sourceforge.net/p/fgspaceshuttledev/code/ci/development/tree/Nasal/canvas/canvas_dialogs.nas

=== FG1000 Updates ===
[[File:Fg1000 mfd.jpg|thumb|PUI-canvas FG1000 early prototype using PUI dialog to speed up development]]

Stuart has been doing some further work on the FG1000 implementation over the christmas break 2017. Key changes are:

# Using Richard's [[Emesary]] IPC frame to link between the MFD and underlying simulation state. This should make it easy to run the MFD on a separate FG instance, and provides a good demarkation between the individual aircraft systems and the FG1000 itself.
# Create various underlying classes to support UI features - highlighting, editing. The idea here is that one can create the UI as an SVG file, and these are used to control it. For an example of this in use, see the Airport Information page. Press the CRSR knob to create a cursor on the ICAO airport ID, then use the inside FMS knob to start editing the ID. This should make creating most of the rest of the pages far easier. See [[Canvas MFD Framework]] for details of the elements now supported.

There's still a huge number of pages to write, and the pages around route planning will likely be particular "fun", but it should be far faster now these blocks are in place.

The [[FG1000]] wiki page shows the pages that have been created so far (4 out of 28!). Stuart is pretty happy with the overall architecture now, so if anyone wants to create some of the pages they are very welcome to do so!<ref>{{cite web |url = https://sourceforge.net/p/flightgear/mailman/message/36179339/ |title = <nowiki> Re: [Flightgear-devel] FG1000 Status Update </nowiki> |author = <nowiki> Stuart Buchanan </nowiki> |date = Jan 5th, 2018 |added = Jan 5th, 2018 |script_version = 0.36 }}</ref>

You can access it from the Debug menu. All the buttons and knobs are set up, though some of them don't actually do anything!
See the Garmin website for documentation, but for a quick cheat's guide:

* Use the outer FMS knob (shift-mouse wheel on the FMS knob on the bottom right) to navigate through the page groups.
* Use the inner FMS knob (mouse wheel on the FMS knob on the bottom right) to navigate through the pages within the group.
* To moved around the page, click on the FMS knob, and then use the FMS knob to navigate around the page.
* Press ENT when any frequency is highlighted to load it into the standby frequency of the NAV/COM.

<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=326383&sid=3bf022788187248462943dc0bf1a47ba#p326383
|title = <nowiki> Re: Canvas G1000 </nowiki>
|author = <nowiki> stuart </nowiki>
|date = Jan 14th, 2018
|added = Jan 14th, 2018
|script_version = 0.36
}}</ref>

Learn more at [[FG1000]] ...

=== Airbus GPWS ===
FlightGear now provides better [[GPWS]] support for Airbus aircraft - the unit which triggers voice alerts like "''Pull up!''" and altitude callouts ''...50-40-30-20-10''. The original FlightGear GPWS implementation was made to exactly match all details of a specific real-world hardware unit. The specific unit was never intended to be installed on Airbus aircraft, hence, so far lacked the Airbus-specific warnings and callouts.

Starting with FG2018.1, the FlightGear GPWS unit was extended with optional support for Airbus callouts. The short description of how to enable the Airbus mode is: set the "category-4" configuation value in the "mk-viii" section of the aircraft's "...-set.xml" file to "1000". The long and detailed description is: read the [[GPWS#Altitude_Callouts|Wiki page]]. :-) You can also improve the realism of the unit by providing more realistic Airbus-style voice samples (.wav files).

'''So, what's different with an Airbus GPWS then?'''

While some callouts may depend on an airline's company policy, there's usually several voice alerts specific to Airbus, which are not to be heard on a Boeing aircraft.

* '''2500'''!: When landing with an Airbus, you'll hear the first GPWS altitude announcement earlier - starting with an early "''2500''" callout when descending below 2500ft.
* '''Hundred above!''': An additional "''Hundred above!''" callout is issued at 100ft above the ''selected decision height''. The decision height is the altitude where the crew needs to make their final decision whether to continue with the approach or whether they need to abort due to bad visibility. The "''Hundred above!''" callout gives an Airbus crew some extra time to make up their minds. Seconds later, the actual decision height is then announced by the "Minimums!" callout - which is also common with Boeing and many other aircraft.
* '''Retard! Retard! Retard!''': Retard? Well, yes. This is the infamous Airbus-specific callout which has caused thousands of teenagers to leave more or less funny comments and questions on YouTube Airbus cockpit videos. The "''Retard!''" callout is triggered, when an Airbus decends below 20-30ft above the runway and the thrust-levers are not yet set to idle. The callouts reminds the crew to "''Retard the thrust-levers '''now'''!''". So, why did Airbus decide to use the word "retard"? Well, since the engineers certainly didn't care about teenage YouTube comments. Instead, they needed to find a word which is short and also uniquely connected to a thrust-lever. Something like "''Pull the thrust-levers all the way back to idle now!''" would have been far to long - and also "''pull''" is already associated with the yoke/stick (remember the "''Pull up! Pull up!''" alert). "Retard" is nice and short - and certainly not connected with any other control input. So, on an Airbus, you simply "''retard the thrust-levers to idle''" just before landing the aircraft...

== New software tools and projects ==
Sidi has updated the iOS version of FGYoke and make it available on AppStore recently.
For details, check [[Yoke_for_FlightGear]]
[[File:Screenshot of FGYoke in AppStore.png|thumbnail|center|Screenshot of FGYoke in AppStore]]



== In the hangar ==




=== New aircraft ===

=== Aérospatiale SA 315B Lama ===
[[File:Lama Overhead.png|thumb|Overhead panel for SA 315B Lama]]
The FGUK Development team are very pleased to announce the '''Aérospatiale SA 315B Lama''' for FlightGear. An incredibly accurate model with a selection of liveries, equipment loadouts and a totally custom FDM for flying by the book

More photos on the [https://www.facebook.com/FlightGearUK/ FGUK Facebook Page]

[http://www.http://fguk.eu/index.php/hangar/download/13-rotary-wing/558-aerospatiale-sa-315b-lama Download here]







== AI ==

== 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 Google+ ===
Since November 2011 there is a [https://plus.google.com/+flightgear FlightGear page on Google+]. If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

== 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 ====
FlightGear's Screenshot of the Month January 2017 is '''Flying high with the Lama''' by StuartC
[[File:SOTM-Jan18.jpg|900px|center|Flying high with the Lama - StuartC]]

If you want to participate in the screenshot contest of February 2018, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=33703 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=33703#p327123 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 edition of February 2018.

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

[[Category:FlightGear Newsletter|2018 01]]
[[Category:Changes after 2017.3]]
[[de:FlightGear Newsletter Januar 2018]]

File:Lama Overhead.png

2018-01-31T14:02:16Z

Avionyx: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Overhead panel for SA 315B Lama}}
|date=2018-01-31
|source={{own}}
|author=[[User:Avionyx|Avionyx]]
|permission=
|other versions=
}}

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

[[Category:Aircraft]]

FlightGear Newsletter

2017-01-04T08:43:14Z

Avionyx: added December as the currently being written issue

[[File:magagazine.png|right]]

The '''FlightGear Newsletter''' is intended to provide a collection of the latest developments from the worldwide [[FlightGear]] community. With so much development ongoing, it's almost impossible for anyone to keep up. The newsletter was started in July 2009, and is presented on a monthly basis. It is a collaborative effort that is created, edited and distributed via the [[FlightGear Wiki]], and all FlightGear users, contributors and developers are invited to contribute.

=== Archive ===
{| class="prettytable"
! align="left" | 2009
! align="left" | 2010
! align="left" | 2011
! align="left" | 2012
! align="left" | 2013
! align="left" | 2014
! align="left" | 2015
! align="left" | 2016
|-
| valign="bottom" |
* [[FlightGear Newsletter July 2009|July]]
* [[FlightGear Newsletter August 2009|August]]
* [[FlightGear Newsletter September 2009|September]]
* [[FlightGear Newsletter October 2009|October]]
* [[FlightGear Newsletter November 2009|November]]
* [[FlightGear Newsletter December 2009|December]]
| valign="top" |
* [[FlightGear Newsletter January 2010|January]]
* [[FlightGear Newsletter February 2010|February]]
* [[FlightGear Newsletter March 2010|March]]
* [[FlightGear Newsletter April 2010|April]]
* [[FlightGear Newsletter May 2010|May]]
* [[FlightGear Newsletter June 2010|June]]
* [[FlightGear Newsletter July 2010|July]]
* [[FlightGear Newsletter August 2010|August]]
* [[FlightGear Newsletter September 2010|September]]
* [[FlightGear Newsletter October 2010|October]]
* [[FlightGear Newsletter November 2010|November]]
* [[FlightGear Newsletter December 2010|December]]
| valign="top" |
* [[FlightGear Newsletter January 2011|January]]
* [[FlightGear Newsletter February 2011|February]]
* [[FlightGear Newsletter March 2011|March]]
* [[FlightGear Newsletter April 2011|April]]
* [[FlightGear Newsletter May 2011|May]]
* [[FlightGear Newsletter June 2011|June]]
* [[FlightGear Newsletter July 2011|July]]
* [[FlightGear Newsletter August 2011|August]]
* [[FlightGear Newsletter September 2011|September]]
* [[FlightGear Newsletter October 2011|October]]
* [[FlightGear Newsletter November 2011|November]]
* [[FlightGear Newsletter December 2011|December]]
| valign="top" |
* [[FlightGear Newsletter January 2012|January]]
* [[FlightGear Newsletter February 2012|February]]
* [[FlightGear Newsletter March 2012|March]]
* [[FlightGear Newsletter April 2012|April]]
* [[FlightGear Newsletter May 2012|May]]
* [[FlightGear Newsletter June 2012|June]]
* [[FlightGear Newsletter July 2012|July]]
* [[FlightGear Newsletter August 2012|August]]
* [[FlightGear Newsletter September 2012|September]]
* [[FlightGear Newsletter October 2012|October]]
* [[FlightGear Newsletter November 2012|November]]
* [[FlightGear Newsletter December 2012|December]]
| valign="top" |
* [[FlightGear Newsletter January 2013|January]]
* [[FlightGear Newsletter February 2013|February]]
* [[FlightGear Newsletter March 2013|March]]
* [[FlightGear Newsletter April 2013|April]]
* [[FlightGear Newsletter May 2013|May]]
* [[FlightGear Newsletter June 2013|June]]
* [[FlightGear Newsletter July 2013|July]]
* [[FlightGear Newsletter August 2013|August]]
* [[FlightGear Newsletter September 2013|September]]
* [[FlightGear Newsletter October 2013|October]]
* [[FlightGear Newsletter November 2013|November]]
* [[FlightGear Newsletter December 2013|December]]
| valign="top" |
* [[FlightGear Newsletter January 2014|January]]
* [[FlightGear Newsletter February 2014|February]]
* [[FlightGear Newsletter March 2014|March]]
* [[FlightGear Newsletter April 2014|April]]
* [[FlightGear Newsletter May 2014|May]]
* [[FlightGear Newsletter June 2014|June]]
* [[FlightGear Newsletter July 2014|July]]
* [[FlightGear Newsletter August 2014|August]]
* [[FlightGear Newsletter September 2014|September]]
* [[FlightGear Newsletter October 2014|October]]
* [[FlightGear Newsletter November 2014|November]]
* [[FlightGear Newsletter December 2014|December]]
| valign="top" |
* [[FlightGear Newsletter January 2015|January]]
* [[FlightGear Newsletter February 2015|February]]
* [[FlightGear Newsletter March 2015|March]]
* [[FlightGear Newsletter April 2015|April]]
* [[FlightGear Newsletter May 2015|May]]
* [[FlightGear Newsletter June 2015|June]]
* [[FlightGear Newsletter July 2015|July]]
* [[FlightGear Newsletter August 2015|August]]
* [[FlightGear Newsletter September 2015|September]]
* [[FlightGear Newsletter October 2015|October]]
* [[FlightGear Newsletter November 2015|November]]
* [[FlightGear Newsletter December 2015|December]]
| valign="top" |
* [[FlightGear Newsletter January 2016|January]]
* [[FlightGear Newsletter February 2016|February]]
* [[FlightGear Newsletter March 2016|March]]
* [[FlightGear Newsletter April 2016|April]]
* [[FlightGear Newsletter May 2016|May]]
* [[FlightGear Newsletter June 2016|June]]
* [[FlightGear Newsletter July 2016|July]]
* [[FlightGear Newsletter August 2016|August]]
* [[FlightGear Newsletter September 2016|September]]
* [[FlightGear Newsletter October 2016|October]]
* [[FlightGear Newsletter November 2016|November]]
* [[FlightGear Newsletter December 2016|December]] – ''Currently being written''
|}

Some newsletter editions have been translated in other languages:
* [[File:De.gif|16px|link=:De:FlightGear Newsletter]] [[:De:FlightGear Newsletter|Deutsch]]
* [[File:Es.gif|16px|link=:Es:FlightGear Newsletter]] [[:Es:FlightGear Newsletter|Español]]
* [[File:Fr.gif|16px|link=:Fr:FlightGear Newsletter]] [[:Fr:FlightGear Newsletter|Français]]

=== You are invited to contribute! ===
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. The FlightGear Newsletter is a community-driven newsletter, which means that it is created and edited by people like ''you''. You don't need to be a long-time FlightGear user (or even a developer) to contribute to the newsletter.

In fact, helping write the monthly FlightGear newsletter is an excellent way for getting started contributing to the FlightGear community very quickly and very easily.

Even if you don't have to add anything yourself, just reviewing and improving additions by others is also highly appreciated, as are efforts to help translate newsletters or add screen shots (e.g. taken from the forum or mailing lists) to the newsletter. Screen shots can be uploaded at [[Special:Upload]].

Everyone with a wiki account (free to [[Special:UserLogin|register]]) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.

A simple template providing a basic structure for each upcoming newsletter can be taken from [[Talk:Next newsletter]]. This template can be copied/pasted into each new newsletter to help users getting started providing contents.

The draft for the upcoming newsletter can always be found at [[Next newsletter]].

If English is not your native language, please don't be concerned about contributing to the newsletter, you can always easily ask fellow FlightGear users to review or proof-read your changes. Also, one of the easiest ways to get started is simply copying/pasting text from forum or mailing list discussions, such as announcements (e.g., new aircraft, new scenery, etc.).

Another neat option to get started is adding links to FlightGear-related YouTube videos. For this, we have a dedicated section in each newsletter: "[[FlightGear Newsletter {{#time: F Y | last month }}#FlightGear on YouTube|FlightGear on YouTube]]."

If you want to embed a video, please see {{mediawiki|Extension:EmbedVideo#Usage}}

If you are looking for other ways to get involved, please see [[Volunteer]].

[[Category:FlightGear Newsletter]]
[[Category:Community|Newsletter]]
[[Category:Lists|Newsletter]]

[[de:FlightGear Newsletter]]
[[es:FlightGear Newsletter]]
[[fr:FlightGear Newsletter]]

FlightGear Newsletter December 2016

2016-12-30T14:40:02Z

Avionyx: /* In the hangar */

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter November 2016]].}}

{{Newsletter-header|December 2016}}
<div style="border-bottom: 3px double #BBB">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-header|In the hangar}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
[[#Article on FlightSim.com|Article on FlightSim.com]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== Development news ==

=== ALS chute animation effect ===

The ALS effect suite has been expanded by an animation effect for parachutes. The effect simulates the deformation of a round parachute under stresses. The chute changes form and behavior dependent on how much drag it supplies, and can even be made to go through a plausible series of motions when jettisoned.

[[File:Chute seq01.jpg|400px|Drag chute separation sequence 1]] [[File:Chute seq03.jpg|400px|Drag chute separation sequence 2]]

[[ ALS_technical_notes#Chute_animation_effect | Read more...]] on the ALS effect wiki page.

=== ALS model shader options for glossy surfaces ===

The model shader has some issues with preserving the colors when using environment reflections. In particular, a white glossy fuselage might appear grey when adding reflections (left). Using the new 'grain merge' option, the color can be preserved much better (right).

[[File:Reflect model default.jpg|400px|Effect of color mixing in a reflection]]
[[File:Reflect grain merge.jpg|400px|Effect of grain merge in reflection]]

In addition, the reflection has been augmented by a small-angle configurable Fresnel enhancement.

[[ ALS_technical_notes#Glossy_surfaces | Read more...]] on the ALS effect wiki page.

== In the hangar ==

=== Aérospatiale / Westland Gazelle ===
The FGUK Development team are absolutely ecstatic to be able to announce the release of our Gazelle for FlightGear. Encompassing not only the Westland but also the Aerosptiale models with the differences modelled between them this is a real delight for anyone with an interest in these fantastic helicopters.

[http://www.fguk.eu/index.php/hangar/download/13-rotary-wing/252-aerospatiale-westland-gazelle DOWNLOAD HERE: FGUK Download Hangar - Gazelle]

'''Preview video:-'''

https://youtu.be/aog0ZqMbDlc

[[File:Gazellev1.jpg|thumb|Flight Gear Gazelle V1.0]]

''''RELEASE NOTES:-''''

'''V1.0'''

*Extensive FDM rework to provide a more realistic Gazelle flight performance.
*Cockpit textures reworked.
*Both versions have realistic flight instruments. Westland version is based on the British Armed forces version.
*Light switches now located on the Main panel. landing light switch is located on the Collective.
*Collective, Cyclic, Pedals, Rotor brake and Engine power lever all animated.
*Manual start / shut down possible ( see help file ).
*Both support Multiplayer passenger modes so you can take your friends for a flight.
*All cabin doors are animated ( Click to open / close )
*Updated sound pack.
*Configuration options. Westland has the Military kit option, the Aérospatiale has Onions ( try the onions ! )

17 Liveries available between both versions

Browser based Help file available in the "Gazelle" menu option in sim.

More photos on the [https://www.facebook.com/FlightGearUK/ Flight Gear UK Facebook Page]

=== Bobcat Volanti ===
[[Bobcat Volanti]] has been released. It is a fictional helicopter and body is based off GTA Vice City '''Bobcat'''.

[[File:Bobcat Volanti.jpg|400px|Bobcat Volanti]]

== Scenery corner ==

== Community news ==
=== Article on FlightSim.com ===
{{usr|Thorsten}} published a very [http://www.flightsim.com/vbfs/content.php?16990-FlightGear-s-Atmospheric-Light-Scattering-Rendering-Framework interesting article] on [http://www.flightsim.com FlightSim.com] where he describes some features of [[Atmospheric light scattering]] like among others haze, sun phenomena, sunrise, aurora borealis and some aircraft effects. This article also shows some very beautiful screenshots which have been never published anywhere else.

== Contributing ==
=== Translators required ===
{|
| [[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]].
|}

=== 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 ====
Entries for this month's best screenshot can be submitted to [https://forum.flightgear.org/viewtopic.php?f=19&t=31149 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=31149#p300344 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 on this page.

 

 

[[Category:FlightGear Newsletter|2016 12]]
[[Category:Changes after 2016.4]]

[[de:FlightGear Newsletter Dezember 2016]]

File:Gazellev1.jpg

2016-12-30T14:38:31Z

Avionyx: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Flight Gear Gazelle V1.0}}
|date=2016-12-30
|source={{own}}
|author=[[User:Avionyx|Avionyx]]
|permission=
|other versions=
}}

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

Switching default texture format to DDS

2014-09-04T10:16:19Z

Avionyx: /* NVIDIA proprietary driver */

{{WIP}}

== Feedback needed - should Flightgear switch the defaults to dds format for terrain texturing? ==

=== What is this about? ===

The FG development team is considering to switch the format for terrain textures from png to dds. This would offer a number of significant advantages:

* dds is a compressed format, hence the download size of the FG base package may be decreased
* compressed dds can be directly used by many graphics cards, reducing also GPU memory consumption
* dds stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory
* the resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost

Practically all commercial simulations use dds for these reasons.

However, the dds compression algorithm is patented, which means that it is not readily available for OpenSource graphics drivers used by Linux distributions. Dependent on the specific hardware, this may or may not be a problem (modern graphics cards typically do not need the driver to process dds, for older graphics cards there are non-patented workarounds available which decompress the dds on the software level). The development team is concerned about making the Flightgear experience pleasant for all users, hence we would like to gather feedback how many users would be affected by a change in practice.

If there are no problems reported, FG will change defaults to txtures in dds format with the 3.4 release, and then phase out the use of png textures.

== What would we need? ==

Flightgear already provides the simple option to test a dds texture set. If you are running on Linux and use an OpenSource graphics driver, please take 5 minutes to help during your next FG session:

* Open the dialog under View -> Rendering

* Under 'Terrain texture scheme', change the default 'Region-specific' to 'Global alternative (DDS format)'

* Press 'Okay' - FG will reload the terrain

* Do you see proper textures on the terrain (they may look different and may also not fit the location perfectly)? If yes, you're fine. If you see monochromatic colors or other rendering artifacts, your system may have problems with dds.

* Change back to the texture scheme you like best

* Enter your experiences in the list below

Thanks for your help!

== Tested hardware and graphis drivers ==

=== NVIDIA proprietary driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|GeForce GTX 670M
|310.19
|{{yes}}
|ThorstenR
|-
|GeForce GT 540M
|331.82
|{{yes}}
|Gijs
|-
|N13M-NS Optimus
|340.32
|{{yes}}
|Tom_ch
|-
|GeForce GT640
|343.13
|{{yes}}
|lumni1968
|-
|GeForce GTX 780 Ti
|340.52
|{{yes}}
|Avionyx
|}

=== NVIDIA OpenSource driver ===

=== Intel proprietary driver ===

=== Intel OpenSource driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|HD Graphics 3000 (i7-2600K)
|10.2.6
|{{yes}}
|cdesai
|}

=== ATI/AMD proprietary driver ===

=== ATI/AMD OpenSource driver ===

== Excerpts from the ongoing discussion ==

{{FGCquote
|Here is my suggestion how to proceed:

* Let's do your 1) and 2) on as many information channels we have.
* Collect the responses on a public place, I'd suggest a wiki page
* Do this for a well defined time frame. Is three month too much/too short?
* If we have the impression, it's safe to switch to DDS, define the dds texture sets as default, keeping the png sets as a fallback and publish how to use this fallback
* Keep this for one release.
* Depending on the feedback we get, keep it that way or move entirely to DDS.

Does that sound reasonable for everybody?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32788459/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|let's collect some some feedback until late November and restart this 
topic. We probably know by then what we do for the next release. 
 
"Somebody" needs to collect the feedback, however. That's definitely not 
me - any volunteers? 
 
Torsten
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32791750/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-03</nowiki>
}}
}}

== Misc ==
{{FGCquote
|I'd propose [...] this process:
# Get out the information first that one can change materials files, where to do it and what the characteristics of the different sets are.
# Ask users (especially those running with ATI or Intel on Linux) nicely to do a quick check whether dds works fine.

I think we have an information management problem in relation to the user base - a frequent forum situation is that a user requests something that's already there, but the information is just not out. So if we even envision such a change, I would start spreading the relevant information basically yesterday.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Challenges ==
{{FGCquote
|"dds on an open source driver (radeon and intel) I was forced to use radeon at some time, and it was fun, the planes were pink :) once libtxc-dxtn installed, dds were loaded fine again, so it can be used on open source if you are ok to use the lib." 
 
Unless there's some way to make sure Linux users have that lib installed automatically, I'd say that's a no. We can't have a random user guess what additional packages to install. And maybe someone can educate me - googling the lib, this appears to be working for mesa - which usually is what we try to avoid if users do 3d rendering via mesa for performance reasons? 
 
Also, what does 'If you are okay to use the lib' mean precisely? If that's some piece of code which circumvents a patented thing and isn't exactly legal and needs to be obtained from special servers outside the normal repo (sort of like the DVD decryption under Linux), then I doubt that's an option. Can anyone clarify?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32786414/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Another potential option would be to convert regions to .dds but keep 
both global-png and global-dds, but making that user-friendly would 
require a way to automatically detect lack of .dds support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|On my system (Intel Ivybridge), DDS works with or without libtxc, but 
this may not be true of all Intel hardware. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|You can specify the dependency on libtxc_dxtn, but then distributions like 
openSUSE cannot ship FlightGear anymore. libtxc_dxtn implements S3 texture 
compression which is patented in many parts of the world. Linux distributions 
therefore cannot ship it. You can easily find it in add-on repositories, but 
as I said, distributions would not be able to include FlightGear creating a 
huge hurdle to installation for users.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787143/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Stefan Seifert</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Debian/Ubuntu's libtxc is libtxc-dxtn-s2tc, which claims to avoid the 
patent at a small cost in visual quality: 
https://github.com/divVerent/s2tc/wiki/libtxc_dxtn 
That site also states that modern hardware doesn't need this software 
fallback anyway (and hence won't hit either this quality loss or the 
slowness of any software decoder), but doesn't define "modern hardware".
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787296/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|The dds textures seem to have some advantages over our png textures and 
using them is tempting. 
But the points from Thorsten R. are good points and if there is any 
chance to have a step-wise transition to the new format, I'd prefer that 
path. 
 
Don't we have an alternate dds texture set already in fgdata that is 
enabled with an option? What about making this the default, keeping the 
png texture set as an alternate. That would get us reports from users 
unable to run dds textures and provide an easy fallback method.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787378/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|We currently have regions-png, global-png and global-dds; as I noted 
earlier, switching to regions-dds, global-png and global-dds has the 
issue that while changing the texture set is easy (dropdown in View > 
Rendering Options), knowing that one needs to do so may not be.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787717/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Can we invert the logic in, say, preferences.xml so xxx-dds is enabled 
by default and switching to xxx-png has to be done in rendering options? 
 
Torsten
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787787/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Changing the default (which is in preferences.xml) is easy: the problem 
is how do users with non-.dds-supporting hardware (if this exists) know 
they need to change back.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787851/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Conversion ==
{{FGCquote
|Automatic conversion script is welcome indeed. Also I'm pretty sure that we have some people here ready to convert a PNG to DDS as soon as you say "Hey boys I created a new PNG file, can you convert this file for me please ?" :-)
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785592/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|A few world about the conversion: once a png/rgb/jpg found, the script 
try to guess the suitable dds format: with or without alpha channel, 
bumpmap, if a .dds is allready found we just erase the png one, if not 
we use nvcompress to get the dds. After we change the textures name 
called in the differents files and that's it. There's a way to tell the 
script what to do for each file, if the automatic mode is a failure. 
 
I guess speaking theorically is not the best to make an opinion, so if 
some of you are interested to make a test, I will make a 3.2 minimal dds 
fgdata this we, once on my FG pc.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}
== Pros ==
{{FGCquote
|I always got a loading problem with png textures, large textures take 
seconds to load and convert, and that ruin my close flight where you 
can't afford to take pause in the air. 
that's why i did a batch script to convert to dds ALL the textures in 
the data, not only the matérial set, but everything. Now i only flight a 
dds version of flightgear, and am quite happy with it, that's why i 
propose to provide a dds fgdata for test, and maybe to make it an 
alternate download possibility.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Contra ==
{{FGCquote
|FG actually runs with dds textures, it just doesn't render anything reasonable, I believe you get monochromatic colors. But I don't expect the menu to be affected, it doesn't use textures.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|If it's relevant, I recall having S2TC compression problems when running Flightgear, and updating this package to a newer version manually (outside of the main repos) fixed the issue. I'm on an Intel HD 3000, but I'm guessing that Intel HD 4000 doesn't have this problem, since it seems to have better OpenGL and OpenCL support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787875/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Saikrishna Arcot</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

Switching default texture format to DDS

2014-09-04T10:15:58Z

Avionyx: /* NVIDIA proprietary driver */

{{WIP}}

== Feedback needed - should Flightgear switch the defaults to dds format for terrain texturing? ==

=== What is this about? ===

The FG development team is considering to switch the format for terrain textures from png to dds. This would offer a number of significant advantages:

* dds is a compressed format, hence the download size of the FG base package may be decreased
* compressed dds can be directly used by many graphics cards, reducing also GPU memory consumption
* dds stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory
* the resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost

Practically all commercial simulations use dds for these reasons.

However, the dds compression algorithm is patented, which means that it is not readily available for OpenSource graphics drivers used by Linux distributions. Dependent on the specific hardware, this may or may not be a problem (modern graphics cards typically do not need the driver to process dds, for older graphics cards there are non-patented workarounds available which decompress the dds on the software level). The development team is concerned about making the Flightgear experience pleasant for all users, hence we would like to gather feedback how many users would be affected by a change in practice.

If there are no problems reported, FG will change defaults to txtures in dds format with the 3.4 release, and then phase out the use of png textures.

== What would we need? ==

Flightgear already provides the simple option to test a dds texture set. If you are running on Linux and use an OpenSource graphics driver, please take 5 minutes to help during your next FG session:

* Open the dialog under View -> Rendering

* Under 'Terrain texture scheme', change the default 'Region-specific' to 'Global alternative (DDS format)'

* Press 'Okay' - FG will reload the terrain

* Do you see proper textures on the terrain (they may look different and may also not fit the location perfectly)? If yes, you're fine. If you see monochromatic colors or other rendering artifacts, your system may have problems with dds.

* Change back to the texture scheme you like best

* Enter your experiences in the list below

Thanks for your help!

== Tested hardware and graphis drivers ==

=== NVIDIA proprietary driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|GeForce GTX 670M
|310.19
|{{yes}}
|ThorstenR
|-
|GeForce GT 540M
|331.82
|{{yes}}
|Gijs
|-
|N13M-NS Optimus
|340.32
|{{yes}}
|Tom_ch
|-
|GeForce GT640
|343.13
|{{yes}}
|lumni1968
|-
|GeForce GTX 780 Ti
|340.52
|{{yes}}
|Axionyx
|}

=== NVIDIA OpenSource driver ===

=== Intel proprietary driver ===

=== Intel OpenSource driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|HD Graphics 3000 (i7-2600K)
|10.2.6
|{{yes}}
|cdesai
|}

=== ATI/AMD proprietary driver ===

=== ATI/AMD OpenSource driver ===

== Excerpts from the ongoing discussion ==

{{FGCquote
|Here is my suggestion how to proceed:

* Let's do your 1) and 2) on as many information channels we have.
* Collect the responses on a public place, I'd suggest a wiki page
* Do this for a well defined time frame. Is three month too much/too short?
* If we have the impression, it's safe to switch to DDS, define the dds texture sets as default, keeping the png sets as a fallback and publish how to use this fallback
* Keep this for one release.
* Depending on the feedback we get, keep it that way or move entirely to DDS.

Does that sound reasonable for everybody?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32788459/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|let's collect some some feedback until late November and restart this 
topic. We probably know by then what we do for the next release. 
 
"Somebody" needs to collect the feedback, however. That's definitely not 
me - any volunteers? 
 
Torsten
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32791750/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-03</nowiki>
}}
}}

== Misc ==
{{FGCquote
|I'd propose [...] this process:
# Get out the information first that one can change materials files, where to do it and what the characteristics of the different sets are.
# Ask users (especially those running with ATI or Intel on Linux) nicely to do a quick check whether dds works fine.

I think we have an information management problem in relation to the user base - a frequent forum situation is that a user requests something that's already there, but the information is just not out. So if we even envision such a change, I would start spreading the relevant information basically yesterday.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Challenges ==
{{FGCquote
|"dds on an open source driver (radeon and intel) I was forced to use radeon at some time, and it was fun, the planes were pink :) once libtxc-dxtn installed, dds were loaded fine again, so it can be used on open source if you are ok to use the lib." 
 
Unless there's some way to make sure Linux users have that lib installed automatically, I'd say that's a no. We can't have a random user guess what additional packages to install. And maybe someone can educate me - googling the lib, this appears to be working for mesa - which usually is what we try to avoid if users do 3d rendering via mesa for performance reasons? 
 
Also, what does 'If you are okay to use the lib' mean precisely? If that's some piece of code which circumvents a patented thing and isn't exactly legal and needs to be obtained from special servers outside the normal repo (sort of like the DVD decryption under Linux), then I doubt that's an option. Can anyone clarify?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32786414/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Another potential option would be to convert regions to .dds but keep 
both global-png and global-dds, but making that user-friendly would 
require a way to automatically detect lack of .dds support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|On my system (Intel Ivybridge), DDS works with or without libtxc, but 
this may not be true of all Intel hardware. 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|You can specify the dependency on libtxc_dxtn, but then distributions like 
openSUSE cannot ship FlightGear anymore. libtxc_dxtn implements S3 texture 
compression which is patented in many parts of the world. Linux distributions 
therefore cannot ship it. You can easily find it in add-on repositories, but 
as I said, distributions would not be able to include FlightGear creating a 
huge hurdle to installation for users.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787143/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Stefan Seifert</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Debian/Ubuntu's libtxc is libtxc-dxtn-s2tc, which claims to avoid the 
patent at a small cost in visual quality: 
https://github.com/divVerent/s2tc/wiki/libtxc_dxtn 
That site also states that modern hardware doesn't need this software 
fallback anyway (and hence won't hit either this quality loss or the 
slowness of any software decoder), but doesn't define "modern hardware".
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787296/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|The dds textures seem to have some advantages over our png textures and 
using them is tempting. 
But the points from Thorsten R. are good points and if there is any 
chance to have a step-wise transition to the new format, I'd prefer that 
path. 
 
Don't we have an alternate dds texture set already in fgdata that is 
enabled with an option? What about making this the default, keeping the 
png texture set as an alternate. That would get us reports from users 
unable to run dds textures and provide an easy fallback method.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787378/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|We currently have regions-png, global-png and global-dds; as I noted 
earlier, switching to regions-dds, global-png and global-dds has the 
issue that while changing the texture set is easy (dropdown in View > 
Rendering Options), knowing that one needs to do so may not be.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787717/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Can we invert the logic in, say, preferences.xml so xxx-dds is enabled 
by default and switching to xxx-png has to be done in rendering options? 
 
Torsten
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787787/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Changing the default (which is in preferences.xml) is easy: the problem 
is how do users with non-.dds-supporting hardware (if this exists) know 
they need to change back.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787851/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Conversion ==
{{FGCquote
|Automatic conversion script is welcome indeed. Also I'm pretty sure that we have some people here ready to convert a PNG to DDS as soon as you say "Hey boys I created a new PNG file, can you convert this file for me please ?" :-)
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785592/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|A few world about the conversion: once a png/rgb/jpg found, the script 
try to guess the suitable dds format: with or without alpha channel, 
bumpmap, if a .dds is allready found we just erase the png one, if not 
we use nvcompress to get the dds. After we change the textures name 
called in the differents files and that's it. There's a way to tell the 
script what to do for each file, if the automatic mode is a failure. 
 
I guess speaking theorically is not the best to make an opinion, so if 
some of you are interested to make a test, I will make a 3.2 minimal dds 
fgdata this we, once on my FG pc.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}
== Pros ==
{{FGCquote
|I always got a loading problem with png textures, large textures take 
seconds to load and convert, and that ruin my close flight where you 
can't afford to take pause in the air. 
that's why i did a batch script to convert to dds ALL the textures in 
the data, not only the matérial set, but everything. Now i only flight a 
dds version of flightgear, and am quite happy with it, that's why i 
propose to provide a dds fgdata for test, and maybe to make it an 
alternate download possibility.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Contra ==
{{FGCquote
|FG actually runs with dds textures, it just doesn't render anything reasonable, I believe you get monochromatic colors. But I don't expect the menu to be affected, it doesn't use textures.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|If it's relevant, I recall having S2TC compression problems when running Flightgear, and updating this package to a newer version manually (outside of the main repos) fixed the issue. I'm on an Intel HD 3000, but I'm guessing that Intel HD 4000 doesn't have this problem, since it seems to have better OpenGL and OpenCL support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787875/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Saikrishna Arcot</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

OpenRadar

2010-12-09T16:19:29Z

Avionyx: update of project status

{{Infobox Software
| title = OpenRadar
| logo =
| image = OpenRadar_KSFO_large.png
| alt = San Francisco bay area
| developedby = Ralf Gerlich
| initialrelease =
| latestrelease =
| writtenin = Java
| os =
| platform =
| developmentstatus = Active
| type =
| license =
| website = http://mapserver.flightgear.org/git/gitweb.pl?p=openradar
}}
[[Image:OpenRadar_KSFO_closeup.png|thumb|270px|[[San Francisco International Airport]].]]
'''OpenRadar''' is a standalone radar screen which connects to the [[FlightGear]] [[Howto: Multiplayer|multiplayer]] servers. Coastlines, lakes, airfield layouts and airspaces (at least the 2D part) are being read from shapefiles.

As of December 2010 development has restarted, no development had been undertaken since 2008. This page will be updated shortly.

[[Category:Java]]

FGSignMaker

2010-06-26T08:26:37Z

Avionyx: /* Most wanted */

[[File:FGSignMaker_overview.png|400px|thumb|right|FGSignMaker 1.0.1]]
FGSignMaker is an (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign codes for [[FlightGear]] licensed under the [[GNU General Public License]]. It can be used in conjunction with the [[UFO]] and your favorite plain text editor to add [[Signs|taxiway signs]] for FlightGear. The latest release available is version 1.0.1.

== Web browser compatibility ==

=== Known compatible browsers ===

FGSignMaker 1.0.1 is known to work well with the following web browsers:
* Safari
* Mozilla Camino
* Mozilla Firefox 3.6
* Opera 9
* Internet Explorer 6 ('''not recommended''', due to JavaScript/CSS bugs and for just being a horrible browser in general)
* Internet Explorer 7

=== Most wanted ===

These browsers are "most wanted." If FGSignMaker works correctly under one of these browsers, please add them to the list above.
* Google Chrome

== Interface ==

=== Sign preview ===

[[File:FGSignMaker_signpreview.png|Sign preview]] 
The sign preview, which updates automatically as you modify the sign code, gives you a rough (but fairly accurate) idea of how your sign will look when in FlightGear.

=== Sign code box ===

[[File:FGSignMaker_codebox.png|Sign code box]] 
The sign code text box displays the actual code for the taxiway sign. You can insert glyphs here and type custom text. The "Select All" button selects all the text in this box and the "Clear" button deletes all the text. ''Without warning.''

=== Character counter and syntax checker ===

[[File:FGSignMaker_countersyntax.png|Character counter/syntax checker]] 
The character counter (the "Character 15" in this screenshot) displays your cursor's position in the sign code box. It is mostly useful for debugging. The syntax checker is a basic, automatic tool that checks for misplaced braces ({ and }). It displays the position at which a misplaced brace was found.

=== Glyph inserter ===

[[File:FGSignMaker_glyphinserter.png|Glyph insertion tools]] 
Last but certainly not least, the glyph inserter allows you to place predefined taxiway types and features. Currently it includes the four FAA-standard types implemented in FlightGear (L858-Y, L858-R, L858-L, L858-B), a line (vertical pipe |), and a no-entry sign.

== Placing taxiway signs ==

[[File:FGSignMaker_signfg-signmaker.png|250px|thumb|right|A taxiway sign in FlightGear (background) and in FGSignMaker (inset)]]
This tutorial explains how to add [[Signs|taxiway signs]] to FlightGear along with FGSignMaker. You are highly encouraged to add taxiway signs to your favorite airport, even if they are inaccurately placed.

=== Step 1: Launch FlightGear ===

[[File:FGSignMaker_tut1.png|400px|Step 1]] 
First things first, we'll launch FlightGear in the [[UFO]] at the airport we will be working on (in this case [[KSFO]]). Here I will be using my fancy Linux terminal, but [[FlightGear Launch Control|fgrun]] will also suffice.

=== Step 2: Place taxiway sign(s) ===

[[File:FGSignMaker_tut2.png|830px|Step 2]] 
With FlightGear loaded, fly the UFO to the location of the sign you want to place. Press the spacebar to bring up the model select dialog, choose "Aircraft/ufo/Models/sign.ac," and click where you want to place the new sign. Alt+Click the terrain to reposition the sign if need be. Press tab to bring up the adjustment dialog and use the heading slider and arrows to turn the sign. For more information on this process, see [[Howto: Place 3D objects with the UFO]].

=== Step 3: Build your sign in FGSignMaker ===

[[File:FGSignMaker_tut3.png|531px|Step 3]] 
Now we create the actual taxiway sign code in FGSignMaker. In this case, a pilot looking at the sign would be on taxiway Delta, taxiway Charlie would be on the left, the end of runway 36L would be right in front, and the end of runway 18R would be on the right. To create this sign in FGSignMaker, we would:
* Click the L858-Y button
* Click the left arrow
* Type "C" into the sign code box
* Click the L858-L button
* Type "D" into the sign code box
* Click the L858-R button
* Type "36L-18R" into the sign code box
* Click the right arrow

=== Step 4: Add the sign into the *.stg file ===

Press D to dump the export data to the command line or fgrun log window. You will see several lines similar to this example:

# w130n30/w123n37/942050.stg
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

------------------------------------------------------------------

As you add more signs and/or scenery objects, this output will grow. The last object you placed is on the last line.

The most important piece of information we need right now is the *.stg file to edit. This is displayed in the comment (line with the hash # at the front).

# w130n30/w123n37/942050.stg

This tells us that the wanted *.stg file can be found at "FG_SCENERY/Objects/w130n30/w123n37/942050.stg"- obviously, the path will vary depending on where you placed the sign.

Now open that *.stg file in your favorite plain text editor. Insert the desired OBJECT_SIGN line from the command line output from earlier, like so:

...
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

Now replace the "{@size=10,@material=RedSign}NO_CONTENTS_[random number]" with the taxiway sign code you generated in step 3. Save the file.

=== Step 5: View your new sign(s) in FlightGear ===

[[File:FGSignMaker_signsinfg.png|300px|right|thumb|KBFL taxiway signs made with FGSignMaker]]
You won't immediately see your changes in FlightGear- you'll have to restart the simulator. Once you do, you should be able to see the new taxiway signs.

== Submitting your work ==

If you are happy with your work, please submit it into the [[FlightGear Scenery Database]]. See [[FlightGear Scenery Database#Contributing_Positions|here]] for more details.

== External links ==

* [http://www.flightgear.org/forums/viewtopic.php?t=8596 Forum thread]
* [http://drop.io/cocu73e Download version 1.0.1]

[[Category:Scenery enhancement]]
[[Category:Software]]

FGSignMaker

2010-06-26T08:26:18Z

Avionyx: /* Known compatible browsers */

[[File:FGSignMaker_overview.png|400px|thumb|right|FGSignMaker 1.0.1]]
FGSignMaker is an (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign codes for [[FlightGear]] licensed under the [[GNU General Public License]]. It can be used in conjunction with the [[UFO]] and your favorite plain text editor to add [[Signs|taxiway signs]] for FlightGear. The latest release available is version 1.0.1.

== Web browser compatibility ==

=== Known compatible browsers ===

FGSignMaker 1.0.1 is known to work well with the following web browsers:
* Safari
* Mozilla Camino
* Mozilla Firefox 3.6
* Opera 9
* Internet Explorer 6 ('''not recommended''', due to JavaScript/CSS bugs and for just being a horrible browser in general)
* Internet Explorer 7

=== Most wanted ===

These browsers are "most wanted." If FGSignMaker works correctly under one of these browsers, please add them to the list above.
* Safari
* Google Chrome

== Interface ==

=== Sign preview ===

[[File:FGSignMaker_signpreview.png|Sign preview]] 
The sign preview, which updates automatically as you modify the sign code, gives you a rough (but fairly accurate) idea of how your sign will look when in FlightGear.

=== Sign code box ===

[[File:FGSignMaker_codebox.png|Sign code box]] 
The sign code text box displays the actual code for the taxiway sign. You can insert glyphs here and type custom text. The "Select All" button selects all the text in this box and the "Clear" button deletes all the text. ''Without warning.''

=== Character counter and syntax checker ===

[[File:FGSignMaker_countersyntax.png|Character counter/syntax checker]] 
The character counter (the "Character 15" in this screenshot) displays your cursor's position in the sign code box. It is mostly useful for debugging. The syntax checker is a basic, automatic tool that checks for misplaced braces ({ and }). It displays the position at which a misplaced brace was found.

=== Glyph inserter ===

[[File:FGSignMaker_glyphinserter.png|Glyph insertion tools]] 
Last but certainly not least, the glyph inserter allows you to place predefined taxiway types and features. Currently it includes the four FAA-standard types implemented in FlightGear (L858-Y, L858-R, L858-L, L858-B), a line (vertical pipe |), and a no-entry sign.

== Placing taxiway signs ==

[[File:FGSignMaker_signfg-signmaker.png|250px|thumb|right|A taxiway sign in FlightGear (background) and in FGSignMaker (inset)]]
This tutorial explains how to add [[Signs|taxiway signs]] to FlightGear along with FGSignMaker. You are highly encouraged to add taxiway signs to your favorite airport, even if they are inaccurately placed.

=== Step 1: Launch FlightGear ===

[[File:FGSignMaker_tut1.png|400px|Step 1]] 
First things first, we'll launch FlightGear in the [[UFO]] at the airport we will be working on (in this case [[KSFO]]). Here I will be using my fancy Linux terminal, but [[FlightGear Launch Control|fgrun]] will also suffice.

=== Step 2: Place taxiway sign(s) ===

[[File:FGSignMaker_tut2.png|830px|Step 2]] 
With FlightGear loaded, fly the UFO to the location of the sign you want to place. Press the spacebar to bring up the model select dialog, choose "Aircraft/ufo/Models/sign.ac," and click where you want to place the new sign. Alt+Click the terrain to reposition the sign if need be. Press tab to bring up the adjustment dialog and use the heading slider and arrows to turn the sign. For more information on this process, see [[Howto: Place 3D objects with the UFO]].

=== Step 3: Build your sign in FGSignMaker ===

[[File:FGSignMaker_tut3.png|531px|Step 3]] 
Now we create the actual taxiway sign code in FGSignMaker. In this case, a pilot looking at the sign would be on taxiway Delta, taxiway Charlie would be on the left, the end of runway 36L would be right in front, and the end of runway 18R would be on the right. To create this sign in FGSignMaker, we would:
* Click the L858-Y button
* Click the left arrow
* Type "C" into the sign code box
* Click the L858-L button
* Type "D" into the sign code box
* Click the L858-R button
* Type "36L-18R" into the sign code box
* Click the right arrow

=== Step 4: Add the sign into the *.stg file ===

Press D to dump the export data to the command line or fgrun log window. You will see several lines similar to this example:

# w130n30/w123n37/942050.stg
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

------------------------------------------------------------------

As you add more signs and/or scenery objects, this output will grow. The last object you placed is on the last line.

The most important piece of information we need right now is the *.stg file to edit. This is displayed in the comment (line with the hash # at the front).

# w130n30/w123n37/942050.stg

This tells us that the wanted *.stg file can be found at "FG_SCENERY/Objects/w130n30/w123n37/942050.stg"- obviously, the path will vary depending on where you placed the sign.

Now open that *.stg file in your favorite plain text editor. Insert the desired OBJECT_SIGN line from the command line output from earlier, like so:

...
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

Now replace the "{@size=10,@material=RedSign}NO_CONTENTS_[random number]" with the taxiway sign code you generated in step 3. Save the file.

=== Step 5: View your new sign(s) in FlightGear ===

[[File:FGSignMaker_signsinfg.png|300px|right|thumb|KBFL taxiway signs made with FGSignMaker]]
You won't immediately see your changes in FlightGear- you'll have to restart the simulator. Once you do, you should be able to see the new taxiway signs.

== Submitting your work ==

If you are happy with your work, please submit it into the [[FlightGear Scenery Database]]. See [[FlightGear Scenery Database#Contributing_Positions|here]] for more details.

== External links ==

* [http://www.flightgear.org/forums/viewtopic.php?t=8596 Forum thread]
* [http://drop.io/cocu73e Download version 1.0.1]

[[Category:Scenery enhancement]]
[[Category:Software]]