Template:Help wanted: Difference between revisions
Legoboyvdlp (talk | contribs) |
No edit summary |
||
| (34 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
=== Post LTS work === | === Post LTS work === | ||
After the 2020.2 release, some work lies ahead - any help would be greatly appreciated | 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. | ||
See [[Post FlightGear 2020.2 LTS changes]] for details. | This may for example include: | ||
* [[OpenGL#Status|Switching to the OpenGL Core profile]]: | |||
** [[Shiva Alternatives|Helping retarget Canvas.Path to get rid of Shiva]] | |||
** [[Unifying_the_2D_rendering_backend_via_canvas#HUD|Porting the legacy HUD system to become Canvas based]] | |||
** [[Post_FlightGear_2020.2_LTS_changes#2D_Panels|Help retarget]] the [[2D Panels|2D panels system]] to become [[Canvas]] based | |||
* [[Aircraft_testing_checklist|Checking that aircraft work with the LTS and documenting any major problems]] | |||
* Include ffmpeg libraries in Windows and Mac builds, to enable [[Video_encoding|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 === | === 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. {{wikipedia|Aerial_photography#Radio-controlled_model_aircraft|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: [[Howto:Create_textures_from_photos#Taking_your_own_photos|How to: take photos of terrain for textures]]. For examples of final textures: see /data/Textures/Terrain. e.g. [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Textures/Terrain/uk_countryside2.png UK countryside]. | |||
You can get in touch via the [https://forum.flightgear.org/viewforum.php?f=5 Scenery forum] or the [[Mailing_lists|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 [[:File:EC_135_in_Hawaii_(Flightgear_2018.x).jpg|multiple layers]] of trees and bushes. | |||
Strong shadows should be avoided. Each tree should be against a background of a different colour: [https://commons.wikimedia.org/wiki/File:Tree_on_skyline_-_geograph.org.uk_-_817006.jpg sky] (preferably) , [https://commons.wikimedia.org/wiki/File:Tree_on_the_skyline_-_geograph.org.uk_-_409721.jpg clouds] , or [https://commons.wikimedia.org/wiki/File:Tree,_sky,_top_roof.jpg buildings]. This allows the tree to be separated from the background in a photo-editor like GIMP. | |||
See: [[Howto:Create_textures_from_photos#Taking_your_own_photos|How to: take photos of vegetation]]. For examples of final textures: see /data/Textures/Trees. e.g. [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Textures/Trees/coniferous-alt.png Coniferous]. | |||
You can get in touch via the [https://forum.flightgear.org/viewforum.php?f=5 Scenery forum] or the [[Mailing_lists|flightgear-devel]] mailing list. | |||
===Submissions of labels for craft=== | |||
Wanted: Submissions of labels (tags) giving a rough description of aircraft - [[Catalog_metadata|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 [[FlightGear_Qt_launcher|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 [[Catalog_metadata#Supported_Tags|here]] - more can be added if needed. To [[Catalog_metadata#Adding_metadata_to_aircraft|add tags]] to craft yourself, the tags are stored in the set-xml file. | |||
If you are willing and able to take up this role, please reach out to | A list of FGAddon craft needing tags is [http://adalin.com/ehtw.info/flightgear-metadata.txt here]. See [https://forum.flightgear.org/viewtopic.php?f=6&t=31915 this] forum thread to submit tags. The [[Mailing_lists|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 <ref>https://forum.flightgear.org/viewtopic.php?f=42&t=37155</ref> | |||
<references/><noinclude> | <references/><noinclude> | ||
[[Category:Newsletter templates]] | |||
[[Category:Undocumented templates]] | [[Category:Undocumented templates]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 00:54, 13 December 2022
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:
- 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.
.jpg){kind=link}
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 [1]