FlightGear Newsletter June 2019

<Previous editionNext edition >

Enjoy reading the latest edition!

Please help us write the coming edition!

June 2019

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.

Help wanted

Post LTS work

After the 2020.2 release, some work lies ahead to improve the LTS and to help us pave the way for migrating to the OpenGL Core profile - any help would be greatly appreciated.

This may for example include:

• Switching to the OpenGL Core profile:
  • Helping retarget Canvas.Path to get rid of Shiva
  • Porting the legacy HUD system to become Canvas based
  • Help retarget the 2D panels system to become Canvas based
• Checking that aircraft work with the LTS and documenting any major problems
• Include ffmpeg libraries in Windows and Mac builds, to enable built-in video encoding.
• Cppunit effort and FlightGear Headless (see Testing)
• Deboosting FlightGear

Please get in touch via the developers mailing list to learn more. See Post FlightGear 2020.2 LTS changes and 2022.X Release Plan for more details.

World Scenery 3.0

The FlightGear project is in the process of exploring how Virtual Planet Builder can be adopted. For details, see: World Scenery 3.0 roadmap

Aerial (drone) photos for Terrain textures

Wanted: good top-down aerial photos to create textures from to use with the procedural Regional Texturing system. Drones with cameras are ideal. People with access to drones are in a good position to take high-quality photographs.

A particular need as of 2020 is photos of agriculture (farm lands) from different parts of the world.

Good GPLv2 compatible photos suitable for textures are hard to find, and an easy way is for people to take photos of their region. Flightgear's procedural systems can do a lot with less art content, so photo contributions can strongly improve visuals.

See: How to: take photos of terrain for textures. For examples of final textures: see /data/Textures/Terrain. e.g. UK countryside.

You can get in touch via the Scenery forum or the flightgear-devel mailing list

Photos of trees for textures

Wanted: good quality photos of different trees and vegetation from various parts of the world. Flightgear's vegetation system can handle multiple layers of trees and bushes.

Strong shadows should be avoided. Each tree should be against a background of a different colour: sky (preferably) , clouds , or buildings. This allows the tree to be separated from the background in a photo-editor like GIMP.

See: How to: take photos of vegetation. For examples of final textures: see /data/Textures/Trees. e.g. Coniferous.

You can get in touch via the Scenery forum or the flightgear-devel mailing list.

Submissions of labels for craft

Wanted: Submissions of labels (tags) giving a rough description of aircraft - Metadata tags. A quick read of a craft's Wikipedia page will normally be enough to set labels. This info will be searchable from the launcher GUI. For example, filtering craft by propulsion like single-propeller or 4-engine jet craft, or by a manufacturer like Airbus or Grumman, or by speed like supersonic craft, or craft by era like WW2. A list of tags is here - more can be added if needed. To add tags to craft yourself, the tags are stored in the set-xml file.

A list of FGAddon craft needing tags is here. See this forum thread to submit tags. The flightgear-devel mailing list or the craft's maintainer can also be contacted.

Windows Package Maintainer

The core team needs help from Windows users able to maintain a good working Windows build. This process already exists to support our Nightly and Release builds, but we are seeking additional help to keep it in good working order. The ability to compile FG from source and some Windows batch scripting is a required skill. If you are willing and able to take up this role, please reach out to James Turner (mailing list), or get in touch via the forum

In the hangar

Updated aircraft

F-14 V1.9

• Interior cockpit shadows working
• Fixes (JSBSim) for FG 2019.1 or later.
• Better APC (thanks Josh)
• FDM aero improvements to flaps and low speed handling
• 3D Model optimisations (single mesh for exterior/interior with a texture atlas for each)

F-15 V1.9

• Nasal optimisations
• optimised Canvas displays
• Using emesary M_exec for Nasal mainloop
• JSBSim runtime error fixes
• FCS/AFCS improvements (Joshua Davidson)
• Improved MPCD SIT (map) (Nikolai)
• VSD fixed target aspect display
• FDM mass properties corrections(fuel/payload/stores/pylons positions)

AI

The AI team makes FlightGear more realistic, colorful and lively every month. You can support the important development of Interactive Traffic and contribute at the FlightGear AI subforum .

Scenery corner

Belgium

The Belgian scenery development is back on track !

Need to add a fancy and very fat screenshot representing this scenery. (feel free to add somethings very fat !)

The scenery development of Belgium started around 2011 and stalled around 2013. Some parts of this external scenery has been pushed to TerraSync in 2015. But since 2015 nothing has been improved in TerraSync.

The author of the Belgian scenery is a great fan of ULM's, GA and helicopters. No wonder that he focus on little airfields. However, he currently work back on the massive EBBR (Brussels Airport) and EBBL (Kleine-Brogel) mil and many more little airfields.

Actually, most of the Belgian airports got a technical update, to match the current FlightGear requirements. (mind the elevation data, airport accuracy, optimizing of objects and textures, night texture animation, adding shared models to fill up the airfields...).

Some airfields, so far EBBL and EBSW, got a serious lifting since 2013 and needs testers before these data get pushed to the TerraSync server. Much more will come very soon.

Those who love military stuff would love EBBL. The EBBL military airbase is completely photo realistic textured and require a special attention to testers! The EBBL military airfield is build like how it is in real life !

We need testers ! Volunteers who test and report issues on: https://github.com/dvanmosselbeen/flightgear-belgian-custom-scenery/issues before the scenery get pushed to the TerraSync server.

The current status:

A Belgian page has been created on the FlightGear Wiki to give you more information of the current development status.

However, for the moment, as the documentation is also in progress, the documentation is stored on the wiki of the projects repo. In the mean time, the documentation should move to the wiki of FlightGear. For the full list of improved airports with screenshots and more information of each Belgian airfield, see: https://github.com/dvanmosselbeen/flightgear-belgian-custom-scenery/wiki/Airports-list

Follow, download and contribute to it's development on: https://github.com/dvanmosselbeen/flightgear-belgian-custom-scenery/wiki

If any Belgian has contacts with local pilots or airfield employees, or have usable information, feel free to contact David Van Mosselbeen (david.van.mosselbeen@gmail.com - +32 496 28 38 96).

Community news

FlightGear on Facebook

Since early December 2010, FlightGear has an official Facebook page. If you have a Facebook account please feel free to join the page.

FlightGear on Instagram

In January 2018 the @flightgear_sim Instagram account was brought back to life. If you've got nice screenshots to be featured, feel free to contact the maintainer .

FlightGear on FlightSim.com

Flightgear has also a sub-forum on flightsim.com - just like the commercial flightsims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

Contributing

Translators needed

	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.
	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 Help:Traduire.
	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 Help:Übersetzen an.
	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 Help:Vertalen.
	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 Help:Traducir.
	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 Help:Traduir.
	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 Help:Traduzir.
	FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 Help:Translate.

FlightGear logos

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

Screenshots

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

Screenshot of the Month

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

Thanks for reading FlightGear Newsletter June 2019!

References