@Steven Winslow: Jeff's work is wonderful, and I have much of it installed. But there are still many SOCAL airports without custom scenery, aren't there? For those airports, I'd much rather have Legos than nothing. To that end, Zengei has been organizing an effort to make Legos for all the airports in the PE coverage area. He's developed a spreadsheet of ZLA airports without any lego scenery. Perhaps he might consider adding a column indicating which airfields have scenery by Jeff and other custom designers. See this thread:
viewtopic.php?f=12&t=5066
As for the hierarchy in scenery_packs.ini: if we have base mesh and such in our scenery_packs.ini, we don't want to put Global Airports below that, do we? I have lines like this in my scenery_packs.ini: SCENERY_PACK Custom Scenery/zzz_hd_global_scenery3/ . That mesh should go below almost everything, I would think. I'm not as sure about the World2XP betas I have installed, things like: SCENERY_PACK Custom Scenery/w2xp_Australia-Oceania_beta6.0-hd/ , but the guidelines for that scenery suggest putting it just above the mesh and below everything else.
As for exclusion zones, hmm, they mostly work fine for me without any noticeable performance hit. I have had one or two issues, admittedly, but I'm not sure they are caused by underlying Legos. (I recently saw some trees growing on the runway at Heathrow, but I think it was caused by the trees-and-farms scenery, not Legos.)
I guess my bottom line is that I'm reluctant to disable my Global Airports, as I'm often pleasantly surprised to find Lego scenery at a small airfield, and I far prefer Legos to nothing at all.