8,574
edits
FlightGear Launch Control: Difference between revisions
Jump to navigation
Jump to search
→Page One - Paths: slightly clearer
(Remove old links and statements.) |
(→Page One - Paths: slightly clearer) |
||
| Line 36: | Line 36: | ||
In the first page, the paths needed by FGRun are recalled and can be set. If FGRun was installed with a binary package, either under Windows or Linux, these paths are normally initialized by the installation procedure. | In the first page, the paths needed by FGRun are recalled and can be set. If FGRun was installed with a binary package, either under Windows or Linux, these paths are normally initialized by the installation procedure. | ||
* '''Executable''': the full path to the FlightGear program (<tt>fgfs</tt>). One can choose it directly using the file selection dialog that pops up when the folder button is hit. | * '''Executable''': the full path to the FlightGear program (<tt>fgfs</tt> or <tt>fgfs.exe</tt> on Windows). One can choose it directly using the file selection dialog that pops up when the folder button is hit. | ||
* '''[[$FG ROOT|FG_ROOT]]''': the full path to the FlightGear base package (<tt>data/</tt> directory). If this path is wrong, no [[aircraft]] would be displayed and FlightGear won't run. | * '''[[$FG ROOT|FG_ROOT]]''': the full path to the FlightGear base package (<tt>data/</tt> directory). If this path is wrong, no [[aircraft]] would be displayed and FlightGear won't run. | ||
* '''[[$FG_AIRCRAFT|FG_AIRCRAFT]]''': can link to external aircraft packages. Leave empty when all your aircraft are installed in <tt>[[$FG_ROOT]]/Aircraft</tt>. | * '''[[$FG_AIRCRAFT|FG_AIRCRAFT]]''': can link to external aircraft packages. Leave empty when all your aircraft are installed in <tt>[[$FG_ROOT]]/Aircraft</tt>. | ||
* '''[[FG SCENERY]]''': the paths to [[scenery]] folders. These folders usually have a 'Terrain', and optionally a 'Objects' , subfolders. You can add a new path with the 'Add...' button. Priorities among folders are managed with the up and down arrows; the top most folder having the highest priority. If there is no scenery for a location in the top folder, FlightGear will look in the next folder etc. | * '''[[FG SCENERY]]''': the paths to [[scenery]] folders. These folders usually have a 'Terrain', and optionally a 'Objects' , subfolders. You can add a new path with the 'Add...' button. Priorities among folders are managed with the up and down arrows; the top most folder having the highest priority. If there is no scenery for a location in the top folder, FlightGear will look in the next folder etc. | ||
* '''Airports Cache''': the location of the file that stores the [[:Category:Airports|airport]] ids found in the scenery. It is faster to access that file than to scan scenery directories to build the airport list. It is possible to delete that file if things go wrong. That will force a new scan when the third page will be shown. | * '''Airports Cache''': the location of the file that stores the [[:Category:Airports|airport]] ids found in the scenery. You should not need to change this one. It is faster to access that file than to scan scenery directories to build the airport list. It is possible to delete that file if things go wrong. That will force a new scan when the third page will be shown. | ||
'''Hint''': If things go wrong and FlightGear cannot start anymore, and you want to start over with a bare installation, remove or rename the file named 'fgrun.prefs' located in the parent directory of the airport cache file. You will have to reenter path by hand, but the silly options you could have entered will be deleted. | '''Hint''': If things go wrong and FlightGear cannot start anymore, and you want to start over with a bare installation, remove or rename the file named 'fgrun.prefs' located in the parent directory of the airport cache file. You will have to reenter path by hand, but the silly options you could have entered will be deleted. | ||