Hi All,

Using the MSFS version of ADE (Alpha 21) I'm trying to figure out how to open/edit either 3rd party airports or default airports. My objective is to be able to alter parking position codes to allow better AI parking.

In the old version for P3D it was pretty straight forward...you just open the relevant .BGL make some changes and compile. Perhaps I'm missing something obvious but I can't figure out how to open an airport in the MSFS version. I presume I need to create a project to model off but trying to open FLYTAMPAs YSSY .BGL (which I presume is the SYD_Build.BGL file) gives me a bunch of error messages and no airport to model off.

 

Anybody able to walk me thought it or point me in the direction of a tutorial... the manual wasn't much help.

 

Cheers

 

try your question over here https://www.fsdeveloper.com/forum/forums/airport-design-editor-for-msfs-2020.160/

Thanks. I was hoping to avoid creating another forum login but I guess thats whats best. 

 

2 hours ago, KL Oo said:

Hi All,

Using the MSFS version of ADE (Alpha 21) I'm trying to figure out how to open/edit either 3rd party airports or default airports. My objective is to be able to alter parking position codes to allow better AI parking.

In the old version for P3D it was pretty straight forward...you just open the relevant .BGL make some changes and compile. Perhaps I'm missing something obvious but I can't figure out how to open an airport in the MSFS version. I presume I need to create a project to model off but trying to open FLYTAMPAs YSSY .BGL (which I presume is the SYD_Build.BGL file) gives me a bunch of error messages and no airport to model off.

 

Anybody able to walk me thought it or point me in the direction of a tutorial... the manual wasn't much help.

 

Cheers

 

It's the same as P3d and FSX was. You need to find the bgl. my example is for Fly Tampa YSSY Sydney. The bgl is located in my ORBX library folder H:\ORBX\msfs\YSSY Sydney International Airport\Community\flytampagg-sydney\scenery\world\scenery\Syd_build.bgl 

Make sure before anything you download the MSFS sdk in developer mode and also download the online documents. Both are in the developer help menu. And yes you will need to create a new project using the create project from MSFS bgl. Also use the ADE wizard to setup the core files it needs to use.

Edited November 27, 20214 yr by RW1

Hi @RW1,

 

Thanks for the reply. I've downloaded the SDK and ADE is setup with the correct paths (they were identified automatically). I'm trying to create a project using the same file that you've loaded above but get nothing but errors. Are you sure that you've loaded the FLYTAMPA file? I note that there are no parking codes on the one you've got above...looks like the stock one....

First I'm using this option

Then completing this screen. The fields look OK to me but maybe I'm missing something...

 

Which gives me these errors

 

And then fails to load any airport and returns to a blank ADE screen.....

Any ideas?

 

Edited November 27, 20214 yr by KL Oo

I assure you the bgl is not stock. I copied from the FT original and placed it in my work folder then loaded ADE with that bgl. You need to enable the 2 tabs at the bottom visible in store and can be referenced, then click save. I have no idea why you get xml errors. 

12 hours ago, RW1 said:

I assure you the bgl is not stock. I copied from the FT original and placed it in my work folder then loaded ADE with that bgl. You need to enable the 2 tabs at the bottom visible in store and can be referenced, then click save. I have no idea why you get xml errors. 

I am finding this somewhat curious since I get the same schema error for the referenced bgl file as the OP.  I can't see what version of ADE 2020 you are using.  I suspect it is prior to Alpha 21.  We had to change the decompiler after Alpha 20 due to the original become unsupported.   I get a load in Alpha 19 as you do but in Alpha 21 there is the error.  My guess is that the new decompiler is not generating correct XML source.  I will try and fix that soon

We have fixed on problem which 'lost' the secondary approach lights and now just have the decompiler to sort out