I’m not sure you understood the detailed answer you got from me.
Nowhere I said, here or on my email reply to you, that any PC user ever solved the problem by reinstalling the whole program, at least in relationship with the Jetway problems at LSZH, or any other issues of the scenery.
Those who installed the Beta HAD to go through a very large mandatory update when SU6 came out, and they also had their Community folder cleared up, but this doesn’t have anything to do with LSZH, or anything else bought on the Marketplace, because such add-ons don’t use the Community folder at all.
The whole jetway missing problem was never a problem of the scenery itself, it was a bug introduced with SU5, which was the first version for Xbox as well. With SU5, almost each and every 3rd party airport had troubles with disappearing jetways. In some cases, they disappeared also on default airports.
This has been reported by us and other developers as soon as the Beta for SU5 started, but it wasn’t fixed until SU6 on PC, and it was fixed for 100% of users, and it was fixed without having to reinstall anything or change anything in the scenery. Yes, we released a patch for LSZH the day SU5 came out but, it didn’t solve much, it only lessened the problem, because it was a bug in SU5 and it has completely fixed with SU6, because only Asobo could fix that, being an SU5-specific bug.
Of course, all PC users got clear proof the scenery has always been perfectly fine right from the start, the moment SU6 came out, because jetways immediately reappeared at LSZH, and on many other sceneries which were affected by the same bug.
However, the problem still doesn’t seem to be fixed on XBOX. Asobo confirmed multiple times that, if something works on PC, it MUST work on XBOX as well and, as long as we respect the new “XBOX LOD rules”, which mandates to have at least 3 LOD levels for objects to prevent the risk of them being removed on Xbox, we should be fine. The added a “Xbox LOD simulation” to the SDK, so we can test how the scenery would look like on Xbox.
And of course, LSZH obviously works perfectly fine on PC ( we can’t test on Xbox ), even when the Xbox LOD simulation is enabled. Jetways always shows up, meaning the Xbox simulation on the PC SDK is not 100% reliable, most likely because it cannot anticipate possible bugs in the Xbox code. But that’s the only way we can test on Xbox.
I had a theory, because of the several sceneries we made, one have the jetways working normally on Xbox, and it’s Chicago O’Hare. And there, the only difference it’s that Jetways have 5 LOD levels instead of 3. The default Asobo Jetway used to have 3 LOD levels, now it has 5 so, MY theory is that Jetways are a bit of exception and, on Xbox only, they require 5 LOD levels, instead of the normal 3 the SDK is recommending to be sure objects won’t be removed automatically on Xbox. We don’t know if this is intentional they just forgot to document fact the jetways are behaving differently, or it’s just a bug.
So, we sent an update for LSZH to the Marketplace team, asking them “Could you please confirm Jetways works on Xbox too?”, because we don’t have ANY means to test on a REAL Xbox. Only the Marketplace testers can.
This was 18 days ago, when I first posted about this and, we finally got our answer in the meantime, it’s confirmed jetways works now. Well, the reply wasn’t specifically about jetways but, in general, the test report said there were “No LOD problems anywhere”.
So, the scenery update will be appear in the Marketplace, as soon it will clear up the released queue, which again might take a few weeks.