Hi Ken:
First, do indeed send the log to Scruffyduck so that he can interpret what happened, and continue to enhance ADE's ability to deal with even more folder location / Area layer / file loading sequence processing and display scenarios for FS9 ...since such topics are still under discussion in this and a few other recent threads.
Based on what you described above, you should not have a conflict due to file naming, as the default file name submitted for use by IS3 is indeed "
Instant Scenery.bgl".
FYI: It might be helpful in the future to over-strike the file name submitted for use by IS3 and instead give the exclude file a descriptive name such as "
KBHM_Tower_Exclude.bgl"
Alternatively, one can use the
MSFS file load order method of alphanumeric file naming, and give the Exclusion BGL a file name prefix of "
Z_excl_" so that it has a name such as
"Z_excl_KBHM_Tower.bgl".
The
"Z_excl_KBHM_Tower.bgl" file can then be located physically inside the
same sub-folder and Area layer
...as the file which 'places' that tower ex:
[BHM2008 install path\Scenery\KBHM_scenery.bgl
...and because of the "
higher-priority-order" file name prefix used, it will be read and processed
after (aka with a "higher" relative position) in the MSFS scenery loading / rendering sequence
. 
IIUC, IS3 may have read a variable it stores in a certain 'Most Recently Used' (aka "MRU") section of
ex: the Windows registry, and proposed:
C:\FS9\scenery\Namw\scenery\Instant Scenery.bgl
...rather than its out-of-the-box default, which apparently on your installation of FS9 would
normally be:
C:\FS9\Addon scenery\scenery\Instant Scenery.bgl
This choice of location may simply be due to a variable IS3 retained from a
prior file open and/or file write procedure you performed in that path of:
C:\FS9\scenery\Namw\scenery\
Regardless, your reported choice of file name "
Instant Scenery.bgl" for the 'exclude' should
not have altered the default FS9 airport file located at:
C:\FS9\scenery\Namw\scenery\AP915150.BGL
As discussed in the posts immediately above, the goal at this point was to create a
BGLComp-XML rectangle used as a exclude for the KBHM Tower in your edited version of the freeware add-on scenery package.
In keeping with the requirements for use of a
BGLComp-XML rectangle used as a exclude, your edited
KBHM_scenery.bgl would normally be located in a sub-folder mapped to an Area layer physically
above the default airport in the scenery library GUI (thereby giving it a
higher display priority).
Thus, IIUC, one would
wish to place the IS3 BGL file containing (only) the KBHM Tower XML exclusion rectangle in a sub-folder mapped to an Area layer physically above that folder containing your edited
KBHM_scenery.bgl near the top of the scenery library GUI (thereby giving it a
higher display priority than the Area layer mapped to the sub-folder containing your edited
KBHM_scenery.bgl).
So, assuming you have not previously opened the default airport file in IS3 and accidentally over-written (or otherwise altered the content of) :
C:\FS9\scenery\Namw\scenery\AP915150.BGL
...you should be able to simply place the
IS3 BGL file containing (only) the KBHM Tower XML exclusion rectangle in a sub-folder mapped to an Area layer physically
above that folder containing your edited
KBHM_scenery.bgl ...in order to achieve your goal of Tower exclusion.
Hope this helps sort out the current situation for your project.
GaryGB
