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-
|