• 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 Navaids in AFD files

danfoster

danfoster

Messages
359
Country
unitedkingdom
Given that FS9 can read Navaids from the stock files, why do some AF2, AFX, and ADE files contain Navaid data? Do the VORs and NDBs in these add-on files not appear in the stock files?

Also, in the xml code some of these navaids appear within the Airport record, and some of them appear afterwards. What's the difference?

Cheers,

Dan
 
danfoster said:
Given that FS9 can read Navaids from the stock files, why do some AF2, AFX, and ADE files contain Navaid data? Do the VORs and NDBs in these add-on files not appear in the stock files?

Also, in the xml code some of these navaids appear within the Airport record, and some of them appear afterwards. What's the difference?

Cheers,

Dan
Click to expand...

ADE stores navaid data in the project file so that it can be used by the approach editor.

Terminal Navaids are located in the Airport record. ILS are stored in the Bgl File along with the airport although in the file itself they are compiled separately (as are taxi signs)

So you are likely to find ILS and terminal NDBs in the airport record.
 
I see, so terminal navaids such as NDBs and Markers appear in the airport record of stock files too, I guess.

What about those navaids outside the airport record (I've seen VORs listed here), but still within the Add-on AFD file? Is that the result of having edited them at some point in the past?

Thanks,

Dan
 
In FS9 it is possible to move navaids to some extent. AFCAD certainly creates duplicates when they are moved so if they have been changed from the stock then they will turn up in the AF2 file. In FSX moving causes duplication so ADE does not allow it. Other utilities do so it is possible to see duplicated navaids in FSX bgl files. In truth the behavior of modified naviads in both FS9 and FSX is not very helpful!
 
danfoster said:
Given that FS9 can read Navaids from the stock files, why do some AF2, AFX, and ADE files contain Navaid data? Do the VORs and NDBs in these add-on files not appear in the stock files?

Also, in the xml code some of these navaids appear within the Airport record, and some of them appear afterwards. What's the difference?

Cheers,

Dan
Click to expand...

Dan

You have to be careful when comparing af2/afx/ad2 naviads.

In the developement of AFCAD (which AFX mimics) we did not know that certain Navaids cannot or should not be moved. AFCAD like ADE shows certain Navaids on the grid but are not compiled as part of the XML. The only time Lee added a NDB or VOR to the XML was if it was moved. In FS9 a VOR and a NDB can be moved a certain amount but will eventually duplicate. FS9 will fallback on the stock navaid position and also read the moved position in Map Mode (from the afcad bgl).

There are 3 Navaids that are also read from another bgl and tied to the route Jet/Victor airways. Those are the Waypoint, NDB and VOR. These type Navaids do not belong to the airport so if a utility does move them then they have to be listed outside the airport record.

Like Jon says we discourage the moving of any Waypoint, NDB or VOR. On the surface, yes in FS9 they can be moved a certain distance but this can also corrupt the route airways. If the route airway becomes corrupt the Map Mode will not open in the Flightplanner and FS9 will crash.

In the GPS the Waypoint is magenta or pink in color. FS assigns that color when the waypoint nest outside the airport record.

If you place a Waypoint or a NDB into the airport record then FS assigns it as a Terminal_Waypoint or Terminal_NDB. These have nothing to do with the route data and can be moved up to a further distance (within the Visual Zone Sector of the airport). The Terminal_Navaid is used for approaches so because approach data is in the airport record so are the Terminal_Navaids. Transitions to the approach phase of a runway may start 45-60 NM's away. The entrance point to the transition is normally a route data type navaid (Waypoint, NDB or VOR). This is why we show them in the project ad2 file for the approach mode editor but do not add them to the XML for compile.

A Terminal_Waypoint nest inside the airport record so FS assigns it the blue color you see in the GPS.

FS9 is a little more forgiving to movement of Navaids then FSX but the only difference is distance before they start duplicating.

In the Navaid property window we do not allow certain data of a navaid to be edited. That is another part of problems that FS does not allow or honor in some cases.
 
Thanks!

Your answers are a perfect explanation of why I am seeing Navaids listed in various different places within my Add-On AFD files.
 
You must log in or register to reply here.
Back
Top