Lateral AP navigation is broken, on all planes

[Bendead]

@hobanagerik

What would you like them to say

Well, many things “from Asobo not MS” :

• We recognize that it’s not working as well as we hoped so
• We will do less tweaking based on our feeling, and use pilot/AP maker feedback or math formulas
• We will speak with our BETA team, to find out why so many issue are not detected by them

[Norman999933]

Yep.

There’s already a thread gaining votes, I encourage you to add a comment a d vote yourself to help raise awareness of this glaring issue.

Autopilot behavior not linear using HDG or NAV

After the 11/24 update, when setting the heading bug or capturing a flightpath, the turn rate is not linear. Try this test: From straight and level with autopilot on make a 180 degree turn using the heading bug. Start a timer. You should reach 180 degrees from your start point in 60 seconds (standard rate turn.) Initially, the plane (in this case the C172 with steam gauges) banks as it should and turns at three degrees per second. As it gets within 30-40 degrees of the requested heading…

Basically, bank angle and turn rate is now broken. Makes it impossible to fly IFR procedures such as holds/sector entries & circling approaches, on the AP.

[Bendead]

Done and done

[CIMBALTO]

76/5000

It’s not just about landscaping, it’s about learning how to make a real plane from PMDG.

[CouncilCoast363]

Ap seems to be working latest a320nx dev update. Now im in a gently rocking boat. Dont kniw if its the wind or a bug

[antonvs3161]

The funny thing is that with an issue so critical as this, one person reporting to Zendesk should be all that is necessary. Why would you have to wait for a number of reports before you look into it. Good business sense would surely be to check it out immediately and report back to the community that it has been checked and identified if it has been found to be a bug. At least we would feel included. They always say how much they respect our feedback but not in actions.

[Bendead]

@flightlevel300

The funny thing is that with an issue so critical as this, one person reporting to Zendesk should be all that is necessary

Maybe for them it’s not that critical, or they just don’t think it’s a bug.

It’s like the cloud, right now they think it’s because of users setting, but with more and more reports on Zendesk about the same issue with proof, they will have no choice but to investigate deeper.

@flightlevel300

Good business sense would surely be to check it out immediately and report back to the community that it has been checked and identified if it has been found to be a bug. At least we would feel included. They always say how much they respect our feedback but not in actions.

Yes, that would be great. but sadly it’s not the case. like during the Q&A session where only 2-3% of the questions were answered, both on live and on the forum later. I don’t see the point in posting there anymore…

[TrowserOwner]

@flightlevel300

The funny thing is that with an issue so critical as this, one person reporting to Zendesk should be all that is necessary. Why would you have to wait for a number of reports before you look into it. Good business sense would surely be to check it out immediately and report back to the community that it has been checked and identified if it has been found to be a bug.

You’re assuming that their support and QA resources have enough bandwidth to address all bug reports. I very much suspect this is not the case.

[funkbrotha10]

@Bendead

Why no in-house testers saw that issue???

Yup. It’s very clear that their are either not testing properly or thoroughly. Or are not testing to proper “flight simulation first and foremost” standards that they claimed this game was developed under.

To date. This “simulator” has missed the mark. And it’s not a close miss either.