Fsbuild-2 Flight Planner

I'm not able to get several settings to work in the isg.cfg or aircraftname.cfg file.

Here is a concorde profile I experimenting and learning from using the Smith FMS.
Items not marked are not understood or their function is not clearly observed in the displays or behavior
Items marked with * are items I know to work as far as I've been able to observe and control them.
Items marked with [] do not do what I expect or not work at all. I've bolded the most troublesome setting to make them easier to find:

ISG File Start-----------
LoadFuelonFlightPlanLoad=0 // 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)
[]VnavSetSpd=0 // Does not set speed when VNAV is on (default is 1) IGNORED. AIRSPEED STILL CHANGES WHEN VNAV ACTIVATED.


concorde.cfg file start ------
; AEROSPATIALE Concorde
ClimbTas=780
ClimbIas=400 // Climb Indicated Airspeed (kts)
ClimbRate=100
MaxVnavClimbRate=2000
DescentTas=620 // Use for supersonic? 620=300 mile descent. Current Cruise Alt has to be within 120ft of cruise set alt (DES ECON PATH DES TO T/D data activates)
//DescentIas=350
DescentRate=2000
*MaxVnavDescRate=2500
*DescAltRest=6000
*DescSpdRest=250
*FPA=1.7 // Flight Path climb/descent Angle (Over-rides climb-descent rates)
MaxCruise=60000
MinVnavIas=150
CruiseTas=1150
CruiseIas=410

[]VnavSetMachCruiseSpd=2.00 // In Vnav mode Sets speed as mach value instead of Ias value when in cruise. IGNORED
VnavSetSpdRestDist=15 // Distance from speed restriction wpt the restriction speed is applied (default is 25 nm)

MinVNavRadioAlt=1000

// Smiths:
LnavSetEnRouteFreqs=1
VnavOffOnManAltChg=1 // Turns off VNAV if manual altitude change is detected.
VnavSetSpdOffOnManSpdChg=1 // Turns off VNAV speed setting if manual speed change is detected
CruiseIasMax=530 // Maximum cruise speed (Ias) used in Smiths fms only. WHEN AND WHY USED IS CONFUSING. UNPREDICTABLE RESULTS
CruiseIasMin=410 // Minimum cruise speed (Ias) used in Smiths fms only. WHEN AND WHY USED IS CONFUSING. UNPREDICTABLE RESULTS

[]WptProcChgDist=3.5 // Waypoint change distance for procedures (Sid,Star, etc) IGNORED
[]WptChgDist=7.0 // The distance (in Lnav mode) the autopilot changes to tracking the next waypoint (default is 4.0 nm) IGNORED
BestHoldIas=225 // Best Hold speed (Smiths FMS)
ClimbIasMax=530 // Maximum climb speed (Ias) used in Smiths fms only.
ClimbIasMin=180 // Minimum climb speed (Ias) used in Smiths fms only.
DescentIasMax=350 // Maximum descent speed (Ias) used in Smiths fms only. SEEMS TO BE THE ONLY DESCENT SPEED USED UNTIL RESTRICTION
DescentIasMin=320 // Minimum descent speed (Ias) used in Smiths fms only.
*CostIndex=180 // Default Cost Index value for smiths fms , range is between 0 and 200.

*EngThrust=30650 // Thrust value for each engine. Displays on the smiths fms Ident page.
*ModelId=AEROSPATIALE_Concorde

*V1=180 // Default Takeoff V1 speed displayed in the smiths fms takeoff page
*VR=190 // Default Takeoff V1 speed displayed in the smiths fms takeoff page
*V2=200 // Default Takeoff V1 speed displayed in the smiths fms takeoff page
*Vref=155 // Min Default Vref speed value (displayed next to LSK R4 on smiths fms approach page).
VrefMin=155 // Min Vref speed setting (displayed as first vref item on smiths fms approach page.
VrefMid=158 // Mid Vref speed setting (displayed as second vref item on smiths fms approach page.
VrefMax=162 // Max Vref speed setting (displayed as third vref item on smiths fms approach page.
*TOFlaps=0 // Default Takeoff flaps value isplayed in the smiths fms takeoff page
*TOFlapsRange=0 // The range of selectable flaps values in the smiths fms takeoff page. Up to 5 settings allowed, must be separated by comma’s. The default values are 1,5,10,15,25

[]//FlightPlansFolder=concordeplans WHEN SET, NO FPs ARE DISPLAYED THOUGH VALID FPs EXIST WHICH WORK IN DEFAULT "flightplans" dir
ParkingFile=isg_Parking.txt
MFDTextAntiAlias=0

Thank you for clarifying many of these items.

"VnavSetSpd=0 // Does not set speed when VNAV is on (default is 1) IGNORED. AIRSPEED STILL CHANGES WHEN VNAV ACTIVATED.

This setting works. Its been confirmed many times.

Make sure there is not a conflicting setting in the (AircraftId).cfg file, as when both files have the same setting, the AircraftId's setting will override the main isg.cfg settings."

As you can see from the content of the two files, there is not a conflict. The value appears only in the isg.cfg though in testing over the last 20 hours,
I experience these conditions:
Value=0 in isg and not in aircraft: VNAV engaged= AP IAS is set to a new value
Value=0 in aircraft and not isg: VNAV engaged= AP IAS is set to a new value
Value=0 in both files: VNAV engaged= AP IAS is set to a new value
The behavior I'm getting is as if this setting is always ignored for me if I interpret this plainly. However, there is an additional subtlety:
When the value is left off:
There is an initial AP speed change on VNAV activation AND subsequent changes as conditions change.
When the value is included:
There is an initial AP speed change on VNAV activation AND NO subsequent changes as conditions change.
Note: Only tested in descent condition.
This needs further testing, but there is the possibility the value: VnavSetSpdOffOnManSpdChg=1 // Turns off VNAV speed setting if manual speed change is detected conflicts with VnavSetSpd=0 , or detects my attempt to correct the value in the AP and correctly disables further VNAV input.

---------------------------------------------------------------------------
"CruiseIasMax=530 // Maximum cruise speed (Ias) used in Smiths fms only. WHEN AND WHY USED IS CONFUSING. UNPREDICTABLE RESULTS
CruiseIasMin=410 // Minimum cruise speed (Ias) used in Smiths fms only. WHEN AND WHY USED IS CONFUSING. UNPREDICTABLE RESULTS

These values are displayed on the PERF LIMITS page of the FMC. The settings above overdie the defaults.
These settings are applied only when a Cost Index is set. "

How the Cost Index is scaled is confusing. Until you mentioned this relationship here, I would never have derived this from the documentation.
Would I get more predictable results if I leaved the Cost Index out? Is the idea, the higher the index,
the higher speed the FMS will use and thus force a higher fuel rate? Perhaps am Index in the middle of its scale and a very small difference between
the max and min values?

---------------------------------------------------------------------------
"WptProcChgDist=3.5 // Waypoint change distance for procedures (Sid,Star, etc) IGNORED
WptChgDist=7.0 // The distance (in Lnav mode) the autopilot changes to tracking the next waypoint (default is 4.0 nm) IGNORED

These all work, and are all confirmed to work, and have done so for years."

Confirming my installer applied version 1.8. Any way to tell?
The installer filename does not contain a version and the the Windows file property sheet version = 0.0.0.0
Size = 17.2 Megs
Date Modified 9/3/2012 8:44 PM (unfortunately, this looks like the download timestamp, not original file creation)
My OS is Win7X64 and FSX Deluxe. 1.8 and my OS/FS version have been tested to confirm this?

When I first started using these two files together, the isg file contained the setting:
WptProcChgDist=2.3 // Waypoint change distance for procedures (Sid,Star, etc)
I commented it out when I could not get the aircraft file to modify the behavior.

For me, the turn to next waypoint is always 3.0 exactly whether it's a waypoint or procedure, not the default 4.0:
WptChgDist The distance (in Lnav mode) the autopilot changes to tracking the next waypoint
(default is 4.0 nm)

I would then ask if the word "tracking" is significant? Is "tracking" different than "Activated" If I use the word "activated" I could say:
The turns in my flight plan get "activated" ALWAYS exactly 3.0 miles prior to crossing the waypoint regardless of any setting in the cfg file.

I was hoping this setting would affect when the turn got activated because the current 3.0 miles causes the Concorde to "S" turn for about 10 miles when a waypoint or procedure is activated. I have an external navigation program which when it activates, starts turns in the Concorde @12 miles ahead of the waypoint, I get a smooth arc over the waypoint with no "swimming."

---------------------------------------------------------------------------
Thanks again for the clarification on DescentIasMax. The Settings document doesn't specifically detail the relationship between the various min/max values.
Again, would it be better to use no cost index value and/or come combination of mid value for the index and small (if any) min/max to get predictable results?

---------------------------------------------------------------------------
"FlightPlansFolder=concordeplans WHEN SET, NO FPs ARE DISPLAYED THOUGH VALID FPs EXIST WHICH WORK IN DEFAULT "flightplans" dir

You need to use the 'full' directory path (ie C:\Program Files...")."

THIS HELPS A LOT. No mention of this detail in the doc.

---------------------------------------------------------------------------
The Fuel quantity values as displayed in the smiths FMS are 20K lbs lower than the actual fuel quantity as displayed by the FS fuel dialog
and 20K lbs less than an XML gauge using the value:

FUEL TOTAL QUANTITY WEIGHT,pounds

Since this difference was the quantity of CENTER2 at the time I noticed the discrepancy, wondering if the FMS gets it's total from adding up tanks and one or more tanks are not included in the calculation? I need to run more tests with various tanks zeroed to see if I can get the correct value and what the condition is. I have an aircraft which uses 7 tanks but I have not placed the ISG1 software in this plane since it would be very time consuming to do so at this time (trying to get the Concorde working.)

---------------------------------------------------------------------------
VnavSetMachCruiseSpd In Vnav mode Sets speed as mach value instead of Ias value when in cruise.

Example:
VnavSetMachCruiseSpd=2.00

Does not get used. Always some other value gets set for cruise. I assume this is another Cost Index conflict? Leave out the Cost Index value to get more predictable results?

Thanks again for rapid responses and much more understanding than the documentation provides.
-Pv-

Fuel remaining error in Smiths FMS.
Testing confirms the quantity of only three tanks are combined to display the total fuel remaining:
FUEL TANK LEFT MAIN QUANTITY
FUEL TANK RIGHT MAIN QUANTITY
FUEL TANK CENTER QUANTITY

In FSX there are a possibility of 11 tanks. Most of my self-created aircraft use 4 or more with the SR-71 using seven. The Concord is currently configured for five.

Suggest using FUEL TOTAL QUANTITY which will always be accurate.
-Pv-

There appears no way to apply an altitude speed restriction to departure, only destination. The results is VNAV can only be engaged after climbing above restriction when flying in ATC controlled space like VATNET since airliners do not climb at restriction speed.

Unless I can be convinced otherwise, it's not possible to control the Concorde's climb profile properly using this tool. The Concorde is too complex. It climbs at different rates at different altitudes.
At the simplest level not including any finesse (averages):
0-6000= (or restriction alt) ft 250 KIAS, 1500 ft/min
6k-32K= 400 KIAS, 1500 ft/min
32K-50K= 400 - 530 KIAS riding the barber pole limit, 1000 to 1800 ft/min
50K ft and above = Mach 2.0, 50 ft/min (100 in FS = minimum)

As such, it may be possible to handle the 0-32K portion of the climb above restriction, Top of cruise (engage VNAV) and descent ( I have the descent somewhat working, but when the descent is triggered and other small problems are still being worked on.

Edit...
OK scratch that. Climb is too complex for the tool. VNAV cannot accommodate the 130 knots range of speed necessary over hundreds of miles and tens of thousands of feet.

So, while trying to get the Cruise/Descent transition working, I have this problem:
If I engage VNAV after the top of climb as shown as the highest altitude waypoint matching the cruise value in the init page, a command is immediately sent to the AP speed to slow to decent speed (even though the plane is till hundreds of miles from the descent point. The plane will then fly at this reduced speed for hundreds of miles, then at the correct distance of @300 miles from destination, the plane will descend at the correct rate. To solve this problem I need one or both of the following possibilities:
1) The VnavSetSpd=0 to work on the ISG or aircraft file so the pilot can set the speed manully (and not have to correct the initial speed the VNAV sets)
2) The VNAV to set the descent speed at a designated distance from the decent point (configurable) in this case about 50-75 miles ahead of the descent vertical dive point, not the current behavior where it doesn't matter how far from the decent point the plane is.
3) I need to acquire a better understanding than 45+ hours of reading and experimenting could provide.

If I cannot solve these problems, all VNAV can do for the Concorde is manage the vertical descent when the pilot engages it at the proper time (at the vertical descent point) having avoided engaging VNAV throughout the flight until then.
-Pv-

Another problem with cruise speed and is why I thought the FMS was setting the descent rate early.

I start the test flying at FL 550. Cruise Alt is set for FL550.
Current speed is Mach 2.01 @452 IAS, 1158 TAS with AP Speed hold in MACH mode.

I look at the CRZ display page with FL550 set as the cruise alt in the Init page:
ECON CRUISE

Contents:
CRZ OPT Alt/Max
FL550
TGT SPD
347/2.02 <---- I explain below why I think this display is wrong and why it's important

Related Settings in aircraft file used by Smiths:
CruiseTas=1145
VnavSetMachCruiseSpd
VnavSetSpd=0 (no file conflict confirmed)

Commented out these former settings:
//CruiseIasMax=455
//CruiseIasMin=445

Problem:
When clicking VNAV, speed is immediately set to 347 IAS, Mach 1.54 in Mach Hold mode

This makes no sense.

I commented the line VnavSetMachCruiseSpd reset and the CRZ display was the same. Clicked VNAV and the results were the same. The program always sets this air speed and whether or not SetMach is used, the program does not switch between mach and IAS bug modes but uses whatever mode it's in. The only values I have similar to this in the cfg file are:
DescentIas=350
DescentIasMax=350
DescentIasMin=345
CostIndex=100

This looks to me as if the Cruise TAS is calculating as Mach 2.02 correctly as displayed in the CRZ page, but the Descent Speed is being
used instead as the cruise IAS speed as displayed in the CRZ page.
I think the the IAS portion of the CRZ display is taken from the Descent values and the Mach portion of the display is correct.
The program uses the IAS portion of the display (or the same source for the value) for cruise which is incorrect instead of the Mach portion of the display which is correct for the current TAS and altitude.
What am I missing or is this norked?

While I have your attention, the program badly needs a Mach Hold Setting variable so planes which fly at a certain mach can do so regardless of the weather or altitude. Using IAS or TAS is too dependent on altitude to be used reliably, especially the Concorde which cracks up slightly above Mach 2 and flies inefficiently much below that value. Modern airliners also are affected by the TAS or IAS. Mach hold works much better since the plane can then fly at any altitude within its spec in any weather and fly correctly.
-Pv-

"Hmmm,

I just tried it, and you are right 'VnavSetSpd=0' does not work, its not accepting VnavSetSpd=0 for some reason, we must have
broke it in the 1.8 update.

As a workaround use VnavSetSpd=3, that should work in place of 0 with the same effect."

HEAVY GORTS! Glad you found it! Will use the work around.

"The Fuel quantity values as displayed in the smiths FMS are 20K lbs lower than the actual fuel quantity as displayed by the FS fuel dialog
and 20K lbs less than an XML gauge using the value:

FUEL TOTAL QUANTITY WEIGHT,pounds

Since this difference was the quantity of CENTER2 at the time I noticed the discrepancy...

It only takes into account the one center tank. This was already noted as an issue previously on the forum."

Great. Hopefully using the FS value which automatically add all the tanks together will prevent this problem under all circumstances.

"VnavSetMachCruiseSpd In Vnav mode Sets speed as mach value instead of Ias value when in cruise.

Example:
VnavSetMachCruiseSpd=2.00"

I realized the next day this was a misunderstanding on my part (and wishful thinking too.)
Need a set cruise to a mach speed variable config setting.

""FlightPlansFolder=concordeplans WHEN SET, NO FPs ARE DISPLAYED THOUGH VALID FPs EXIST WHICH WORK IN DEFAULT "flightplans" dir

You need to use the 'full' directory path (ie C:\Program Files...")."

THIS HELPS A LOT. No mention of this detail in the doc.

It is mentioned...twice"

It helps if you know which of the 18 docs this is in. I could have sorted this out earlier if this additional information was in the Settings doc where the feature is described and I'm trying to learn the settings.

"For me, the turn to next waypoint is always 3.0 exactly whether it's a waypoint or procedure, not the default 4.0:
WptChgDist The distance (in Lnav mode) the autopilot changes to tracking the next waypoint
(default is 4.0 nm)


I just tried them, they both work.

But really WptChgSecs=xx is going to the better overall setting. As that wil cause both distances to vary based on the
aircraft's speed instead of a single hard distance value for each turn."

I'll try the seconds. Did you test on a waypoint which is in the path of a descent?
Thanks again for all your help on this.
-Pv-

There seems to be a number sign error in the code somewhere associated with triggering VNAV descent. The descent target altitude is set properly and the vertical speed is set to a positive number instead of a negative causing the plane to climb.
The two times I've experienced this is when VNAV was on during start of cruise. When it doesn't happen is when I have VNAV off during cruise and turn it on just before the calculated TOD.
-Pv-

The default descent speed for all the aircraft I fly is set myself in the FS aircraft.cfg file. None of my aircraft have 1500 set as the default vertical speed. In the case of the Concorde where this fault has been observed twice, the default VS is 1200.

When the VNAV commands an altitude change, the smallest change it will command is 1500+-. This has been observed in the two aircraft where I have installed your gauges.

If for instance the aircraft is at FL550 and 1000 miles from now there is an altitude set for a waypoint to cross at 8000.
When the error occurs, it is usually hundreds of miles from the decent point TOD ( long after reaching cruise and the FMS display is showing cruise mode which is triggered within 220 ft of the set cruise alt) the AP will be commanded to 8000ft +1500. The aircraft will go into a sharp climb and stay there until it stalls or pilot takes corrective action.

In FSX, the alt set and the vertical set will operate coordinated unless the vertical speed bug is commanded separately as follows:
1) Set new altitude: VS bug will change up or down based on whether the new alt is higher or lower than current.
2) Set VS bug but NOT the Alt bug: Alt bug will not change and the aircraft will descend or climb independent of the altitude set in the alt bug.
3) Set new Altitude, then set the VS bug to anything you want. Regardless of 000 or +- values, the AP VS will command the plane to whatever you set even if the result is above or below the set altitude.

BTW: I seem like an imbecile because I'm trying so desperately with the limited time I have to learn your interfaces and build proper CFG files, but I've been flying in FS for 28 years and know it inside-out. I have built many complex aircraft dynamics which are widely distributed on the NET. I have also built gauges which will command the aircraft features and know something about the FS AP. I'm also an automated software tester for a company whose product costs $thousands per license. I'm not a professional coder, but I write hundreds of lines of code every day. though I sometimes come to wrong conclusions and assumptions, I know when I'm right (not guessing) about something and I'm right about this.

Since I do not have 1500 configured as a vertical speed in the aircraft (to confirm this all I have to do is change the altitude bug and watch the vertical speed command itself to the ft/min I have set which it does correctly) the 1500 is coming from VNAV and it is being set independently from the altitude command and done incorrectly.

What is REALLY happening is 8000 ft is being set in the altitude bug and +1500 ft is being set in the VS bug. I'm not wrong about this and the the FS aircraft.cfg file is configured properly.

I appreciate your aggressive and rapid support of your product so all I'm doing is asserting why I know what I know and will not accept the easy answer this time.

I wish the the program would command smaller than 1500 when close to the target altitude. Otherwise the pilot is forced to override the VNAV close to the target to avoid the sudden jerk as the AP tries to pull the plane out of the sharp dive at the last moment.
-Pv-

There are some screenshots illustrating the Cruise and descent speed errors as displayed in the Smiths FMS. Following two posts contain additional screenies.

conc_cruise1.jpg
Concorde at cruise, ECON CRUISE screen on FMS. TGT airspeed is wrong. Mach is correct. Current altitude and pressure is not taken into account for the airspeed.

-Pv-

conc_cruise2a.jpg
Concorde at cruise, ECON PATH DES screen on FMS. TGT MACH is wrong, airspeed correct. Current altitude and pressure is not taken into account.
-Pv-

I've also noticed once the VNAV has sent the maximum descent rate (MaxVnavDescRate=2500) to the AP or it's internal minimum of -1500 to the AP, it disables itself (VNAV button changes from yellow to white.) The Max setting is usually set at the TOD. This happens in both my test aircraft. In the 727 I'm using FPA=3.2 and in the Conc I'm using:
DescentRate=1200
MaxVnavDescRate=2500

While disabling itself at -1500 near the bottom of decent can easily be dealt with, disabling itself at the TOP of Descent just after setting the max rate is inconvenient if I don't notice it. The plane will continue to dive at the max rate. If the VNAV is re-enabled, it continues "normally" until -1500 minimum.
-Pv-