- Confirmed everything I've installed has been as administrator.
The installers automatically install themselves with admin rights so, it's not something that could be wrong, and it won't cause this issue anyway even if they didn't.
- Confirmed Windows Defender was off for both download and install (I do not have any other anti-virus software installed).
The antivirus doesn't have anything to do with this. If you had an antivirus problem, one of the modules won't run, so you won't see ANY buildings, not even when getting close.
Confirmed no FSX related programs, including FSX itself, are running in compatibility mode.
I'm sorry, but I stil think this is the most likely explanation. Every user that ever reported this issue, had the Compatibility flag checked either for FSX or for some other 3rd party program that starts with it.
Followed these steps from http://www.fsdreamteam.com/forum/index.php/topic,2794.0.html
None of these are relevant. See the explanation about the antivirus. If you see the buildings only when you get close, it means the software IS RUNNING CORRECTLY.
- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.
TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.
Same as above. The software is running. These steps are ONLY needed when it's NOT running, so you don't see anything, not even when getting close.
Even with the Addon Manager being the only module running, I still have missing buildings that only appear after getting very close to them. The buildings that are missing are usually different with every launch.
So, the only explanation left is the Compatibility mode enabled.
The OP also posted in the Flightbeam forums and stated that the determined solution was to install Acceleration. If the airports worked perfectly on my Win 7 install but not on Win 10, I fail to see how changing the sim I use is an acceptable solution. Any other input would be greatly appreciated.
There's no difference between FSX SP2 and Acceleration, regarding this problem. The user probably THOUGHT it was "fixed" by changing the sim, because when doing this, he got either his Compatibility settings reset (FSX install with all of them off by default), or the FSX.CFG has been reset.
In fact, you don't say if you tried to rest the FSX.CFG, and apply ONLY the HIGHMEMFIX=1 fix, and nothing else.