Jump to content

Why doesn't auto pilot work (at times)?


Recommended Posts

I have noticed at least twice in the past that the auto pilot in the Beechcraft King Air didn't seem to work and it has just happened again.

Here is the scenario -

Flight plan loaded (via load/save)

Flight plan verified in the G3000

Approach loaded in the G3000 and visually verified

On the auto pilot panel -

FD set ON

NAV set ON

YD set ON

Initial ALTitude set to 4500

VS set to +800

Take off

Gear up

Flaps up

AP set ON (altitude at the time around 1000)

The aircraft did NOT follow the flight plan and just headed around the same heading as the runway

The altitude continued to climb past 4500 even though 4500 was set and AP was ON.

I can't remember if I checked that the CDI was set to FMS but in the past I have never seen it set to anything else but FMS on startup.

 

Am I doing something incorrect or is there a problem?

Edited by jparnold
CDI set to FMS

John

Gigabyte Z390 UD Intel Core i7-9700K 3.60 Ghz Dual 16Gb DDR4 2666

Gigabyte RTX2060 OC 6GB 2 X 256MB SSD drives 1 X 500GB HDD

Windows 10 64bit Home Logitech Extreme 3D Pro joystick

Link to comment
Share on other sites

Loading from a saved flight can make the autopilot unresponsive at first. If you toggle each of the autopilot buttons on/off once or twice after engine start, they should work normally.

Tim Wright "The older I get, the better I was..."

Xbox Series X, Asus Prime H510M-K, Intel Core i5-11400F 4.40GHz, 16Gb DDR4 3200, 2TB WD Black NVME SSD, 1TB Samsung SATA SSD

NVidia RTX3060 Ti 8Gb, Logitech Flight Yoke System, CH Pro Pedals, Acer K272HL 27", Windows 11 Home x64

Link to comment
Share on other sites

Thanks Tim.

 

I have also noticed that the aircraft doesn't always follow the 'lines' drawn on the map between my custom waypoints (which doesn't always link all the custom waypoints) BUT it always flies close to the custom waypoints. When I first noticed this it was a little off putting thinking that the autopilot (NAV) wasn't working until I noticed the aircraft flying close to those custom waypoints.

 

One think though which puzzles me is that the flightpath (between waypoints) doesn't always change to magenta as the aircraft in in that section of the flight path. The first leg is usually colored magenta and also the last leg before transition and then the legs in the approach - maybe that is the answer.

John

Gigabyte Z390 UD Intel Core i7-9700K 3.60 Ghz Dual 16Gb DDR4 2666

Gigabyte RTX2060 OC 6GB 2 X 256MB SSD drives 1 X 500GB HDD

Windows 10 64bit Home Logitech Extreme 3D Pro joystick

Link to comment
Share on other sites

Thanks Tim.

 

I have also noticed that the aircraft doesn't always follow the 'lines' drawn on the map between my custom waypoints (which doesn't always link all the custom waypoints) BUT it always flies close to the custom waypoints. When I first noticed this it was a little off putting thinking that the autopilot (NAV) wasn't working until I noticed the aircraft flying close to those custom waypoints.

 

One think though which puzzles me is that the flightpath (between waypoints) doesn't always change to magenta as the aircraft in in that section of the flight path. The first leg is usually colored magenta and also the last leg before transition and then the legs in the approach - maybe that is the answer.

 

I'm not a real pilot but it seems like I see some real-world aspects to how MSFS autopilot works. Or attempts anyway. The "line" you refer to is the representation of a line between two of your waypoints. But your plane is not trying to fly on the line, it's trying to fly to the next waypoint.

 

I've noticed that when the waypoints require turns, the VFR screen attempts to show you curved lines to represent where the plane will probably go, but if you've zoomed in enough those lines are not accurate. Instead, the plane is only going to turn once it has actually reached the waypoint.

Intel Core i7 10700KF (8-Core 5.1GHz Turbo Boost), RTX 3070 8GB, 32GB Dual Channel at 3200MHz, 512GB M.2 PCIe NVMe SSD. Monitor: Samsung C49RG9x. VR: Oculus Quest 2.
Link to comment
Share on other sites

I'm not a real pilot but it seems like I see some real-world aspects to how MSFS autopilot works. Or attempts anyway. The "line" you refer to is the representation of a line between two of your waypoints. But your plane is not trying to fly on the line, it's trying to fly to the next waypoint.

 

I've noticed that when the waypoints require turns, the VFR screen attempts to show you curved lines to represent where the plane will probably go, but if you've zoomed in enough those lines are not accurate. Instead, the plane is only going to turn once it has actually reached the waypoint.

 

Thanks. That is what I thought but needed confirmation.

 

Regarding the 'drawn' flight plan and that parts of it are sometimes displayed in magenta. Consider the following image. When I took off this section was displayed in magenta as shown, after a few minutes as the aircraft was turning towards the flight path to intercept it, the line changed to white and then a few minutes later it changed to magenta again. After the aircraft passed the first custom waypoint that section remained as magenta and the next section remained white even when half from the first waypoint to the next waypoint. This happens much the same at the end of the flight, the last section changes to magenta but the sections already flown have never changed to magenta.

I am wondering what this (change to magenta) signifies.

pfd flight plan.jpg

John

Gigabyte Z390 UD Intel Core i7-9700K 3.60 Ghz Dual 16Gb DDR4 2666

Gigabyte RTX2060 OC 6GB 2 X 256MB SSD drives 1 X 500GB HDD

Windows 10 64bit Home Logitech Extreme 3D Pro joystick

Link to comment
Share on other sites

Thanks. That is what I thought but needed confirmation.

 

Regarding the 'drawn' flight plan and that parts of it are sometimes displayed in magenta. Consider the following image. When I took off this section was displayed in magenta as shown, after a few minutes as the aircraft was turning towards the flight path to intercept it, the line changed to white and then a few minutes later it changed to magenta again. After the aircraft passed the first custom waypoint that section remained as magenta and the next section remained white even when half from the first waypoint to the next waypoint. This happens much the same at the end of the flight, the last section changes to magenta but the sections already flown have never changed to magenta.

I am wondering what this (change to magenta) signifies.

 

This could just be an MSFS bug, as it tries to simulate the real-world G3000 as best as it can. The theory is that the line should be magenta when it is the active leg of your trip. Once you hit a waypoint, the next line is supposed to turn magenta. In the simulation it may be that this just doesn't happen perfectly. (I assume it does happen perfectly in real life but I'm not a RL pilot so I have no idea).

 

MSFS still has a lot of kinks it is working out on autopilot, ATC, etc.

Intel Core i7 10700KF (8-Core 5.1GHz Turbo Boost), RTX 3070 8GB, 32GB Dual Channel at 3200MHz, 512GB M.2 PCIe NVMe SSD. Monitor: Samsung C49RG9x. VR: Oculus Quest 2.
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...