Problem after the update SU11

[Iceman7]

I noticed some issues after updating with the 737. The plane no longer follows its flight path (LNAV/VNAV on), when i tried to press Heading to follow the heading manually nothing works and the AP CMD A doesn't work either. After taking off, i engage the AP but the plane nose dives for no valid reason or a significant climb at 20°.

[[email protected]]

I can not confirm this, the AP works fine, LNAV and VNAV is flown correctly.

[DDowns]

I noticed some issues after updating with the 737. The plane no longer follows its flight path (LNAV/VNAV on), when i tried to press Heading to follow the heading manually nothing works and the AP CMD A doesn't work either. After taking off, i engage the AP but the plane nose dives for no valid reason or a significant climb at 20°.

This is usually due to not turning off ALL MSFS Pilot Assist options.

[Iceman7]

Nothing is enabled. I set everything to hard, i hate assists.

[jmarauder04]

I had this issue earlier. I deleted the "Startup State" and reloaded into the sim. Issue was solved. Not sure if that was the root cause, but a quick reload fixed it.

[Iceman7]

ok i'll try.

[Iceman7]

It works! thx!

[Captain Kevin]

Corrupt panel state, I am guessing.

[Iceman7]

I think. The SU11 kill my sim.

[Hilly32]

Corrupt panel state, I am guessing.

One thing I got into the habit of doing with P3D was loading the plane in default state and then loading my desired panel rather than using my desired panel as the startup state.

Is this the recommended approach again in MSFS? If so, why is a startup option even offered?

[Pieterqe]

I had this issue earlier. I deleted the "Startup State" and reloaded into the sim. Issue was solved. Not sure if that was the root cause, but a quick reload fixed it.

Where can i find this

[Pieterqe]

Cant find it

[Iceman7]

strange it's for in the content manager that i deleted it. but i thought that the problem was fixed but i still have the same problem. When i engage the AP the plane either climbs 20° too high or falls at 25°. I have to fly manually.

[Pieterqe]

I think its a pmdg problem, cuz it started after su11. I guess we need to wait until they fix it

[Iceman7]

Yeah, same for after the SU11. I don't see any other solution at the moment. Wait next update.

[Iceman7]

The problem indeed comes from the panel state. When i start on the runway everything is good but when i start in cold and dark (panel customized) the same problem happens again and again.

[Pieterqe]

for me plane nose dives down and a/t is broken whether its approach state or runway it always does this

[Iceman7]

Was the issue resolved after the last update?

[Falcon99]

for me plane nose dives down and a/t is broken whether its approach state or runway it always does this

Hard to assist without more information. Which model, what’s your controller setup, route, etc. screenshots are helpful.

[antriq]

I too seem to have this exact problem when attempting to engage the autopilot from cold and dark. Checklist has been followed every time.
Engaging the autopilot works, but the plane climbs or descends unreliably, doesn't follow your altitude input and doesn't follow either VNAV or Heading (tried both).
I'm yet to try from another startup state.

[Falcon99]

Carl can you give us your flight plan screenshots of the panel? Hard to diagnose with so little information.

[ac5]

Similar problem here, after the SU11. If I load a panel state, the 737 would not follow the VNAV properly, mostly descending too slow, and subsequently missing the approach.
All other AP modes were OK, including LNAV.
NOT loading any panel state and configuring everything manually, solves the problem, the 737 follows the VNAV perfectly, as it did before the SU11!
Deleting all the "old" panel states and saving a new one does not solve the problem, as soon as I load the new saved panel,
the 737 does not follow the VNAV properly. PMDG, please advise.

[Falcon99]

Similar problem here, after the SU11. If I load a panel state, the 737 would not follow the VNAV properly, mostly descending too slow, and subsequently missing the approach.
All other AP modes were OK, including LNAV.
NOT loading any panel state and configuring everything manually, solves the problem, the 737 follows the VNAV perfectly, as it did before the SU11!
Deleting all the "old" panel states and saving a new one does not solve the problem, as soon as I load the new saved panel,
the 737 does not follow the VNAV properly. PMDG, please advise.

We have not seen this in testing. I suggest opening a ticket with PMDG support.

[ac5]

Well, you have not seen this in testing... Did you do exactly what I did?

[DDowns]

Well, you have not seen this in testing... Did you do exactly what I did?

Not possible with the lack of detail in your problem description.

[ac5]

Not possible with the lack of detail in your problem description.

Lack of description? It's quite simple.
One loads a panel state, the VNAV does not work properly.
One DOES NOT load a panel state, the VNAV does not works properly.

[Captain Kevin]

Lack of description? It's quite simple.
One loads a panel state, the VNAV does not work properly.
One DOES NOT load a panel state, the VNAV does not works properly.

So in other words, VNAV doesn't work at all for you. But in that case, if VNAV never worked, presumably they would have seen it and it wouldn't have been released.

[Falcon99]

Lack of description? It's quite simple.
One loads a panel state, the VNAV does not work properly.
One DOES NOT load a panel state, the VNAV does not works properly.

Please open a ticket with PMDG support. They will assist sorting this out for you.

As mentioned if VNAV didn’t work, you would see other global remediations from PMDG. VNAV is working so this must be something with your specific install. PMDG will assist helping you correct the problem.

[ac5]

Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
This did not happen before SU 11.

[Falcon99]

Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
This did not happen before SU 11.

With all do respect and kindness… Did you read what you wrote??

Lack of description? It's quite simple.
One loads a panel state, the VNAV does not work properly.
One DOES NOT load a panel state, the VNAV does not works properly.

The two “does not work” is what I was responding to.

Regardless I highly recommend opening a ticket. Panel Saves are working as well.

[Captain Kevin]

Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
This did not happen before SU 11.

Yes, I read what you wrote, this was what you said.

Lack of description? It's quite simple.
One loads a panel state, the VNAV does not work properly.
One DOES NOT load a panel state, the VNAV does not works properly.

Notice that you said in both cases, it doesn't work properly, hence my befuddlement. In any event, have you tried to create a new panel state and see if the new panel state works. A lot of the time, if an update for the aircraft is released, the panel states get corrupt since more parameters may have been added in that the older panel states don't have.

[Iceman7]

Ok, i found where the problem came from since the release of the SU11. That's when i press the key on pause. When i press pause during takeoff or landing when i take shots, and i press the "pause" key again to resume my flight that the problems arise. the plane no longer followed its flight plan, impossible to start the APU, i tried but nothing worked, when i stopped the engines, the engines continued to operate and remained at 20% N1, when i enable the GPU, it's not displayed on the overhead so it's impossible to connect it...no pressurization, Flt Alt/Land Alt becomes dotted lines, the plane climbs/descends without reason, nose dive...until PMDG restores this problem, don't use the pause button during your flight.

[LH201]

I have the same problem. I did a flight using the Pause at TOD option and afterwards the autopilot would not do anything I entered.
I then did a flight without ever using any pause option and there where no issues at all.

[DDowns]

Ok, i found where the problem came from since the release of the SU11. That's when i press the key on pause. When i press pause during takeoff or landing when i take shots, and i press the "pause" key again to resume my flight that the problems arise. the plane no longer followed its flight plan, impossible to start the APU, i tried but nothing worked, when i stopped the engines, the engines continued to operate and remained at 20% N1, when i enable the GPU, it's not displayed on the overhead so it's impossible to connect it...no pressurization, Flt Alt/Land Alt becomes dotted lines, the plane climbs/descends without reason, nose dive...until PMDG restores this problem, don't use the pause button during your flight.

In MSFS, Pause and Un-pause are two different things. See the Introduction pg 28 "Other Important Settings."

[Iceman7]

In MSFS, Pause and Un-pause are two different things. See the Introduction pg 28 "Other Important Settings."

I'm talking about putting on "pause" on the MSFS toolbar.

[DDowns]

I've got no idea what you are talking about... I don't think I've ever found anything on the toolbar to be useful.... LOL didn't know it had a pause. If you following the "important" recommendation in the Introduction you won't have a problem.

[LH201]

I tried another flight today, following the pause options as per "Other Important Settings" and still got the autopilot misbehaviour after pause at T/D.
I will open a support ticket.