6.1 Should I purchase a computer or build my own?.3 Recommended hardware for FlightGear 3.20+.2.1.2 Target settings: rendering and scenery:.2.1 Mostly high and Max settings with 2015+ mid range GPU.
2 Recommended hardware for FlightGear 2018.3 LTS.1 Recommendations for FlightGear in 2022 (2020.3 LTS).You may also want to check out the following article on building your own FlightGear box based on decommissioned and refurbished server at Howto: Build a cheap FlightGear box, and also learn about how the FlightGear project handles old hardware support at FlightGear and old Hardware - see Minimal Startup Profile to start with a bare minumum and turn up settings one by one.
The performance of FlightGear depends on three main components in your computer: the CPU (processor), which makes all the computations the graphics card, which renders the visual aspect of FlightGear, and RAM (also known as memory) which generally allows FlightGear to have more information running (for the lack of a more technical phrase). These hardware recommendations for FlightGear are based on community feedback, be sure to consult other sources before making serious decisions regarding computer hardware. 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…) 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. Note FlightGear is currently undergoing a lot of huge changes.