Re: [Flightgear-devel] Hidden vs public files

[Richard H. <rj...@za...>]

> What other files inside FG_HOME are relevant? Alan mentioned joystick configurations, but personally I have never touched one of them inside FG_HOME.

Items that I've had to manually manage:

migrate settings from the autosave after upgrading into the new autosave.

rm aircraft-data/* (sometimes when a new model is released there are 
incompatibilities, sometimes because an alternative model uses the same 
name, and sometimes just because what has been saved is broken due to 
some other fault in the model)

input/Joysticks - this is a bit more complicated as it stores the 
modified XML; sometimes I have to remove the files, and other times I'll 
copy files in where I've customised a configuration from the default 
(either with the built in tool, or directly with an editor).

Runnig out of diskspace whilst writing an XML (leaving me with an 
unrecoverable exception). After a few years of having acres of free 
space since getting an SSD running out of diskspace is once again 
something that happens all too often (as APPDATA is on the same drive 
the my database server files and transactional logs).

It took me probably a month of flying to discover and start to manually 
manage %APPDATA%\flightgear.org - I rather suspect that one solution is 
to come up with a common list and add a tool (possibly into the 
launcher) that will allow the basic management and fault recovery 
without having to delve into the deep.

1. input/Joysticks: save and restore your all customisations (into 
Documents/FlightGear/Input/Joystick).
2. Clear nav db cache.
3. View log file
4. Reset aircraft state data (either for the currently selected model, 
or all models)
5. delete all from  %APPDATA%\flightgear.org