5 hours ago, Robin Cornelissen said:

You have to turn on the flight director 😂

Yes. Thanks. That was it. Please don't tell anyone.

Flying EDDL - EPWA. very very slow climb out to initial 10,000 then even slower up to FL390 as directed by atc. at FL350 was directed to FL390, once started the very slow climb the aircraft started to oscillate wildly. hade to use VS to overcome the slow climb plus descended to FL350 but still wild oscillation

Never had these problems prior to the patch yesterday

Flying EDDL - EPWA. very very slow climb out to initial 10,000 then even slower up to FL390 as directed by atc. at FL350 was directed to FL390, once started the very slow climb the aircraft started to oscillate wildly. hade to use VS to overcome the slow climb plus descended to FL350 but still wild oscillation

Never had these problems prior to the patch yesterday

Flying EDDL - EPWA. very very slow climb out to initial 10,000 then even slower up to FL390 as directed by atc. at FL350 was directed to FL390, once started the very slow climb the aircraft started to oscillate wildly. hade to use VS to overcome the slow climb plus descended to FL350 but still wild oscillation

Never had these problems prior to the patch yesterday

sorry duplicate post

Edited November 1, 20205 yr by raknal
duplicate

On 11/1/2020 at 1:56 PM, DAD said:

Thx for letting me know. Just installed latest stable and trying yet another long haul, now from Heathrow to KBOS. Fingers crossed that I do not get another CTD enroute like with all 3 previous attempts. Though they are in no way confirmed to be related to the FBW mod. Thanks to the FBW guys and gals 

I did it. First 07:55 hours long haul without CTD! Great flight, quite good autoland. even greater pics, had to post some here. sorry for sharing

Edit: just realize that the livery actually changed. That was the very same flight, evening over UK and morning at Boston. I started with LH livery and landed with default livery. funny

Edited November 2, 20205 yr by DAD

Hi all. I downloaded and installed it and it shows up in the Community folder as A32NX on top of the Asobe planes etc. Yet when I start MSFS the NX does not show up. The total number of planes available remains at 30. 

I must be missing a step somewhere along the line. 

I am looking forward to some guidance. 

Thanks,

Rolf

The FlyBy a/c does not show up as a different a/c. Basically, it over writes the default. If you have it correctly installed (which it appears you do), just load the A320 with any livery, and see the differences.

Quick check - see if the INS align switches (top left of over head panel) work.

Edited November 2, 20205 yr by stubbornswiss

Thanks a lot. Will try.

Rolf

4 minutes ago, Rolfspan said:

Thanks a lot. Will try.

Rolf

Let us know how it works out or if you need more help.

And my suggestion - check the FlyByWire installer/downloader before each flight to see if there is a new dev. version. They come out pretty often, and always with something new or something better.

This is what I do.

Great, thanks. The INS switches work fine. Rolf

16 hours ago, Will Fly For Cheese said:

Yes. Thanks. That was it. Please don't tell anyone.

Done the same yesterday lol...

The problem of the wing swinging I had it only one time, and I solved still with the AP on, moving a bit the ailerons in the opposite side of the swing, and then it stopped.

42 minutes ago, Rolfspan said:

Great, thanks. The INS switches work fine. Rolf

Glad to hear!

Fly safe & stay safe!!

I always like to fly it down to the runway from about 4-5 miles out, throttles are not closed ever, until the the Retard call...Occasionally i do a autoland, whilst it does work on occasion, the issues that prevent it seem to be more with the individual airports ILS, or bugs

Edited November 2, 20205 yr by Car147