![]() ![]() Since I don't use the Windows partition much, my Windows Nvidia programs were way out of date even though they worked. Rolling back the driver resolved the problem. Please see the post at the end of this sentence for the solution, should anyone have a similar problem: White screen upon load. That resulted in FlightGear not responding properly. Microsoft issued new updates to Windows and evidently the update for the video driver failed. I also had a congruence of of unfortunate " issues" while I was experimenting with how to set a new default airport. Once I clicked on it, I realized what needed to be done. The problem of setting a new default airport was the result of me not knowing the purpose of the " back" tab under " location". the launcher won't use them but one doesn't have to start with the launcher if one doesn't want to. that's why you specifying the airport didn't work. in the launcher, some things are going to be slightly restricted because the launcher needs to know about them when it starts instead of afterward. so anyway, use the command line options or the additional settings in the launcher. never really should have at all but heck, we still have folks putting their additional craft in FGData instead of in their own private directory and point FG to it. but you really should not be editing that file. No, it was renamed to defaults.xml because that's more in line with its job. I was unable to find "preferences.xml" that is supposed to be located in: "C:\Documents and Settings\\Application Data\\", Possibly this reference was not updated to reflect the Window's revision from XP to Windows 10. While that added KRMH to the "tools" -> "view command line", FlightGear still booted into LKPR. I also added KRMH under "settings" -> "additional settings". (a copy of the file is displayed below) I ran a file search and was unable to find a source file for setting an airport. I did not see any airport settings in this file. It appears that Windows settings are now stored in "C:\Users\Stephen\AppData\Roaming\\FlightGear\flightgear.ini". With the Windows 10 installation, I have not been able to replace the default airport of LKPR with a new default airport of KRMH. I installed FlightGear 2017.3.1 on my Windows 10 partition to compare how FlightGear compares between the two operating systems. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |