![]() There is a lot to check out if you are curious - power users can run multiple installs of FlightGear in parallel. A lot of work (but not all) is already on the next branch (i.e. There are a lot of big projects that are currently under way - see the January newsletter for details for some of these projects. If you need suitable screenshots for the homepage ( examples) for a specific craft or feature that aren't already available ( 1, 2, 3) in the wiki or forum, you can try asking in the forum media section. The points are the important thing, don't worry if your English is not perfect. since 2018.3 was released, with screenshots. There is a draft page here for submissions of material for posts on the homepage about changes to FlightGear, Aircraft, Addons etc. See this discussion of hardware recommendations for modern FlightGear - although it is for 2018.3 LTS and doesn't cover the new experimental OSM2City (see the OSM2City page info for perfromance tips). Release builds now include Appimages for Linux. Click to enlarge.Ĭalifornia regional definitions - airport keep See 2020.3.8 LTS change log - included are improvements to Europe agriculture appearance, update to random scenery objects such as farm or industrial buildings and silos, California regional definitions improvements (now active), and updated water depth data (bathymetry). See 1st World-build of OSM2City for information on what's included, and tips on performance/troubleshooting. Automatic generation for areas without objects is disabled for this release. Objects that are in the Open Street Map (OSM) database will be present. Ģ020.3.8 LTS released - OSM2City world-build releaseįlightGear 2020.3.8 LTS has been released with an experimental 1st rollout of OSM2City buildings, roads and other objects for the entire world. That's what we recommend for everyone who wants to fly and enjoy flying. If next works for someone, that is great, but if you want stability, stable FPS and comaptability with older hardware, there is an easy answer: use 2020.3. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!) Of course we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. In that time the minimum system requirements, performance baseline and basically everything else are going to change (and keep changing). 'next' is work-in-progress: likely 12 or 18 months before it becomes a release. We tried to communicate this: 2020.3 is the last release that will work on really old hardware: 'next' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU. It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022). More importantly: moving to the OpenGL core profile, WS 3.0, osm2city buildings, photoscenery and Compositor shadows&lights. Development news Note FG is currently undergoing a lot of huge changes. 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. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. 5.3 Aerial (drone) photos for Terrain textures.3.3 Space Shuttle Milestone 13 released.2.1.3 New nightlies and debug build release.2.1.1 Mumble 1.4.0 development master received plugin framework.1.4 New rendering pipeline for Compositor.1.3.2.1 2021.x development preview release plans.1.3.2 World Scenery 3.0 update & FG 2021.x preview release plans.1.3.1 Data Distribution Services Update: Property tree support.1.1 2020.3.8 LTS released - OSM2City world-build release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |