If that is the case, it is a bug – please file a bug with a complete small scenery pack demonstrating this (e.g. one draped polygon at an airport with a normal map.)

how exactly can i load a normal map in these situations so that PBR can be used ?

Sorry!

The cost always varies – it’s very specific to the code, subsystem, etc.

“Major version” compatibility between 10 and 11 is _definitely_ worse than between 9 and 10 – our goals for major version are never “perfect no-touch compatibility” but overall 10-11 has been harder for two reasons:

1. “Holding our breath” for 5 years on compatibility breaks – we have a lot of stuff to clean up and we’re trying to get it all out now so we can keep the v11 updates trouble-free.

2. Add-ons are WAY more complex than they were five years ago.

Danny – this is your FOURTH post of this on this blog post. Please stop reposting this over and over.

Please DO file a bug if you have not done so already; no amount of reposting on the blog gets the issue into the bug database.

[EDIT — duplicate post removed.]

Use X-Camera then it can resume those controles.

That legacy price penalty description is very helpful, Ben. Thanks for that. I hope that there are some no price penalty options for some things… 😉

Same to me here, on reloading the next set of whatever(?) my CPU load shoots up to the limit an XP11 hangs completely for 10-20 seconds. I fiddled around with all my settings but can’t get that fixed.

Hi Bob,

The new 2-d G430 absolutely has complete working buttons. It looks like there’s a bug where they pop up AND work – I’ll check with Philipp on that.

The screen does look garbled at tiny size; however, if the panel ends up being drawn bigger because the user has a big monitor, the quality returns. We may be able to get some better anti-aliasing in, but in the end of the day if you’re going to make a Garmin at the scale that we use for X-Plane 6, it’s not going to be a terribly useful display.

Here’s the thing about legacy tech and compatibility: there is a persistent tax on all new development of X-Plane to maintain all old features, particularly if we want perfect compatibility. For five years we really tried hard to avoid compatibility breaks, sometimes jumping through crazy hoops to make it happen.

That’s one reason why there’s so much “why did you guys change X” in v11 – we have five years of accumulated architectural change.

In the case of the GPS, we don’t think that the old legacy GPS/FMS components are adding enough value compared to their new counter-parts to maintain a permanent system that uses both code paths. Only by denying the old instruments to NEW planes now can we drop the old tech and stop paying for it in dev time in several years.

cheers
Ben