Indeed, Tom I appreciate your good intentions with that; and I must acknowledge as well that numerous other FS utilities including Instant Scenery use:
[FSX install path]Addon Scenery\Scenery
...as their default file output sub-folder path (until- and unless- the user manually
changes that path in which they opt to save their output files).
IMHO, in this particular case, Ken is "
lucky" that the unwanted Generic Building objects and their placement BGLs which he is excluding, are sourced from FS default (sub-)folder chains which are AFAIK, purposely, and by design, located by ACES' installer at Area layers within the Scenery.Cfg file that may be designated as as 'lower-priority' layers only by virtue of their being located
below the Area layer position of the
Addon Scenery\Scenery folder chain.
Thus, with the
Addon Scenery\Scenery sub-folder also being located by ACES' installer at an Area layer within the Scenery.Cfg file as a 'higher-priority' layer which is AFAIK, purposely, and by design, '
above' those default FS default folder chains that are the source for the objects and their placement BGLs that Ken is excluding, he is experiencing success.
I do still believe that when one considers the amount of inevitable "gotcha" scenarios that scenery developers will likely encounter 'eventually', the use of:
[FSX install path]Addon Scenery\Scenery
...as a "catch-all" folder for BGLs should be
deprecated, as it is more likely to become a cause of trouble-shooting problems for novice developers.
GaryGB