The FMOD developers modified FMOD to allow for the loading of multiple master banks -as long as- the master BUS has the same GUID in both master banks. FMOD is reference counted and objects are globally identified, so when you load the third party master bank with a GUID-matched master bus, FMOD goes “oh, I already made the master bus” and figures out that the third party mixing elements “plug in” to FMOD’s master bus.

We found we could achieve this by modifying the XML inside the FMOD project file to change the master bus ID in a third party project; our intention was to provide some kind of script that third parties could run on their FMOD projects to validate that they were correctly structured for X-Plane and to do the GUID changes.

Our expectation is that aircraft add-ons will want to replace major parts of the mix environment…e.g. you want to hear our environmental sounds through the ‘sound proofing’ effects of YOUR aircraft when inside the plane. To that end we are working on a spec for what buses an aircraft -must- provide, e.g. every aircraft should have a “world” bus, with processing such that when inside the aircraft the world is muted, and then when the doors are open or the camera is outside, the muting is removed.

Thanks Ben! I figured it would be some problems adapting the FMOD “entire app = 1 project” model and I wonder how did you solve it, but the rest of the integration sounds wonderful. I look forward to learning more about this, I think X-Plane was lacking a nice soundscape to complement the excellent fleet available and this will be a turning point to the series.

RIP 🙁

I second , third and forth that.

I had not noticed (probably because I have it off), this is a bug then of 10.5x. File a bug report and I will too after verifying it on my set-up.

Hi Joe,
Our plan is to have an announcement every Friday. We announced more information about the UI on Friday Oct. 14. There were posts on the site and on our social media.

The change on the website is pretty subtle–there is a small grey bar called “The latest” that lists our blog posts. I would recommend following us either on social media or our blog so you don’t miss tomorrow’s post.

The static aircraft placement isn’t synchronized now either for slaved displays.

Might want to check out the Night Light Translation FlyWithLUA script over at the .Org: http://forums.x-plane.org/index.php?/files/file/23164-night-light-transition-and-white-clouds-lua-scripts/. It’s not perfect, but it’s helps.

Understood that edge matching is a bear. There are places that I’ve flown over in Alaska that seem to have this problem in the HD mesh, and it’s probably something that seems to get worse as the latitude increases.

I don’t know about these things, I’ve only got a layman’s POV to the problems you face here, Ben. But I was wondering if a DSF tile might be made something like a quarter mile larger than the coordinates it’s designed to fill, with some sort of procedural alpha blending along the edges. This is just an idea – likely one you and Andras may have already considered, I wouldn’t be surprised to learn.