• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

ADE 178 Error - no NAVAIDS after compiling .bgl or when opening an external .bgl

bworld1

bworld1

Messages
10
Country
us-illinois
Well, it's my turn to add to questions about NAVAIDS in ADE. In my case, I discovered a problem that was probably there all along. So, I am still flying P3D 4.5, and I usually fly the A320 from FSdeveloper KCLE35 to WashintonX KDCA. So, I recently upgraded to FSHUD so I could get away form the horrible P3D ATC. I love FSHud! So, one last bit of background, for the AI aircraft, I am using Traffic Global aircraft, but my issue is specifically with ADE and the NAVAIDs. So, FSHud handles the AI aircraft along with everything else. And it uses the latest Navigraph which I purchased.

So, at KCLE, I noticed that the AI aircraft were landing extremely irregular, like touching down half way down the runway, and rolling way past the end. Or diving and ascending sharply during approaches. So, I loaded the edited12_JZ.bgl into ADE. Looking at the approaches, some had approach errors. And when I listed the Navaids, there was only 1 NAVAID listed!. So, I then loaded the .ade file for KCLE35 and in approach mode, I found that a full complement of NAVAIDS were listed.

So, I compiled it, and no matter now many different ways I compiled, the .bgl still had only 1 NAVAID listed! By the way, the Intersection that was needed for runways 24 L/R and 28 was DJB and it was not there in the .bgl and was there in the .ade. So, as a final test today, I loaded the .bgl from WashingtonX for KDCA and went to approach mode. Sure enough, there were approach errors, I specifically looked at RNAV33, and sure enough, there was only 1 NAVAID listed.

I'm trying to figure out what is going on. I always fly out of KCLE and into KDCA for practice, so I didn't catch the approach errors at KCLE in the A320, but I have had a lot of errors trying to approach KDCA, and I thought it was just me making mistakes. The attached file shows .bgl for RNAV33 approach and it's NAVAID list in ADE. Let me know what anybody thinks, please!
 

Attachments

  • image_2023-09-24_151109574.png
    image_2023-09-24_151109574.png
    64.5 KB · Views: 164
Well, I did figure something out in ADE 1.79! When I open an airport such as FSDEV KCLE using BGL and go to approaches, ILS 24L for example is broken, and there are no navaids listed. What I discovered is that the GP.bgl file does have the correct navaids and the approaches are not broken! And even though there is a dropdown "Import approaches" and I can import from the GP.bgl, and it corrects the approaches in the main BGL airport file, if I then compile it, the main BGL is broken and the GP.bgl that gets created is good. I guess I don't understand this. I think that the reason that FSHUD AI aircraft go bonkers is because FSHUD only is looking at the main airport BGL and not the GP BGL. By the way, I also saved the XML with the compile, and the approach data in there is also completely correct, but again P3D 4.5 can use XML scenery, but FSHUD doesn't see that. So, I guess I am done investigating this for now. Also, by the way, other third party airports like Washington X have a similar issue.
 
You must log in or register to reply here.
Back
Top