I updated this afternoon to the latest dev mod with the custom FBW and started getting the turning off course when engaging the AP.  The FD went all the way left and the plane started a steep right bank.  I disengaged the AP and reengaged it and tried to go direct to the next fix on the route but that didn't fix it.  Anyone else seeing this?

 

Also, should the EFB pushback be working?  Every time i have tried nothing happens. 

I have had this a couple of times, i usually update it daily (Dev version) first thing in the morning GMT. I also keep the last proven working version in case i have issues with the latest D/L

I don't know what causes it, maybe they are working on it at the time, but if i get the issue i have i usually revert to the previous one ( I kept) and then look for an update later in the day.

I had the same as you twice in the past week, downloaded a later version and all was good again.

As far as i am aware the push back in the EFB is not working yet.

Edited March 5, 20215 yr by Car147

3 hours ago, Car147 said:

I have had this a couple of times, i usually update it daily (Dev version) first thing in the morning GMT. I also keep the last proven working version in case i have issues with the latest D/L

I don't know what causes it, maybe they are working on it at the time, but if i get the issue i have i usually revert to the previous one ( I kept) and then look for an update later in the day.

I had the same as you twice in the past week, downloaded a later version and all was good again.

As far as i am aware the push back in the EFB is not working yet.

Yeah...I am always like should I download it or not since my latest version is working well? 

But you are so tempted to see what they added. 

I wish there was a tracker that told if the version you're about to download will steer off course or start the dolphin dance at x sim speed...lol

Edited March 6, 20215 yr by knich

I have also noted recently that the transponder is not working, can’t key in a squark code.

1 hour ago, RaptyrOne said:

I have also noted recently that the transponder is not working, can’t key in a squark code.

I had the same issue - after some deductions, I figured the "new" procedure was to "clear" the transponder of any code, then it allows you to enter your allocated code.

3 hours ago, knich said:

Yeah...I am always like should I download it or not since my latest version is working well? 

But you are so tempted to see what they added. 

I wish there was a tracker that told if the version you're about to download will steer off course or start the dolphin dance at x sim speed...lol

I use this to keep track of additions, https://github.com/flybywiresim/a32nx/pulls?q=is%3Apr+is%3Aclosed+is%3Amerged+base%3Amaster+sort%3Aupdated-desc

The banking issue is usually a dead zone sensitivity setting.  Should be set to 20% 

AFAIK the team has identified 3 primary causes and solutions:

1. The deadzone of one of your control axis is sending microsignals that stops the AP from doing what it wants. Setting your deadzones to 20% and then working down can solve this.

2. A lot of people leave keyboard commands for flight controls on. (I.E., the < key will turn the aileron 1 increment to the left and hold it). If while typing you hit one of these buttons, the input stays in until you hit the opposite key or move your control axis. It's advised to remove any key bindings to the keyboard that control any of the control surfaces.

3. Once you insert a SID into the FMGS the AP has difficulty flying the subsequent legs, among other glaring issues. The AP may attempt to suicide instead of flying to the IAF, for instance, and it's advised you fly on HDG mode or try "DIRECT TO" a bunch of times.

Note that the FBW team have yet to change any of the flight guidance systems from default. All of these issues are due to Asobo's programming.

Good luck!

4 hours ago, D-Green said:

The banking issue is usually a dead zone sensitivity setting.  Should be set to 20% 

Thanks I will check this.

4 hours ago, WestAir said:

AFAIK the team has identified 3 primary causes and solutions:

1. The deadzone of one of your control axis is sending microsignals that stops the AP from doing what it wants. Setting your deadzones to 20% and then working down can solve this.

2. A lot of people leave keyboard commands for flight controls on. (I.E., the < key will turn the aileron 1 increment to the left and hold it). If while typing you hit one of these buttons, the input stays in until you hit the opposite key or move your control axis. It's advised to remove any key bindings to the keyboard that control any of the control surfaces.

3. Once you insert a SID into the FMGS the AP has difficulty flying the subsequent legs, among other glaring issues. The AP may attempt to suicide instead of flying to the IAF, for instance, and it's advised you fly on HDG mode or try "DIRECT TO" a bunch of times.

Note that the FBW team have yet to change any of the flight guidance systems from default. All of these issues are due to Asobo's programming.

Good luck!

Is the Dolphin dance at high sim rates also an Asobo or dead zone problem?   The only reason I ask is because some of the dev updates have no problem at sim rate 8 or even 16 but others I get problem even at 4.  

My banking away issue is solved since weeks. With deadzone around 10 and - yes - untighting the screw under my hotas X stick. Don’t ask me why. 
however, yesterday AP disconnected while climbing when strong (side) winds kicked in. Never saw that before. 

23 hours ago, XCLTM3 said:

I had the same issue - after some deductions, I figured the "new" procedure was to "clear" the transponder of any code, then it allows you to enter your allocated code.

Yes, that is the way the real aircraft transponder works.

21 hours ago, D-Green said:

The banking issue is usually a dead zone sensitivity setting.  Should be set to 20% 

This.

On 3/6/2021 at 4:57 AM, RaptyrOne said:

I have also noted recently that the transponder is not working, can’t key in a squark code.

Couple of days ago I had the same problem. I pushed the clr button on the transponder which cleared the numbers. After that I managed to put the squawk the atc asked. 

Edit: should have read the entire thread, the question was already answered. My bad...

Edited March 7, 20215 yr by Virtpilot

20 hours ago, DAD said:

With deadzone around 10 and - yes - untighting the screw under my hotas X stick. Don’t ask me why. 
. 

I just had to tighten that screw under the stick as it worked as an additional rudder hence transferring every single vibration to the A32NX as well.

Hans