FGFSRC(5)
π FGFSRC(5) β the FlightGear command-line options file π
okay so bestie, this is the manual page for fgfsrc from the FlightGear man pages. Sit down, grab a strawberry π, and let's get into it.
β¨ NAME β¨
fgfsrc β the FlightGear command-line options file. that's the whole vibe π
πΈ DESCRIPTION πΈ
So fgfsrc is literally just a file full of command-line options that fgfs(1) reads at startup. That's it. That's the girl. π
Who is it for? It's for the people who do not use a graphical launcher to run the simulator. Because like, if you're launching from a terminal every single time, you deserve to put your most preferences that do not change often in one place β think custom scenery locations, custom aircraft locations, screen size options, all that β and then only put the stuff you change constantly (like the starting airport) on the command line. Chef's kiss. π
Now the rules, and there ARE rules:
- The file must be in plain-text format and ASCII-encoded. No fancy encoding, bestie. π
- It must contain one or more command-line options listed in
fgfs(1). Iffgfs(1)doesn't know it, it doesn't go here. - Each option must be given on a separate line. One option per line, no stacking, no chaos.
And the comment situation:
If the first non-whitespace character in a line is an octothorpe (#), then fgfs(1) treats that line as a comment and ignores it. Cute, right? But listen β
Do NOT add comments after an option. Like, not at the end of the line. That might cause the simulator to fail under some conditions β notably, when the command-line argument given on that line is of the form --prop=. So justβ¦ don't. π
And one more thing that gets people every time:
Variables in paths, like $HOME or $FG_HOME, are not expanded. Nope. Not a thing. It sees the literal characters and keeps it moving. π
π¦ FILES π¦
~/.fgfsrc.hostname,~/.fgfsrcβ configuration files containing command-line options forfgfs(1).
Here's the order of operations, because it matters:
- The simulator parses command-line arguments first.
- Then it reads
~/.fgfsrc.hostname(where hostname is the hostname of the machine). - Then it reads
~/.fgfsrc.
β¦and it only reads those last two if they exist, in that order. so if you're on multiple machines, the hostname one lets you get specific per machine, iykyk β¨
π EXAMPLE π
Here's an example config file, and honestly? It's giving main character energy. It synchronizes the simulator clock with the local real-world time, loads real-world weather data, sets the window size to 1024x768, and enables random scenery objects and AI traffic:
--time-match-local
--enable-real-weather-fetch
--geometry=1024x768
--enable-random-objects
--enable-ai-traffic
Look at her. Five lines. Fully slaying. π₯
π SEE ALSO π
and that's the whole page, bestie β no cap. This was the FGFSRC(5) page from the FlightGear man pages, dated 2017-05-28. π«Ά periodt. πβ¨
π¦ where this page comes from
- debian bookworm: flightgear 1:2020.3.16+dfsg-1+deb12u1 Β· GPL-2.0-or-later
- debian trixie: flightgear 1:2020.3.19+dfsg-1 Β· GPL-2.0-or-later
- fedora 43: FlightGear 2024.1.2-1.fc43 Β· GPL-2.0-or-later
- fedora 43: FlightGear 2024.1.6-1.fc43 Β· GPL-2.0-or-later
- fedora 44: FlightGear 2024.1.4-1.fc44 Β· GPL-2.0-or-later
- fedora 44: FlightGear 2024.1.6-1.fc44 Β· GPL-2.0-or-later
- opensuse-leap 16.0: FlightGear 2020.3.19-bp160.1.6 Β· GPL-2.0-only
- opensuse-leap 16.0: FlightGear 2020.3.19-bp160.1.6 Β· GPL-2.0-only
- opensuse-leap 16.0: FlightGear 2020.3.19-bp160.1.6 Β· GPL-2.0-only
- ubuntu jammy: flightgear 1:2020.3.6+dfsg-1build1 Β· GPL-2.0-or-later
- ubuntu noble: flightgear 1:2020.3.18+dfsg-1.1 Β· GPL-2.0-or-later
- ubuntu questing: flightgear 1:2020.3.19+dfsg-1build1
- ubuntu resolute: flightgear 1:2024.1.4+dfsg-2 Β· GPL-2.0-or-later
- ubuntu stonking: flightgear 1:2024.1.5+dfsg-1 Β· GPL-2.0-or-later
- Copyright (C) 2017 Alessandro Menti
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms