Direct to function not working properly and other avionics issues

Bug Reporting Hub Aircraft & Systems
, ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue: Direct to function of FMC not working properly. When selecting Direct to a waypoint the FMC places the waypoint in the top “from” line and directs from that point to the following point.
Constant issues at various airports with frequencies not auto loading, but then also when manual loading, not receiving. Various times and airports where procedures seem to load into the FMC but won’t showing on the MFD map and autopilot will not fly.

If applicable, which aircraft is experiencing this issue:King Air GTX

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Often. Almost every flight.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start flight
  2. Program FMC
  3. Watch plane not go direct to a fix or do weird avionics things.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?
no

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

12
[PC Only] What GPU (Graphics Card) do you use?

4080 Super
[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

I like to fly this plane. It’s a good platform, but it’s trying to get me violated or kill me…virtually speaking of course.

3

Flew from LOWG to LOWS and noticed all was good until I added the ILS approach to 15 LOWS mid-flight. Had to remove the ILS to prevent the FMC from advancing past NUBRA on the arrival. Waited until past NUBRA on the arrival then added the ILS again, and all was good from that point.
Weird stuff.
Had a direct to fix and it worked fine. Apparently, the FMC doesn’t like it when you add an approach early.

4

You mean advancing past NUBRA but not on the NUBR3R STAR?

Was there a discontinuity between NUBRA an SBG?

5

Do you have the same issue if you follow the OP’s steps to reproduce it?
• FMC will not accept any TO points in the RTE page

Provide extra information to complete the original description of the issue:
• This was working yesterday (12/30) not working today (12/31)

If relevant, provide additional screenshots/video:
•

6

So when you are initially setting up the route on the RTE 1 page you can enter an intersection as a direct? I used this yesterday and it worked perfectly. To elaborate - I enter the first fix - MOBLE and when I click the LSK R1 I would expect MOBLE to populate the TO but nothing happens.

SOLVED: This only happens when departing from RWY 09C at KORD. Super weird!

7

No discontinuity. The FMC advances to show NUBRA as the from waypoint and WS501 as the to and from NUBRA, if that makes sense. Autopilot was left without direction and went to present heading mode with no map line to NUBRA. All the waypoints were present still after NUBRA. I’ll post a screenshot next time.

8

I’ve had it work and not work. I’ve used the direct to button and brought the waypoint up to the TO LSK. Sometimes it works and others it doesn’t. I don’t know of anything that is absolute yet. I have been flying the GTX almost exclusively, and regularly(Atleast 2 flights a day). I have issues with FMC routing and direct to almost every flight.
I like the GTX model a lot. It just needs tuned. The dip when you engage the autopilot on climb out is a biggie. There’s several other minor issues. Prop beta would be nice to have working so you don’t have to ride the brakes during taxi all the time.

9

Just so I don’t misunderstand you: You came directly from LOWG and had programmed the NUBR3R STAR followed by the ILS RWY 15 approach with the SBG transition?

10

That is correct. When I programmed the ILS mid-flight I lost nav to NUBRA, but waypoints remained in the FMC. Just lost direct to NUBRA because it showed NUBRA as the from waypoint. When I removed the ILS I regained capability and direct to NUBRA.

11

One possible explanation that i can think of could be that on the legs page of the FMC sequencing was inhibited. Can you rule that out?

12

Possible. I’ll look for that. I definitely didn’t inhibit sequencing, so that would be an issue if it did by itself. Also, various issues like not receiving navaid reception at various locations/airports, after manually entering frequencies, points to the need for avionics bug fixes.
Good troubleshooting info though.

13

I have noticed that when I configure an ILS Flight Plan
on the EFB, the FMS by default shows (magenta line) the flight Direct to the Final Approach Fix, FAF.

Before takeoff:
I always have to select the first Waypoint and make the flight Direct to it.
The FMS will then fly the plane, as planned, to the FAF and then the ILS.

Being a sim pilot, I think this occurs because the ILS is activated too early.
Maybe in R/L, Pilots will wait until a later time in the flight to activate the ILS
when they are nearing the FAF.

14

You’re welcome.

Yesterday I recreated your flight myself in two different ways:

  1. Spawning on the runway, all systems running and only the basic flight plan manually entered (LOWG/34C DCT NUBRA DCT LOWS/15). Then before reaching NUBRA I entered the NUBR3R STAR and the ILSRW15 approach. NUBRA remained the next waypoint and the autopilot followed the leg LOWG - NUBRA in NAV mode correctly. At NUBRA, however, the aircraft did not turn onto the STAR, but continued to fly straight ahead. Only then did I realize that sequencing was inhibited.

  2. Cold and dark from the parking position. Complete flight plan manually entered before take-off (LOWG/34C DCT VATET DCT NUBRA NUBR3R LOWS/SBG.I15). Sequencing set to AUTO. The autopilot followed the flight plan to LOWS without any problems. Also VNAV was working perfectly.

My result: The autopilot is basically OK.

15

Your right, it’s not the autopilot, it’s the FMC that gives the autopilot commands. The autopilot’s biggest issue is following vertical climb commands on initial engagement. Tends to pitch down and not slave to the flight director vertical commands until several minutes into a flight.

As far as the FMC/NAV issues, we should be able to use any combination of FMC input at any point in the flight and it work properly. You should be able to take off in a heading with only departure and destination, for that matter neither, and load a flight plan, add an arrival, add an approach, remove an approach/arrival, whatever, and to add to this run-on sentence, have it do whatever you have input without it not wanting to fly it.
I’m not bashing on this platform/aircraft, I’m just saying this nicely modeled King Air needs some fixing with the NAV issues.
I flew a LYPG to LYBE flight today without issues, but that is the rarity.

16

I found that it was a weird issue that when I departed on runway 09 it would not accept the direct to, when I set it to 27 al was well. Maybe this is an issue with the database.

17

Anyone else showing an amber(yellow) Active Data Base? Mine turned yellow several days ago. Not sure what the dates were then, but show 26DEC25/22JAN25. Not sure if this has anything to do with some of the FMC issues, but those dates are wacked. I’m guessing this is an Asobo thing. Probably supposed to read 26DEC24/22JAN25, and may be why it’s amber.

Anyways, flew a flight from EDMO to LOWK. Flight plan would not recall from Simbrief to the FMC. I have it recall sometimes and not others.
Manually entering the flight plan. FMC did load airway L173 from MAH to TAKEX, but then wouldn’t load M867at any point to RADIZ. Arrival and approach loaded fine. It did take a Direct To to VAVOR to join M867.