Interestingly this problem applies to BOTH the 737 and Airbus products, so I suspect

common broken gauge programming. Its easy to reproduce and I sure would like a fix

as things stand I fly the Aerosoft Airbus X with its FMS for dummies because at least

it can fly a SID correctly....

 

Here's one easy scenario to reproduce. Fly KPDX-KLAX, use this flight plan:

WHAMY2 JOGEN Q7 AVE SADDE6

 

So, after takeoff enable LNAV... at first it looks good, the plane will correctly go

to PEGTY and then head for KELYY, but things go wrong as you approach that

intersection, what SHOULD happen is KELYY->WANOS->TOSEH->WHAMY, but

what actually happens is as you get close to KELYY the FMS just decides its within

throwing distance of the next 3 intersections and immediately sets the destination

to WHAMY.

 

This is not the only RNAV SID that I've seen this kind of behavior with, and I find it

very annoying. Sure would like a fix for it... pretty please?? :help:

Are the waypoints displayed correctly in your legs page? Just asking. I too have noticed the FMC/Lnav "getting lost" then correcting itself off course. Not unlike a S turn scenerio.

Are the waypoints displayed correctly in your legs page? Just asking. I too have noticed the FMC/Lnav "getting lost" then correcting itself off course. Not unlike a S turn scenerio.

 

Yes, the FMC actually does the correct SID setup when you program it, changes waypoints based on the runways

as it should, its during flight that it seems to make this 'shortcut' operation. The waypoints in the SID are fairly close

together at that point (say 5 or 6 miles maybe?), so I'm guessing that its just deciding they've all been tagged.

 

I've seen the annoying S turn also. I even remember when, I was departing KSAN, PEBLE3 departure, and the first

waypoint was very close, as soon as I engaged LNAV the stupid thing started to veer off to the right, but then before

I had a chance to hit the heading button it corrected.

Have to update this, I was wrong in claiming that both the Airbus and 737 were having

this problem, although I could have sworn I saw it on the 737 tonight I was experimenting

and found that the 737 behaves correctly. I had loaded the flight plan with the SID all

parsed for the Airbus, and I thought maybe if I hand-entered the route it would work.

 

Well, the first thing I discovered was an old bug I remember from the first Airbus, namely,

if you pre-load NO flightplan in the sim before spawning the aircraft, and then go to the

FMC, and try to enter KPDX/KLAX at the upper right... it completely crashes the sim...

 

I mean, good gried, has Wilco ever heard of QA, this is an obvious NULL pointer problem

somewhere that ANY decent testing should have found. So, basically, its bloody impossible

to enter a plan from scratch that must've been far too subtle for their testing to find... :LMAO:

 

Anyway, by loading the plan into the sim, and then 'importing' it into the FMC it works... and

once there I tried to then enter the RWY/SID, thinking maybe it would make a difference...

but it didn't. It still cut the SID short as I described in my first post. But the 737 is fine... my

mistake in that.

Why don't you just make the first few waypoints flyover waypoints. You know the button with the small triangle on it in the FMGS, problem solved.