Having performed this monkey motion, and eventually making it to Houston, I was thereafter able to launch from Houston with Terrasync off, thence return to Pensacola and have scenery the whole way.Įach scenery area file is divided into a number of scenery sub-files. Each time I quit FG, loaded an airport existant in the missing scenery area using Terrasync quit once the runway appeared then backtracked loading an airport with last visible scenery, and relaunched with Terrasync off. Hit boundaries beyond which there was no scenery around Pascagoola, Slidell, Lafayette, Lake Charles, Beaumont, and Houston. The scenery areas were all recorded pre 18.1.1 in my Terrasync File. Tested the above by attempting a flight from Pensacola to Houston with Terrasync off. Scenery never appears, as it otherwise would using Terrasync. However, if I fly a modest distance from the launch airport, I encounter a boundary beyond which Unfortunately, it also entails long initial scenery downloading time not to mention the fact it wouldn't work at all, if internet is unavailable. The program accesses the Terrasync file and produces the scenery.Īs things stand, the only practical way to fly cross country is with Terrasync on (which works fine). Nevertheless, if I go to the same area with Terrasync on, but quit the program once on runway and then refly with Terrasync off,
When I go to an area not previously visited using 2018.1.1 with Terrasync off, the sceneryįails to load, even though the scenery exists in my Terrasync file. Other than the two Hawaii default scenery areas. The laptops I tested on had nothing in 2018.1.1>data>scenery, The problem, as the program will default to the scenery stored in the data>scenery file. Has the same scenery area in their FlightGear 18.1.1>data>scenery file, will not seem to encounter This is to elaborate on the above posts after further tests.įirst, someone who has the previously (pre 2018.1.1) scenery installed in their Terrasync file, but also Best Regards dilbert Posts: 725 Joined: Wed 9:36 pm Location: KJKA, Alabama, USA Callsign: db1 Version: 220.3.18 OS: W10,Ubuntu64 Still don't know why program didn't load stored scenery will check latest log.Ĭhecking log found statement with: "cxx:244: FGStg Terrain:: init-init tile mgr".Īre two colons between Terrain and init-init correct, or should it be just one?
and program did not crash which resolved part, but not all of the problem, as I got the blue ocean, rather than the scenery stored in the TerraSync file. Log has statement: "fg.init.cxx: 373: Aircraft does not specify a minimum FG version: please add one at /sim/minimum_fg_version". Have been flying Dave Culp's T2C, which I really like. Haven't yet found why, but will continue to look. Having rechecked log found this: ground cache.cxx:399: prepare_ground cache_ (): trying to build cache without any scenery below the aircraftĪlso found: JBSM.cxx.1333: FG Interface is being called without scenery below aircraft ! Hope I don't have to re-fly every scenery area with terrasync, which would be very time consuming.
However, in this instance, the program does not crash and I can reverse course and fly back into a working scenery area.
#Flightgear scenery download failed Patch#
The white patch seems to indicate the default ocean tiles have failed to load. However, if I fly on to another area, I get a big white patch (not the ocean), unless I haveĪlready downloaded that area using 2018.1.1. Yes, after at least one online session, the scenery works correctly whether or not auto scenery loading remains selected. So there seems to be two problems:Ģ018.1.1 tries but fails to load the retained terrasync scenery tiles, possibly not recognizing them then it tries to load the default ocean tiles, after which,it crashes without displaying them. It was trying to load scenery tiles, after which it defaulted to loading ocean tiles just before it crashed. Afraid am not much good at interpreting crash report and log.
0 kommentar(er)
