Issues with the AP in 2024

dadgametime

I’ve posted this before but got no answer. The autopilot does not engage NAV mode if you use a third party livery in 2024. I don’t know what causes it. Any help is greatly appreciated by my passengers. If no one else is having this issue, I will delete this, but it's consistent for me in 2024

MD82

I've had 4x 4-hour flights in it. NAV mode works like a champ. MSFS2024 SU3 Beta. I assume you have a valid LEG, you are close enough to it, your NAV SRC is set to FMS and you are pressing NAV on the AP control panel, correct?

Avionic

Flying first default and then the third party OY-GEA livery from flightsim.to in 2024 SU3 Beta, I have had no issues engaging NAV mode on the AP.

If it is a consistent issue, maybe post a video or screenshot and more detailed description of what is happening, and perhaps someone can help you identify what is going on.

dadgametime

Yeah. I’ve had zero issues with the default liveries and have lots of flights in it, but if I fly the Haida livery, for example, it won’t activate NAV in FMS mode. It will activate in VOR mode, but only balks at FMs

Marionettework

Are you sure you didn’t talk to ATC at some point during the flight? I keep having this issue too, and I thought it came from loading a flight plan from the EFB so I did my first flight yesterday without loading any flight plan and the NAV button worked fine, even though I announced intention to take off. My next flight, I also didn’t load any flight plan, but the NAV button stopped working, and during that flight I requested flight following. I have to test again and see if that’s what breaks it.

dadgametime

Nope. I have never loaded a flight plan from the EFB in the Starship. Entered it as intended through the CDU and put the Nav Source as FMS1 Click NAV on the AP and nothing happens. Switch to VOR as a Source and NAV works fine. It only occurs with third party liveries in '24. I will check 2020 today, but last I checked it, everything was fine in that version. I wonder if it is all liveries or maybe just the one?

Marionettework

@dadgametime said in Issues with the AP in 2024:

Nope. I have never loaded a flight plan from the EFB in the Starship. Entered it as intended through the CDU and put the Nav Source as FMS1 Click NAV on the AP and nothing happens. Switch to VOR as a Source and NAV works fine. It only occurs with third party liveries in '24. I will check 2020 today, but last I checked it, everything was fine in that version. I wonder if it is all liveries or maybe just the one?

Well I'll be damned... I think you're right. I see that in the OY-GEA livery the author put a panel.xml with the following:

<PlaneHTMLConfig>
	
	<Instrument>
		<Name>AS430_1</Name>
		<ComIndex>1</ComIndex>
		<NavIndex>1</NavIndex>
		<NewCDIBehavior>True</NewCDIBehavior>
		<SupportAPFlightDirector>True</SupportAPFlightDirector>
		<DisableAPNavArm>True</DisableAPNavArm>
		<Electric>
			<Simvar name="CIRCUIT ON:135" unit="Boolean"/>
		</Electric>
	</Instrument>

	<Instrument>
		<Name>AS430_2</Name>
		<ComIndex>2</ComIndex>
		<NavIndex>2</NavIndex>
		<NewCDIBehavior>True</NewCDIBehavior>
		<SupportAPFlightDirector>True</SupportAPFlightDirector>
		<DisableAPNavArm>True</DisableAPNavArm>
		<Electric>
			<Simvar name="CIRCUIT ON:135" unit="Boolean"/>
		</Electric>
	</Instrument>

</PlaneHTMLConfig>

I'll add this to the Haida livery and see if that helps.

Marionettework

I think it's fixed now, I uploaded a new version of the MSFS 2024 livery if you want to try it out. You are the man!

andyW2025

I had exactly the same issue and was scratching my head as to why NAV wouldnt activate. Only had the issue with the Haida livery. At least I now know it wasn’t pilot error

dadgametime

It’s absolutely fixed now @Marionettework !