[BUG] Plane starts random left hand turn

[Tinpanva]

Mod Version 3cde833 vs built": "2021-02-07T13:04:27+00:00

Describe the bug In the 3cde833 version the plane reaches TOC and then starts a left hand circling. Tried setting sensitivity to 20% which helped but the planne only slowed its circling. Reverted back to built": "2021-02-07T13:04:27+00:00 and the issue went away. I don't use the FMC for navifation, I use a 3rd party EFB Aivlasoft 2.0, it navigates via GPS as I understand it. I've always used this with FBW and never had an issue.

To Reproduce 1.Flight plan from KATL to KSLT on pencil2 dep, once TOC is reached it starts circling. 2. 3.

Expected behavior To follow the flight plan

Actual behavior Starts a counter clockwise circling

References

Additional context when I load up the built": "2021-02-07T13:04:27+00:00 ver the issue goes away.

Was this working before/when did the issue start occurring?

Is this a problem in the vanilla unmodded game?

Discord username (if different from GitHub):

[Benjozork]

What input device do you use for flying ?

[Tinpanva]

Thrust master T.16000M FCS

[JEP795]

I’ve had this issue in the past happen like two or three times. I’m using Honeycomb peripherals and Airbus side stick by TM. On all three occasions I was making changes for routing/altitude on FMC. Once I was switching approaches after ATC instructed different approach, another I was setting altitude constraints in flight, and the third time I think I was deleting a waypoint elsewhere in the flight plan. I haven’t tried to replicate it and it doesn’t happen often dine I usually don’t mess with waypoints/constraints in flight but not sure if it would happen if I did more.

[Talent442]

Well I have a similar issue. I had this issue the last 3 times too, but only when I am on approach. The plane randomly starts a left or right turn and leaves the route (route from MCDU). Especially approaching LEPA is more or less a direct straight approach and he starts a right turn. When I approached LTAI the plane wanted to create a shortcut and didn't follow my route. So in these cases changing the heading manually works.

[derl30n]

Can you please check your deadzones and try increasing it.

[Talent442]

Well I flew with autopilot activated. My Deadzones are set to 0.

[Benjozork]

Exactly. Can you try increasing them ?

Some people need up to a whopping 25% for the control inputs to stop affecting the AP for no reason.

[Tinpanva]

Todays flight KSTL to KDTW using dev ver b851485 as soon as I took off and engaged the AP plane took a hard left and eventually crashed. FD was clearly calling for climb to the right as shown in the below pic.

[derl30n]

@Tinpanva Please increase your deadzone as requested by @Benjozork

[Tinpanva]

Yeah, I tried it up to 30% which is crazy, this doesn't feel like a deadzone issue, feels like a GPS issue

[Tinpanva]

Just duplicated the flight with built": "2021-02-07T13:04:27+00:00 and it works fine

[Tinpanva]

correction, I am mid cruise and it just started a left circle, I was able to stop it with a direct to on the next way point.

[Tinpanva]

would this hitch in the route cause it?

[DaveBC]

Does an actual airbus disconnect A/P if manual input is given? Could possibly prevent inadvertent interference from deadzones.

[Asianblade]

would this hitch in the route cause it?

Way to fix it: Direct to your next waypoint. Thank you

[riveroalbert]

Does an actual airbus disconnect A/P if manual input is given? Could possibly prevent inadvertent interference from deadzones.

As far as I'm concerned the autopilot should indeed disengage after a manual override. I have had the issues you guys are mentioning before. And I'm also pretty sure it is not due to dead center issues. AP stays on but it starts to misbehave sometimes it is impossible to recover

[Benjozork]

@Tinpanva your screenshot shows that the AP knows where to go as the FDs are completely different from the actual inputs. Something somewhere is overriding the AP.

Can you try unplugging any control devices with aileron axis when this happens ?

[Tinpanva]

I'm happy to report 3 separate flights this morning (all different) had zero navigational issues, whatever was jacking up the route (GPS) in the previous ver is gone in 7da6cf1 I'm going to try and back down the deadzone (it's killing by butter smooth landings) to something that feels better to me 10% or so and see what happens

[DaveBC]

Does an actual airbus disconnect A/P if manual input is given? Could possibly prevent inadvertent interference from deadzones.

As far as I'm concerned the autopilot should indeed disengage after a manual override. I have had the issues you guys are mentioning before. And I'm also pretty sure it is not due to dead center issues. AP stays on but it starts to misbehave sometimes it is impossible to recover

According to this (https://aviation.stackexchange.com/a/53074), it should disconnect but only after a pressure threshold is exceeded. If this was to be modelled, a small input caused by deadzoning is probably not enough 'pressure'. Saying that, I'd be happy if there was an option for autopilot to be disconnected from control stick input exceeding a small time frame, regardless of 'pressure'.

[Tinpanva]

As of right now I'm at 8% deadzone and it's not causing any issues at all.

@DaveBC I thought this was modeled in already. Or maybe i'm thinking of another aircraft. Thinking back, I feel like I missed the slope on an approach once and just forced the nose down to try and catch it, it disconnect the AP when I did that.

[Knallhartmuth]

Same issue, same controller (dual T.16000). After reaching T/C at FL110 the aircraft started circling to the left. Bank angle was way above 60° but without losing altitude. Heading mode and approach mode both worked fine. Manual landing was no problem. Doesn't look like a controller issue to me.

[Benjozork]

To everyone experiencing issues:

Update to the very latest development build.

Try unplugging any control devices with aileron axis when it happens.

Provide screenshot of flight directors.

[Tinpanva]

Version f908616 On flight from KJFK to KDCA once I reached approx TOD had a terrible time keeping plane on course.

Flight plan was from Zizzi to ATR to Lafln and then to Bilit. as soon as I passed Zizzi it started vering off course to the south so I tried a direct to ATR which cause me to go way north, it wouldn't go to ATR. I tried direct to Lafln and same thing, stayed north. I deleted the approach and reloaded it and did a direct to Bilit which worked and I was able to continue the flight plan just fine. Good news was it didn't do any hard uncontrollable banking or nose dives but I couldn't force the plane to where i wanted. I didn't think to try and manually dial in a heading.

interestingly enough, I had that "hitch" show up in my flight plan again but once I got passed it it was fine.

At this point everything flew as it should

I just noticed a newer update was avail, will try that later tonight

[Sierrapappayankee]

For every flight now, the entire flight goes by without a problem, until the aircraft gets to the STAR or the approach, a that point it starts a hard bank away from the flight path. I'm also getting random additional USR waypoints on my flight plans.

One of the Navigraph mods on the FS forums told me that it has to do with the waypoints being truncated on loading & therefore incorrect (If I understand correctly?)

[Tinpanva]

It had been a non-issue for me for about a week or so, working just fine but tonight on my flight from KCLT to KMEM it happened twice. The first time I was able to 'direct to' but the second time it just spiraled out of control. Just upgraded to 34e1338 and will try again tomorrow.

[Benjozork]

For every flight now, the entire flight goes by without a problem, until the aircraft gets to the STAR or the approach, a that point it starts a hard bank away from the flight path. I'm also getting random additional USR waypoints on my flight plans.

See #939

[Tinpanva]

So it happened again today during the cruise phase of my flight about 30 miles from TOD. It happened as soon as I tried to use the TOD calculator, as soon as I entered my altitude plane banked hard left, no control at all. Using 34e1338

[Tinpanva]

duplicated the issue, restarted MSFS2020, got to cruise level and sent the STAR to the FMC, set the VOR and course. Everything was fine, as soon as I ran the TOC calculator banks to the left off course. Was using ver d6d5f02 this time.

[Benjozork]

This is probably caused by the fact that number keybinds trigger aileron movements, and that the EFB does not cancel keybinds because of an MSFS limitation.

A soft keyboard will be added to the EFB.

[Tinpanva]

Bingo! Give that man a prize! Just checked the keybindings and sure enough, 2 of the keys effected rudder left and yaw left. mental note to self, remove all key bindings from num pad

[Tinpanva]

so this particular version (4355e19) has been the worst so far for randomly loosing the flight plan and banking hard, sometimes right after take off, sometimes at TOD, or TOC. Only thing consistent is it has happened on every single flight so far (approx 5). In two cases I was making changes to the flight plan (adding my arrivals) but other times was just in mid flight watching a movie. In two cases I was able to 'direct to' but in others it was unrecoverable. Honestly, if I could roll back a version or two I would ;)

[derl30n]

Issue seems resolved now.