377
edits
$FG HOME: Difference between revisions
Jump to navigation
Jump to search
Fix case of fgfsrc, otherwise it won't work on case-sensitive filesystems (which is the case of most filesystems on Linux and traditional Unices)
m (Use “navdata cache” instead of “NavDB cache” for consistency (“Navdata cache” being the canonical name of the corresponding page on the wiki)) |
(Fix case of fgfsrc, otherwise it won't work on case-sensitive filesystems (which is the case of most filesystems on Linux and traditional Unices)) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
{{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}} | {{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}} | ||
{{note|FlightGear reads the <code>[[Fgfsrc]]</code> config file from <code>$FG_HOME</code> if it exists (<tt>fgfsrc</tt> without any leading dot), in addition to <tt>.fgfsrc</tt> from <code>$HOME</code> (with a leading dot in this case).}} | {{note|FlightGear reads the <code>[[Fgfsrc|fgfsrc]]</code> config file from <code>$FG_HOME</code> if it exists (<tt>fgfsrc</tt> without any leading dot), in addition to <tt>.fgfsrc</tt> from <code>$HOME</code> (with a leading dot in this case).}} | ||
== Content == | == Content == | ||
| Line 41: | Line 41: | ||
=== Windows === | === Windows === | ||
==== FlightGear 3.0 and later ==== | ==== FlightGear 3.0 and later ==== | ||
<code>% | <code>%userprofile%\Documents\FlightGear</code> | ||
<code>% | <code>%userprofile%</code> is <code>%homedrive%\Users\''User name''</code> by default, and <Code>%homedrive%</code> is usually C:\. | ||
==== Before FlightGear 3.0 ==== | ==== Before FlightGear 3.0 ==== | ||
| Line 54: | Line 54: | ||
When you encounter problems, try deleting the files, but '''always''' keep the <code>fgfs.log</code> and <code>fgfs_0.log</code> log files to help in troubleshooting. | When you encounter problems, try deleting the files, but '''always''' keep the <code>fgfs.log</code> and <code>fgfs_0.log</code> log files to help in troubleshooting. | ||
== Power Users == | |||
Note you can also override FG_HOME in the environment, to have totally distinct installs - this would be my recommend approach to running multiple versions in parallel. | |||
(The installers will always replace the stable / dev version as other commenters pointed out, so you can't use those so easily, you need to copy files around - I'm nota Windows expert so I don't know if there something that could be changed or improved here) | |||
If you start multiple instances (the same version or different) of FGFS using the same value of FG_HOME (whether that be the default or a custom one), we use a lock file to ensure only one (the first) has write access. The rest will go into read-only mode, and as you can maybe guess, treat FG_HOME as read-only. | |||
Sharing of aircraft / scenery is entirely about which paths are configured, BTW. However, one final caveat is that having multiple instances both running TerraSync, using the same terrasync dir, would likely act a bit funny. It ought to actually work, but it might download some things twice, and it's not a tested or supported configuration for the moment.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=304170#p304170 | |||
|title = <nowiki> Re: Is it possible to install multiple instanes of FG in Win </nowiki> | |||
|author = <nowiki> zakalawe </nowiki> | |||
|date = Jan 25th, 2017 | |||
|added = Jan 25th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== Related content == | == Related content == | ||