Compile Error - Duplicate VOR/ILS

[Colin Gray]

Good morning all,

I am trying to convert a FS9 airport to FSX. If I import it into ADE and try to compile it, I get an error message for duplicate VOR/ILS. Looking at the default FSX airport and the one that I am trying to port over shows that the ILS's are in different locations. I'm not sure if this is the issue or not. I'm also not sure which location would be correct. What I've read up until now is that you cannot remove FSX nav aids. I am assuming this is the case here. Am I correct in thinking this would result in two ILS with the same identifiers at slightly different locations? Is there anything I can do about this? Would this be a case of me needing to orphan one of the ILS's, or is it something else?

Here is the error message I get when compiling...

Parsing document: C:\MSFS\FS Design Tools\Airport Design Editor 170\!AdeTempWorkOnly\PAOM_ADEX_RW_ADE.xml

INTERNAL COMPILER ERROR: #C2593:
**** DUPLICATE VOR/ILS ****
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = United States
ERROR: state = Alaska
ERROR: city = Nome
ERROR: name = Nome
ERROR: lat = 64.5122028887272
ERROR: lon = -165.445247143507
ERROR: alt = 11.278M
ERROR: magvar = -17.1990051269531
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: ident = PAOM
ERROR: >
ERROR: <Runway
ERROR: lat = 64.5115306600928
ERROR: lon = -165.450102835894
ERROR: alt = 11.278M
ERROR: surface = ASPHALT
ERROR: heading = 109.75
ERROR: length = 1823.01M
ERROR: width = 45.72M
ERROR: number = 09
ERROR: designator = NONE
ERROR: patternAltitude = 335.28M
ERROR: primaryTakeoff = YES
ERROR: primaryLanding = YES
ERROR: primaryPattern = LEFT
ERROR: secondaryTakeoff = YES
ERROR: secondaryLanding = YES
ERROR: secondaryPattern = LEFT
ERROR: >
ERROR: <Ils
ERROR: lat = 64.515511058
ERROR: lon = -165.475822538
ERROR: alt = 11.278M
ERROR: heading = 289.748992919922
ERROR: frequency = 108.700
ERROR: end = SECONDARY
ERROR: range = 27.0N
ERROR: magvar = -17.1990051269531
ERROR: ident = IOME
ERROR: width = 5
ERROR: name = ILS/DME 27
ERROR: backCourse = FALSE
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2024: Failed to process closing element tag <Ils> near line 160!
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed

 

[scruffyduck]

Please attach the project file (.ad4) to a post in this thread so that we can check it

 

[Colin Gray]

Good morning Jon,

Thanks for getting back. Here is the project file. I have the pro key, so I should be able to make any changes you suggest.

Cheers,

colin

 

[tgibson]

In Raw Data View, open the airport tree, then open Rwy 9. Look at the bottom of that tree, there are two identical ILSs there. Pick the one with the later modified date (I assume this is the one that got added) and click the Delete button. It will disappear. The airport will now compile.

Hope this helps,

 

[Colin Gray]

That seems to have worked. Thank you very much !!

 

[Jay Bloomfield]

I didn't want to start a new thread about this, but my question is about Navaid ID changes. Some time during 2018, the RL VOR at OBBI (Bahrain) was changed from BAH to BHR. I assume that the solution is the same as for the ILS issue. I open the stock airport, edit the VOR name and ID in raw data view and compile. But since there is no tag like "deleteAllNavaids", how does the sim decide that there are aren't two VORs for OBBI, one from the compiled file (highest priority in my scenery library) and one from the stock OBBI in the APX file?

 

[tgibson]

Glad to help.

Jay, it won't. You will end up with two navaids located there.

 

[Jay Bloomfield]

Thanks Tom. I figured as much. The only way to get rid of the old VOR is to update the stock NVX file.

 

[Jay Bloomfield]

I have one more question, sorry. Where does ADE find the VOR information for a stock airport? I assumed that it found the information in the corresponding stock NVX.BGL file? I know that ADE doesn't compile them. The reason that I asked is that I did a test by changing the BAH VOR entry to BHR and recompiling the NVX BGL file. ADE still listed the VOR as being BAH.

 

[scruffyduck]

ADE uses it's own databases which were created from stock bgl files. The general idea is that we should not modify stock bgl files. There is a function to recreate the databases which is in the current development version under Tools. However I checked it this morning and it seems to be throwing a silent error. I am currently in the process of packing myself to travel to Florida. I am not sure I will have time to figure out why this is failing before I leave. If not then I will take a look once I get settled in down in FL

 

[Jay Bloomfield]

Enjoy the warm weather. I only noticed this, because fsaerodata updates the stock P3d4/FSX files, as it maintains the sim's database at the most recent AIRAC:

https://www.fsaerodata.com/

fsaerodata actually replaces the stock APX files (as I understand it, to update ILS and NDB) and then adds other BGL files to the scenery library in order to update navaids (it doesn't modify the NVX files), comms, SIDs, STARs, approaches, magdec and airspace boundaries. Little NavMap lists the scenery order correctly with fsaerodata installed and P3d4 also recognizes all the updates correctly.