Thanks for the update! Well, LPV approaches are not _that_ boring.
Great news, getting more data *in* X-Plane. Please don’t forget the add-on developers who want to get the new data *out* of X-Plane… By the way, is the data for LPV not supplied by NaviGraph and NavDataPro?

Mostly lying on a floating mat in the pool and sipping Pina Coladas.
Honestly though, really booooring features for the time after 10.50. Boring unless you are interested in correctly flying LPV approaches for example. Suffice it to say that I attended a meeting with the FAA in Washington so we can get more and better data in X-Plane that I care for for instrument training.

The intent is the entire pipeline – one consistent lighting model everywhere.

With that in mind, the detail in the reflections may be -seriously- limited/impaired/hacked for things other than the aircraft – we have to pick our battles. But for that matter, I don’t know how much reflections we get, and it will certainly be variable based on rendering settings. That stuff is TBD – what we have now is not even close to fast enough to ship.

I know you probably can’t answer, but incase you can:

I was wondering if PBR in the next version is just for aircraft, or is it meant to work for the entire pipeline? (Ie, reflections/haze off of runways, more physically accurate atmospheric scattering)

If its just for aircraft, thats totally ok (or if its mostly fudged with shaders and comes “close” to looking real). If you are on the fence about the atmospheric scattering part… for what its worth, and for all of its limitations as currently implemented, Real Terra Haze gave me a greater sense of depth and distance than tons of objects ever had (it’d be nice to get an overclocked i7 and a $currentFastestCard to have both!) – I had not realized how important that was to a sense of realism. So a re-jiggered scattering support would be a way for us with old sad machines to benefit even if we had to dial everything else way down.

I was blown away that the sample renders looked better than what a ray tracer could do when I was a kid. Awesome work!

Here’s my expectation:
1. FMOD will be packaged with the sim, making it available.
2. The X-Plane C SDK will contain minimal FMOD support – e.g. there might be a dataref letting you get FMOD’s system object. (In other words, if you want to code, write fmod code directly and we’re only going to help with things where we have to because of global resources owned by the sim. FMOD’s API is such that you don’t need us to wrap it.)
3. There will be an -authoring- interface to associate FMOD events (FMOD sounds are called ‘events’ for some reason) with commands or datarefs in the sim. That will be something you do with your aircraft, but it’s -data driven-, e.g. no code required.

Well, our general goal for aircraft compatibility is:
1. Aircraft from the previous version more or less work.
2. There may be a small number of mandatory updates at major versions – these are usually for add-ons using very old technology. (E.g. if the airplane from v8 worked by compatibility in v9, it needed some work for v10 – the last version rule isn’t recursive.)
3. Usually the aircraft without the updates is acceptable to users but not quite what authors want, so they tune it.

The move to HDR and global lighting was a level of compatibility we were comfortable with: most aircraft “just worked” with HDR, some needed updates, and with HDR off, things were mostly fine.

Another question that crossed my mind… Will the future interface look and feel will influence the xpsdk widget look and feel?
Thank you for the great show.

That is the spirit.
I wish they had a monthly donation thingy, I sure would have loved to support LR.