![]() Taking Miguel's point ( thanks Miguel ), should I start again and download 2020.4.0 - then how does one start the process of loading say UK scenery because I can't fly there until there is some scenery. Since FG created the "Custom scenery" directory in the first place, it presumably "knows" about it. Do I then run "7-zip" with each of these files in turn and allow all the required sub directories and files to be created automatically. Presumably I place the downloaded scenery files in the "Custom scenery" directory. Ĭ:\Users\my name\Documents\FlightGear\AircraftĬ:\Users\my name\Documents\FlightGear\Custom sceneryĬ:\Users\my name\Documents\FlightGear\TerraSync Then I reinstalled and have noted the references under "Users". Just so i could get back to a known starting point I uninstalled FG and deleted any references to it that I could find. the correct way to handle this is by adding a "-config=blahblah.xml" to your command line. it was renamed to defaults.xml back in Jan 2017. You'll also find instructions telling folks to edit their preferences.xml file which doesn't exists any more. this is the same way you also add custom craft directories for craft you are building or have downloaded from some hanger other than the default one. if you don't use the launcher, you have to add a "-fg-scenery=blahblah" entry to your command line where "blahblah" points to your custom scenery directory. then you add this directory to the launcher's list of scenery directories. The correct way is to create yourself a directory to store your scenery in if you are downloading and installing it manually. ![]() that could have been months of their work they didn't have anywhere else. One reason for this work on separating things in a cleaner manner like this is for when someone updates an existing install or uninstalls to install a new version clean, custom stuff they had added could very well be deleted. a lot of work was done on the sim to allow for private scenery and craft base directories for each user to place the scenery and craft they wanted to use without corrupting the original installation. Yes, that is the wrong way to do it and has been for a while but it is how many people did it in the past. Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.Peterg1000 wrote in Mon 11:14 pm:This said to load them into "flightgear\data\scenery" - which operation failed because the directories are protected? If you are seeing corrupted/broken textures, please see this article. To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests). please upload a screenshot of the problem. copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher). is there any output printed to the console (black window)? does the problem occur with any aircraft, at any airport? what OS (Windows Xp/Vista, Mac etc.) are you running? Make sure to include answers to at least the following questions in your initial post. In order to help you, we need to know a lot of information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |