Quite the contrary is true for me. With version 2.0 the scenery worked fine (apart from the movement of pedestrians, and not having tested the landing lights)
I can only repeat and confirm the missing menu bar and the progressive loss of fps was always present in Zurich in version 2.0. And besides, you said yourself that those threads were referring to 2.0, that would be enough indication the problem was already there, because people HAD noticed it! It was, as I've said, a 2.0 bug that we HOPED it would be fixed with 2.1, but it hasn't. We obviously reported to LM as soon we find it out, and we even got word that it would have been looked at, but the a few days before the final release, they said there wasn't no time. But with all the reports coming in with problems with 2.1, I'm fairly sure it will be patched again very soon.
But now with 2.1 I have black (2D) panels and no instruments in the VC plus the missing menue bar, therefore I can not use this scenery with version 2.1 at all.
I was referring ONLY to the missing menu bar, and the progressive loss of fps and this WAS present since 2.0. The black 2D panel is something new, that might have been appeared in 2.1, but that doesn't change the fact the *cause* is exactly the same as it was with 2.0, even if the *effect* is now even worse, and of course the *solution* is also the same: remove that .BGL, while waiting we'll come out with a better fix.
But ANY other scenery that uses runway lights made in a certain way (using an invisible SCASM runway) will EITHER have the missing menu OR they will miss runway lights.
Well, so it appears that Aerosoft uses a different way at least for their Stuttgart scenery. As you can see from the (hopefully) attached screenshot, I have the panel, the menue bar and also the runway lights.
You said:
"
I use a lot of other sceneries mainly from Aerosoft and Fly Tampa. None of them has major problems apart from missing runway lights with some of the very old sceneries"
Not all sceneries (only 4 out of 13 of our own sceneries have this issue) have problems, but it's NOT an FSDT-specific problem either, since you said that some sceneries from other developers have missing runway lights too.
I'll repeat it again: ONLY sceneries, coming from EVERY developer, using a SCASM invisible runway command, which is not supported in P3D 2.x will show this problem.
We don't use this method since many years, but just like like those older sceneries from Aerosoft and FlyTampa you were probably referring to that when you said they were also missing runway lights, our older sceneries will have to be patched.
There might be hundreds of sceneries affected too, especially freeware and/or older stuff. Zurich was our first scenery, it was released 7 years ago, when almost everybody used FS9, and that method was very common and 100% legit to use, and didn't had any problem until P3D 2.0, not even P3D 1.x had problems with it.
