Does that mean that you can fix now the Zurich V2 for Xbox related to ground markings?
Unfortunately not, that fix is only related to the Scenery Editor itself, so now one can Hide/Unhide projected meshes in the editor, but that's only for the scenery you are editing.
The problem is just there's no way to exclude a projected mesh from an underlying scenery with any kind of Exclude command, I think it's the only thing that still can't be excluded ( a while ago, it wasn't possible to exclude default roads or road lights, now it is ), I guess they never thought about it, because they don't usually use Projected Meshes in default airports, it was mainly used by 3rd party developers to create a completely custom ground marking set without using any default elements, which is not usual for default airports, in fact I think Microsoft Zurich is basically the only included scenery that use it.
This, coupled with the problem you can't Delete anything that belongs to the Standard scenery on Xbox ( on PC the issues is very easy, just remove the Microsoft Zurich or flag it as "False" in the CONTENT.XML file ), makes the problem impossible to fix for us, until they come with a proper fix.
Note that, there's an overall issue with Exclusion at large, in addition to the project meshes, which makes impossible to Exclude *anything*, if *another* scenery "below" already added its own Exclusions. So, for example, consider this situation:
- A default scenery comes with Jetways
- A default "handcrafted" airports Excludes the Jetways of the default with its own version, maybe better placed to match the enhanced buildings.
- A 3rd party add-on tries to Exclude Jetways again, because it comes with fully custom models, also possibly placed differently.
What's happening now is that it will work ( because it's supposed to ) only on the FIRST startup of the sim, when a new CONTENT.XML is being regenerated, indicating the sceneries did their Exclusion correctly. However, on subsequent startups of the sim, when the existing CONTENT.XML is just being loaded, since no changes happened to the installed sceneries, Exclusions for the 3rd scenery won't work anymore, so you'll see some mix-up of the 2nd and the 3rd scenery.
Again, this has been reported by us as soon as we found out ( because, again, we have a scenery that was affected, that is KORD, which has a default version, and handcrafted version and our version ), which was in January:
https://devsupport.flightsimulator.com/questions/5082/possible-bug-with-deletealljetways.htmlAsobo confirmed it as a bug and they were able to reproduce it, but it seems the fix didn't make it in SU9, so we can only hope it will appear in SU10.
At least this one doesn't affect KORD on XBOX, because since Asobo KORD is a part of a Premium package, it *can* be Deleted, the problem with Zurich is the airport is considered Standard, and for some reason Xbox users are prevented to touch anything that is part of the Standard package. I could understand not letting remove something that might be important for the sim to work, but an *airport* should always be removed, if only because having two airports on the same place, even if one is Excluded, WILL have some impact, if anything, on startup time, since the sim will surely need to scan the whole library anyway.