1,746
edits
m (add entry for C172S project, cleanup) |
(Add a bit more info for people returning to FG after the new release and wanting to know what's happening. Add info for: RedGriffin ATC 2.0, C172S model request. Cleanup.) |
||
Line 50: | Line 50: | ||
''See [[FlightGear_Newsletter_October_2020#Help_wanted|Help wanted]]. | ''See [[FlightGear_Newsletter_October_2020#Help_wanted|Help wanted]]. | ||
There are a lot of big infrastructure changes already well underway and planned for the LTS after 2020.3.x. To name a couple: [[Compositor]], [[World_Scenery_3.0_roadmap|World Scenery 3.0]], switching to [[Virtual_Planet_Builder|Virtual Planet Builder]] instead of terragear for terrain building, replacement of the in-sim UI, infrastructure for regular world builds, runtime airport generation, move to a higher version of OpenGL, OSM2City world build and [[OSM2City]] tech improvements etc. | There are a lot of big infrastructure changes already well underway and planned for the LTS after 2020.3.x. To name a couple: [[Compositor]], [[World_Scenery_3.0_roadmap|World Scenery 3.0]], switching to [[Virtual_Planet_Builder|Virtual Planet Builder]] instead of terragear for terrain building, [[CompositeViewer_Support|Composite Viewer]], replacement of the in-sim UI, infrastructure for regular world builds, runtime airport generation, move to a higher version of [[OpenGL#Status|OpenGL]] (4.x is planned), OSM2City world build and [[OSM2City]] tech improvements etc. | ||
The 'next' branch will build towards the next Development Preview release, and ultimately the next LTS. As always nightly builds of the next branch are available at [http://download.flightgear.org/builds/nightly/ download.flightgear.org]. | If you are wondering when Flightgear will move to Vulkan using the newly released [[Vulkan Scene Graph]] (VSG) which is the successor to OSG that FG currently uses, VSG will be looked at after the current set of infrastructure and OpenGL 4.x according to plans mentioned by devs - as Vulkan Scene Graph hopefully should be mature and stable by then. | ||
For those curious keep and eye on the 'next' branch, or the nightly builds. Already, there are big changes recently merged into the next branch (initial WS 3.0 / VPB code), and there are big changes planned /planned/ to be merged within just the next several weeks (switching to Compositor as the main rendering framework, Composite viewer, possibly some work on in-sim UI replacement ..). | |||
The 'next' branch will build towards the next Development Preview release, and ultimately the next LTS. As always, nightly builds of the next branch are available at [http://download.flightgear.org/builds/nightly/ download.flightgear.org]. | |||
====Updates to the FG homepage==== | ====Updates to the FG homepage==== | ||
Line 81: | Line 85: | ||
== New software tools and projects == | == New software tools and projects == | ||
<!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --> | <!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --> | ||
=== FGCom-mumble === | === FGCom-mumble === | ||
Line 126: | Line 131: | ||
This will bring fixed ground nets in S/W Coordinates (like KSFO), 8.33 channel spacing support and experimental native FGCom-mumble support. | This will bring fixed ground nets in S/W Coordinates (like KSFO), 8.33 channel spacing support and experimental native FGCom-mumble support. | ||
=== Red Griffin ATC 2.0 released === | |||
Antonello Biancalana (Red Griffin) has released [[Red Griffin ATC|version 2.0]] of his speaking Air Traffic Controller (ATC) [[Addon]]. This addon uses TTS, and simulates an AI ATC. This is also available from FGAddon. | |||
For feedback see the {{forum link|t=36755|title=Red Griffin ATC - Speaking ATC addon for FlightGear}} thread. | |||
Demo of a previous version of the ATC addon: | |||
{{#ev:youtube|ZOxDTGj9UnQ|480px||Demonstration video of a previous version of the Red Griffin ATC addon for an older version of Flightgear. Video from March 2020.}} | |||
== In the hangar == | == In the hangar == | ||
Line 138: | Line 152: | ||
The team are requesting thorough testing to find any needed tuning changes and missing elements. | The team are requesting thorough testing to find any needed tuning changes and missing elements. | ||
The engine and systems work is already available, done, or will be completed shortly. | |||
The team are placing a request/call for help with "exterior and interior cabin modeling" to make this a complete C172S. | |||
See the [https://forum.flightgear.org/viewtopic.php?f=4&t=38240 forum thread] for more information and screenshots ([https://i.imgur.com/QsjgtGc.png 1], [https://i.imgur.com/TlsZ5dw.png 2], [https://i.imgur.com/rA8a2D0.png 3]). | See the [https://forum.flightgear.org/viewtopic.php?f=4&t=38240 forum thread] for more information and screenshots ([https://i.imgur.com/QsjgtGc.png 1], [https://i.imgur.com/TlsZ5dw.png 2], [https://i.imgur.com/rA8a2D0.png 3]). |
edits