Northeastern292

Tanocapo, it worked! Two problematic sceneries rectified. Feels good!

Precisely. I tried deactivating a couple of South American sceneries. No dice.

UPDATE: It's an addon EBOS (Oostende) airport that's causing the Netherlands to be effed up. Now to see what's going on in the Southern Hemisphere.

Now I have come to find out that all of the Netherlands is messed up. Might I include a copy of my scenery.cfg?

Different problem: the altitude is incorrect: the plane is halfway in the ground.

My mistake, no, not from my terrain.cfg This is though // Airport Backgrounds (FSX) - Flatten + MaskClassMap + ExcludeAutoGen [Texture.164] Name=Airport_Backgrounds_Flatten_MaskClassMap_ExcludeAutoGen Color=FFFFFF00 guid={46BFB3BD-CE68-418E-8112-FEBA17428ACE} FlattenMode=flat FlattenPriority=51000 LandClassRemapType=none ExcludeAutogen=Yes RenderToTexture=No RenderPriority=20000 Water=No Textures=GRASS_SKIRTING_1

Joe, you might be onto something! [Area.164] Title=VATJO-OJAI-EXCLUSION Local=Addon Scenery\VATJO-OJAI-EXCLUSION Layer=164 Active=TRUE Required=FALSE

Nope, all have CVX files. EHAM is an AFCAD of all things. I might end up having to play around with the database and deactivate what might not work. Granted I have 800 (yikes!) plus entries.

I have noticed this problem at least at two airports: EHAM (default with Ray Smith's wonderful AFCAD) and Marcelo Veneziale, Posadas Guillermo and Pablo Contouris' SABE. Could it be as something as simple as a scenery database ordering issue or something more complex?

Agreed. Something I have learned quite well in tech support.