Fsbuild-2 Flight Planner

Ernie,

Can you explain what you meant by this:

VNAV mode meets the crossing restrictions but does not climb or descend past the MCP entered altitudes.

Thanx

Ernie--

I did as you suggested and entered the line VnavSetAlts=0 in the ISG cfg file and it had the opposite effect--the VNAV function no longer captured altitudes. So I put it back on a setting of 1 which makes it work consistently, at least up to the highest altitude specified in the flightplan.

But it still fails to get the descending altitudes right.
It seems to work if I turn off the VNAV and then turn it back on again but is that the right thing to be doing? Is there a correlation between the distances between waypoints?

Speaking of which, I tried changing the distance that the autopilot switches over to the next waypoint, since mine seems a bit early. My FMS defaults at 3 miles so I entered the following line in the ISG cfg file:

FlyoverWptChgDist=1.0

However, this didn't seem to change anything--as soon as the distance to the next waypoint falls below 3 miles, the plane changes course for the next waypoint as it did before. Is there a different way to go about altering this parameter?

Thanks!

Ernie--

I did as you suggested and entered the line VnavSetAlts=0 in the ISG cfg file and it had the opposite effect--the VNAV function no longer captured altitudes. So I put it back on a setting of 1 which makes it work consistently, at least up to the highest altitude specified in the flightplan.

But it still fails to get the descending altitudes right.
It seems to work if I turn off the VNAV and then turn it back on again but is that the right thing to be doing? Is there a correlation between the distances between waypoints?

Speaking of which, I tried changing the distance that the autopilot switches over to the next waypoint, since mine seems a bit early. My FMS defaults at 3 miles so I entered the following line in the ISG cfg file:

FlyoverWptChgDist=1.0

However, this didn't seem to change anything--as soon as the distance to the next waypoint falls below 3 miles, the plane changes course for the next waypoint as it did before. Is there a different way to go about altering this parameter?

Thanks!

Thanks for the help here, Ernie.

Okay, here is what my ISG cfg file looks like:

LoadFuelonFlightPlanLoad=1 // Load Fuel automatically when Flight Plan is loaded into FMC or MCU
SetDestLoadTowerViewDist=20 // The distance from the destination airport when the tower view is changed to the destination (FS9 only)
SetMCUToPageOnFPlanLoad=1 // Set the active page on the MCU to the 'TO:' page when a flight plan is loaded.
DispAppPtrnAlts=1 // Display Approach and traffic pattern alts
ShowTodBodIndicators=1 // Show TOD/BOD indicators
DispPrevWpt=1 // Display Previous flight plan waypoint (MFD,EHSI).
ParkingFile=isg_parking.txt // Parking positions file
WptProcChgDist=2.3 // Waypoint change distance for procedures (Sid,Star, etc)
WptChgDist=1.0 //The distance (Lnav) the autopilot switches to tracking the next waypoint
VnavSetAlts=1 //Does not set altitudes when VNAV is on (default is 1)

What I do is make changes here, save it, and then load the sim. That would work right?

I find that speeds and altitudes are preset by the FMS by default with this setting. When I change them in the FMS, they show an 'A' after the altitude (see upper pic). So, in the case of PADDR, the 3500 was changed by me, as all them were.

That's why I don't understand why it makes any distinction between the first five altitudes and the last four.