So now LM is the guilty?? What about Flightbeam, LatinVFR, Drzewiecki Design, ORBX? Only your software have floating buildings.
That's wrong, first because none of these sceneries are fully PBR from the ground up (DD it's not even 0% PBR, and OrbX said they'll release their first fully PBR scenery shortly).
And if you look at many forums of other developers, it's very well know this is something that requires a fix from LM, look at Aerosoft forum, for example:
https://forum.aerosoft.com/index.php?/topic/145966-objects-in-the-air-at-gclp-sim-wings/Some of them offered a non-PBR version of the scenery so, if what you said were true, there wasn't any need to do that, wouldn't ?
And, I think I explained quite clearly why we couldn't offer a non-PBR version of KORD: there's just no such thing, since this was started as a PBR-only project 2 years ago, even before knowing if P3D would ever get PBR. Other developers could simply offer the non-PBR version of their textures, simply because they might have an FSX version or a P3D non-PBR version available, but we don't, and we would have to do one from scratch, an useless work, after LM will release the fix.
And the biggest laugh of all is that "Umberto/Vitualli, or whoever runs this one man company has never in my experience accepted responsibility for any of the issues. He/she is much better at placing blame then programming quality software.
Wrong, of course. First, we couldn't reproduce the problem, we only had at T5, so we converted that one into a Simobject, which prevented the issue. And, we wanted to have most of the scenery using plain .BGL, to fix the loading pauses which were a problem with our previous sceneries, and prove we didn't use Simobject for fun, but only because we couldn't do much with .BGLs in FSX. Now that we don't need to run in FSX anymore, we could stay more clean, but unfortunately, that bug in P3D 4.5 affects *ONLY* objects made as .BGLs.
But that's besides the point. What would be of that useless comment you just made AFTER LM will release the fix ? Would you come here saying "you were right" ?
And it's not this hasn't happened before. Here's a short list of the issue we encountered along the P3D history of updates:
- When P3D 4.0 was released, if a certain number of sceneries using the add-on.xml method was installed, textures started to disappear and go black. We were the first to use that format, which of course the the "native" P3D4 method, yet users complained to us about the problem and, just as you are doing now, said we always blame others.
And guess what, the problem was fixed by LM in 4.1, with no intervention required on our part.
- When P3D 4.1 came out, a bug happened that resulted in the automatic selection of menu entries, as if you pressed the keyboard, even if you didn't. All add-ons using menus, like SODE, FS Passengers, and of course GSX, were affected by this, but since GSX is the most popular of all, users complained to us about the problem and, just as you are doing now, said we always blame others.
And guess what, the problem was fixed by LM in 4.2, with no intervention required on our part.
- When P3D 4.4 came out, there was a bug of corrupted textures in objects using the 2nd UV channel. Nobody knew about this problem except us, because it affected us when working at KORD. It doesn't happen to any other scenery out there, because nobody ever used the 2nd UV channel. Now that KORD is out, users with 4.4 will see this problem, and will likely complain to us, saying we always put blame on others after hearing the explanation (which is also in the manual)
- And guess what, the problem was fixed by LM in 4.5, with no intervention required on our part.
