Afcad Problem, wrong aircraft placement.

Harpsi I don't know if you've seen this in FS9 but I found something really weird with the Minneapolis area. They have an AFCAD actually tied to airport scenery. There's a default afcad for KMSP that if you delete it you loose all the local area airports. This makes for a problem child with add-ons such as Blueprint's KMSP (which needs it's own afcad). When you add an afcad on top of the default afcad for KMSP performance suffers. There's no way to get around a double afacd when add-on scenery is created for airports like KMSP. I wonder what Aces was thinking when they did this? It would have been nice like in most cases to be able to shut down the default afcad and used one specifically designed for the add-on airport in question. When you have double afcads in FS9 performance is really affected for that area.