FBW STABLE version
This has been discussed before and was wondering if there is a fix or workaround or am I doing something wrong?
I load the flight plan in MSFS using high level and ILS approach.
A320 FBW then abandons the flight plan/route after 15-20 minutes, then seems to head directly to the ILS?
It is still in Nav mode but I have seen it change to Heading.
The aircraft can be directed manually back to the flight path and within ILS range it will go into approach mode and land correctly.
This is a picture of the flight plan being ignored Phoenix to SF
Since the stable version uses the Asobo FMS, this is how it is - but has already been described several times.
Use the developer version and you’ll be fine.
They have moved over to Dev one now, no more experimental for now. Dev mode is the best one to use, I use it daily no problems, adjust a few waypoints after sim brief loading and you’re set.
Just flew a short flight from KMER to KSFO using DEV FBW and it was perfect. Zero problems and everything looked really good, well chuffed. The Dev version is the business.
I’m using the latest A320 FBW dev build and experiencing something similar to what @TastierOsprey80 reported. Currently enroute on a simbrief generated flightplan from KORD to KIAD, but using heading adjustments and not HNAV. Checked the flightplan from the MCDU FPLN knob setting on the ground prior to departure and all looked good. Immediately after departure the MCDU did not display any waypoints in the ARC setting (even on maximum 320 KM range). However, the waypoints are listed as expected in the MCDU. After some fiddling around trying some direct waypoints listed in the flight plan a set of arrival waypoints eventually displayed. These waypoints displayed after manually entering a direct waypoint not far from departure no where near the arrival.
Side-note: Still in CRZ mode where I have not selected the APPR phase. If I attempt to re-enable HNAV a dot shows up next to my heading, but the aircraft continues on the heading selection. It does not change to dashes
Perhaps internally it was not inserted, but there was no indication that anything needed to be inserted. One more note is that I had selected the arrival RWY prior to departure where I chose Insert and the flight plan updated as expected. It may have been this insertion that tripped things up. I mention this because there was a known issue with the Dev and Stable builds where you could not select the arrival RWY, which appears to be fixed; though inserting the arrival RWY might lead to this side-effect. Can’t say
so when it showed up in Flightplan mode( on ground and inserted), i needs to be shown in map mode (on ground)aswell. or something is wrong. or you are at the wrong airport
Thanks for the suggestions. Flight simulator put me at the airport based on my flight plan, which was definitely KORD. Did observe that the flight plan did not show up in the nav map after departure when the problem became apparent. Will double check this prior to departure on the next flight
Back on track currently enroute from KIAD to KSEA after updating to the latest FBW development build (6803283). Flight plan loaded & persisted in the MCDU without issues even after updating the KSEA destination RWY. Kept an eye on the VFR map through departure where the only thing I noticed is that it took a bit of time (30 seconds - 1 minute) for the route to show up after initially bringing up the map. Currently cruising along with the AP following the waypoints. Not sure what happened yesterday
Going from KTUS to KPHX using FBW dev build, I only use the MSFS route planner and normally select an ILS runway.
9 times out of 10 I would have to enter the ILS Frequency into the MCDU but using the DEV version I have noticed that even if I forget to check, and the ILS Freq has not appeared loaded into the MCDU when I check it again 5 or 10 mins into the flight it has actually appeared where it should.
I have a really good connection so I don’t see why this should not populate before take off. Technically it cannot be difficult to achieve as when you select the RW the ILS Freq never varies.
Now I select Nav Aids when planning the route and just make a note of the Freq if it doesn’t appear.
Fmc auto tunes in the frequencys. So on takeoff you do not need the ils of the destination thats why it will auto tune along the flight. It also auto tunes in the vors along the route. Normal behaviour
Thanks for the info, I have noticed with the FBW DEV version I input the usual Departure and Arrival airports in the Sim, then I select the Altitude and then the ILS runway. This I have done since the beginning and it works.
But the FBW seems to be moving on, my method gives me takeoff phase, climb, cruise, descent, waypoints approach etc. ( these points are all shown on the built-in Map ) But when I look at the MCDU or the ND the only points that are shown are the Approach points, basically the route turns into a Straight line + Approach straight line, and that’s it.
You can see the aircraft flying Straight over the map and the meandering planned route sections below turning red as you enter them but you do not fly the same route.
Think I will have to invest more time in Simbrief or LittleNavMap.
When entering waypoints it should turn yellowish colour for “planned” after you hit insert(lower right LSK button) it should save it in your flightplan as set
