• 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.

FS2004 Simulator not accepting new AFCAD changes

Messages
102
Hi y'all,

Recently started updating my AUS airport again, this time adding approaches. I had started from scratch (long story) saving an airport file out of the afcad file from the AUS2007 addon scenery, and had no problems changing gates, adding buildings, etc. But when I started to add approaches to it, the next time I would start up the sim, the default addon airport would show, completely ignoring all changes made (it's basically just going with the default addon afcad included).

I have faced this problem before. Eliminating the "default addon" afcad simply reverts the airport back to the default FS2004 airport. Priority listing in the addon scenery was checked.

What may be causing this? Changes I made:

-Added waypoints for the approaches (all terminal_waypoints)
-Added ILS/RNAV approaches to 17L/35R (none yet for 17R/35L)
-Departures only out of 17R/35L, TOL ok for 17L/35R (this is symmetric, and even if it wasn't, this tends to only make the sim ignore your runway TOL designations, not outright clear your airport of modifications).

I experimented adding ILS s (no approaches added) to all 4 runway ends to see if that would fix the problem but again this had no effect. I'm aware without touching approaches or navaids, the airport is using the default approaches and navaids, and adding just 1 approach clears the default approaches until you remove the afcad.

This is actually the second time I have added approaches to this airport. The first time was not-eventful, but for some reason this time modifying approaches makes the sim ignore all changes.

The reason I'm doing it a "second time" is I forgot to save the airport files after a factory reset (years of work..), and attempting to create an airport file out of a bgl file you create with ADE in the past makes the sim ignore all changes, like in this case, so I had to start from scratch if I wanted to make any more changes.
 
Last edited:
Bump! I won't bump again. Just hoping at least somebody has similar experiences and might have a theory as to why this may happen.

Note that I cannot see the default navaids on ADE, but I can see them on AFCAD.

Adding ILS also breaks the file (i.e., ignored by FS9) the same way adding approaches does.
 
Last edited:
I have... made an odd discovery.

Note I have Windows 11.

Recently using AFCAD, the sim decided not to honor the changes I made. I wondered "why was the older file accepted but not the newer one?". I thought maybe having a decimal right at all before .bgl broke the file, but that was not the case. I renamed KLGA J3.bgl to just KLGA J.bgl.... and it worked. Changing it to .#.bgl appears to break the file in all cases. I did several tests and this happens to be the case.

Going back to KAUS, simply renaming the file so that it doesn't have a decimal before .bgl, the file works good as new, back to normal.

I conclude having decimals (which I had never done before. Usually "version a, b, c, etc.") before the .bgl breaks the file and causes the sim to ignore it. I also suspect this is why a previous JFK file did not work as well (I also have 1.1 in the name).
 
I am facing the same issue where the stock airport is showing up and my custom terminal isn't showing up I am using Windows 11 as well and could you tell me what the issue is?

My three bgl files are below:
1)CYYG buildings.BGL
2)CYYG je.bgl
3)CYYGTERM_.mdl
 
Back
Top