FSXA Orhan ILS couses dublicate VOR/ILS error.

[soulmaril]

Orphan ILS couses dublicate VOR/ILS error.

I am a newbie and in my first run I deleted a stock runway (with complete ignorence). NOW this caused me an Orphan ILS which I ignored at the begining until I finished the manual. While reading and applying the manual I have come so far that nearly I finished the project but as it is explained in the last quarter of the manual, I faced my orphan ILS at the finals.

It may seem rather OK to have an orphan ILS but what I did before was to create a new ILS with the exact name of the stock one. Thus causing the error message below

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

I can't delete the orphan ILS and I can't delete my new ILS as ADE thinks it is a stock ILS.

How can I come over this problem?

 

[jvile]

I am a newbie and in my first run I deleted a stock runway (with complete ignorence). NOW this caused me an Orphan ILS which I ignored at the begining until I finished the manual. While reading and applying the manual I have come so far that nearly I finished the project but as it is explained in the last quarter of the manual, I faced my orhan ILS at the finals.

It may seem rather OK to have an orphan ILS but what I did before was to create a new ILS with the exact name of the stock one. Thus causing the error message below

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

I can't delete the orphan ILS and I can't delete my new ILS as ADE thinks it is a stock ILS.

How can I come over this problem?

One sure way is to open the XML with notepad and hand delete the code. When you save and compile ADE will generate a XML type file if you place a checkmark in the settings menu. You then open the XML and make the changes /save. Using ADE open the saved XML and then save it as your new .ade project file. You can now add back any original ILS that was seen as a orphan.

There are other ways to get back the original ILS so someone else may give more options.

 

[tgibson]

Hi,

The only problem using the edited XML approach is that you may lose some of the ADE functionality that it provides when you only work from an .ADE file. That may or may not be important in your particular case.

As you found, within ADE the loss of the ILS following the deletion of a runway is a permanent thing - you can't get it back.

The only "perfectly safe" way to get it back is to Open the Stock Airport again, and start over. Depending on how much work you have done, this might not be an option. If so (and you are essentially done with the airport) the XML approach will hopefully not cause much trouble for you.

If after opening your edited XML file in ADE there are some default objects missing from your airport, try using Tools/Load Stock Data to get them back. This might get you back to where you were before. However, check carefully for any problems after this, and save back up .ADE files at each step so you can go back if needed.

Hope this helps,

 

[scruffyduck]

Hi,

The only problem using the edited XML approach is that you may lose some of the ADE functionality that it provides when you only work from an .ADE file. That may or may not be important in your particular case.

As you found, within ADE the loss of the ILS following the deletion of a runway is a permanent thing - you can't get it back.

The only "perfectly safe" way to get it back is to Open the Stock Airport again, and start over. Depending on how much work you have done, this might not be an option. If so (and you are essentially done with the airport) the XML approach will hopefully not cause much trouble for you.

If after opening your edited XML file in ADE there are some default objects missing from your airport, try using Tools/Load Stock Data to get them back. This might get you back to where you were before. However, check carefully for any problems after this, and save back up .ADE files at each step so you can go back if needed.

Hope this helps,

Tom

Perhaps we need to add this to the issue tracker so that we can look at how to recover the situation with orphaned ILS?

 

[tgibson]

OK, It's been added.

 

[scruffyduck]

Thanks Tom

 

[Pyscen]

Tom

Perhaps we need to add this to the issue tracker so that we can look at how to recover the situation with orphaned ILS?

Jon,... maybe this could be one of the "locked" items and when the user unlocks,.. ADE gives a warning? Sounds good?

 

[soulmaril]

Experience is too valuable, thanks for the support, thank you all.

 

[scruffyduck]

Jon,... maybe this could be one of the "locked" items and when the user unlocks,.. ADE gives a warning? Sounds good?

As I recall there are dire warnings when a runway with stock ILS is deleted. It would be quite simple to rec-connect the ILS to its old runway (assuming it still exists) but there are all sorts of interesting issues if the user renumbers and then adds user ILS etc that need to be considered

 

[Pyscen]

As I recall there are dire warnings when a runway with stock ILS is deleted. It would be quite simple to rec-connect the ILS to its old runway (assuming it still exists) but there are all sorts of interesting issues if the user renumbers and then adds user ILS etc that need to be considered

Then to add to the complications,... when the rubber band enviroment comes into play