Alright guys I got some bad news and even worse news. I'll start with the worse news first, cause it will make more sence like that.
I HAVE NO FSX!!!!!!!!!!!!!
Now the bad news
MY COMPUTER DOESN'T WORK, so I HAVE to switch to fs9 to fly.
At least I may be able to get rid of that stupid Terminal D Problem.
I was wondering what ever happened to you since it had been so long since your last post. I figured you finally had gotten rid of the problem with the building showing up at Terminal D.
Maybe a fresh install of FSX will do the trick. I still have a feeling that you had a rogue AFCAD somewhere mixed in your install that you couldn't locate.
Here's what I would do though. After you install FSX and all the service packs, GEX, REX, and UTX assuming that you use any or all of those, I would install your FSDT sceneries first and make sure they all work ok and you dont have the same problem with Terminal D. Then assuming KDFW is ok, then begin to add in your other sceneries and keep a log on a note pad of what you installed and when you installed it. That way if a problem like the one you had comes up along the way, you can look at the list of things you installed and begin to remove them starting with the last one first and see what is causing the conflict at Terminal D or any other airport you may encounter a problem with. Makes it a lot easier to trouble shoot problems in the future.
Once all you sceneries are installed you can then go back and rearrange the layers if you need to. I generally start installing airports and scenery going from West to East, meaning that I will install sceneries for airports and photosceneries beginning with California and then start working my way across the world going West, making sure to always keep photosceneries in a layer below and airport scenery for the same area. For me arranging them in this fashion makes it easier to keep track of what I have installed for a given area and its easier to look at when viewing you scenery.cfg.