Most airport scenery not visible upon arrival **SOLVED**

[Sploosh]

All FSDreamTeam airports do the same thing (those that I have purchased). For example, I take off from KLAX and land in KLAS. The origin loads perfect. By the time I arrive at my destination, the FSDreamTeam airport scenery doesn't load. I land with pieces and parts showing and NOT showing. Some items load, such as roofs and vehicles, but tarmac walls, passenger gates, and airport lighting (for example) just don't load. I land at a "broken" airport.

If at the beginning of a flight I literally SLEW from airport to airport they load perfectly, in tact, and whole. If I FLY from one to another, they don't... every time. Why is this?

Thanks for your time and consideration.

skan

[virtuali]

Some items load, such as roofs and vehicles, but tarmac walls, passenger gates, and airport lighting (for example) just don't load.

Please be more specific: are these partial objects looking to be FSDT objects, or default objects ?

[Sploosh]

Yes, FSDreamTeam objects only partially appearing. I have this happen to KLAX, KLAS, KDFW,  KJFK2, and FlightBeam's KSFO, and Cloud9's KMCO (these are the ones I have purchased and show active AND installed within the Addon Manager in FSX). And yes, both Addon Manager and the Couat..(spelling) engine show up on the Menu bar within FSX.

I have already installed the latest of ALL of the above listed airports by downloading them from their respective sites, and installing them. I installed Addon Manager first, then GSX, then the airports, all with new downloads.

[virtuali]

Yes, FSDreamTeam objects only partially appearing.

Then it means the problem is not related in any way to the software or the installation (you said yourself their menus are there), the most likely explanation why it only happens after a flight and not when positioning at the start of a flight, seems to indicate a problem with video/ram memory corruption/exhaustion along the course of the flight, which result in partial objects being displayed.

Just to be more clear: we don't have any means to display *partial* objects from our code (it would be interesting if we could...), so it's entirely out of our control, and it must happen within the FSX graphic engine.

[01pewterz28]

I had this happen it could be too many active sceneries loading in FS. Disable scenery areas you are not flying to. If you do LAX-KAS no need to have scenery for New York ensbled.

[Sploosh]

I found what I believe to be the answer. I had "//", in effect attempting to "comment out" some of the auto-entered-into-FSX.cfg additions. Among those were "TextureMaxLoad=6", HIGHMEMFIX=1", and "SmallPartRejectRadius=1". These can't be "commented out" with "//" preceding the entry in the FSX.cfg file. They are needed to make the scenery work. I am not technically knowledgeable enough to understand why. I just know that it works. The scenery loads and appears as it should.

Thanks all.

[virtuali]

These can't be "commented out" with "//" preceding the entry in the FSX.cfg file.

That's part of the problem. // comments are not legal in .INI file ( the FSX.CFG is an .INI file, just with a different extension ), the standard comment for an .INI file is the semicolon ;

They are needed to make the scenery work. I am not technically knowledgeable enough to understand why. I just know that it works. The scenery loads and appears as it should.

The HIGHMEMFIX=1 is basically a mandatory fix when using videocards with more than 512MB or RAM, otherwise FSX won't use it. The scenery doesn't have anything to do with it, except that the overall VRAM requirement at that location exceed 512MB, which is very likely nowadays.

It's not default because they are not that common when FSX was released, but it's considered as a default by the Addon Manager Defaults settings button, and it's now default on the new FSX Steam edition.