4/9/2024 0 Comments World scenery in flightgear![]() To see the full impact of the new regional definitions you also need the new terrain - the current terrain is less detailed, and some land class types will not be visible. The terrain has land classifications that call new visual effects from new engine features frtps has worked on like cliffs and plantations. The terrain integrates multiple data-sources, and has high resolution water bodies like rivers. The new terrain has been submitted to be added to TerraSync at a future point. WS2 format) that is downloaded automatically as you fly. The new terrain is intended to be added to the current TerraSync scenery (i.e. To go with the regional definitions there is also a new detailed terrain (higher resolutions elevation data including cliffs, water, and land classifications). ![]() The regional definitions are part of the Australia scenery project. nightly builds), as they need a bit of adaptation to account for new changes. The new regional definitions are not available in the next branch as of early September (i.e. These regional definitions improve the visuals of different types of terrain and vegetation. James Hester (frtps) has merged the 1st iteration of improved regional definitions for Australia into branch for upcoming point releases in the 2020.3 branch - that is, a 2020.3.12+ point release. See the July newsletter for more information and plans. This installer is available since 2020.3.9. There is now a web-installer for Windows that will update existing installations and will download only changed and new files. 11 LTS point release is out - see the change logs. The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 Īlso, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…) įlightGear 2020.3. 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 compatibility 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 build dependencies, 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). In addition, adopting OSG 3.6 means that the experimental CompositeViewer Support can be more widely enabled and tested (it is already enabled by default on next).Īlso, as part of the CompositeViewer effort, Canvas FBO rendering is in the process of being moved out of the scene graph into dedicated viewer-level cameras, which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.įurthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our Canvas Path backend from Shiva to ‘something else’ (see Shiva Alternatives) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL. More importantly: Adopting OSG 3.6+, moving to the OpenGL core profile, WS 3.0, Osm2city buildings, Photoscenery and Compositor shadows & lights. Development news Note FlightGear is currently undergoing a lot of huge changes. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |