by wlbragg » Fri Sep 04, 2015 6:11 pm
If you attempt to run FG 3.4 and 3.6 nightly using the same user config, chances are this will continue to cause issues for you even if you clear it out once..
What I do to get around this, is rename the user config folder that I am currently not using (on Windows it is C:\Users\%USERNAME%\AppData\Roaming\flightgear.org) to keep the two versions separate.
For example
I install FG 3.4 and run it. When finished I rename .....\flightgear.org to .....\flightgear.org34.
Then I can install 3.6 and run it. When I want to switch back to 3.4, I will rename the newly created .....\flightgear.org (which is now setup for FG ver 3.6) to ....\flightgear.org36 and then copy or rename the original \flightgear.org34 to \flightgear.org. Then I can run FG 3.4 based on the 3.4 user config.
It can be automated if you want to take the time to write a script.
Even with this, less than optimal, way of keeping your FG user configs separate, I still find myself having to wipe parts of the config from time to time to clean something up that went awry.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q