I am still in the process of testing out this theory, and I am not flying the FBW product.  But I did experience a lot of the A/P problems others have experienced with the A320 not following the flight plan, and I have read a number of various work arounds, from "not starting from Cold and Dark" to Starting cold and dark, saving the flight, then continuing.  I've even read that the newest dev build of FBW fixes it from some, and doesn't fix it from others.

Taking nothing away from the FBW folks, and I am slowly wading into that deeper pool (such as figuring out exactly when I can pick my approach from the MCDU and not get the NOT ALLOWED message).  I have recently been flying with the default A320, and actually was liking it.  And then the US update came and broke it....

I started trying different theories and they all had mixed results.  excecpt.

I did delete and reinstall the Asobo 320, and then I did a flight using the default livery from C&D and that worked.  It had never worked before.  So now I repeated the flight with my Jet Blue livery.   chaos.  Ok, switch back to default livery....success....for the most part.  It even follows the localizer which the other one refused to do after the update.  The AP does seem dampened.  The AC won't go more than 20 degree bank when making course corrections and for some reason between 20k and 30k it climbs painfully slow, even in selected altitude mode (OP Climb).  

But for the most part it's flyable.  I'm wondering if all those changes they had livery folks make 2 updates ago are now causing an issue.   I'm in the process of undoing the changes for one of the liveries and see if I can make it fly like the default livery.

I'm also wondering if anyone else has had success with the default Livery.  I'm not really interested in  the FBW folks at this time, because that is separate development and there are too many changes in that A/C to be a useful comparison for me.  But I am interested in hearing if anyone else has had success with the default A320 with the default livery.  And if not, does deleting and redownloading the plane help.

BTW, you don't have to "remove" the liveries for this test, simply fly the A320 with the default paint......

Thanks for all who can give this a try.

I have experienced the issue with the default livery. The only common thread with the problem that I can find is that it always happens when starting cold and dark. Did you happen to start cold and dark the first time then start on the runway the second flight?

3 hours ago, Hyperfocal said:

I have experienced the issue with the default livery. The only common thread with the problem that I can find is that it always happens when starting cold and dark. Did you happen to start cold and dark the first time then start on the runway the second flight?

No.  I started cold and dark on the first flight.  The next plane was also cold and dark with the default livery.  

1 hour ago, wthomas33065 said:

No.  I started cold and dark on the first flight.  The next plane was also cold and dark with the default livery.  

Try starting on the runway (everything up and running)
No issues for me.
But with cold and dark the issue is there.

get the latest "Developer" one. It seem to have fixed the AP issue for me.

Livery files do not affect aircraft performance or systems. It appears the autopilot issue (irrespective of the default A320neo or the A32NX) is somewhat random, so you likely experienced a coincidence. We are still investigating the cause as we have not fully resolved the issue.

@wthomas33065

Flew with the default livery C&D, manually entered flight plan, but I had A320 liveries in the community folder  -> AP issues (right bank spiral)

Removed all A320 liveries from the community folder. Started C&D, manually entered flight plan -> No AP issues.

This may explain why I was not seeing any AP issues on Tuesday.  I removed all contents from the community folder before updating and I ran several test flights.

 

Added liveries back to community folder while flying default livery -> Sluggish turns in the flight plan.

Removed liveries --> normal turns.

 

 

 

5 hours ago, IcemanFBW said:

Livery files do not affect aircraft performance or systems. It appears the autopilot issue (irrespective of the default A320neo or the A32NX) is somewhat random, so you likely experienced a coincidence. We are still investigating the cause as we have not fully resolved the issue.

I would agree, but the new liveries required, for patch 1.10.7.0 that a new model folder and model.cfg file be added for each livery.  I'm not sure if that might not affect something.

For the last two updates, they said they "fixed" the liveries so they removed that requirements.

I took one of the liveries and undid the changes mentioned in flightsim.to (For Creators: Patch 1.10.7.0 breaks your Liveries – How to fix it – Flight Simulator 2020 News & Updates – by Flightsim.to) and that plane started flying better.

Again, might be coincidence, I'll try another flight cold and dark again just to see if I have confirmation bias or not.

 

EDIT:  The JetBlue tried to kill me again with overspeed and death spiral, even with the modifications.  Repeated the flight with the A320-NEO default paint, and it behaved better.  It didn't try to kill me, but still was painful climbing thorough FL200 to FL300  (400 to 500 FPM).

 

So can't fly the liveries, but the default paint is doable for now.   Hope they find a fix.

Edited November 28, 20205 yr by wthomas33065

4 hours ago, altenae said:

Try starting on the runway (everything up and running)
No issues for me.
But with cold and dark the issue is there.

Still cannot shut engines down with a runway span at start in any livery.

6 hours ago, simon747 said:

Still cannot shut engines down with a runway span at start in any livery.

This was about the AP when engage the plane starts banking / diving. 

This only happens with me after a cold and dark start. 

Not when started on the runway. 

Anyway it's a mess 

8 hours ago, Traveler Ray said:

@wthomas33065

Flew with the default livery C&D, manually entered flight plan, but I had A320 liveries in the community folder  -> AP issues (right bank spiral)

Removed all A320 liveries from the community folder. Started C&D, manually entered flight plan -> No AP issues.

This may explain why I was not seeing any AP issues on Tuesday.  I removed all contents from the community folder before updating and I ran several test flights.

 

Added liveries back to community folder while flying default livery -> Sluggish turns in the flight plan.

Removed liveries --> normal turns.

 

 

 

Every update they break modifications. 

Unbelievable 

Edited November 28, 20205 yr by altenae