Afraid w100n40 is irrelevant to this problem, which now seems general for Documents>FlightGear>Scenery.
I have the scenery for the Western hemisphere downloaded and installed in Documents>FlightGear>Scenery.
If I select a new location where no Terrasync files have been downloaded to Documents>FlightGear>Scenery, the program crashes .
Then, if I select the same location with Terrasync on, it does not crash, but adds a limited number of tiles to the Terrasync file.
Thereafter, with Terrasync off, the program loads successfully, but if I fly out of the immediate area of the downloaded Terrasync tiles, the program defaults to blue ocean tiles.
However, if I start in an original location with Terrasync on, then go to File and scenery download in the top menu, and then unclick scenery download; the scenery in Documents>FlightGear>Scenery loads and works fine:
there are no blue ocean tiles when I leave the immediate area of the previously downloaded Terrasync tiles.
I know , for a fact, that the program is operating on the Documents>FlightGear>Scenery, because I can see the point in the scenery download log where the program has ceased to download the Terrasync files and
has integrated and begun using the Documents>FlightGear>Scenery files.
The problem with this is that one can't start in an entirely new scenery area or airport without having at least once visited it with Terrasync active; even though scenery is available in the
Documents>FlightGear>Scenery folder.