fortuneanna.blogg.se

1. Flightgear 2018.1 install#
2. Flightgear 2018.1 archive#
3. Flightgear 2018.1 zip#
4. Flightgear 2018.1 download#

the old problems with using SVN are no more since SVN is not used at all any more. The new format of terrasync utilizes checksum files so files that are new, changed or removed will be added/updated/removed automatically. Only recently realized my established Terrasync files lacked a complete inventory of sub-files which is why I tried downloading a scenery area from the archive, this has also been reported.ĭilbert wrote in Sun 4:16 pm:Long since and through many system upgrades came to depend on Terrasync alone. then we found another bug in that that scenery directory was added to the scenery addons directory list again. the launcher properly extracted and installed it to my ~/.fgfs/Scenery directory it created since it did not already exist. I did try with another scenery file i already had downloaded,.

probably because i had to type its name and it wasn't coded to find it as a *.zip.

Flightgear 2018.1 zip#

Here i have to stop because it doesn't like the zip file. found a bug which has been reported - i had to type in the name of the file because the file mask did not allow for *.zip files.i navigated to my "Downloads/flightgear/scenery/test" directory.now we're back on the pop-up screen from step 4 where i clicked the button.

Flightgear 2018.1 download#

Flightgear 2018.1 install#

Of available files to install if the launcher's installer validates the files first to make sure If the downloaded file is not complete (partial download), it may not show up in the list Note that the w090n40.zip file is 546Meg in size so it takes a few minutes to download.

Flightgear 2018.1 archive#

Since the scenery archive names start with 'e' and 'w', i would expect them to be in alphabetical order starting with the 'e' one first and then way down near the bottom the 'w' ones.

they are not the same and are treated quite differently.

you seem to be mixing "directory" and "file" at times. As a result, 090w40n could not be selected for installation (even though it actually resided in the file). dilbert Posts: 725 Joined: Wed 9:36 pm Location: KJKA, Alabama, USA Callsign: db1 Version: 220.3.18 OS: W10,Ubuntu64ĭilbert wrote in Sun 11:50 am:Regarding other machines: thought it significant I couldn't get downloaded scenery working on any of them also, with regard to the I-3 machine: I couldn't install the scenery from my Download file for the peculiar reason that when the install routine in the program was employed, and the Download directory selected, only a few of the downloaded files displayed and the 090w40n scenery file was not among them. It was my thought that this problem and the one on the A8 machine might be somehow related. Regarding other machines: thought it significant I couldn't get downloaded scenery working on any of them also, with regard to the I-3 machine: I couldn't install the scenery from my Download file for the peculiar reason that when the install routine in the program was employed, and the Download directory selected, only a few of the downloaded files displayed and the 090w40n scenery file was not among them. rather than C"\Program Files., no path is available for selection. "Choose Scenery Folder" only permits C:\Program Files\FlightGear 2018.1.1>bin and C \Program Files\2018.1.1 as directories for folder sourcing. Just now tried to add an alternative path to the "additional scenery menu", using "+". In the "additional scenery locations" menu of the add-on section of the launcher, points to a non-existent location. Scenery downloaded and program installed it in C:\Users\/Documents/FlightGear/Scenery" path, which FlightGear 2018.1.1 has automatically written and displayed

Just attempted W090n40 scenery installation on AMD-8 laptop, which previously was only run using Terrasync and had an empty scenery file.