We had already seen in a very long and exhaustive test that xml (BGLComp) excludes will not reliably remove autogen.In spite of being documented in the BGLComp manual, xml excludes (ExcludeAllObjects) will only remove autogen in entire quad 15 chunks. So, they are not very useful for this purpose.We have been advised to use vector (Shp2Vec) excludes - FLX - instead.However, I have now found that, in certain instances, they are not reliably removing autogen either.In most instances - exclude polygons over default terrain - all autogen objects seem to be removed correctly.But, on land class polygons (PKX), there are objects that remain with no way to exclude them.Here is a design project:http://forums.avsim.net/user_files/163132.jpgAn exclude polygon is drawn on top of the PKX. This is the result:http://forums.avsim.net/user_files/163133.jpgNo matter the land class chosen for the PKX, there will always be instances of single trees that remain.This behavior has now been confirmed by the developers and filed as a bug for further investigation.Of course, there are work-arounds:1. Draw the land class polygon in such a way that there is a hole where the exclude applies. This exclude will therefore only cover the underlying land class and will work correctly.2. Instead of an exclude, draw a land class polygon for a texture without autogen, for example, grass, or another.Or anything that you can imagine, as there must be other solutions.Dick Ludowise has imagined a very neat trick of a small invisible ground tile compiled with Resample that will, like all custom textures, eliminate autogen.This exception to autogen excludes will be added to the pinned topic concerning methods for excluding autogen with Shp2Vec.Best regards.Luis

Luis,I noticed the same while trying to to clear the path of the Moscoso bridge at TJSJ. I had to create a polygon of grass to exclude the autogen in the vecinity.Juan

Same hereI also noticed that a lot of thought was not put into autogen trees that border airports. When autogen is increased, the runway becomes blocked by the amount of trees and the height used which renders the (arrival) runway inoperative. The 50 ft rule departure applies to a lot of GA airports in the database but arrival is near impossible without laying down some polygon grass texture or some of the other GUID's to remove the trees.