Fsbuild-2 Flight Planner

Ernie,

Many thanks for the ISG1 suite, which I bought a few weeks ago. Great piece of programming! It really does add a whole new level of realism to FS9.

I'm now getting the configuration files to the state where the planes now do pretty much what they are supposed to do; however I've a few queries...

- Once the cruise altitude is set in the Smiths FMS, it's possible to change it by changing the setting in the 'econ crz' screen. However, if you then change something else like the descent speed, the cruise altitude re-sets to the value that you originally set. I noticed this also in one of the threads below, so just to confirm that, really.

- I use the 737 gauge a lot (I fly 737s a lot!), but it doesn't appear to display the names of the waypoints, as the illustration in the ISG settings PDF shows. Am I missing a command in the cfg file?

- the VnavSetMachCruiseSpd command in the aircraftID.cfg for setting mach value instead of IAS in cruise: what's the format for using this command? I've tried VnavSetMachCruiseSpd=1, and VnavSetMachCruiseSpd=0.79 (the 737NG cruise speed) but the autopilot still displays in IAS. I've got around it by manually switching to Mach at around FL220 and then setting cruise Mach manually. It switches back to IAS when the plane reaches TOD.

- There are some references to a 'performance data' file, which I don't seem to have, as I don't have FSBuild. What kind of difference does this make?

- Is it possible to start in the middle of a saved flight, and have the gauges where they were when the flight was saved? I've tried it, and the cruise altitude won't enter.

I started off using the 'ResetApHdg=1' in the cfg files but it seemed to make the FMC too unpredictable. I REMmed it out of the cfg file and it's much better now. The autopilot responds fine so it ioesn't look like I needed the command anyway. Also, the FMC occasionally won't accept input specific descent values, but that may be more to do with me asking the FMC to use a higher speed than it thinks is appropriate. I'll keep experimenting with that.

Many thanks for a great product!

Cheers,
Martyn

PS: reading through the posts, I've discovered that the lack of waypoint names was a font problem. I've reinstalled direct to the FS9 folder, and this problem's gone away.

Thanks very much for the response, Ernie; much appreciated.

Cheers,
Martyn