Thanks for the response.
Afraid am not much good at interpreting crash report and log. It was trying to load scenery tiles, after which it defaulted to loading ocean tiles just before it crashed. So there seems to be two problems:
2018.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.
Yes, after at least one online session, the scenery works correctly whether or not auto scenery loading remains selected. However, if I fly on to another area, I get a big white patch (not the ocean), unless I have
already downloaded that area using 2018.1.1. The white patch seems to indicate the default ocean tiles have failed to load. However, in this instance, the program does not crash; and I can reverse course and fly back into a working scenery area.
Hope I don't have to re-fly every scenery area with terrasync, which would be very time consuming.
Having rechecked log found this: ground cache.cxx:399: prepare_ground cache_ (): trying to build cache without any scenery below the aircraft
also found: JBSM.cxx.1333: FG Interface is being called without scenery below aircraft !
haven't yet found why, but will continue to look.
Have been flying Dave Culp's T2C, which I really like.
Log has statement: "fg.init.cxx: 373: Aircraft does not specify a minimum FG version: please add one at /sim/minimum_fg_version".
Could this be causing the problem?
Yes, tried using A6 with terrasync off. 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.
Still don't know why program didn't load stored scenery; will check latest log.
Checking log found statement with: "cxx:244: FGStg Terrain:: init-init tile mgr".
Are two colons between Terrain and init-init correct, or should it be just one?
Thanks again for your help. Best Regards