Difference between revisions of "FlightGear Flight Simulator"
From PCGamingWiki, the wiki about fixing PC games
m |
m (fixed typo) |
||
| (35 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
| + | {{cleanup|([[User:Dandelion Sprout|Dandelion Sprout]]:) Various paragraphs need to be compressed quite a lot to make them easier to read}} | ||
{{State|state=postdev}} | {{State|state=postdev}} | ||
{{Infobox game | {{Infobox game | ||
| − | |cover = | + | |cover = FlightGear_2020.3.11_LTS_cover.png |
|developers = | |developers = | ||
{{Infobox game/row/developer|FlightGear.org developers & contributors}} | {{Infobox game/row/developer|FlightGear.org developers & contributors}} | ||
|publishers = | |publishers = | ||
| − | |||
|engines = | |engines = | ||
|release dates= | |release dates= | ||
| − | {{Infobox game/row/date|Windows| | + | {{Infobox game/row/date|Windows| December 17, 2007|ref=<ref>{{Refurl|url=https://wiki.flightgear.org/FlightGear_history#Release_timeline|title=FlightGear Wiki |date=December 4, 2023 }}</ref>}} |
| + | {{Infobox game/row/date|OS X| December 17, 2007}} | ||
| + | {{Infobox game/row/date|Linux| December 17, 2007}} | ||
|reception = | |reception = | ||
{{Infobox game/row/reception|Metacritic|link|rating}} | {{Infobox game/row/reception|Metacritic|link|rating}} | ||
{{Infobox game/row/reception|OpenCritic|link|rating}} | {{Infobox game/row/reception|OpenCritic|link|rating}} | ||
| − | {{Infobox game/row/reception|IGDB| | + | {{Infobox game/row/reception|IGDB|flightgear|rating}} |
|taxonomy = | |taxonomy = | ||
{{Infobox game/row/taxonomy/monetization | Freeware }} | {{Infobox game/row/taxonomy/monetization | Freeware }} | ||
{{Infobox game/row/taxonomy/microtransactions | }} | {{Infobox game/row/taxonomy/microtransactions | }} | ||
| − | {{Infobox game/row/taxonomy/modes | Multiplayer }} | + | {{Infobox game/row/taxonomy/modes | Singleplayer, Multiplayer }} |
| − | {{Infobox game/row/taxonomy/pacing | }} | + | {{Infobox game/row/taxonomy/pacing | Relaxed}} |
| − | {{Infobox game/row/taxonomy/perspectives | }} | + | {{Infobox game/row/taxonomy/perspectives | First-person, Third-person}} |
| − | {{Infobox game/row/taxonomy/controls | }} | + | {{Infobox game/row/taxonomy/controls | Direct control }} |
| − | {{Infobox game/row/taxonomy/genres | }} | + | {{Infobox game/row/taxonomy/genres | Simulation, Vehicle simulator}} |
{{Infobox game/row/taxonomy/sports | }} | {{Infobox game/row/taxonomy/sports | }} | ||
| − | {{Infobox game/row/taxonomy/vehicles | }} | + | {{Infobox game/row/taxonomy/vehicles | Flight }} |
| − | {{Infobox game/row/taxonomy/art styles | }} | + | {{Infobox game/row/taxonomy/art styles | Realistic}} |
{{Infobox game/row/taxonomy/themes | }} | {{Infobox game/row/taxonomy/themes | }} | ||
| − | {{Infobox game/row/taxonomy/series | | + | {{Infobox game/row/taxonomy/series | }} |
|steam appid = | |steam appid = | ||
|steam appid side = | |steam appid side = | ||
| Line 34: | Line 36: | ||
|hltb = | |hltb = | ||
|igdb = <!-- Only needs to be set if there is no IGDB reception row --> | |igdb = <!-- Only needs to be set if there is no IGDB reception row --> | ||
| − | |lutris = | + | |lutris = flightgear/ |
| − | |mobygames = | + | |mobygames = 60588/flightgear/ |
|strategywiki = | |strategywiki = | ||
|wikipedia = FlightGear | |wikipedia = FlightGear | ||
| − | |winehq = | + | |winehq = 9104 |
|license = Freeware | |license = Freeware | ||
}} | }} | ||
| Line 44: | Line 46: | ||
{{Introduction | {{Introduction | ||
|introduction = | |introduction = | ||
| − | + | '''FlightGear Flight Simulator''' is a free, open-source, multi-platform, cooperative flight simulator development project made by [https://www.flightgear.org/ FlightGear.org]. It also simulates space flight in Earth's orbit. | |
| − | + | FlightGear's flight dynamics engine (JSBSim) is used in a [https://en.wikipedia.org/wiki/FlightGear#Benchmark_testing_by_NASA 2015 NASA benchmark] to judge new simulation code to the standards of the space industry. | |
| − | FlightGear's | + | FlightGear 2020.3 has over 700 aircraft and spacecraft projects<ref>{{Refurl|url=https://wiki.flightgear.org/Changelog_2020.3|title=Changelog 2020.3 - FlightGear wiki|date=2022-09-11}}</ref> that can be filtered by advancement level in art/FDM/systems in the launcher's browser<ref>{{Refurl|url=https://www.youtube.com/watch?v=a-UIrw7nEy4|title=Installing aircraft in FlightGear - the easy way - Youtube|date=2022-09-12}}</ref><ref>{{Refurl|url=https://wiki.flightgear.org/FlightGear_Qt_launcher|title=FlightGear Qt launcher - FlightGear wiki|date=2022-09-12}}</ref>. The rest are available through [https://wiki.flightgear.org/FlightGear_hangars#Third_party_sites 3rd party hangars] or from development repositories. It's used professionally for research and development, and is available for home desktop or DiY project users. |
| + | |||
| + | The project is more similar to Linux-type scientific software rather than "arcade" commercial flight simulators and flight games. Being open-source, the sim has received development from the science and engineering community.<ref>{{Refurl|url=https://wiki.flightgear.org/w/index.php?title=How_the_FlightGear_project_works&oldid=108424#Is_this_program_just_for_scientists_and_engineers.3F|title=How the FlightGear project works - FlightGear wiki|date=2022-09-15|snippet= FAQ: Question:Is this program just for scientists and engineers? Answer: No, but at least historically, the FlightGear project tends to attract certain types of people, many of them having some sort of academic background and some involvement or interest in aviation, i.e. in engineering, maths, physics, IT/computing or just real life pilots (hobby, professional, test pilots, retired). This applies especially to long-term contributors. Obviously, the people who contribute for a long time, get to shape the project more so than people who just happen to show up and post some ideas, features requests or bug reports. In part, this is also due to the reputation they get to enjoy among fellow contributors, so their feedback has automatically also more weight, too. That might explain why many long-term contributors seem to have a fairly similar mindset, and why some things are done the way they are. Some of these decisions are hard to understand without having a similar background, be it education, professional experience, families, real life obligations and such.}}</ref> | ||
| + | Some aspects of the simulators presentation, features, and project itself may go against common video game practices. Examples: | ||
| + | |||
| + | : <li> Multiple release streams: Long Term Stable (LTS), development previews, and nightly builds. These installs can exist side-by-side.</li> | ||
| + | |||
| + | : <li> Aircraft project updates since last LTS listed in changelogs are updated by the launcher before flying the moment they are available, and are often available for the previous LTS if compatible. The next branch has in-development aircraft. Scenery models and terrain improvements are automatically downloaded on demand. </li> | ||
| − | + | : <li> The sim is a command-line program like a lot of Linux software, and the launcher UI and the in-sim UI don't cover absolutely everything - e.g. highest AA settings. Command-line options change a property tree. However, the user can enter command-line options via the launcher, or edit the property tree using the in-sim menu.<ref>{{Refurl|url=https://wiki.flightgear.org/Command_line_options|title=Command line options - FlightGear wiki|date=2022-09-13}}</ref> </li> | |
| − | + | |release history = FlightGear 2020.3 was released for Windows, macOS, and Linux on the website on November 6, 2020. The release version was 2020.3.2, and it has been given updates since. See [https://wiki.flightgear.org/Changelog_2020.3 2020.3 Changelog]. | |
| − | + | 2020.3.7 added automatic downloading of 3d models of buildings, roads, cities etc. , based on Open StreetMap (OSM) data and automatic generation, for the whole world. This is intended to be used alongside [https://wiki.flightgear.org/Project3000#How_to_use_.28as_a_pilot.29 Project 3000] extra airport scenery. | |
| − | + | [https://wiki.flightgear.org/Addon Addons] in the official repository, like RedGriffinATC, have been updated since release. As of 2020.3.13, addons need to be downloaded manually, unlike aircraft in the official repository. | |
| − | |current state = | + | |current state = |
}} | }} | ||
==Availability== | ==Availability== | ||
{{Availability| | {{Availability| | ||
| − | {{Availability/row| | + | {{Availability/row| developer | https://www.flightgear.org/download/ | DRM-free | GPL source code is also available. | | Windows, OS X, Linux }} |
}} | }} | ||
| Line 71: | Line 80: | ||
|dlc = | |dlc = | ||
|expansion pack = | |expansion pack = | ||
| − | |freeware = | + | |freeware = The game is open-source. |
|free-to-play = | |free-to-play = | ||
|one-time game purchase = | |one-time game purchase = | ||
| Line 101: | Line 110: | ||
===Configuration file(s) location=== | ===Configuration file(s) location=== | ||
{{Game data| | {{Game data| | ||
| − | {{Game data/config|Windows|}} | + | {{Game data/config|Windows|{{P|userprofile}}\FlightGear\|{{P|userprofile\Documents}}\FlightGear ''(FlightGear 3.0 to FlightGear 2018.3)''|{{P|appdata}}\flightgear.org\ ''(Versions before FlightGear 3.0)''}} |
| + | {{Game data/config|OS X|{{p|osxhome}}/Library/Application Support/FlightGear}} | ||
| + | {{Game data/config|Linux|{{p|linuxhome}}/.fgfs/}} | ||
}} | }} | ||
| + | {{ii}} The user data location is known as [https://wiki.flightgear.org/$FG_HOME# $FG_HOME], it can be changed in many ways, including as an OS environment variable. It's where files for all types of user options and data are stored. There also sub-folders where significant amounts of downloaded data are stored e.g. Terrain data as the user flies (TerraSync data), aircraft, etc. If the user eventually runs out of space on a small hard drive this is where to clean out some data for regions the user doesn't fly in. See wiki for details. | ||
| + | {{ii}} It's possible to change the location of different types of data stored in $FG_HOME sub directories - e.g. terrain or aircraft folders in a separate data drive. The user can use '''Launcher > Settings > Downloads > Show more > change Downloads path for scenery and aircraft'''. | ||
| + | {{ii}} Some settings are not saved between sessions, if the user wants to set these [https://wiki.flightgear.org/Properties_persistent_between_sessions to be saved], or just change start up values, the user can just create an XML file and load it using the [https://wiki.flightgear.org/FlightGear_configuration_via_XML#Adding_your_own_settings <code>--config</code> option]. This applies to any property in the property tree e.g. startup state properties for specific aircraft, or new custom properties the user create for their projects. | ||
| + | {{ii}} Custom scenery and aircraft folders can be anywhere, and can be added through the launcher ('''Launcher > Add-ons''') as well as through any way that accepts FG command-line options. | ||
| + | {{ii}} If FlightGear data in an old location is found users will be prompted to move data to the new location, to save bandwidth re-downloading terrain, aircraft etc. | ||
===Save game data location=== | ===Save game data location=== | ||
{{Game data| | {{Game data| | ||
| − | {{Game data/saves|Windows|}} | + | {{Game data/saves|Windows|{{P|userprofile}}\FlightGear\aircraft-data}} |
| + | {{Game data/saves|OS X|}} | ||
| + | {{Game data/saves|Linux|}} | ||
}} | }} | ||
| + | {{ii}} Aircraft that can save complete state in mid-flight e.g. the Space Shuttle, Cessna 172P etc. have xml files in [https://wiki.flightgear.org/$FG_HOME $FG_HOME]\aircraft-data, or a subfolder like aircraft-data\SpaceShuttleSave. Aircraft that save some preferences or partial state will also use this folder. | ||
| + | <!-- | ||
===[[Glossary:Save game cloud syncing|Save game cloud syncing]]=== | ===[[Glossary:Save game cloud syncing|Save game cloud syncing]]=== | ||
{{Save game cloud syncing | {{Save game cloud syncing | ||
| Line 126: | Line 146: | ||
|xbox cloud notes = | |xbox cloud notes = | ||
}} | }} | ||
| + | --> | ||
==Video== | ==Video== | ||
| Line 135: | Line 156: | ||
|4k ultra hd wsgf award = | |4k ultra hd wsgf award = | ||
|widescreen resolution = true | |widescreen resolution = true | ||
| − | |widescreen resolution notes= | + | |widescreen resolution notes= Arbitrary resolution support. Configure via '''Launcher > settings > show more > window size > custom size''', or through relevant [https://wiki.flightgear.org/Command_line_options command-line option]. |
|multimonitor = true | |multimonitor = true | ||
| − | |multimonitor notes = | + | |multimonitor notes = Extremely versatile in type and combination of monitors used. See [https://wiki.flightgear.org/Howto:Configure_camera_view_windows configuring view windows], [https://wiki.flightgear.org/Howto:Activate_multi_core_and_multi_GPU_support how to activate multi core and multi GPU support] and [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.multiscreen data/docs/README.multiscreen]. |
|ultrawidescreen = true | |ultrawidescreen = true | ||
|ultrawidescreen notes = | |ultrawidescreen notes = | ||
| Line 143: | Line 164: | ||
|4k ultra hd notes = | |4k ultra hd notes = | ||
|fov = true | |fov = true | ||
| − | |fov notes = Default keys: x | + | |fov notes = Default keys: {{Key|X}} and {{Key|x}} to change FoV. Zooming in and out is meant to be used when clicking on 3d cockpits. Use extreme FoV like binoculars when looking at environment, or from airport tower views. ~0.1 to 120 degrees by default. See FlightGear Wiki: [https://wiki.flightgear.org/Field_of_view FoV article]. |
|windowed = true | |windowed = true | ||
|windowed notes = | |windowed notes = | ||
| Line 151: | Line 172: | ||
|anisotropic notes = | |anisotropic notes = | ||
|antialiasing = true | |antialiasing = true | ||
| − | |antialiasing notes = Use launcher. See [https://wiki.flightgear.org/Anti-aliasing wiki]. Use [https://wiki.flightgear.org/Command_line_options#Rendering_Options command-line options] to get higher AA: --prop:/sim/rendering/multi-samples=N , valid values for N | + | |antialiasing notes = Use launcher. See [https://wiki.flightgear.org/Anti-aliasing wiki]. Use [https://wiki.flightgear.org/Command_line_options#Rendering_Options command-line options] to get higher AA: <code>--prop:/sim/rendering/multi-samples=N</code>, valid values for <code>N</code> are 2x, 4x, 8x, 16x. Tansparency anti-aliasing (NVIDIA) or Adaptive anti-aliasing (AMD) can help with ground detail with overlays on<ref>{{Refurl|url=https://wiki.flightgear.org/Anti-aliasing#Transparency_anti-aliasing|title=Anti-aliasing - FlightGear wiki|date=2022-09-15}}</ref> |
| + | |upscaling = unknown | ||
| + | |upscaling tech = | ||
| + | |upscaling notes = | ||
|vsync = true | |vsync = true | ||
| − | |vsync notes = To hit | + | |vsync notes = To hit Vsync limits, unlock FPS throttle from '''in-sim menu > view > rendering'''. |
|60 fps = true | |60 fps = true | ||
|60 fps notes = | |60 fps notes = | ||
|120 fps = true | |120 fps = true | ||
| − | |120 fps notes = No | + | |120 fps notes = No limit once unlocked. Unlock FPS throttle from '''in-sim menu > view > rendering'''. |
|hdr = false | |hdr = false | ||
|hdr notes = | |hdr notes = | ||
| Line 167: | Line 191: | ||
==Input== | ==Input== | ||
| + | FlightGear allows complete control and interfacing with hardware, for more professional and DiY cockpit/hardware settings. See [https://wiki.flightgear.org/Input_device Input devices] wiki page to start, and [https://wiki.flightgear.org/Interfacing_FlightGear interfacing] for custom/complex hardware configurations. | ||
| + | |||
| + | Control axes from input can be used in any way to operate flight control surfaces - see [https://wiki.flightgear.org/Control_surfaces common plane surfaces]. This includes 2 axes from a mouse. Note for helicopters: Joysticks have a constant centering force, and don't reflect the way sticks work on helicopters - one solution is to remove springs if possible, another is to use a mouse for stick axes (or dual mouse on Linux) - see [https://wiki.flightgear.org/Howto:Fly_a_helicopter Helicopter flying]. Buttons/sliders/throttles from joysticks, keypads, or custom devices can also be set up to control different things in different contexts. | ||
| + | |||
| + | FlightGear can recognise input devices with profiles in XML text files. These profiles are just a starting point, and can be customised for the aircraft the user flies. See [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Input/Joysticks/ latest Joystick inputs], and [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Input/Event/ other input]. See the [https://forum.flightgear.org/viewforum.php?f=24 hardware section] on the forum and stickied threads for more profiles - console/gamepad controller profiles are also available. | ||
| + | |||
| + | Some common controls like joysticks with a constant centering force are unsuitable altogether for helicopter stick controls. The most needed range of motion for physical aircraft controls, needs to map to a ''compromise'' for the available range of the home control device. For example helicopter sticks have a large range of motion, but helicopters are flown with small wrist motions e.g. while resting the hand on a leg<ref>{{Refurl|url=https://www.youtube.com/watch?v=ysadvsXDVDU|title=How To Fly a Helicopter - Youtube|date=2022-09-14|snippet=See Cyclic stick section from 1m 20s}}</ref>. The range of input will differ by typical activity - e.g. transport flying to aerobatics. | ||
| + | |||
{{Input | {{Input | ||
| − | |key remap = | + | |key remap = true |
| − | |key remap notes = | + | |key remap notes = Possible to have complex key remap bindings, combinations, contexts for different keypad hardware or joystick buttons (not just keyboard) and aircraft. Done via editing XML files. See [https://wiki.flightgear.org/Howto:Reassign_keyboard_bindings Howto:Reassign_keyboard_bindings]. Players are expected to fine-tune sensitivities and controls, including in text files. |
|acceleration option = unknown | |acceleration option = unknown | ||
|acceleration option notes = | |acceleration option notes = | ||
| − | |mouse sensitivity = | + | |mouse sensitivity = true |
| − | |mouse sensitivity notes = | + | |mouse sensitivity notes = Done via XML files for different axes in different contexts, completely customisable. Simple sensitivity via menu on post-2020.3 nightlies. Keyboard + mouse control possible, but harder to fly most aircraft without an axis for rudder. Use LMB+mouse movement for rudder, or less preferably use auto-coordination. Can use mouse for stick axes for helicopters if centering force on joystick is uncomfortable. Defaults are {{key|Tab}} to cycle mouse control modes: aircraft flight control, cockpit & UI manipulation ({{key|Ctrl}}+{{key|c}} to highlight interactive elements), view. |
| − | |mouse menu = | + | |mouse menu = true |
| − | |mouse menu notes = | + | |mouse menu notes = 2 schemes: old RMB to look around in all 3 mouse modes, use RMB to cycle modes. Users are expected to move camera around to emulate moving head around to better look at cockpit, see data/mice.xml for controls in modes (e.g. hold {{key|Ctrl}} or RMB + mouse movement). |
| − | |invert mouse y-axis = | + | |invert mouse y-axis = true |
|invert mouse y-axis notes = | |invert mouse y-axis notes = | ||
| − | |touchscreen = | + | |touchscreen = true |
|touchscreen notes = | |touchscreen notes = | ||
| − | |controller support = | + | |controller support = true |
| − | |controller support notes = | + | |controller support notes = Search forum [https://forum.flightgear.org/viewforum.php?f=24&sid=36da74c27c0876bacb83d540102434ad hardware section] for more controller profiles. |
|full controller = unknown | |full controller = unknown | ||
|full controller notes = | |full controller notes = | ||
| − | |controller remap = | + | |controller remap = true |
| − | |controller remap notes = | + | |controller remap notes = There is a fgjs/jsdemo [https://wiki.flightgear.org/Input_device#Adding_support_for_your_joystick configuration utility] for new/unknown hardware. |
| − | |controller sensitivity = | + | |controller sensitivity = true |
|controller sensitivity notes= | |controller sensitivity notes= | ||
|invert controller y-axis = unknown | |invert controller y-axis = unknown | ||
| Line 208: | Line 240: | ||
|tracked motion prompts = unknown | |tracked motion prompts = unknown | ||
|tracked motion prompts notes = | |tracked motion prompts notes = | ||
| − | |other controllers = | + | |other controllers = true |
| − | |other controllers notes = | + | |other controllers notes = All sorts of flight hardware, incl. flight sticks, yokes, rubber pedals, throttles, as well as Wii Remote.<ref>{{Refurl|url=https://github.com/uglyDwarf/linuxtrack/wiki/Input-Devices|title= Input Devices - Linux Track|date=2022-09-14}}</ref> Search forum [https://forum.flightgear.org/viewforum.php?f=24&sid=36da74c27c0876bacb83d540102434ad hardware section] for more hardware profiles. |
|other button prompts = unknown | |other button prompts = unknown | ||
|other button prompts notes= | |other button prompts notes= | ||
|controller hotplug = unknown | |controller hotplug = unknown | ||
|controller hotplug notes = | |controller hotplug notes = | ||
| − | |haptic feedback = | + | |haptic feedback = true |
| − | |haptic feedback notes = | + | |haptic feedback notes = See [https://wiki.flightgear.org/Force_feedback Force Feedback]. |
| − | |simultaneous input = | + | |simultaneous input = true |
|simultaneous input notes = | |simultaneous input notes = | ||
|steam input api = unknown | |steam input api = unknown | ||
| Line 232: | Line 264: | ||
==Audio== | ==Audio== | ||
{{Audio | {{Audio | ||
| − | |separate volume = | + | |separate volume = true |
|separate volume notes = | |separate volume notes = | ||
|surround sound = unknown | |surround sound = unknown | ||
|surround sound notes = | |surround sound notes = | ||
| − | |subtitles = | + | |subtitles = true |
| − | |subtitles notes = | + | |subtitles notes = |
|closed captions = unknown | |closed captions = unknown | ||
|closed captions notes = | |closed captions notes = | ||
|mute on focus lost = unknown | |mute on focus lost = unknown | ||
|mute on focus lost notes = | |mute on focus lost notes = | ||
| − | |eax support = | + | |eax support = true |
|eax support notes = | |eax support notes = | ||
| + | |royalty free audio = unknown | ||
| + | |royalty free audio notes = | ||
|red book cd audio = | |red book cd audio = | ||
|red book cd audio notes = | |red book cd audio notes = | ||
| Line 257: | Line 291: | ||
|audio = unknown | |audio = unknown | ||
|subtitles = unknown | |subtitles = unknown | ||
| + | |notes = | ||
| + | |fan = | ||
| + | |ref = | ||
| + | }} | ||
| + | {{L10n/switch | ||
| + | |language = Simplified Chinese | ||
| + | |interface = true | ||
| + | |audio = n/a | ||
| + | |subtitles = n/a | ||
|notes = | |notes = | ||
|fan = | |fan = | ||
| Line 317: | Line 360: | ||
|notes = | |notes = | ||
|fan = | |fan = | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{L10n/switch | {{L10n/switch | ||
| Line 334: | Line 368: | ||
|notes = Translated manual. | |notes = Translated manual. | ||
|fan = | |fan = | ||
| − | |||
}} | }} | ||
{{L10n/switch | {{L10n/switch | ||
| Line 358: | Line 391: | ||
|online play = true | |online play = true | ||
|online play players = | |online play players = | ||
| − | |online play modes = | + | |online play modes = Co-op |
| − | |online play notes = | + | |online play notes = Supports both FlightGear-specific servers and the VATSIM cross-sim network. See [https://wiki.flightgear.org/Howto:Multiplayer How to: Multiplayer]. |
|asynchronous = | |asynchronous = | ||
|asynchronous notes = | |asynchronous notes = | ||
| Line 367: | Line 400: | ||
|p2p = | |p2p = | ||
|p2p notes = | |p2p notes = | ||
| − | |dedicated = | + | |dedicated = true |
|dedicated notes = | |dedicated notes = | ||
|self-hosting = | |self-hosting = | ||
| Line 377: | Line 410: | ||
|udp = | |udp = | ||
|upnp = | |upnp = | ||
| + | }} | ||
| + | |||
| + | ==VR support== | ||
| + | {{VR support | ||
| + | |gg3d name = | ||
| + | |native 3d gg3d award = | ||
| + | |nvidia 3d vision gg3d award = | ||
| + | |tridef 3d gg3d award = | ||
| + | |iz3d gg3d award = | ||
| + | |native 3d = true | ||
| + | |native 3d notes = Only confirmed with red-blue glasses.<ref>{{Refurl|url=https://wiki.flightgear.org/Anaglyph_(3D)|title=Anaglyph (3D) - FlightGear Wiki|date=6 June 2023}}</ref> | ||
| + | |nvidia 3d vision = false | ||
| + | |nvidia 3d vision notes = | ||
| + | |tridef 3d = unknown | ||
| + | |tridef 3d notes = | ||
| + | |iz3d = unknown | ||
| + | |iz3d notes = | ||
| + | |vr only = false | ||
| + | |vorpx = unknown | ||
| + | |vorpx modes = | ||
| + | |vorpx notes = | ||
| + | |htc vive = true | ||
| + | |htc vive notes = As of Sept. 2022, VR headset users should look at the next branch (mainly tested on Linux)<ref>{{Refurl|url=https://wiki.flightgear.org/Virtual_Reality#Status|title=Virtual reality support - FlightGear wiki|date=2022-09-13}}.</ref> | ||
| + | |oculus rift = true | ||
| + | |oculus rift notes = | ||
| + | |osvr = unknown | ||
| + | |osvr notes = | ||
| + | |windows mixed reality = false | ||
| + | |windows mixed reality notes = | ||
| + | |keyboard-mouse = unknown | ||
| + | |keyboard-mouse notes = | ||
| + | |3rd space gaming vest = unknown | ||
| + | |3rd space gaming vest notes = | ||
| + | |novint falcon = unknown | ||
| + | |novint falcon notes = | ||
| + | |trackir = true | ||
| + | |trackir notes = | ||
| + | |tobii eye tracking = unknown | ||
| + | |tobii eye tracking notes = | ||
| + | |play area seated = unknown | ||
| + | |play area seated notes = | ||
| + | |play area standing = unknown | ||
| + | |play area standing notes = | ||
| + | |play area room-scale = unknown | ||
| + | |play area room-scale notes = | ||
}} | }} | ||
| Line 389: | Line 467: | ||
|wing notes = | |wing notes = | ||
|opengl versions = | |opengl versions = | ||
| − | |opengl notes = Try for at least 2. | + | |opengl notes = Try for at least 2.{{cn}} |
|glide versions = | |glide versions = | ||
|glide notes = | |glide notes = | ||
| Line 403: | Line 481: | ||
|dos modes notes = | |dos modes notes = | ||
|shader model versions = | |shader model versions = | ||
| − | |shader model notes = Newer renderers like ALS use higher shader models, as features are enabled. There's a fallback system for specific effects. Still supports old default renderer without shaders. | + | |shader model notes = Newer renderers like ALS use higher shader models, as features are enabled. There's a fallback system for specific effects. Still supports old "default" renderer without shaders. |
|windows 32-bit exe = unknown | |windows 32-bit exe = unknown | ||
|windows 64-bit exe = true | |windows 64-bit exe = true | ||
|windows arm app = unknown | |windows arm app = unknown | ||
|windows exe notes = | |windows exe notes = | ||
| − | |mac os x powerpc app = | + | |mac os x powerpc app = unknown |
|macos intel 32-bit app = unknown | |macos intel 32-bit app = unknown | ||
|macos intel 64-bit app = true | |macos intel 64-bit app = true | ||
|macos arm app = unknown | |macos arm app = unknown | ||
|macos app notes = | |macos app notes = | ||
| − | |linux powerpc app = | + | |linux powerpc app = true |
| − | |linux 32-bit executable= | + | |linux 32-bit executable= true |
|linux 64-bit executable= true | |linux 64-bit executable= true | ||
| − | |linux arm app = | + | |linux arm app = true |
| − | |linux executable notes = | + | |linux executable notes = <ref>{{Refurl|url=https://rpmfind.net/linux/rpm2html/search.php?query=flightgear|title=RPM resource flightgear - Rpmfind|date=4 June 2023}}</ref> |
}} | }} | ||
| Line 439: | Line 517: | ||
==System requirements== | ==System requirements== | ||
| − | + | A larger range of hardware is supported than normally expected, and can run on non-gaming (e.g. weak GPU or laptop) hardware and complex configurations<ref>{{Refurl|url=https://en.wikipedia.org/wiki/FlightGear#Applications_and_usages|title=FlightGear#Applications and usages - Wikipedia|date=2022-09-12}}</ref> alike, like having multiple instances of FlightGear on different devices running limited parts of the sim following a master instance, effectively distributing functionality across multiple embedded processors/systems over LAN or internet.<ref>{{Refurl|url=https://wiki.flightgear.org/Data_Distribution_Services_support|title=Data_Distribution Services support|date=2022-09-12}}</ref><ref>{{Refurl|url=https://wiki.flightgear.org/List_of_Android_apps_to_use_with_FlightGear|title=List_of_Android apps to use with FlightGear - FlightGear wiki|date=2022-09-12}}</ref><ref>{{Refurl|url=https://wiki.flightgear.org/Phi|title=Phi - FlightGear Wiki|date=2022-09-12}}</ref><ref>{{Refurl|url=https://wiki.flightgear.org/Raspberry_OS_setup|title=Raspberry OS setup|date=2022-09-12}}</ref><ref>{{Refurl|url=https://www.youtube.com/watch?v=8MODOU447EE|title=Radio Panel Airbus. FG Interface Powered - Youtube video|date=2022-09-12}}</ref> | |
FlightGear can scale to a huge range of hardware. FlightGear keeps renderers from older eras, has lots of settings configurability, has multiple weather and physics engines with differing requirements, and is backwards compatible with older versions of aircraft.<ref>{{Refurl|url=https://wiki.flightgear.org/Hardware_recommendations FlightGear|title=Hardware reconmendations - FlightGear wiki|date=2022-09-12}}</ref> | FlightGear can scale to a huge range of hardware. FlightGear keeps renderers from older eras, has lots of settings configurability, has multiple weather and physics engines with differing requirements, and is backwards compatible with older versions of aircraft.<ref>{{Refurl|url=https://wiki.flightgear.org/Hardware_recommendations FlightGear|title=Hardware reconmendations - FlightGear wiki|date=2022-09-12}}</ref> | ||
| − | For marginal systems it's recommended for people to try running latest FG with lower settings, older renderers like shaderless, older terrain (e.g. WS 1.0), older aircraft, or less complex aircraft, before switching to older FlightGear versions. | + | For marginal systems it's recommended for people to try running latest FG with lower settings, older renderers like shaderless, older terrain (e.g. WS 1.0), older aircraft, or less complex aircraft, before switching to older FlightGear versions. Try turning off world-wide AI traffic as it can be demanding. |
| − | |||
| − | |||
| − | |||
| − | |||
See wiki pages for requirements: | See wiki pages for requirements: | ||
| − | * [https://wiki.flightgear.org/Minimal_Startup_Profile FlightGear Minimum Startup Profile] | + | * [https://wiki.flightgear.org/Minimal_Startup_Profile FlightGear Minimum Startup Profile] - on marginal systems can use this and turn settings up one by one. |
* [https://wiki.flightgear.org/Hardware_recommendations FlightGear Hardware recommendations] | * [https://wiki.flightgear.org/Hardware_recommendations FlightGear Hardware recommendations] | ||
* [https://wiki.flightgear.org/OSM2City_1st_Worldbuild#Performance Performance tips for worldwide 3d buildings, roads, cities (2020.3.7 and later)] | * [https://wiki.flightgear.org/OSM2City_1st_Worldbuild#Performance Performance tips for worldwide 3d buildings, roads, cities (2020.3.7 and later)] | ||
| Line 456: | Line 530: | ||
* [https://mirrors.ibiblio.org/flightgear/ftp/ Aircraft from older versions of FlightGear] | * [https://mirrors.ibiblio.org/flightgear/ftp/ Aircraft from older versions of FlightGear] | ||
| + | FlightGear has been [https://www.youtube.com/watch?v=tiXkN9WA8ng shown] working on Steam Deck (July 2022). | ||
| + | {{ii}} Graphics settings are turned off so the sim starts up on non-gaming or older hardware. Renderers from older eras like "Default" or "Rembrandt" remain available - e.g FlightGear 2020.3 still supports 3D graphics without shaders at lower settings in the "Default" renderer. Turn on view/rendering and environment settings with menu inside the simulator as well as launcher menu. | ||
| + | {{ii}} The following, taken from the official FlightGear wiki, should be considered a baseline for higher quality settings at 1080p. As stated above, what airplane is being flown, how detailed the underlying simulation, the renderer and detail of rendering, etc., will change these requirements. | ||
{{System requirements | {{System requirements | ||
|OSfamily = Windows | |OSfamily = Windows | ||
|minOS = | |minOS = | ||
| − | |minCPU = | + | |minCPU = Intel Core i5-2500 |
| − | |minRAM = | + | |minRAM = 8 GB |
|minHD = | |minHD = | ||
| − | |minGPU = | + | |minGPU = Nvidia GeForce GTX 960 |
|recOS = | |recOS = | ||
| − | |recCPU = | + | |recCPU = Intel Core i5-4xxx series |
| − | |recRAM = | + | |recCPU2 = AMD Ryzen series |
| + | |recRAM = 16 GB | ||
|recHD = | |recHD = | ||
| − | |recGPU = | + | |recGPU = Nvidia GeForce GTX 1050 Ti |
| − | |notes = | + | |notes = System requirements for high-ish settings at 1080p. FlightGear can run on much lower spec hardware, including with recent integrated GPUs. Max-ish settings need better hardware, GTX 1060+ at 1080p. |
| + | |ref = <ref name="FlightGear_2018-3_sysreq">{{Refurl|url=https://wiki.flightgear.org/Hardware_recommendations#Hardware_build:|title=FlightGear Wiki - Hardware build|date=2022-09-12}}</ref> | ||
}} | }} | ||
| Line 478: | Line 557: | ||
{{System requirements | {{System requirements | ||
|OSfamily = OS X | |OSfamily = OS X | ||
| − | |||
|minOS = | |minOS = | ||
| − | |minCPU = | + | |minCPU = Intel Core i5-2500 |
| − | |minRAM = | + | |minRAM = 8 GB |
|minHD = | |minHD = | ||
| − | |minGPU = | + | |minGPU = Nvidia GeForce GTX 960 |
|recOS = | |recOS = | ||
| − | |recCPU = | + | |recCPU = Intel Core i5-4xxx series |
| − | |recRAM = | + | |recCPU2 = AMD Ryzen series |
| + | |recRAM = 16 GB | ||
|recHD = | |recHD = | ||
| − | |recGPU = | + | |recGPU = Nvidia GeForce GTX 1050 Ti |
| − | |notes = | + | |notes = System requirements for high-ish settings. FlightGear can run on much lower spec hardware. |
| + | |ref = <ref name="FlightGear_2018-3_sysreq"/> | ||
}} | }} | ||
| Line 497: | Line 577: | ||
{{System requirements | {{System requirements | ||
|OSfamily = Linux | |OSfamily = Linux | ||
| − | |||
|minOS = | |minOS = | ||
| − | |minCPU = | + | |minCPU = Intel Core i5-2500 |
| − | |minRAM = | + | |minRAM = 8 GB |
|minHD = | |minHD = | ||
| − | |minGPU = | + | |minGPU = Nvidia GeForce GTX 960 |
|recOS = | |recOS = | ||
| − | |recCPU = | + | |recCPU = Intel Core i5-4xxx series |
| − | |recRAM = | + | |recCPU2 = AMD Ryzen series |
| + | |recRAM = 16 GB | ||
|recHD = | |recHD = | ||
| − | |recGPU = | + | |recGPU = Nvidia GeForce GTX 1050 Ti |
| − | |notes = | + | |notes = System requirements for high-ish settings. FlightGear can run on much lower spec hardware. |
| − | + | |ref = <ref name="FlightGear_2018-3_sysreq"/> | |
| − | |||
}} | }} | ||
{{References}} | {{References}} | ||
Latest revision as of 17:33, 4 December 2023
This page is a stub: it lacks content and/or basic article components. You can help to expand this page
by adding an image or additional information.
This page may require cleanup to meet basic quality standards. The specific problem is: (Dandelion Sprout:) Various paragraphs need to be compressed quite a lot to make them easier to read. You can help by modifying
the article. The discussion page may contain useful suggestions.
Although this product has been released, it remains under active development - information may change frequently and could be outdated or irrelevant.
 |
|
| Developers | |
|---|---|
| FlightGear.org developers & contributors | |
| Release dates | |
| Windows | December 17, 2007[1] |
| macOS (OS X) | December 17, 2007 |
| Linux | December 17, 2007 |
| Taxonomy | |
| Monetization | Freeware |
| Modes | Singleplayer, Multiplayer |
| Pacing | Relaxed |
| Perspectives | First-person, Third-person |
| Controls | Direct control |
| Genres | Simulation, Vehicle simulator |
| Vehicles | Flight |
| Art styles | Realistic |
 |
|
FlightGear Flight Simulator is a free, open-source, multi-platform, cooperative flight simulator development project made by FlightGear.org. It also simulates space flight in Earth's orbit.
FlightGear's flight dynamics engine (JSBSim) is used in a 2015 NASA benchmark to judge new simulation code to the standards of the space industry.
FlightGear 2020.3 has over 700 aircraft and spacecraft projects[2] that can be filtered by advancement level in art/FDM/systems in the launcher's browser[3][4]. The rest are available through 3rd party hangars or from development repositories. It's used professionally for research and development, and is available for home desktop or DiY project users.
The project is more similar to Linux-type scientific software rather than "arcade" commercial flight simulators and flight games. Being open-source, the sim has received development from the science and engineering community.[5] Some aspects of the simulators presentation, features, and project itself may go against common video game practices. Examples:
- Multiple release streams: Long Term Stable (LTS), development previews, and nightly builds. These installs can exist side-by-side.
- Aircraft project updates since last LTS listed in changelogs are updated by the launcher before flying the moment they are available, and are often available for the previous LTS if compatible. The next branch has in-development aircraft. Scenery models and terrain improvements are automatically downloaded on demand.
- The sim is a command-line program like a lot of Linux software, and the launcher UI and the in-sim UI don't cover absolutely everything - e.g. highest AA settings. Command-line options change a property tree. However, the user can enter command-line options via the launcher, or edit the property tree using the in-sim menu.[6]
FlightGear 2020.3 was released for Windows, macOS, and Linux on the website on November 6, 2020. The release version was 2020.3.2, and it has been given updates since. See 2020.3 Changelog.
2020.3.7 added automatic downloading of 3d models of buildings, roads, cities etc. , based on Open StreetMap (OSM) data and automatic generation, for the whole world. This is intended to be used alongside Project 3000 extra airport scenery.
Addons in the official repository, like RedGriffinATC, have been updated since release. As of 2020.3.13, addons need to be downloaded manually, unlike aircraft in the official repository.
Availability
| Source | DRM | Notes | Keys | OS |
|---|---|---|---|---|
| Developer website | |
GPL source code is also available. | |
Monetization
| Type | Notes |
|---|---|
| Freeware | The game is open-source. |
Microtransactions
| Type | Notes |
|---|---|
| No microtransactions | None |
Game data
Configuration file(s) location
| System | Location |
|---|---|
| Windows | %USERPROFILE%\FlightGear\ %USERPROFILE%\Documents\FlightGear (FlightGear 3.0 to FlightGear 2018.3) %APPDATA%\flightgear.org\ (Versions before FlightGear 3.0) |
| macOS (OS X) | $HOME/Library/Application Support/FlightGear |
| Linux | $HOME/.fgfs/ |
- The user data location is known as $FG_HOME, it can be changed in many ways, including as an OS environment variable. It's where files for all types of user options and data are stored. There also sub-folders where significant amounts of downloaded data are stored e.g. Terrain data as the user flies (TerraSync data), aircraft, etc. If the user eventually runs out of space on a small hard drive this is where to clean out some data for regions the user doesn't fly in. See wiki for details.
- It's possible to change the location of different types of data stored in $FG_HOME sub directories - e.g. terrain or aircraft folders in a separate data drive. The user can use Launcher > Settings > Downloads > Show more > change Downloads path for scenery and aircraft.
- Some settings are not saved between sessions, if the user wants to set these to be saved, or just change start up values, the user can just create an XML file and load it using the
--configoption. This applies to any property in the property tree e.g. startup state properties for specific aircraft, or new custom properties the user create for their projects. - Custom scenery and aircraft folders can be anywhere, and can be added through the launcher (Launcher > Add-ons) as well as through any way that accepts FG command-line options.
- If FlightGear data in an old location is found users will be prompted to move data to the new location, to save bandwidth re-downloading terrain, aircraft etc.
Save game data location
| System | Location |
|---|---|
| Windows | %USERPROFILE%\FlightGear\aircraft-data |
| macOS (OS X) | |
| Linux |
- Aircraft that can save complete state in mid-flight e.g. the Space Shuttle, Cessna 172P etc. have xml files in $FG_HOME\aircraft-data, or a subfolder like aircraft-data\SpaceShuttleSave. Aircraft that save some preferences or partial state will also use this folder.
Video
| Graphics feature | State | Notes | |
|---|---|---|---|
| Widescreen resolution | Arbitrary resolution support. Configure via Launcher > settings > show more > window size > custom size, or through relevant command-line option. | ||
| Multi-monitor | Extremely versatile in type and combination of monitors used. See configuring view windows, how to activate multi core and multi GPU support and data/docs/README.multiscreen. | ||
| Ultra-widescreen | |||
| 4K Ultra HD | |||
| Field of view (FOV) | Default keys: X and x to change FoV. Zooming in and out is meant to be used when clicking on 3d cockpits. Use extreme FoV like binoculars when looking at environment, or from airport tower views. ~0.1 to 120 degrees by default. See FlightGear Wiki: FoV article. | ||
| Windowed | |||
| Borderless fullscreen windowed | |||
| Anisotropic filtering (AF) | |||
| Anti-aliasing (AA) | Use launcher. See wiki. Use command-line options to get higher AA: --prop:/sim/rendering/multi-samples=N, valid values for N are 2x, 4x, 8x, 16x. Tansparency anti-aliasing (NVIDIA) or Adaptive anti-aliasing (AMD) can help with ground detail with overlays on[7] |
||
| Vertical sync (Vsync) | To hit Vsync limits, unlock FPS throttle from in-sim menu > view > rendering. | ||
| 60 FPS and 120+ FPS | No limit once unlocked. Unlock FPS throttle from in-sim menu > view > rendering. | ||
| High dynamic range display (HDR) | |||
| Ray tracing (RT) | |||
Input
FlightGear allows complete control and interfacing with hardware, for more professional and DiY cockpit/hardware settings. See Input devices wiki page to start, and interfacing for custom/complex hardware configurations.
Control axes from input can be used in any way to operate flight control surfaces - see common plane surfaces. This includes 2 axes from a mouse. Note for helicopters: Joysticks have a constant centering force, and don't reflect the way sticks work on helicopters - one solution is to remove springs if possible, another is to use a mouse for stick axes (or dual mouse on Linux) - see Helicopter flying. Buttons/sliders/throttles from joysticks, keypads, or custom devices can also be set up to control different things in different contexts.
FlightGear can recognise input devices with profiles in XML text files. These profiles are just a starting point, and can be customised for the aircraft the user flies. See latest Joystick inputs, and other input. See the hardware section on the forum and stickied threads for more profiles - console/gamepad controller profiles are also available.
Some common controls like joysticks with a constant centering force are unsuitable altogether for helicopter stick controls. The most needed range of motion for physical aircraft controls, needs to map to a compromise for the available range of the home control device. For example helicopter sticks have a large range of motion, but helicopters are flown with small wrist motions e.g. while resting the hand on a leg[8]. The range of input will differ by typical activity - e.g. transport flying to aerobatics.
| Keyboard and mouse, touch | State | Notes |
|---|---|---|
| Remapping | Possible to have complex key remap bindings, combinations, contexts for different keypad hardware or joystick buttons (not just keyboard) and aircraft. Done via editing XML files. See Howto:Reassign_keyboard_bindings. Players are expected to fine-tune sensitivities and controls, including in text files. | |
| Mouse acceleration | ||
| Mouse sensitivity | Done via XML files for different axes in different contexts, completely customisable. Simple sensitivity via menu on post-2020.3 nightlies. Keyboard + mouse control possible, but harder to fly most aircraft without an axis for rudder. Use LMB+mouse movement for rudder, or less preferably use auto-coordination. Can use mouse for stick axes for helicopters if centering force on joystick is uncomfortable. Defaults are Tab ↹ to cycle mouse control modes: aircraft flight control, cockpit & UI manipulation (Ctrl+c to highlight interactive elements), view. | |
| Mouse input in menus | 2 schemes: old RMB to look around in all 3 mouse modes, use RMB to cycle modes. Users are expected to move camera around to emulate moving head around to better look at cockpit, see data/mice.xml for controls in modes (e.g. hold Ctrl or RMB + mouse movement). | |
| Mouse Y-axis inversion | ||
| Touchscreen optimised | ||
| Controller | ||
| Controller support | Search forum hardware section for more controller profiles. | |
| Full controller support | ||
| Controller remapping | There is a fgjs/jsdemo configuration utility for new/unknown hardware. | |
| Controller sensitivity | ||
| Controller Y-axis inversion |
| Controller types |
|---|
| XInput-compatible controllers |
|---|
| PlayStation controllers |
|---|
| Tracked motion controllers |
|---|
| Generic/other controllers | All sorts of flight hardware, incl. flight sticks, yokes, rubber pedals, throttles, as well as Wii Remote.[9] Search forum hardware section for more hardware profiles. | |
|---|---|---|
| Button prompts |
| Additional information | ||
|---|---|---|
| Controller hotplugging | ||
| Haptic feedback | See Force Feedback. | |
| Digital movement supported | ||
| Simultaneous controller+KB/M |
Audio
| Audio feature | State | Notes |
|---|---|---|
| Separate volume controls | ||
| Surround sound | ||
| Subtitles | ||
| Closed captions | ||
| Mute on focus lost | ||
| EAX support | ||
| Royalty free audio |
Localizations
See FGData/translations for new language updates to the latest 2020.3 LTS release.
| Language | UI | Audio | Sub | Notes |
|---|---|---|---|---|
| English | ||||
| Simplified Chinese | ||||
| Dutch | ||||
| French | Translated manual. | |||
| German | Translated manual. | |||
| Italian | Translated manual. | |||
| Polish | Translated manual. | |||
| Russian | ||||
| Turkish | ||||
| Slovak | Translated manual. | |||
| Spanish | Translated manual. |
Network
Multiplayer types
| Type | Native | Notes | |
|---|---|---|---|
| Local play | |||
| LAN play | |||
| Online play | Co-op Supports both FlightGear-specific servers and the VATSIM cross-sim network. See How to: Multiplayer. |
||
Connection types
| Type | Native | Notes |
|---|---|---|
| Dedicated |
VR support
| 3D modes | State | Notes | |
|---|---|---|---|
| Native 3D | Only confirmed with red-blue glasses.[10] | ||
| Nvidia 3D Vision | |||
| Headsets | |||
|---|---|---|---|
| SteamVR | As of Sept. 2022, VR headset users should look at the next branch (mainly tested on Linux)[11] | ||
| Oculus VR (LibOVR) | |||
| Windows Mixed Reality | This game might be playable with the Revive Compatibility Layer, or Windows Mixed Reality for SteamVR. | ||
| Devices | |||
|---|---|---|---|
| Tracked motion controllers | |||
| Traditional controller | See Input for details. | ||
| Keyboard/Mouse | |||
| TrackIR | |||
| Play area | |||
|---|---|---|---|
| Seated | |||
| Standing | |||
| Room-scale | |||
Other information
API
| Executable | PPC | 32-bit | 64-bit | ARM | Notes |
|---|---|---|---|---|---|
| Windows | |||||
| macOS (OS X) | |||||
| Linux | [12] |
Middleware
- No middleware information; you can edit this page to add it.
System requirements
A larger range of hardware is supported than normally expected, and can run on non-gaming (e.g. weak GPU or laptop) hardware and complex configurations[13] alike, like having multiple instances of FlightGear on different devices running limited parts of the sim following a master instance, effectively distributing functionality across multiple embedded processors/systems over LAN or internet.[14][15][16][17][18]
FlightGear can scale to a huge range of hardware. FlightGear keeps renderers from older eras, has lots of settings configurability, has multiple weather and physics engines with differing requirements, and is backwards compatible with older versions of aircraft.[19]
For marginal systems it's recommended for people to try running latest FG with lower settings, older renderers like shaderless, older terrain (e.g. WS 1.0), older aircraft, or less complex aircraft, before switching to older FlightGear versions. Try turning off world-wide AI traffic as it can be demanding.
See wiki pages for requirements:
- FlightGear Minimum Startup Profile - on marginal systems can use this and turn settings up one by one.
- FlightGear Hardware recommendations
- Performance tips for worldwide 3d buildings, roads, cities (2020.3.7 and later)
- Example screenshots of appearance when using equivalent of GTX 1050 Ti or higher at 1080p, at 25+ FPS, with 4 core i5 or equivalent CPU.
- Aircraft from older versions of FlightGear
FlightGear has been shown working on Steam Deck (July 2022).
- Graphics settings are turned off so the sim starts up on non-gaming or older hardware. Renderers from older eras like "Default" or "Rembrandt" remain available - e.g FlightGear 2020.3 still supports 3D graphics without shaders at lower settings in the "Default" renderer. Turn on view/rendering and environment settings with menu inside the simulator as well as launcher menu.
- The following, taken from the official FlightGear wiki, should be considered a baseline for higher quality settings at 1080p. As stated above, what airplane is being flown, how detailed the underlying simulation, the renderer and detail of rendering, etc., will change these requirements.
| Windows | ||
|---|---|---|
| Minimum[20] | Recommended | |
| Operating system (OS) | ||
| Processor (CPU) | Intel Core i5-2500 | Intel Core i5-4xxx series AMD Ryzen series |
| System memory (RAM) | 8 GB | 16 GB |
| Hard disk drive (HDD) | ||
| Video card (GPU) | Nvidia GeForce GTX 960 | Nvidia GeForce GTX 1050 Ti |
| macOS (OS X) | ||
|---|---|---|
| Minimum[20] | Recommended | |
| Operating system (OS) | ||
| Processor (CPU) | Intel Core i5-2500 | Intel Core i5-4xxx series AMD Ryzen series |
| System memory (RAM) | 8 GB | 16 GB |
| Hard disk drive (HDD) | ||
| Video card (GPU) | Nvidia GeForce GTX 960 | Nvidia GeForce GTX 1050 Ti |
| Linux | ||
|---|---|---|
| Minimum[20] | Recommended | |
| Operating system (OS) | ||
| Processor (CPU) | Intel Core i5-2500 | Intel Core i5-4xxx series AMD Ryzen series |
| System memory (RAM) | 8 GB | 16 GB |
| Hard disk drive (HDD) | ||
| Video card (GPU) | Nvidia GeForce GTX 960 | Nvidia GeForce GTX 1050 Ti |
References
- ↑ FlightGear Wiki - last accessed on December 4, 2023
- ↑ Changelog 2020.3 - FlightGear wiki - last accessed on 2022-09-11
- ↑ Installing aircraft in FlightGear - the easy way - Youtube - last accessed on 2022-09-12
- ↑ FlightGear Qt launcher - FlightGear wiki - last accessed on 2022-09-12
- ↑ How the FlightGear project works - FlightGear wiki - last accessed on 2022-09-15
- "FAQ: Question:Is this program just for scientists and engineers? Answer: No, but at least historically, the FlightGear project tends to attract certain types of people, many of them having some sort of academic background and some involvement or interest in aviation, i.e. in engineering, maths, physics, IT/computing or just real life pilots (hobby, professional, test pilots, retired). This applies especially to long-term contributors. Obviously, the people who contribute for a long time, get to shape the project more so than people who just happen to show up and post some ideas, features requests or bug reports. In part, this is also due to the reputation they get to enjoy among fellow contributors, so their feedback has automatically also more weight, too. That might explain why many long-term contributors seem to have a fairly similar mindset, and why some things are done the way they are. Some of these decisions are hard to understand without having a similar background, be it education, professional experience, families, real life obligations and such."
- ↑ Command line options - FlightGear wiki - last accessed on 2022-09-13
- ↑ Anti-aliasing - FlightGear wiki - last accessed on 2022-09-15
- ↑ How To Fly a Helicopter - Youtube - last accessed on 2022-09-14
- "See Cyclic stick section from 1m 20s"
- ↑ Input Devices - Linux Track - last accessed on 2022-09-14
- ↑ Anaglyph (3D) - FlightGear Wiki - last accessed on 6 June 2023
- ↑ Virtual reality support - FlightGear wiki - last accessed on 2022-09-13.
- ↑ RPM resource flightgear - Rpmfind - last accessed on 4 June 2023
- ↑ FlightGear#Applications and usages - Wikipedia - last accessed on 2022-09-12
- ↑ Data_Distribution Services support - last accessed on 2022-09-12
- ↑ List_of_Android apps to use with FlightGear - FlightGear wiki - last accessed on 2022-09-12
- ↑ Phi - FlightGear Wiki - last accessed on 2022-09-12
- ↑ Raspberry OS setup - last accessed on 2022-09-12
- ↑ Radio Panel Airbus. FG Interface Powered - Youtube video - last accessed on 2022-09-12
- ↑ FlightGear Hardware reconmendations - FlightGear wiki - last accessed on 2022-09-12
- ↑ 20.0 20.1 20.2 FlightGear Wiki - Hardware build - last accessed on 2022-09-12