From this end I'm beginning to suspect an automatic tree enhancement installer program used quite some time ago

In that case maybe you have another object library containing the same .mdls with the same GUIDs in another active scenery folder somewhere whos accompanying texture folder is missing it's copy of MTtrees2.bmp. Perhaps the placement .bgl (Kowloon-Billboards_OB1.bgl) is calling out the GUIDs it needs and expecting to get them from the MTtrees2.bgl located in the 9Dragons V2\scenery folder but in fact they are loading from a completely different obj library located in another (alphabetically first?) active scenery folder. This scenario would be consistent with a complete reinstall of 9Dragons failing to fix the problem.The first and most obvious thing to do is a search of any/all active scenery folders for another copy of MTtrees2.bgl, but it doesn't necessarily have to have the same filename as long as the GUIDs are there. Do a top-down search of your entire Flight Simulator 9 folder and anywhere else you might have scenery installed.Another thing you could try if you don't find that exact filename is to temporarily disable MTtrees2.bgl in the 9Dragons V2\scenery folder (restore the original Kowloon-Billboards_OB1.bgl you were messing around with first), start the sim and see if the white textureless trees are still there. If so, you'll know for sure there's another obj library somewhere.Failing all of the above, move MTtrees2.bmp and MTtrees4.bmp into the Flight Simulator 9\Texture folder where they can be accessed by anything installed anywhere. Note that this is a crude way of solving the problem, a "band-aid" if you will. Your buddies will loose respect for you if you settle for this "fix" :) .Jim

Jim (and David),Jim, you hit the BULL's EYE !!!I found two more MTtrees.bgls, one in the Grantly Adams airport scenery of Barbados and the other in the Ata Turk airport scenery of Turkey. The one in Turkey did not have it's own MTtrees.bmp so I copied the one from the Kai Tak scenery over to that texture folder, restored the three Kai Tak .bgls with which I had been messing around and Halejuja !!! No more untextured trees at Kai Tak.Jim, I love you !!!Hans

Did I come too late to join the party?! :( Boy, I've never seen such an in-depth discussion 'bout my trees in 9D. Sure glad you guys figured it out as I was about to start scratching my head on how to help ya. Clutch9Dragons

Did I come too late to join the party?! :( Boy, I've never seen such an in-depth discussion 'bout my trees in 9D. Sure glad you guys figured it out as I was about to start scratching my head on how to help ya. Clutch9Dragons

Yep, the Fat Lady has Sung, and the party is over! :(

I'm glad you got it sorted Hans and thanks for reporting back. :( Jim

Hi Guys,This was certainly a strange problem, especially the basic cause of it.Something I hadn't mentioned before in this thread was that during the period that my original Kai Tak problem still existed and after exiting FS9 (shutting down) from a test "looking around flight" at Kai Tak, I kept getting the infamous "fatal error message" with the choice of informing Microsoft about it, etc. In this message UTIL.DLL was stated as being the culprit. Also, my Autower module (fantastic little program) which accurately and automatically takes care of all my Tower views, was suddenly "Not able to connect to FSUIPC". Very strange indeed, especially after actually shutting down FS9, under which circumstances one would not expect these types of "heavy" error messages.However, after the untextured Kai Tak tree problem was fixed, these error messages automatically disappeared as well. Very strange that a single missing texture file in a totally different airport folder can cause all these problems, especially when no untextured trees were noticed at that airport before. I now even see trees at other unrelated airports, trees which were certainly not there before.I learned a lot from this whole issue but must also admit that I was extremely lucky that further "MTtrees2.bgl" files could easily be found in my FS9. If the same files would have existed but with other names, I would certainly have been "up the creek". Long live .mdl files and GUIDs !!!Thanks again for all your input, especially to Jim and David.Hans