FlyByWire A320nx new Experimental Version

I’ve just switched to the new experimental version and made my daily check flight.

The custom flight plan manager works perfectly. No USR waypoints, no straight lines between Wypoints when a curve has to be flown. The aircraft flies to every point in the flight plan.
So far perfect.
Thanks!!

4 Likes

Wow, Good to know. Hope it will be implemented in the dev soon. :sunglasses:

1 Like

Yes, done a couple of flights with it yesterday and today and it’s a massive improvement. Only shame for me is I think a little bit more work perhaps needed on STARs, into EGLL last night it took a couple of straight lines where the STAR has a curve and then into LGAV this morning it got a bit confused, looked like it was going to skip one of the waypoints and then suddenly decided to turn back on itself. But not a complaint, definitely a massive upgrade and know they’ll still be working hard on improving it.

will it work with the ingame flight planner?

However, it is also possible that sids and stars are incorrectly stored in the database.
But at least you can edit those in the MCDU and delete unnecessary waypoints. Or add some more.

I haven’t tried it because I don’t use it, but I think it works. I think it doesn’t matter where the MCDU gets the data from.
I only noticed one thing: the course is no longer displayed on the VFR card, at least when I manually program the course into the MCDU.

Possibly, I have the navigraph charts so should be right, on both occasions it had all the right waypoints for the STAR in the route when I went through it, at LGAV in particular though on the XORKI2C STAR it struggled to draw the right route after EGN. The waypoints were in but it picked up a heading as if it was skipping D11.0 IATL and headed straight to D5.0 IATL, then when it was abeam D11.0 IATL it suddenly made a hard right turn to try and intercept it.

Am sure these bits will all get smoothed out though, it’s still experimental after all :slight_smile:

It is exactly like that. :sunglasses:

I’m thrilled that this is working for others. All of my flights today have ended in a CTD. I’ve got no idea what is wrong. Probably my middle-of-the-road computer system. Everything is very stable and the graphics are nice and smooth. I’m hoping this is just a residual issue from Asobo breaking Everything a couple of weeks ago. Coincidentally, the Dev mod works perfectly.

I’ve been using the DEV mode since the sim came out. Ever since SU5 I get nothing but CTD’s and I have a rather high end system. It’s always while I’m entering info into the MCDU. I have no idea what’s causing it. Maybe a livery? I only download one at a time. Flying the stock is just…blah.

Found the same today. Kudos to the team for this, it’s huge. I noticed we now have Discontinuities entered as they should do after the SID and between STAR and approach transitions. No more losing the route at the approach transition. Flew the HLYWD1 STAR into KLAX flawlessly today. I simply used a mix of “managed” descent, FLC, really as it works now, then VS to hit the altitude restrictions on the way down.

I get a ton of CTDs with this version. Going back to the DEV branch. The one flight I did have was very nice though. Cant wait for all the bugs to be fixed!

I have the same problem with the FBW but only when trying to print the METAR. Then I suddenly get a CTD. Other than that it is working superb (dev mod).

The experimental version will not have more or less CTDs than the development version - this is unfortunately more of a thing related to the current instability while we wait for more crash fixes in WU6.

Any kind of correlation between # of CTDs and version used is very likely a coincidence.

This is most likely a livery issue: Printing an ATIS report crashes to desktop some times after upgrading MSFS to SU5 · Issue #5429 · flybywiresim/aircraft · GitHub

1 Like

Ok thanks for the info.

I’ve noticed my CTDs have come on arrival when the NX redraws the flight path to correct for the now slower speed. I definitely don’t have this issue in DEV.

1 Like

Then that is a simulator issue, as all the code running for that is sandboxed and isolated.

Why the switches are now blue and, awkward to use
I have a Modern and DEV version

You must set your cockpit interaction setting to Legacy - then all is like before.