Jon,Is it possible that the "new" pylons can only be seen at close range because the software is expecting to see a low resolution version beyond a certain distance ? If this is indeed the case, then why can the original pylons in the SANFRAN PYLONS package still be seen at a considerable distance, even though they are using the same model in the database ? Or are there two versions of the pylon in my install (one as a .bin file, and another embedded in the modelmip.tag file) ?In fact, now I think about it, that second alternative sounds particularly interesting......EDIT: Just for clarification, BOTH pylon models suffer from this problem, so a solution would need to be found for both of them.

Chris,I'm going "Johnny Pylonseed" for a while and see what happens ;-)Regards,Jon Point

Jon,don't forget, you have a new elevation model for Seattle, may be all pylons are underground or floating, just as a hint.:-wave Andre

Andre,No, this is more insidious! It happens in Sanfran as well. Actually, I'm not sure about my Seattle problem. I went back in FLED and the pylons are all there. Problem is, they aren't visible in FU3. Some are - the ones near Kapowsin and some near Easton, but this (below) is supposed to be a majestic (!!?!) set of 2 parallel sets of HV lines with one set of MV lines kinking off to the left. I can't see ONE :-eekhttp://forums.avsim.net/user_files/177355.jpgRegards,Jon Point

I assume this means that you have added more pylons to the Seattle region, Jon ?

Andre,This problem occurs in both high resolution regions, and ONLY when the user attempts to add any new pylons. ALL of the pylons in my SEATTLE PYLONS and SANFRAN PYLONS packages can be seen from a considerable distance, but these new ones vanish very abruptly only a short distance away :-(