Aircraft refuse to follow localizer

User Support Hub SDK
1

I have made the scenery of MPTO, and there is one ILS (3R) for it. When I try to land there using approach mode, the offset of the aircraft from localizer keeps increasing, and it seems that the aircraft is flying a path parallel but not align with the runway. I’ve checked the aircraft by flying to other airports with ILS, no problem so far. When I disconnect the autopilot to approach manually, it seems that there is no problem with the placement and orientation of the localizer, I can align with runway very well by manually centering the diamond for the localizer. I have no clue on what’s being wrong with the ILS entry. The code for runway 3R is pasted below

	<Runway lat="9.05956666663616" lon="-79.38581527781403" alt="8.32104932889342" heading="29.47999954223633" length="3050.00000000000000" width="45.00000000000000" patternAltitude="304.79998779296875" surface="{2E0DE83F-B79A-4435-905C-DCBBEAC55C59}" transparent="FALSE" number="03" designator="R" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="RIGHT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.00000000000000" secondaryMarkingBias="0.00000000000000" groundMerging="FALSE" excludeVegetationAround="TRUE">
		<RunwayDeformation alt="6.300000" ratio="0.000000"/>
		<RunwayDeformation alt="10.300000" ratio="1.000000"/>
		<Markings edges="TRUE" threshold="TRUE" alternateThreshold="FALSE" fixedDistance="TRUE" alternateFixedDistance="FALSE" touchdown="TRUE" alternateTouchdown="FALSE" dashes="TRUE" ident="TRUE" leadingZeroIdent="FALSE" precision="TRUE" alternatePrecision="FALSE" edgePavement="TRUE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE"/>
		<Lights center="LOW" edge="MEDIUM" centerRed="TRUE"/>
		<BlastPad end="PRIMARY" surface="{00000000-0000-0000-0000-000000000000}" length="60.000000"/>
		<BlastPad end="SECONDARY" surface="{00000000-0000-0000-0000-000000000000}" length="60.000000"/>
		<Overrun end="SECONDARY" surface="{DDA4BB40-36F4-4CD3-8B2A-46D9C954FE00}" length="90.000000" width="90.000000"/>
		<ApproachLights end="PRIMARY" system="CALVERT" strobes="0" endLights="FALSE" touchdown="FALSE" snapToGround="FALSE" reil="FALSE" offset="30.480000" spacing="30.480000" slope="0.000000"/>
		<Vasi end="PRIMARY" side="LEFT" type="PAPI4" biasX="40.000000" biasZ="1065.000000" spacing="90.000000" pitch="3.000000"/>
		<Ils lat="9.07317777777858" lon="-79.37808055555500" alt="16.99999999813735" end="PRIMARY" ident="INAT" range="50017.00000000000000" magvar="4.000000" heading="29.47999954223633" frequency="110.70000000000000" width="5.000000" name="ILS RW03R" backCourse="FALSE">
			<Dme lat="9.05028292596221" lon="-79.39109548867093" alt="7.50000000000000" range="18520.00000000000000"/>
			<GlideSlope lat="9.05028292596221" lon="-79.39109548867093" alt="7.50000000000000" pitch="3.000000" range="18520.00000000000000"/>
		</Ils>
		<RunwayStart end="PRIMARY" lat="9.04797188671075" lon="-79.39241144890073" alt="27.67350224016517" heading="29.47999954223633"/>
		<RunwayStart end="SECONDARY" lat="9.07120007770148" lon="-79.37920129696451" alt="-6.88832043686599" heading="209.47999572753906"/>
	</Runway>

I’ve tried to put the location of glideslope on the center of the runway, and put the DME to be co-located with glideslope (which is far before runway threshold in real case), but none of them help. Does anyone could point out the problem? Thanks in advance

427
4271920×1040 178 KB

2

Are you using the in SDK editor to place the ILS or editing it in the xml file?
I tried doing it by editing the xml file, but found it would never centre on the runway works fine using the sdk ils editor.

3

I entered the location of the localizer, glideslope and DME in XML file using information from AIP directly at first, but the aircraft gets wrong, then I tried to edit the position in developer mode, still no luck

4

Did you remove the edit you made in the xml folder in case it causes a conflict with the in sim sdk editor.
Just to make sure did you make sure to place the dme at the other end of the runway and have the heading set in the direction of landing? Sorry if you have.

5

It just makes no difference

6

I had this issue with my BWI scenery and it turned out to be an issue with the magnetic vs true headings. For the ILS I needed to use magnetic heading instead of true.

1 Like