Coding SID for my custom airport, but the final waypoint of the SID doesn't show.

Mazzar · 13 Mar 2021

In game shows like this, the final waypoint of the SID doesn't show at the FP, but can see the BUTID TRANS at departures page.

Here is the chart I used.

Here is the code of mine.

XML:

<Departure name="BUT01D">
 <RunwayTransitions>
  <RunwayTransitionLegs number="06" designator="NONE">
   <Leg type="VA" magneticCourse="58.0" altitudeDescriptor="+" altitude1="1970.0F"/>
   <Leg type="DF" fixType="VOR" fixRegion="ZY" fixIdent="LJB" flyOver="FALSE" altitudeDescriptor="+" altitude1="7880.0F"/>
  </RunwayTransitionLegs>
 </RunwayTransitions>
 <CommonRouteLegs/>
 <EnrouteTransitions>
  <EnrouteTransitionLegs>
   <Leg type="IF" fixType="VOR" fixRegion="ZY" fixIdent="LJB"/>
   <Leg type="TF" fixType="TERMINAL_WAYPOINT" fixRegion="ZY" fixIdent="BUTID" magneticCourse="108.0"/>
  </EnrouteTransitionLegs>
 </EnrouteTransitions>
</Departure>

PS, I tried to add the lat/long of the BUTID, doesn't works. (I can type the BUTID into the FMC means the waypoint was in the database.) Tried move the Legs from transitionlegs into the runwaytransitionlegs with no luck.

Kenny Chen · 13 Mar 2021

You need to define TERMINAL_WAYPOINT "BUTID" like
<Waypoint lat="xxx" lon="xxx" magvar="0.0" waypointType="NAMED" waypointRegion="xx" waypointIdent="BUTID"/>
in this navaid file, and exclude all TERMINAL_WAYPOINT in airport definition to avoid CTD.

Mazzar · 14 Mar 2021

Kenny Chen said:
You need to define TERMINAL_WAYPOINT "BUTID" like
<Waypoint lat="xxx" lon="xxx" magvar="0.0" waypointType="NAMED" waypointRegion="xx" waypointIdent="BUTID"/>
in this navaid file, and exclude all TERMINAL_WAYPOINT in airport definition to avoid CTD.

Thanks for your advice, I tried like this, but still doesn't work, missing BUTID (PS, I didn't define LJB, but the VOR still useable in the game, even I set the to delete to TURE)

XML:

<DeleteAirport deleteAllApproaches="TRUE" deleteAllApronLights="TRUE" deleteAllAprons="TRUE" deleteAllFrequencies="TRUE" deleteAllHelipads="TRUE" deleteAllRunways="TRUE" deleteAllStarts="TRUE" deleteAllTaxiways="TRUE" deleteAllBlastFences="TRUE" deleteAllBoundaryFences="TRUE" deleteAllJetways="TRUE" deleteAllControlTowers="TRUE" deleteAllDepartures="TRUE" deleteAllArrivals="TRUE" deleteAllPaintedElements="TRUE" deleteAllLightSupports="TRUE" deleteAllTaxiwaySigns="TRUE" deleteAllILSs="TRUE" deleteAllTerminalWaypoints="TRUE" deleteAllTerminalNDBs="TRUE"/>
<Departure name="BUT01D">
 <RunwayTransitions>
  <RunwayTransitionLegs number="06" designator="NONE">
   <Leg type="VA" magneticCourse="58.0" altitudeDescriptor="+" altitude1="1970.0F"/>
   <Leg type="DF" fixType="VOR" fixRegion="ZY" fixIdent="LJB" flyOver="FALSE" altitudeDescriptor="+" altitude1="7880.0F"/>
  </RunwayTransitionLegs>
 </RunwayTransitions>
 <CommonRouteLegs/>
 <EnrouteTransitions>
  <EnrouteTransitionLegs>
   <Leg type="IF" fixType="VOR" fixRegion="ZY" fixIdent="LJB"/>
   <Leg type="TF" fixType="TERMINAL_WAYPOINT" fixRegion="ZY" fixIdent="BUTID" magneticCourse="108.0"/>
  </EnrouteTransitionLegs>
 </EnrouteTransitions>
</Departure>
</Airport>
<Waypoint lon="127.2833333" lat="43.62333333" magvar="9.0" waypointType="NAMED" waypointRegion="ZY" waypointIdent="BUTID"/>
</FSData>

Mazzar · 14 Mar 2021

Tried on CJ4 WT, the SID doesn't work at all.

Kenny Chen · 14 Mar 2021

Try the sequence like
<Waypoint lon="127.2833333" lat="43.62333333" magvar="9.0" waypointType="NAMED" waypointRegion="ZY" waypointIdent="BUTID"/>
</Airport>
------
Looks like <Airport> tag should be the last one.

Mazzar · 14 Mar 2021

Kenny Chen said:
Try the sequence like
<Waypoint lon="127.2833333" lat="43.62333333" magvar="9.0" waypointType="NAMED" waypointRegion="ZY" waypointIdent="BUTID"/>
</Airport>
------
Looks like <Airport> tag should be the last one.

Worked it out, because I use navigraph data so I can use the fixtype WAYPOINT instead of define the waypoint by myself，so if I code the SID like this, the user must have the navigraph data I think.

The trick is change the fixtype of BUTID from TERMINAL_WAYPOINT to WAYPOINT .

XML:

<Departure name="BUT01D">
 <RunwayTransitions>
  <RunwayTransitionLegs number="06" designator="NONE">
   <Leg type="VA" magneticCourse="58.0" altitudeDescriptor="+" altitude1="1970.0F"/>
   <Leg type="DF" fixType="VOR" fixRegion="ZY" fixIdent="LJB" flyOver="FALSE" altitudeDescriptor="+" altitude1="7880.0F"/>
  </RunwayTransitionLegs>
 </RunwayTransitions>
 <CommonRouteLegs/>
 <EnrouteTransitions>
  <EnrouteTransitionLegs>
   <Leg type="IF" fixType="VOR" fixRegion="ZY" fixIdent="LJB"/>
   <Leg type="TF" fixType="WAYPOINT" fixRegion="ZY" fixIdent="BUTID" magneticCourse="108.0"/>
  </EnrouteTransitionLegs>
 </EnrouteTransitions>
</Departure>

Mazzar · 15 Mar 2021

I give up on useing the navigraph data，It works when only one SID，but CTD when I create another SID.
The safe way is use the TERMINAL_WAYPOINT and define the waypoint by my self.

Kenny Chen · 15 Mar 2021

Mazzar said:
I give up on useing the navigraph data，It works when only one SID，but CTD when I create another SID.
The safe way is use the TERMINAL_WAYPOINT and define the waypoint by my self.

That’s true for me even I’m not using navigraph. I also needs to define all my waypoints.

Mazzar · 15 Mar 2021

Kenny Chen said:
That’s true for me even I’m not using navigraph. I also needs to define all my waypoints.

Yes, and the waypoint define should be in the <Airport> tag, Thanks for your advice.

Amorisia · 24 May 2021

Kenny Chen said:
That’s true for me even I’m not using navigraph. I also needs to define all my waypoints.

Hi, I have been reading all your replies and I was wondering if maybe you have a clue for me as I got a problem with my region and waypoints definitions for my ILS. I am creating the new Chengdu Tianfu airport as I live in Chengdu. Last year I created it with everything as fictive names for all waypoints and ILS but also the region, in which I randomly put "TF" (for Tianfu, yes that time I was not aware about region definition codes. The SDK documentation say I should put CN for China, but people on this forum put regions found on LittleNavMap so I want to change it for ZP as it is the code for Chengdu).

Now that I got the airport chart I want to add all STARs and SIDs etc but first I am trying to change fictive names into real ones.

Below here is my waypoints and approach definition for the ILS 01 as it has been always working.

XML:

        <Waypoint lat="30.19241146870410" lon="104.37140833238600" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF502"/>
        <Waypoint lat="30.09179600000000" lon="104.32429100000000" magvar="2.2" waypointType="NAMED" waypointRegion="TF" waypointIdent="TF503"/>
        <Waypoint lat="30.42177286446640" lon="104.47929345150200" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF102"/>
        
        <Approach type="ILS" runway="01" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" altitude="5000.0F" heading="024.495" missedAltitude="5000.0F">
            <ApproachLegs>
                <Leg type="IF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF503" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="14.05N" altitudeDescriptor="I" altitude1="5000.0F" altitude2="5000.0F"/>
                <Leg type="CF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" flyOver="FALSE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="7.55N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="5000.0F"/>
                <Leg type="CF" fixType="RUNWAY" fixRegion="TF" fixIdent="RW01" flyOver="TRUE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="1.05N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="442M"/>
            </ApproachLegs>
            <MissedApproachLegs>
                <Leg type="CA" magneticCourse="024.495" altitudeDescriptor="+" altitude1="5000.0F"/>
                <Leg type="DF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" flyOver="TRUE" turnDirection="L" altitudeDescriptor="A" altitude1="5000.0F"/>
                <Leg type="HM" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" turnDirection="L" magneticCourse="204.495" time="1.0" altitudeDescriptor="A" altitude1="5000.0F"/>
            </MissedApproachLegs>
        </Approach>       
        
    </Airport>
</FSData>

When trying this approach, ATC tells me to go for an ILS approach so all is ok except names and distances.

Then anytime I try to change the region to ZP, or waypoints name to real ones (TF503 to TT503 and TF502 to FAF01 or D109F because the FAF does not have name etc) ATC always ask me to go for a visual approach. I can select ILS in the flight organizer, my approach in the A32NX is considered as ILS but the ATC give me visual approach. Also, the VFR map does not display my route correctly and the FPLN page in the FMS refuse to open.

So then I try to change back everything but it just will not come back to the working version, I always need to copy my backup BGL file into the project folder to get the ILS working again with ATC and flight plan.

Any idea about this problem ? I have been stuck here about two days, tried everything, looked every post on this forum, nothing helped and I am just frustrated that I cannot continue to create this inexistant airport in the game.

Thank you

Mazzar · 24 May 2021

Amorisia said:
Hi, I have been reading all your replies and I was wondering if maybe you have a clue for me as I got a problem with my region and waypoints definitions for my ILS. I am creating the new Chengdu Tianfu airport as I live in Chengdu. Last year I created it with everything as fictive names for all waypoints and ILS but also the region, in which I randomly put "TF" (for Tianfu, yes that time I was not aware about region definition codes. The SDK documentation say I should put CN for China, but people on this forum put regions found on LittleNavMap so I want to change it for ZP as it is the code for Chengdu).

Now that I got the airport chart I want to add all STARs and SIDs etc but first I am trying to change fictive names into real ones.

Below here is my waypoints and approach definition for the ILS 01 as it has been always working.

XML:

<Waypoint lat="30.19241146870410" lon="104.37140833238600" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF502"/> <Waypoint lat="30.09179600000000" lon="104.32429100000000" magvar="2.2" waypointType="NAMED" waypointRegion="TF" waypointIdent="TF503"/> <Waypoint lat="30.42177286446640" lon="104.47929345150200" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF102"/> <Approach type="ILS" runway="01" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" altitude="5000.0F" heading="024.495" missedAltitude="5000.0F"> <ApproachLegs> <Leg type="IF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF503" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="14.05N" altitudeDescriptor="I" altitude1="5000.0F" altitude2="5000.0F"/> <Leg type="CF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" flyOver="FALSE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="7.55N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="5000.0F"/> <Leg type="CF" fixType="RUNWAY" fixRegion="TF" fixIdent="RW01" flyOver="TRUE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="1.05N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="442M"/> </ApproachLegs> <MissedApproachLegs> <Leg type="CA" magneticCourse="024.495" altitudeDescriptor="+" altitude1="5000.0F"/> <Leg type="DF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" flyOver="TRUE" turnDirection="L" altitudeDescriptor="A" altitude1="5000.0F"/> <Leg type="HM" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" turnDirection="L" magneticCourse="204.495" time="1.0" altitudeDescriptor="A" altitude1="5000.0F"/> </MissedApproachLegs> </Approach> </Airport> </FSData>

When trying this approach, ATC tells me to go for an ILS approach so all is ok except names and distances.

Then anytime I try to change the region to ZP, or waypoints name to real ones (TF503 to TT503 and TF502 to FAF01 or D109F because the FAF does not have name etc) ATC always ask me to go for a visual approach. I can select ILS in the flight organizer, my approach in the A32NX is considered as ILS but the ATC give me visual approach. Also, the VFR map does not display my route correctly and the FPLN page in the FMS refuse to open.

So then I try to change back everything but it just will not come back to the working version, I always need to copy my backup BGL file into the project folder to get the ILS working again with ATC and flight plan.

Any idea about this problem ? I have been stuck here about two days, tried everything, looked every post on this forum, nothing helped and I am just frustrated that I cannot continue to create this inexistant airport in the game.

Thank you

Sounds like a piority issue, have you setup the to delete tag, and the content.xml？

Amorisia · 24 May 2021

Mazzar said:
Sounds like a piority issue, have you setup the to delete tag, and the content.xml？

Hi Mazzar,

Thank you for your reply. I did not set any delete tag because there were no airport here. As soon as I come back home I will try to select all delete tags and try.

About the content.xml I cannot find this file in my project folder. Do you mean the content info like airport name, region, city, country and also the thumbnail picture ?

Mazzar · 24 May 2021

content.xml define the piorty of the contents, there are sevral navdata like stock navdata, navigraph navdata, senery navdata. the game use content.xml like a sheet, from top to the bottom piorty raises.

C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

Mazzar · 24 May 2021

Amorisia said:
Hi Mazzar,

Thank you for your reply. I did not set any delete tag because there were no airport here. As soon as I come back home I will try to select all delete tags and try.

About the content.xml I cannot find this file in my project folder. Do you mean the content info like airport name, region, city, country and also the thumbnail picture ?

Why you don't use the navigraph procedures？My custom zggg senery works with navigraph procedures very well.
FYI

ILS 01 Z ZGGG wrong ILS frequency

That is just a test, I quit very quickly, I will also delete it.

forum.navigraph.com

Amorisia · 24 May 2021

Mazzar said:
content.xml define the piorty of the contents, there are sevral navdata like stock navdata, navigraph navdata, senery navdata. the game use content.xml like a sheet, from top to the bottom piorty raises.

C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

ok thank you. so if I share my package to other people in the future, they will have to change my package priority in this file also ? or maybe it is a conflict with older versions of my project ? seems very weird as I never did it for other third party addons and all are working well.

Amorisia · 24 May 2021

Mazzar said:
Why you don't use the navigraph procedures？My custom zggg senery works with navigraph procedures very well.
FYI

ILS 01 Z ZGGG wrong ILS frequency

That is just a test, I quit very quickly, I will also delete it.

forum.navigraph.com

I did not buy Navigraph yet. Also, I am not sure Navigraph already has these procedures for ZUTF airport as it is new and still not opened to public. will open on June 30.

Mazzar · 24 May 2021

Amorisia said:
ok thank you. so if I share my package to other people in the future, they will have to change my package priority in this file also ? or maybe it is a conflict with older versions of my project ? seems very weird as I never did it for other third party addons and all are working well.

I don't know the piority thing very clear, just a guess. A friend told me the navigraph have updated the zptf procedures.

Amorisia · 24 May 2021

Mazzar said:
Sounds like a piority issue, have you setup the to delete tag, and the content.xml？

Hi Mazzar,

As you recommended to me, I set all deletes then I first put my package in 15th position in content.xml in order to let asobo default packages first. It first did not work. But then, I tried to put my package in first position and it worked. So, what if I release my package to other people they will need to put it in first position in the content.xml ? I think many people does not know that so they will tell me that my package does not work.

By the way I can now continue to develop my SIDs and STARs with my package in first position in content.xml. Just scared that it will not work for other people...

Thank you very much for your patience

PS : I will maybe have one or two questions later as I will integrate STARs first. On the chinese chart I got, each STAR is set for two runways at the same time. so I will first have a EnrouteTransition for the arrival, then two RunwayTransitions (one for each Runway). then in the ILS approach can I put all the final RNAV waypoints and the ILS ones in one ApproachLegs part, or I have to separate the RNAV waypoints in an other part ? As an exemple I attach the first approach I am working on with the ILS. I think if I understand how to create one, I will easily create all.

Amorisia · 24 May 2021

Mazzar said:
I don't know the piority thing very clear, just a guess. A friend told me the navigraph have updated the zptf procedures.

Many thanks for your time and help. I just finished to create STARs. Everything is working perfectly now. Just this little matter if I share my airport how to automatically manage priority. I will look for a solution before release.

Have a good day,

Chris

GabrielFilipe · 5 May 2023

Amorisia said:
Hi, I have been reading all your replies and I was wondering if maybe you have a clue for me as I got a problem with my region and waypoints definitions for my ILS. I am creating the new Chengdu Tianfu airport as I live in Chengdu. Last year I created it with everything as fictive names for all waypoints and ILS but also the region, in which I randomly put "TF" (for Tianfu, yes that time I was not aware about region definition codes. The SDK documentation say I should put CN for China, but people on this forum put regions found on LittleNavMap so I want to change it for ZP as it is the code for Chengdu).

Now that I got the airport chart I want to add all STARs and SIDs etc but first I am trying to change fictive names into real ones.

Below here is my waypoints and approach definition for the ILS 01 as it has been always working.

XML:

<Waypoint lat="30.19241146870410" lon="104.37140833238600" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF502"/> <Waypoint lat="30.09179600000000" lon="104.32429100000000" magvar="2.2" waypointType="NAMED" waypointRegion="TF" waypointIdent="TF503"/> <Waypoint lat="30.42177286446640" lon="104.47929345150200" magvar="2.2" waypointType="FAF" waypointRegion="TF" waypointIdent="TF102"/> <Approach type="ILS" runway="01" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" altitude="5000.0F" heading="024.495" missedAltitude="5000.0F"> <ApproachLegs> <Leg type="IF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF503" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="14.05N" altitudeDescriptor="I" altitude1="5000.0F" altitude2="5000.0F"/> <Leg type="CF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF502" flyOver="FALSE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="7.55N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="5000.0F"/> <Leg type="CF" fixType="RUNWAY" fixRegion="TF" fixIdent="RW01" flyOver="TRUE" recommendedType="LOCALIZER" recommendedRegion="TF" recommendedIdent="ITF" theta="024.495" rho="1.05N" magneticCourse="024.495" distance="6.5N" altitudeDescriptor="A" altitude1="442M"/> </ApproachLegs> <MissedApproachLegs> <Leg type="CA" magneticCourse="024.495" altitudeDescriptor="+" altitude1="5000.0F"/> <Leg type="DF" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" flyOver="TRUE" turnDirection="L" altitudeDescriptor="A" altitude1="5000.0F"/> <Leg type="HM" fixType="TERMINAL_WAYPOINT" fixRegion="TF" fixIdent="TF102" turnDirection="L" magneticCourse="204.495" time="1.0" altitudeDescriptor="A" altitude1="5000.0F"/> </MissedApproachLegs> </Approach> </Airport> </FSData>

When trying this approach, ATC tells me to go for an ILS approach so all is ok except names and distances.

Then anytime I try to change the region to ZP, or waypoints name to real ones (TF503 to TT503 and TF502 to FAF01 or D109F because the FAF does not have name etc) ATC always ask me to go for a visual approach. I can select ILS in the flight organizer, my approach in the A32NX is considered as ILS but the ATC give me visual approach. Also, the VFR map does not display my route correctly and the FPLN page in the FMS refuse to open.

So then I try to change back everything but it just will not come back to the working version, I always need to copy my backup BGL file into the project folder to get the ILS working again with ATC and flight plan.

Any idea about this problem ? I have been stuck here about two days, tried everything, looked every post on this forum, nothing helped and I am just frustrated that I cannot continue to create this inexistant airport in the game.

Thank you

can you help me create sid and star for my custom airport? I don't know anything about creating, I saw that you created yours

Coding SID for my custom airport, but the final waypoint of the SID doesn't show.

Attachments