This has already being discussed in the forum here:
http://www.fsdreamteam.com/forum/index.php/topic,25734.msg169065.html#msg169065The post explains the technical reasons why it's wrong for LVFR developers to suggest we should revert to the old FSX method of Micro-excludes, which caused so many problems in the past, and was only used to fix an old FSX bug that doesn't exists anymore in MSFS.
If we did partial Exclusions, we would be at risk of any kind of potential conflicts from other sceneries, but even small changes in the default underlying scenery might start to show up mixed with our objects, causing double objects, taking more memory than necessary, lowering fps for no reason, etc.
On PC, the PROPER solution which wouldn't require to change *any* scenery, would be re-arranging the Content.XML file to be sure the Static Aircraft package gets an higher priority so, regardless of the Exclusions made by our scenery, the Static Aircrafts added by it would appear on top of it.
Of course, the thread I've linked have users confirming this solution works:
I tried the fix suggested by virtuali, moving the static aircraft package line to the end of the CONTENT.XML file. It worked. Thank you, virtuali.
However, this is only valid on PC, not on Xbox, because on Xbox you have no way to control the CONTENT.XML file. You might TRY this, instead:
- Uninstall FSDT CYVR from the Content Manager
- Uninstall the Static Aircraft product from the Content Manager
- Exit the simulator
- Start it again
- Go to the Content Manager again, and install CYVR FIRST and the Static Aircraft product NEXT
HOPEFULLY, the Static Aircraft product might end up last in the Content.XML file you can't access but I guess it's there on Xbox too, and the statics should show up again, like they do on PC when editing it manually.