Fsbuild-2 Flight Planner

"The worse that should happen is it overshoots the turn and little and corrects it."

Some screenshots with explanations attempted. More than a little and this is what I've trying to solve.
Oh well. I just get internal server errors so I guess the screenshot story is a bust.

What I wanted to illustrate is LNAV is still rolling the plane back and forth over the track trying to correct for 50 miles and this is while subsonic although the first turn is supersonic.
first turn = 2 mile overshoot on a 28 deg bank.
Reverse bank to 28 degrees
1.5 mile overshoot
reverse bank to 28 degrees
1 mile overshoot
reverse bank to 10 degrees
.5 mile overshoot
reverse bank to 10 degrees
.2 mil overshoot
reverse bank to 5 degrees
.1 mile overshoot
reverse bank to 2 degrees
After this the plane starts to settle down to minor corrections and the bank angles are not longer perceptible.

The higher the speed, the worse the problem. Three miles is simply not enough at mach .7 and higher. The program badly needs some kind of working turn prediction variable for the faster aircraft (faster than GA aircraft or airliners at approach speed.)

Have you flown the VNAV at Mach 0.84 at 35K ft on a forty five plus degree turn recently? Try it.

flightsim.com:
concall2012.zip
-Pv-

I discovered a work around today for the large bank angles cause by the LNAV overshooting the nav track line over and over. I noticed when I first engage LNAV for the waypoint after take off there is no attempt to force the track line from the airport to the waypoint. On large angle turns, if I turn off LNAV and back on again, instead of trying and mostly failing to track the line, like the initial point, it will point the plane at the next waypoint ignoring the track line. This solves that problem for me at faster speeds on large turn angles although it's not very hands off.
-Pv-

Hi pvarn!

Make sure you edit the isg.cfg file located under [..]Microsoft Flight Simulator X\isg\Aircraft, not the file in [...]Microsoft Flight Simulator X\isg. I had the same problem as you, and this was what I did wrong :) I edited both, to be on the safe side :)