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

error message when compiling

M

MINOSI

Messages
37
Country
france
hi all...

is there somebody who already encountered this case?

To be conform with the reality, I would sometimes like to renam an airport runways : here form 14 (and 32) to 13 (and 31).
ADE permits to click on the runways and edit them, without difficulties.

So, in the picture, below, we can see the new number and xml code for one of the runways ("13L" : with the red marker) :
xml10.jpg


But when compiling, all the taxipath remain nevertheless attached to the previous numbering.
erreur10.jpg


Since impossible to compile, it's also impossible to extract the xml global code to find and modify by hand the concerned lines...

Create a new airport from zero is of course a solution... But Is there an other , and faster! way?

in all cases, I Thank you ..

Philippe
 
Go to the Fault Finder and run it. It should find the bad links. You can then edit them and correct the runway number. Or delete them and add them again.
 
Jon...

thank for your answer.....

I have finally found (thanks to you! I havn't though to the fault finder)

and the result is somewhere strange a bit : the fault finder finds the same three errors before and after re-numbering: "This is a RUNWAY link type that does not start and/or end on a runway. This may casue ATC and Traffic problems"

But, if this was without consequences before the new numbering, this was not the case after (why ??)

Whatever...
my problem is solved and I'm embarrassed to having disturbed you for a so little one.
It does not absolve me to thank you very much!

Philippe
 
MINOSI said:
Jon...

thank for your answer.....

I have finally found (thanks to you! I havn't though to the fault finder)

and the result is somewhere strange a bit : the fault finder finds the same three errors before and after re-numbering: "This is a RUNWAY link type that does not start and/or end on a runway. This may casue ATC and Traffic problems"

But, if this was without consequences before the new numbering, this was not the case after (why ??)

Whatever...
my problem is solved and I'm embarrassed to having disturbed you for a so little one.
It does not absolve me to thank you very much!

Philippe
Click to expand...

That fault will appear if one or both end nodes for a runway link do not fall within the runway area. It will not stop the airport compiling but it can cause problems with ATC.
 
You must log in or register to reply here.
Back
Top