Hello,

It seems like ORBX ESSA has 19R exit taxiway links broken (BATC airport map clearly shows this issue) that resulted in arriving traffic tends to disappear after landing. This issue could have been easily fixed back in P3D days, but not anymore, since editing 3rd party airport facilities in MSFS is more complex and not straight-forward. Is there any way to override such deficiencies in BATC?

TIA. 

4 minutes ago, G-YMML1 said:

Hello,

It seems like ORBX ESSA has 19R exit taxiway links broken (BATC airport map clearly shows this issue) that resulted in arriving traffic tends to disappear after landing. This issue could have been easily fixed back in P3D days, but not anymore, since editing 3rd party airport facilities in MSFS is more complex and not straight-forward. Is there any way to override such deficiencies in BATC?

TIA. 

On a different kind of problem I have been suffering from a strange tendency from LPPT 's Traffic to send me backtracking on rw20 for takeoff.

This started since a couple BATC updates and having entered fs2024 beta.

 

You can only ask the devs... In case of ESSA it is Marcus Nyberg. He is very helpful! You can find him via the Orbx forum...

Yeah until BATC decouples their node system from the sceneries or have an editor that allows you to edit the generated nodes we will always run into this issue. 

I read on SI site that they do not take into account ADE taxiways. Interesting

Can ADE even be used for MSFS?   I didn't think Jon (scruffyduck) was developing it anymore.  Or are you referring to it as we used to all it "AFCAD", after the program used to edit?

56 minutes ago, G-YMML1 said:

I read on SI site that they do not take into account ADE taxiways. Interesting

Not sure what you mean by that, but you can just go into developer mode in MSFS, fix what needs to be fixed, save as a new package and then load both the original airport and the new fix-package. This works for BATC. People have already done it for EHAM, LKPR etc. and put it on flightsim.to, specifically for BATC

26 minutes ago, Mace said:

Can ADE even be used for MSFS?   I didn't think Jon (scruffyduck) was developing it anymore.  Or are you referring to it as we used to all it "AFCAD", after the program used to edit?

My understanding, as well of folks from AIG, that MSFS2020 SDK is so convoluted in this area, that it’s almost impossible to produce easy-to-use software similar to ADE that we had back in P3D days. I, myself, created and edited many dozens of ADE for various 3rd party airports. Not anymore 

1 minute ago, Fiorentoni said:

Not sure what you mean by that, but you can just go into developer mode in MSFS, fix what needs to be fixed, save as a new package and then load both the original airport and the new fix-package. This works for BATC. People have already done it for EHAM, LKPR etc. and put it on flightsim.to, specifically for BATC

thanks 
 

Which section of flightsim.to I should look for?

 

Eham for FT is okey 

2 hours ago, G-YMML1 said:

My understanding, as well of folks from AIG, that MSFS2020 SDK is so convoluted in this area, that it’s almost impossible to produce easy-to-use software similar to ADE that we had back in P3D days. I, myself, created and edited many dozens of ADE for various 3rd party airports. Not anymore 

I figured that, but really my question was, are we now calling this an "ADE"?   I've never heard it called that before, we always called it an AFCAD, even though that too was a misnomer even in P3D days

I used the term "AFD file" when I was using ADE to modify parking spots/taxiways/AI pathways in P3D. I must have modified literally hundreds (and possibly thousands) of "AFD" files in FSX and P3D over the years. I enjoyed being able to do it, but my fussy nature resulted in me spending a lot more time tweaking things to perfection than I would have liked. The end result of not being able to do this in MSFS 2020 is that I do a lot more flying than tweaking these days!!

Bearing this in mind, I do think that airport addon developers need to be a bit more careful with stuff like this. There is nothing more frustrating to hardcore flight simmers than incorrectly defined parking spots, incorrectly positioned parking spots (where the alignment with the lines is not very good), and of course my personal top of the list annoyance......misaligned runway centreline markings.

Edited May 15, 20251 yr by Christopher Low

12 hours ago, Christopher Low said:

I used the term "AFD file" when I was using ADE to modify parking spots/taxiways/AI pathways in P3D. I must have modified literally hundreds (and possibly thousands) of "AFD" files in FSX and P3D over the years. I enjoyed being able to do it, but my fussy nature resulted in me spending a lot more time tweaking things to perfection than I would have liked.

Ah yes, I used to get in there and ever-so-slightly drag a node next to another to achieve the desired AI taxi and flow...I have forgotten a lot of what I once knew about this.  There used to be ways to manipulate nodes vs. parking spaces to finesse pushback, control which runways were used, etc. etc.    I come from the Jim Vile school of design, he knew everything there was to know about writing approaches, and a lot about other aspects of airport design, things that we don't have much of today.  Today it's all spam-it-out-and-make-it-look-pretty, but "where's the beef?" as the lady used to say on TV.

I do wish there was an easy way to do it today.  In some ways, P3D and FSX are superior because of this extensibility and tools.  I guess with the passage of time, similar tools to ADE and/or AFCAD will appear for MSFS.