README for FSCaptain version 1.7.4                          APRIL 24, 2017
--------------------------------------------------------------------------

This file is best read with word-wrap enabled, unless you are using a device which can display well over 1030 characters per line. :)

Flights saved under a different version of FSCaptain cannot be restored. Please complete all outstanding flights before upgrading!

The latest version of MakeRwys.exe is included and should be installed to your Flight Sim root folder as long as your current MakeRwys.exe is of an older version. This is a necessary change, as future versions of FSCaptain will use the newly acquired data for a much improved Runways Report. (Thanks as always to Pete Dowson for his diligence, enthusiasm and patience in dealing with multiple requests!)

If the installer asks to overwrite existing files, please reply Yes. Some of the core configuration files are kept as read-only, and the installer needs your permission to update them.


========================================
NOTE - Newly Updated Configuration Files
========================================

The Fixpack version includes an overwriting version of \Config\Notams.txt to include new items. If you have custom NOTAMS in your existing \Config\Notams.txt file, PLEASE BACK UP YOUR CHANGES before installing this Fixpack. Then after installation of the Fixpack, you may copy your changes into the new file.

The Fixpack version includes an overwriting version of \Config\Deice.cfg to allow for a new option which will come into play when Remote Deicing Facilities are enabled. If you have custom airport deicing rules in your existing \Config\Deice.cfg file, PLEASE BACK UP YOUR CHANGES before installing this Fixpack. Then after installation of the Fixpack, you may copy your changes into the new file.

The Fixpack version includes a small set of new transportable items - "Commercial Cargo" - which can be hand copied from \Config\NewItems.cfg into your existing \Config\Items.cfg file.

================================================================================================================
If you are upgrading - to be safe always make a copy of your FSCaptain folder before installing any new version.
Download a safe environment and a README from http://www.fscaptain.net/downloads/My_Safe_Backup.zip
================================================================================================================

To install simply execute the enclosed exe. It will locate your FSX folder for you but you may browse to another folder if you wish. This also works for the FS9 or P3D versions of FSCaptain as well -- simply browse to your FS9 root folder or your P3D root folder before installing.

VERY IMPORTANT !!! When you first install FSCaptain by selecting a target folder manually or by browsing to it, you MUST select the root folder of your FS installation. For example if you have FSX installed in the folder D:\FSX\ then put that path in the target folder for the installer. DO NOT try to install into D:\FSX\FSCaptain\ or any other place. If you do this FSCaptain will not function properly. The installer will automatically find an existing \FSCaptain\ folder and the entire data structure for you in the folder that you specify.

=============================================
NOTE - Anti-virus programs and "new" Software
=============================================

Many anti-virus software packages react to new software they have never encountered before. Since you are about to be one of the first to install a new build of FSCaptain, your anti-virus software will be one of the first of its brand to see the new FSCaptain. Some anti-virus programs will flag this for your attention and your intent. Some anti-virus programs will pro-actively attempt to isolate (or quarantine) a new .EXE or .DLL. We have had a report of a widely-used anti-virus program going so far as to isolate text files (.XML and .CFG) that FSCaptain reads.

Now it is up to each of us to keep our PCs safe. We can't advocate shutting down your anti-virus programs, but if you could put yours into "install mode" or switch off "live scanning" during the installation, then you may be able to avoid some problems.

In general use, if you can have your anti-virus programs exclude your entire flight simulator installation from "real-time scanning," you will better your simulator's performance. Our simulators are constantly reading lots of tiny data files, and if your PC is following each read with having the anti-virus program ask, "What happened just now?" well you can imagine the constant resource drain.

Finally, if your anti-virus program does detect FSCaptain and asks to submit it for closer examination by their technicians, by all means you should do so. The sooner that each version of FSCaptain is analyzed (and not just "patterned matched") the sooner it will be taken off their radar.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

CHANGELIST FOR FSCAPTAIN 1.7.4

General Testing Notes for 1.7.4 -- Please read before installing

=======================================
Testing Notes on Bugs and Changed Items
=======================================

That last item is in respect for one of FSCaptain's first testers, and all-around good man Norman Lane Goodman - "Crash Lane" as he would refer to himself.

Lane was with his wife and children when he passed peacefully in March after a sudden illness. He is missed by all who were lucky to know him.

Lane loved animals, and his family has said that a donation to the Humane Society in Lane's name would be an honor. http://humanesociety.org/

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

CHANGELIST FOR FSCAPTAIN 1.7.3
============================
Testing Notes on New Options
============================


==========================
Testing Notes on New Items
==========================

=================================================================
Exit Mapping - mapping the exits of your aircraft to their "type"
=================================================================

Many years ago Microsoft defined a maximum of four exits for aircraft (controlled by the keys SHIFT-E, SHIFT-E #2, SHIFT-E #3, and SHIFT-E #4), and divided them into three signal able types – Main (Passengers), Cargo and Emergency.

By the time of FSX, many airliners used SHIFT-E to control the main crew & passenger exits, SHIFT-E #2 to control the cargo exits, and SHIFT-E #3 for other passenger or perhaps service (catering) exits.

Prior to FSCaptain 1.7.3, the ACME system allowed Captains to define whether or not the FO / FA team would open and close the exits needed to allow passengers and cargo to load. The catch was that FSCaptain would only open and close the main exit. Now that's no longer the case....

Using Exit Mapping, you can now define which exit numbers belong to a simplified set of exit types: PAX, CARGO, OTHER. You should have at least one PAX or CARGO exit defined. You need not define an OTHER exit if you wish.

By default, both PAX and CARGO exit types are mapped to "Exit 1" - the SHIFT-E controlled exit. This replicates the practice that FSCaptain has previously gone by.

On a PAX flight, your crew will operate the PAX exits first, followed by the Cargo exits. On a Cargo only flight, only the Cargo exits will be operated. In case of an emergency landing, your PAX, Cargo and Other exits will all open to allow full evacuation of the aircraft.

If you are checking an exit type's status, there is an Exit Speed value (in seconds) which is simply the time it should take for an exit to complete moving before the Captain is notified of an "unresponsive

If your aircraft uses the standard (SHIFT-E) system, each exit will need to be moved independently. For example, if you're in the default C208B which I have exits 2 and 1 defined as OTHER (they are the Captain's and FO's doors) then when you're executing an emergency evacuation, the PAX door will open first, followed by Cargo door, then the FO's door and finally the Captain's door. (At a speed of 4 seconds per exit, this will take 16 seconds to open all exits.)

Some complex aircraft will need to be interfaced with the FCDU so we can recognize their exit status. Also, some complex aircraft require their own systems to be used to open and close their exits. It's their aircraft… we can only do our best to operate with it!

You can enter up to four Exit numbers for each of the three Exit types – just use the Exit's number (1 through 4) or leave an entry blank or at "0" to indicate no other exits for a type. If you want FSCaptain to monitor a particular exit, but you don't want FSCaptain to operate it – for example if you use an add-on that wants to control the PAX exits for a special aircraft – just enter those Exit numbers as negative values – in other words use "-1" instead of "1", etc.

If your add-on controls the PAX or Cargo exits at a time where the loading process is ongoing, you may try setting that exit type's mapping to all "0"s, so FSCaptain won't check that exit type's status.

Finally if you can't seem to get your exit mapping working, please email us an FCDU log from an attempt to load or unload and we will attempt to triage. (You could in the meantime declare your exits as INOP on the aircraft configuration form.)

==============================
Testing Notes on Changed Items
==============================

=====================
Testing Notes on Bugs
=====================

==================================
Testing Notes on Interface Changes
==================================



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
CHANGELIST FOR FSCAPTAIN 1.7.1

Testing Notes on New Options

Previously, flights dispatched without an alternate airport were given extra fuel in the amount of 85% of their aircraft's "Reserve Fuel" allocation. That default value has been changed to only 10% extra fuel. An Options.cfg flag of RANGE_FACTOR_SANS_ALTERNATE will allow Captains to set a percentage from 0% extra fuel to 85% extra fuel.

RESERVE_FUEL_IN_MINUTES, HOLDING_FUEL_IN_MINUTES and RESERVE_FUEL_IN_MINUTES_HELI will now accept values down to zero. Captains will be cautioned on their Dispatch Releases if they choose to take on less fuel amounts than are suggested.

If an airport scenery has BGL runway surfaces of a different type than "pictured" - a dirt runway rather than a nicely grooved concrete runway - Dispatch could refuse an aircraft's use of that airport. A new optional file - airport_surface_override.txt will allow you to specify an overall surface type for Dispatch to consider. Details of this file's format are included in the User Guide and the file itself.

Runway lengths for destination and alternate airports have a new default behavior: Dispatch will not offer airports without enough STD/MLW length as a Destination for Charter Flights, nor as any Alternate airport. This is consistent with previous FSCaptain functionality. However if a Captain specifies an airport as either a Destination or an Alternate, Dispatch will release such a flight - with a caution added to the Dispatch Release. However if the option ENFORCE_DEST_RUNWAY_LENGTH=1 is enabled, no flights to such airports can be specified.

The Load Factor used to determine possible payloads is now governed by a "variance range". PAYLOAD_VARIANCE is an integer with valid values from 1 to 25. This will represent the range which your offered payload sizes can vary. (Initially for PAX flights only.) For example if you have a Load Factor of 75 and a PAYLOAD_VARIANCE of 25, you could get PAX loads anywhere from 50% to 100% of capacity. If your PAYLOAD_VARIANCE is 10 (the default value) then you could get PAX loads anywhere from 65% to 85% of capacity.

Runway surface detection (as used by Dispatch) can now be bypassed by setting the option DISABLE_SURFACE_CHECKS to 1. Doing so will allow you to dispatch jetliners to lakes and seaplane bases and grass strips, or float planes to desert landing strips. Use with caution, as Dispatch will not warn you of a possible mismatch. This option does not affect the detection of surface types while on the ground - that is handled by the DISABLESURFACE option.

A new option - REQUIRE_TYPE_FOR_MAP - can be set to zero in order to ignore the TYPE value in load map files. (Allows for "looser matching.")

A new configuration file - ignored_airports.cfg - is available for each Captain to add "troublesome local airports" which hinder normal operations. (See the User Guide for details.)

New options - POSITIVE_CROSSWIND and POSITIVE_HEADWIND - will allow you to format "Headwind/Tailwind" and "Crosswind" data on the Dispatch Release.

If you are due to have a failure in the first half of your flight (or if you are destined to have an engine failure or fire), you can "enhance" the chance of the failure occurring on the takeoff roll by setting TAKEOFF_FAILURE_ENHANCEMENT to a high percentage (max of 100). The default value for this is 0. (So there's no change if you don't desire one.)

If you do not wish to have any failures (aside from flight control failures) in the first half of your flights, set TAKEOFF_FAILURE_ENHANCEMENT to -1.

The maximum pay amount per hour per level has been increased to 400, and that cap can be increased to 1000.

Executing a "manual load" can now allow use of the Acme Fuel Loading service with the new option MANUAL_LOAD_USES_ACME_FUEL.

USE_TAT_FOR_HAZARDS_ALOFT will substitute the simulator's Total Air Temperature value instead of its Ambient Temperature for all in-air hazard pack items.

The Administrator's use of Internet weather to fill in any gaps from your weather engine's data, can be disabled by setting USE_INTERNET_WEATHER=0.

Captains who manage to break many company rules (and/or company aircraft) will find snarky notes in their Areas of Concern if the option ALLOW_INSULTS=1 is set. :-)

Setting ENFORCE_INSPECTIONS to a value above 0 will call for an inspection check if any (actual or possible) damage to an aircraft occurs. This check will take place after the Captain has either gone IN or has CANCELLED the flight. This will prevent any further legs to be flown and will effectively end your current session (simulating reports & interviews)! This does not prevent you from using the same aircraft in future flights - only for your current session.

By default, system failures can occur before your initial takeoff... possibly ruining your planned sim experience. Set TAXIOUT_FAILURES_ALLOWED=0 and on your initial taxiout, no random equipment failure should occur. This only applies to the initial taxiout, if you're making a multi-leg flight, you could have random equipment failure on taxiout for leg #2, etc. Hazard pack items are excluded from this option - you can have your controls frozen due to ground ice, but a deicing would fix that. Likewise if you're driving in rain w/o engine protection, you can have an engine flameout.

A new global option - in options.cfg - can remove the crew's ability to open / close the main doors. CREW_OPERATES_DOORS=1 is the default value, and we have added the ability of an FO to operate the doors on Cargo flights and on PAX flights without an FA! There is also an airline-specific version, so you can leave door-handling globally, but disable it for a specific airline....

Requests to have relief of the 250kt speed requirement may be denied on a random basis. To enable this, set the option.cfg value of ODDS_TO_DECLINE_250=0 anywhere from 0 (never decline) to 100 (always decline).

Finally, there is a feature within FSCaptain to set a periodic automatic save of the simulator's flight data, which would also trigger an automatic save of the FSCaptain flight data!

Here are the notes in the options.cfg file that manage FSCaptain Autosave:

SIM_AUTOSAVE_CLEANUP=0 ; 1 = Removes all simulator save files generated during the flight

; after going IN and updating your company log. Default is 0.

SIM_AUTOSAVE_FILES=10 ; The number (0-16) of autosaved simulator files to generate per

; flight. 0 (Default) = Disables simulator autosave.

SIM_AUTOSAVE_ON_GROUND=0 ; Sets autosaving of simulator files while on the ground.

; 1 = Before takeoff. 2 After landing. 3 = All phases.

; 0 (Default) = Simulator autosave will only occur in air.

SIM_AUTOSAVE_SECONDS=180 ; The number of simulator seconds between simulator autosaves.

; Range is 30 to 1800. Default is 180. (That's three minutes.)

These autosaves will be written to your standard "\User\Documents\[Flight Sim Documents]\" folder, so if you intend to use this feature you must have all rights to write to that folder. Otherwise crashes & CTDs can occur.

Please do not use this feature if you are using another add-on to autosave your simulator flight data (such as FSUIPC 4, or the AutoSave module for FS9).


Testing Notes on New Items

For each build, there's almost always more items added to the FCDU & ADMIN logs.

PAX flights with VIPs and GROUPs are now considered as Priority flights. This means you will not get a penalty for an early arrival, although you would face a 2X-points penalty for being late.

If you are flying with a PLN set of waypoints, and if you miss a waypoint in-flight, your Dispatch office will send a message within several minutes advising you to either cross your waypoint or to advance your PLN active waypoint to the currently active one. Otherwise your block estimates (time and distance) will increasingly be more and more incorrect.

The FCDU will now display the ID of the closest Airport Reference Point on the home ACARS screen when it's powered up or reset. If you have the SELECT AIRPORT option enabled, any change you make there will then be reflected on the home ACARS screen.

If the aircraft's Maximum Takeoff Weight and Minimum Runway Length for Takeoff have been entered, the Dispatch Release should contain an estimated Takeoff Roll that considers the airport's altitude, current reported temperature, and the effects of wet runways if reported.

Your Dispatch Release will contain runway information for your Departure, Destination (and Alternate) airports - this includes Length, Threshold Offset, Width, ILS data, Winds, and whether or not the runway is CL (Closed for Landing) or CT (Closed for Takeoff).

It is now possible to change (or add) a PLN file in the FCDU before a flight starts. On the Revise Flight screen (screen 53), the PLN filename will be present and can be changed. You are limited to PLN names of 32 characters or less, and the ".PLN" extension is not needed. The file must be in the folder where your usual PLN files are, and it must be a valid PLN for your Departure and Destination airports.

Aircraft have a new value - Preload Minimum Fuel Percentage. This allows you to specify a minimum amount of fuel in your aircraft's tank for your first flight of a session. Barring very peculiar procedures, airlines will rarely leave their aircraft's tanks near empty, nor will they leave them parked fully fueled. The range you can select from is between 7.5% and 45.0%, and the default (for aircraft that have not had this value defined) is 10.0%.

Actions which would pause the autoload process are now displayed on the FCDU just as they have been on the pre-loading screen.

"Bright" versions of the FCDU for FS9/FSX/P3D are included as new gauges - FCDU9B is the one for FS9, and for FSX/P3D FCDUB.gau is the grey version and FCDU2B.gau is the bronze version. Please note to change both the !ACARS and the !FCDU references in your panel.cfg files.

A new class of passenger ("Comfort Economy") now can have load stations defined. The code for this class is "W". Both airline & competition pricing tables have been revised to accommodate W class ticket pricing. See the "Sample" Economic files for details.

Cabin Emergencies will trigger alert messages from Dispatch through ACARS. If you have Environmental messages enabled, you will see a yellow/orange CABIN EMERGENCY displayed while the status of the emergency is being evaluated. If the emergency is not verified, the display will vanish. If the emergency is confirmed, the display will appear in red.

Bronze versions of the FCDU (normal and "Bright") are now available for FS9.

When fluid deicing is called for, the aircraft will need to deploy their flaps. (Strictly speaking, flaps should be fully deployed but for now any deployment should suffice.) An INOP check has been added to the Aircraft Configuration panel in the Administrator to handle any aircraft which do not report correct Flap Deployment values, but if you find an aircraft that doesn't work, please let us know.

There is also a new INOP system on the aircraft configuration panel - Beacon Lights. We have enabled a new mandatory light requirement... to have the aircraft's beacon lights on prior to loading, remaining on at all times until unloading has completed. We have enabled an interface for non-standard aircraft, so if your favorite aircraft doesn't use the standard signal (noted on the Interface screen of the FCDU) let us know which aircraft it is and if we have a copy we can begin interfacing it.

When using the Administrator for flight planning, you can change the airline parking code for a flight by editing the code in the "Codeshare" textbox. If you're flying for ACME Airlines but planning to fly in an aircraft with a FedEx livery, you can enter "FDX" and receive FedEx parking assignments!

All save files now make a copy with the flight number and the timestamp of our OUT time. This is to allow recovery in case of accidental overwrites of the actual save file. Details are in the Users Guide.


Testing Notes on Changed Items

Fuel loads are no longer "rounded up" to the nearest 100 / 1000 unit.

Prepar3D Version 3 should be detected better, and the correct dll.xml file should be attended to.

The term "ICE WGT" on the FCDU and FCOM has been changed to "XTRA WT" to better reflect that it's not always "ice" that's being detected.

Safety announcements will now not come during pushback(!).

The physical area around the FCDU's "On" switch has been increased to account for the "On" label itself.

If Ground Service Catering, Fueling, Deicing, or Pushback have been called or are underway, the COMMIT key on the Load Confirm screen (#42!) will be disabled.

Flights involving airports with reported limited visibility and an inoperative RVR system will be flagged on the Dispatch Release.

Airline's Landing Light Policies have been overhauled. Captains can define for their airlines the altitude (6000ft - 21000ft) below which Landing Lights need to be on. Further, Captains can define for their airlines whether or not to require Landing Lights be switched off when above the same altitude. PLEASE READ THE USER GUIDE for details on how this is applied - flights involving airports with elevations that are near (or greater than) the airline Landing Light Policy Altitude, will have the Policy Altitude adjusted higher for the flight.

The process used to define the initial "direct flight" altitudes for flights has been changed. Initially one thousand feet are allocated per 10NM distance, not to exceed the aircraft's standard cruise altitude. Further, for all flights longer than 30NM, FAA-based IFT hemispheric rules are applied where South and West bound flights will be given an initial "even" flight levels, and North and East bound flights will be given "odd" flight levels. (This will not override an aircraft's defined cruise altitude.) Again, this is only the initial "direct flight" altitude and can be overloaded by the Captain's discretion in the Administrator.

A new METAR pattern for winds is now accounted for - "2714KT" means winds from 270 @ 14KT, not winds from 271 @ 4.

Once a flight plan has been loaded in the Administrator, the total distance of the route is displayed.

VIPs and GROUPs which have an airport affinity now can be included on flights TO the airport affinity area. For example, a Hollywood Star could be found on a flight to KLAX from nearly anywhere.

Items may now have multiple airport affinity IDs, although they would share the same affinity radius.

The term "ETE" has changed to "Block Time" - to better define its purpose to signify the OUT to IN block time, rather than "Estimated Time Enroute" which could be taken as OFF to ON time.

If the FSCaptain pushback service is used, "taxi on ground" penalties will not apply during pushback and for approximately one minute after pushback ceases. This will allow Captains a small grace period to remove their aircraft from soft/unsafe surfaces that pushback may have placed them. (Ensure that enough engines have been started to allow movement before pushback has concluded!!)

A bounced landing which carries on too long (at least 3 seconds) will now cancel any Nice Landing Bonus that could have been earned.

Go-arounds can now be called by the FO without having a FA (or PAX) onboard. Also multiple go-arounds can occur on a single approach.

If a declarable emergency occurs at less than 1000ft AGL (on approach for example), you will not be penalized for not declaring such. (This is a retroactive penalty removal, so your score may be elevated!)

The screen which appears once an emergency has been declared now displays the distance & heading to your destination as well as to the closest appropriate airport. Also, the current Range and aircraft Gross Weight are displayed. The Range to let you know how far you can fly, and the Gross Weight to let you know if you're below the aircraft's Maximum Landing Weight (MLW). If your situation is a system failure such as Landing Gear, you may wish to burn off any excess fuel by flying some holding patterns to get below the MLW. However if you have a cabin fire or medical emergency you probably should land ASAP, despite the weight.

Captains earn new awards at 50 Hours Flown, 1500 Hours Flown, 2000 Hours Flown, and 3000 Hours Flown.

Captains who choose to fly large numbers of ferry flights now earn special awards based on the percent of ferry flights versus total flights.

Captains with a high point level who make ferry on occasion will see an increase in points earned - the base point level for a ferry flight is now the minimum of the base points per level -or- the Captain's current average point level.

The option BACKUPAFTER now has three values. 0 = Backup company log before updating the log. (Default) 1 = Backup company log after updating. 2 = Backup company log before and after updating.

Captains who use FSGRW weather will notice that flights with a cruise level below FL260 will see "altitude bands" favoring lower altitudes. Flights above that level will see a wider distribution of "altitude bands."

Work is underway to allow VA exporting of flight to use https / Port 443. To enable this for your VA, open your \Config\VADefault.cfg file and add/edit this line: PORT=443

Destination Runway Lengths required for Scheduled Flights are now factored at 95% of normal Length. This percentage can be changed from 85% to 100% by use of the RUNWAY_FACTOR_FOR_SCHEDULE option.

The Administrator's ETE & Fuel text boxes have been re-enabled and can be used to override values. You must enter the values you desire and then press and hold a SHIFT key while you click on the "Recalculate" button. If you later change your mind and want to accept the ACME values, you will need to click on the "Recalculate" button without using the SHIFT key.

Captains who successfully make Cabin Emergency Landings are now eligible for special awards.

Airport surface exceptions (which are listed in both the "exceptions.cfg" file and the "airport_surface_overrides.cfg" file) are now effective retroactively, instead of only taking effect after they've been added. So check your grades and Quality Points....

If you are using GSX and you release the parking brake or start an engine, all services which would be "available" would be considered as "not available." Services which have "completed" or were "bypassed" would be unaffected. Correcting the error would have those services be seen as "available" again.

If you have GSX installed and GSX pushback is possible, the indicator on the FCDU's Load Complete screen for our pushback is now labeled "ACME PUSHBACK" to avoid any confusion. (There is now also an indicator on that screen that GSX push is also available.)

The ACME pushback system has been reworked. There is now a display of your direct "straight pushback" distance, and then of the turn angle. Unless you have disabled pushback logging, there should be more details logged of each push.

There have been many subtle changes to ground deicing procedures in preparation for future support of off-stand deicing.

If deicing is needed and the departure or destination weather also calls for a gate hold, a request for deicing is now automatically treated as a full gate hold release request. You should receive a message from dispatch during the deicing process indicating this. Furthermore, simple hold releases cannot be requested for the presence of ground ice.

The FO's Welcome can occur up to the aircraft's service altitude (or TOC, whichever comes first).

When in climb or descent, the next PLN waypoint will have the estimated altitude upon reaching it - possibly useful in planning crossing altitudes....

The FCDU's main dispatch screen (#10) can recognize if you and your aircraft can handle both PAX and Cargo flights. If you can, you may be allowed to switch between both types.

If an FCDU screen has more than one page, the Page/Screen indicator in the upper right corner of the display will appear in blue... hopefully highlighting this condition.


Testing Notes on Bugs

Bug #143 - Fuel loader can apply an incorrect amount.

Bug #144 - In isolated areas, weather engine files can be constantly read.

Bug #145 - Min Takeoff and Min Landing Runway values could be confused at times.

Bug #146 - Airports with no parking will cause G5 to be constantly read.

Bug #151 - Hub Generator not including the hub airport in schedule flights.

Bug #153 - Transition Altitude of Destination and Alternate not always considered.

Bug #154 - FO Aircraft Overrides not loading.

Bug #157 - PAX Flight loads do not adhere to "Load Factors".

Bug #158 - Pre-flight parking assignments are sometimes not remembered by the FCDU.

Bug #159 - FO Announcement requests could be made at inappropriate times.

Bug #160 - In-flight Dispatch Release may not use correct waypoint altitudes.

Bug #162 - Reconciliation choice of "Aircraft" does not work.

Bug #163 - FS9 fuel autoload does not load fuel.

Bug #165 - Airline node list does not always affect Schedule or Charter destination.

Bug #166 - FS9 Dates are off by a day.

Bug #172 - ACARS warns of "Invalid configuration" if no load map is found.

Bug #181 - Multiple presses of PLN and EMER keys would disable RETURN choice.

Bug #183 - Landing alert for FAs can be given just after takeoff.

Bug #185 - Passenger Satisfaction value was tied to all flights.

Bug #188 - Alternate airports on subsequent legs may inherit the initial leg's alternate airport.

Bug #189 - Using external Ground Service pushback would mute FA Safety Announcement, which now should occur only after pushback / stand deicing.


Testing Notes on Interface Changes

There is a new built-in interface for David Maltby's BAC One Eleven freeware series (200, 400, 475, 500, and 510). (It corrects the faux "flameout" calls and adds some functionality.)

There is a new built-in interface for the FSDS Hawker Siddeley 748 freeware - as detailed in the Airplane Configuration How-To document.

There is a new built-in interface for the Flysim Cessna 441.

There is a new built-in interface for the Flysim Lear 35.

There is a new built-in interface for the Virtualcol ATR Series Pack.

There is a new built-in interface for the Virtualcol SAAB Regional Pack.

There is a new built-in interface for the Carenado B1900D.

There is a new built-in interface for the Carenado Cessna F406.

There is a new built-in interface for the Carenado PC-12.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
CHANGELIST FOR FSCAPTAIN 1.7.1

==============================
Testing Notes on Changed Items
==============================

The routine to build a new aircraft configuration file (and load map file) is now aware of aircraft with floats as well as aircraft which are amphibious.

Alpha, Beta and Release Candidate versions will have their build date/time logged as well as presented in the Windows title bar for the Administrator and FCDU.EXE.



=====================
Testing Notes on Bugs
=====================

Bug #134 - Airports below sea-level are presented as being in the lower stratosphere.

Bug #135 - Appeals Dialog will not re-open after a successful Appeal.

Bug #136 - ETE times can be amazingly incorrect.




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=




CHANGELIST FOR FSCAPTAIN 1.7.0



=====================
General Testing Notes
=====================

FSCaptain now uses the Visual C++ 2013 RTL libraries which earlier testing has shown that not all Captains have. To check, you should run the Administrator and see if it crashes. If it does, you most likely need the Microsoft VC++ 2013 libraries (the x86 version we believe) which you can download from here: http://www.microsoft.com/en-us/download/details.aspx?id=40784 - once there, just click Download and then select the x86 version. (And if that doesn't allow you to run FSCaptain, go back and download the x64 version from the same page.)

There have been changes to the format of the FSCaptain Aircraft Configuration files to better support non-wheeled aircraft, as well as other per-aircraft functions. Care has been taken to ensure that older format files will be supported, although we are offering converted versions of our pre-1.7.0 files. We strongly urge Captains to move to the new format (there are only small changes, but they are significant).

Over time, errors have crept into the \FSCaptain\Config\Items.cfg file which mostly affect Live items, Medical items, and items which have an affinity to a region. If you have not made any changes to your Items.cfg file, then you may ignore the remainder of this item. If you have made changes to your \FSCaptain\Config\Items.cfg file, then before installation, make a copy of your current \FSCaptain\Config\Items.cfg file and after installation follow the Items.cfg field settings to update your files. (Or email your original Items.cfg file to us and we would be happy to do that for you.)

Each new version of FSCaptain treats "Save files" from earlier formats as incompatible. Please be sure to complete all saved flights before upgrading to this version!

Please note changes to the SceneryScanner (detailed later) as well as changes to how FSCaptain handles "File Selector" calls. If you come across any file such as an airline configuration file or a METAR file that doesn't load properly, please file a report (complete with logs) in email.

If you have participated in the 1.6.3 BETA program and have made changes to any of the newer airport.cfg support files - closed_user.txt, customs_user.txt, military.cfg, new-id_user.txt, or private_user.txt - you will need to go to the Administrator and run the Rebuild Airport Database. You would not need to have it run Makerwys.exe beforehand unless you have made changes to your simulator's scenery.cfg file.

Makerwys.exe Version 4.6.9.2 is included - this version outputs "helipads.csv" which FSCaptain reads.

Copies of the FSCaptain gauges as well as the FS9 version of the FSCaptain.dll are included in new folders inside the \FSCaptain\ installation directory. If Captains restore their FSCaptain folder in the future they could also restore the \Gauges\ and \Modules\ files from backup.



=================
Development Notes
=================

FSCaptain 1.7.0 uses a new gaugesound.dll - it plays through the simulator, not Windows.
Advantage - will offer better performance, "panning" for future voicepacks, as well as layered tracks.
Disadvantage - will need FS9 or FSX to be "the foreground window" to hear sound.

If you have an existing career that you wish to retain, it is strongly advised that you make a backup copy of the entire \FSCaptain\ folder. Use Windows Explorer to "copy" and then "paste" the \FSCaptain\ folder in a safe place (perhaps your Desktop, where it will be readily visible).

If you are updating from a previous version, test things with short flights at first to ensure things are working for you. There's no need to book a multi-hour flight to only find out that it wasn't recorded [for some damnable technical reason]!

FSCaptain 1.7.0 uses a new airport database that is incompatible with earlier versions. The new database denotes "ground only," "ground & water," "water only," "helicopter only," "private-use," "closed" airports, as well as airports which have published that they have no Customs services. A future change will support "re-IDed" airports. (An airport which has changed its ID since circa 2006.)

FSCaptain 1.7.0 uses a new utility program called "SceneryScanner" to build this new database. This program targets the .Net Framework version 3.5 (which is approximately the age of FSX), so you should check that your PC is capable of running applications such as this. (If not, please email travis@fscaptain.net with your system's specifications!)

The Administrator will auto-rebuild the Airports Database if it cannot find a database that's properly configured. This is why we recommend that the first thing that all Captains do after upgrading, is to run the FSCaptain Administrator program. If the Administrator detects a missing (or incompatible) airport database, it will ask to run a complete rescan of your active sceneries and to then build a new database.

SceneryScanner will also output extra files that aren't used for FSCaptain, but which may be of interest to Captains with large scenery collections. These files are: a listing of all scenery layers with airports, a listing of all scenery layers without airports, and a KML file containing airport facility data which can be viewed in Google Earth or any other KML client.



==================
After Installation
==================

Once you've installed the new files, run the Admin.exe program. If it detects a missing or incompatible airport database it will ask to build a new one. Click Ok and Makerwys.exe will run, taking a few moments to build data files, and you will be prompted to close the program when it has finished. At that point, SceneryScanner will run in a "Command Prompt" window. SceneryScanner will automatically close when it is finished.



===================================
Testing Notes on New Optional Items
===================================

There are several new features that require each Captain to modify various options or configuration files to enable the feature in question. You may review the Appendix of the User Guide to see what all options are available. The newer ones are:

Captains can be required to maintain "minimum safe distance from ground" when not in the vicinity of their departure or destination airport. These minimum safe distances will be displayed at the bottom of the current Dispatch Release. Add the line ENABLE_MSD=1 to your options.cfg file.

There is a change in Position Reporting times - a new airline option value allows position reporting intervals to be set from 10 to 70 minutes. The default reporting time will now be 15 minutes, in accordance to proposed r/w changes. This can be changed via the Administrator in the Airlines tab.

A new Hazard Pack option allows brakes to be monitored for abuse. In 1.7.0, engaging the parking brakes while at a groundspeed of over 20kts will fail the brakes and cause gear damage. This can be set via the Administrator in the Options for All Airlines tab / Hazard Pack. This option will expand in future versions.

A new option available in options.cfg will prohibit flights from public-use airports to private-use airports. Flights from private-use airports can always be made to private-use or public-use airports. Add the line RESPECT_PRIVATE_AIRFIELDS=1 to your options.cfg file. The list of private-use airports are maintain in the "private_fsc.txt" and "private_user.txt" files in your \FSCaptain\Config\ folder.

A new option available in options.cfg will prohibit flights to or from airports that have been abandoned (closed) in real life. (We will constantly be working on expanding this list.) Examples of such airports are "NGZ - Alameda Naval Air Station" and "NRC - NASA Crows Landing" both in Northern California. Add the line RESPECT_CLOSED_AIRFIELDS=1 to your options.cfg file. The list of closed airports are maintained in the "closed_fsc.txt" and "closed_user.txt" files in your \FSCaptain\Config\ folder.

A new option will prohibit international flights to airports that are known not to have Customs capabilities. Our dataset for US and Canadian airports is very comprehensive. Our dataset for other airports may lack many airports, and could contain errors. Please bring any such errors to our attention, including any official reference that applies. Add the line RESPECT_CUSTOMS=1 to your options.cfg file to enable this option. The list of airports with known Customs status are maintain in the "customs_fsc.txt" and "customs_user.txt" files in your \FSCaptain\Config\ folder.

New Customs configuration files will allow direct flights from fifteen specific airports to any capable airport in the United States - thanks to the US Customs and Border Protection Preclearance Program. Flying into the Schengen area of Europe is different too - from outside, you must fly to an airport that has active Customs. But once inside the area, you can fly to any capable airport also inside the area!

A new option will prohibit "total system failures" on multi-engine aircraft; this includes electrical, vacuum, hydraulic and pitot systems. Add the line DISABLE_TOTAL_SYSTEM_FAILURES=1 to your options.cfg file to enable this behavior.

The routine used to detect if an aircraft is on a runway has been modified to not run nearly as often as it had. This is believed to be the reason for the spate of recent "FPS drops while taxiing." Add the line RUNWAY_DETECT=0 to your options.cfg file if you want to disable this entirely. Otherwise RUNWAY_DETECT=1 will check once every half-second, RUNWAY_DETECT=2 will check once every second, RUNWAY_DETECT=3 will check once every one-and-a-half seconds, etc.

Captains may choose to silence their FO on some takeoff, climbout and landing callouts. (Mostly v-speed calls and the climbout call to "check the flaps.") However your FO will always caution you to check your flaps if you've not deployed them for takeoff or landing, and to caution you to check your gear before landing. (Those are critical items that your FO's contract will not allow to be silenced.....) These motions-to-silence are available at a "global" level by setting a value in your options.cfg file (DISABLE_FO_TAKEOFF, DISABLE_FO_CLIMBOUT, DISABLE_FO_LANDING), or on a per-aircraft level via the FSCaptain Administrator.

(This is a Windows / Network item.) Captains who use the FCDU.EXE in a remote / networked environment have had to refer to their flight plans via UNC/Network path descriptions rather than local paths. In other words, "\\MY-PC\Users\Me\Documents\" instead of "C:\Users\Me\Documents\". If you add this line to your options.cfg - USE_NETWORK_DOCUMENTS_PATH=1 - the file selector will open already in "UNC" mode.

It is possible that when the FCDU.EXE is running on the same PC as the simulator, the FCDU's window may block FSCaptain audio from being heard (as other windows would if they are topmost.) Adding this line REMOTE_VOICES=1 to your options.cfg file should cause your FCDU.EXE to play FSCaptain audio via the FCDU's window.

In prior versions, Captains whose airlines require Position Reporting needed to make their TOC call within 45 minutes of the start of the ETE clock. This has changed to a period of two Position Reporting periods after takeoff. (So if your Position Reporting interval is every 15 minutes, then you will need to file TOC within 30 minutes of takeoff.) However setting TOC_POLICY=1 in your options.cfg file will change the TOC period to better reflect each aircraft's climb performance measured against the flight's Cruise Altitude - likely reducing the TOC period itself. Whichever policy you choose, the Dispatch Release will advise you of when you will be required to declare TOC.

All aircraft are required to hold enough fuel in reserve for the amount of minutes of flight that constitute a safe amount. Furthermore, aircraft are also required to hold enough fuel to maintain a holding pattern for the amount of minutes that constitute a safe amount. These amounts can be adjusted by the following values in your options.cfg file: RESERVE_FUEL_IN_MINUTES (cannot be less than 30 minutes), HOLDING_FUEL_IN_MINUTES, RESERVE_FUEL_IN_MINUTES_HELI (cannot be less than 20 minutes), HOLDING_FUEL_IN_MINUTES_HELI (usually 0).



==========================
Testing Notes on New Items
==========================

Wheeled aircraft can fly to airports with ground and water runways. Only "water-capable aircraft" can fly to airports with water-only runways. A future change will ensure "water-only aircraft" can only fly to (or from) airports with water runways. Another future change will not allow fixed-wing aircraft to fly to (or from) helicopter-only airports.

Flights to an airport without runways long enough to handle the given aircraft have always been prohibited. In 1.7.0, takeoffs from airports without runways long enough to handle the given aircraft should be given a warning from Dispatch.

Passengers will gasp and scream if you don't fly correctly, but not as often if the PAX have their belts on. :)

Bounced Landings - if your wheels touch down and then you "float" for more than two seconds you will lose any "good landing bonus" that you would otherwise be entitled to. A float of over three seconds will incur a passenger complaint which will cost you points. However if you decide to go-around, the bounce will be forgiven.

Company NOTAMs which are designated as "warning" will be displayed via ACARS. There are three phases for NOTAMs to appear via the ACARS system - DEPARTURE: which will be displayed soon after you go OUT, APPROCH: which will be displayed soon after you are cleared for approach, and ARRIVAL: which will be displayed soon after you touch down at your destination.

Bird Watch - PIREPS of increased bird activity near an airport will be reported as a NOTAM on the Dispatch Release and via ACARS. The issuance of such a NOTAM does not indicate that a bird strike will happen, nor should the lack of a NOTAM indicate that a bird strike will not happen. Such a NOTAM merely indicates the heightened chances of such happening. (To test this, find an airport whose METAR includes " RAE" which indicates that RAin has recently Ended... a good indicator that more birds than usual will be in the area.)

FA Lucy - Lucy is a no-nonsense American English FA. (Please!... don't get on her bad side!)

FA_Regina - Regina is an efficient and multi-lingual FA (English and German).

FO_Peter - Peter's German and currently lives in Canada. That makes for some interesting discussions about beers.

Your aircraft's Center of Gravity value is displayed on the FCDU Information screen.

Your Dispatch Release includes "fuel type times" - the approximate number of minutes that each fuel type (Taxi, Alt Diversion, Holding, etc.) allows.

Your aircraft's left and right flap positions are noted on the Interface screen. This can be used to assist in building SPEEDCALL tables for V1 V2 Vr and Vref speeds.

If an airport has an IATA code (in addition to its ICAO or FAA or TC code) both codes will be displayed on the header of the Dispatch Release (e.g., "FLIGHT 2782 EGLL (LHR) -- KJFK (JFK)").

An as-yet-to-be-implemented feature will allow Captains to refer to airports using IDs that have been updated since the last Microsoft published database of 2006.

The FCDU.exe program will shut itself down if when it initializes it does not detect a flight simulator running - nor an active aircraft.

The FCDU.exe now sports an icon. :)



==============================
Testing Notes on Changed Items
==============================

Multi-leg flights now have variable payloads & manifest items.

Opus TAF is supported.

There is better support for amphibious aircraft. No need to set "parking brakes" if you're on the water. :-)

Military airbases can be specified by ICAO ID in addition to tokens in their name. Use the format ICAO=TheAirportID to make your entries - e.g., ICAO=CYZX

Individual military airfields can have commercial traffic if specified in the military.cfg file by appending ":CIV-MIL" to their ICAO ID. (E.g., ICAO=KMER:CIV-MIL)

Dispatch Releases are updated throughout the flight - the Administrator will write a preliminary release that will not be overwritten, and an "IN" release will be written once going "in," recording OUT OFF ON and IN times, along with messages from Dispatch received during the flight.

In the Administrator, both Captains who have made it to the highest level, as well as Captains who don't have a sufficient score to advance to the next level would see impossible (and/or ludicrous) targets to attain.

Bird strikes can now occur on the takeoff and landing roll, as well as at night and at altitudes above 10000ft - although they would be rare in either of the latter circumstances.

The method used to deem whether an aircraft can appropriately use an airport has been rewritten. Please bring any false flags to our attention with the type of aircraft and its publisher, and the ID of the incorrectly deemed airport along with its publisher.

The functions used to read & decode PLN files have been changed to accommodate PLN files written by REX Essential Plus.

When entering a flight number for a "Specified Details Flight," the Max Flight Number for your airline is better honored.

Offered alternate airport choices now take into account any file-based METAR data, and also are more biased towards having an ILS and Control Tower. Future versions will be able to bias towards airports with published approach procedures.

VA export data now includes some Economic values such as Revenue, Crew Cost, Operations Cost, Profit. There are also other minor tweaks to the Export dialogs & data, most notably that the current version of FSCaptain is noted in the HTTP User-Agent field.

Helicopters are better supported. Airfields with helipads are noted on your flight's Dispatch Release. Improvements will continue in future versions.

Lots of changes to logging. Lots! :-)

"Oil-treated" runways on third-party airports are now considered as "hard surfaces."

Ground ice accumulation from "cold soaked wings" is recognized more effectively.

Payload reconciliation between the manifest and the aircraft should be better recognized.

Nearly all of the existing source code has been overhauled to reduce one possibility of a C++ buffer overrun. There may be other areas that haven't been touched, so be alert for the possibility of overruns still happening.

FSCaptain's text configuration files have always had a restriction that the "last line" of the text file needed to end with a Carriage Return / Line Feed. This should no longer be the case.

If your Ground Services add-on crashes or otherwise becomes unresponsive while you're waiting for a service to complete, you can go to the main FCDU menu (the one that the Save and Restore options are called from) and select the RESET GND SVCS option. That should "reset" the FCDU's connection with your ground services.

In addition to marking the Landing Lights and Engine de-icing equipment on an aircraft class as INOP, you can now mark the Pressurization system, the Nav Lights, the Wing de-icing equipment, and the Barometric Altimeter as INOP.

The altitude where your FO will caution about landing "gear up" has been elevated, and is now aircraft size dependent.

The standard external weather configuration file has been updated to account for different installations of Active Sky Next and of Opus.

A new version of SceneryScanner is in use. It outputs an AirportSceneries file with more information than is used in FSCaptain - mostly Scenery Area & BGL name data - plus the format of the Customs data files have changed to allow for Customs exceptions and Customs preclearance.

When in offline mode, Minimum Safe Distances are ignored.

When airborne, the Information screen no longer points you to the closest parking spot. Instead your current g-force value is displayed.

The Dispatch Release will note that unpressurized aircraft that are planned to be flown above 10000ft will need to have supplemental oxygen onboard. Unpressurized aircraft that are planned to be flown at or above 12000ft will have the "time at unsafe altitude" noted. Your PAX and live cargo will suffer if you linger too long without oxygen, just as they would have done yesterday or last year. Future versions of FSCaptain will simulate supplemental oxygen for those airlines who choose to do so... at a cost to your and your airline's profit margin!

The time period to declare Top Of Climb has changed. Previously it was calculated as 45 minutes from the start of the ETE clock. Now it is the minimum of 30 minutes (or two Position Report durations) since takeoff. The correct value is noted in the Dispatch Release.

The maximum number of "Wind waypoints" has been increased from 16 to 192. This allows a much broader view of upper level wind conditions and their impact on your ETEs.

Alternate airports are now listed in the flight plan section of the Dispatch Release.

The Administrator will now allow you to select any parking spot at your Destination airport, although it will offer Dispatch's suggested spot given the current flight type and aircraft. The list of parking spots includes Type [RAMP, GATE, etc.] Number, (radius in meters), and special codes [A=Airline Code Match, C=Cargo, O=cOmbat, M=Military]. It is up to each Captain's skill to force their aircraft into the chosen parking spot.

The parking director has been modified to give priority to non-military spots, and if failing to find any suitable for the current aircraft and flight type, military spots will be considered.

The rate of climb/dive for aircraft before PAX will complain has been changed. Medium and larger turbojets are limited to rates of 6000fpm. Smaller turbojets, at 5000fpm. Medium and larger turboprops at 4500fpm. Smaller turboprops, at 3500fpm. Other medium and larger aircraft will be flagged beyond 3000fpm. Other smaller aircraft, at 2000fpm.

Piston and Heli-Turbine aircraft are now susceptible to Chilled Precipitation Ingestion and are liable for engine flameout. They need to have propeller & carb heat applied (or if that's not available, to have engine anti-ice deemed INOP).

Changes to how payloads are determined should result in more "fuller" flights.

The Aircraft and Load Map tabs in the Administrator now report if a configuration file is targeted for a single aircraft's registration ID.

The Dispatch Release will now note Takeoff and Landing risks, as well as any expected Service, and need for refueling stops.

PAX service rules have changed. Meal service will begin with an initial Snack followed a half-hour later by the Meal, and subsequent Snacks each hour thereafter. Plus what was "Optional Snack Service" can be "Optional Meal Service" if the duration of the flight (calculated against the number of PAX and the number of Attendants) would warrant such.

The paths to the Flight Plan files have been standardized for each simulator. In addition, if you designate a different folder (perhaps your weather engine's PLN folder) then whenever you next look for a PLN file, that will be your default PLN folder.

Certain controls in the Administrator have been disabled when run from inside the simulator.

FSCaptain is now aware of Prepar3D Version 3.



==================================
Testing Notes on Interface Changes
==================================

There is a new built-in interface for the Carenado Citation.

There is a new built-in interface for the Digital Aviation Fokker.

There is a new built-in interface for the Flight One ATR-72.

The GSX interface is no longer recognized while the aircraft is on water. (!)

There are tweaks to the Aerosoft Twin Otter Extended interface, and to the PMDG 737 & 777 interfaces.

The Majestic Q-400 now reports cabin temperature. Removing the checks on the brake temp and vspeeds seem to have quelled the "freezing" of Beta 1.

There is a correction and an addition to the QualityWings BA46 interface.

There is a correction to the CaptainSim 707 interface.

The Carenado C208EX interface now reports galley power (well, maybe coffeepot power), and window heat. Plus the interface will set the pitot flags, chocks, and tail support when you're parked (and haven't declared an emergency)... and remove them when you start your engines....

There is a tweak to the CaptainSim 727 interface to support v2.6.



=====================
Testing Notes on Bugs
=====================

(The gap between "Bug numbers" do not indicate there are un-fixed bugs. Rather those unlisted items are new features and other issues that are not bug-related.)

Bug 12 - Tweaks to runway contamination declarations.

Bug 18 - If the airline's "economy file" is open when the Administrator starts, the Administrator will report a "loss of 0."

Bug 22 - Add type checking to Gauge and EXE save files. Trying to load a save file in the other type of FCDU will generate an error message.

Bug 27 - The Administrator may fail to write an airline's first flight to the log file.

Bug 29 - PAX flights with zero passengers are possible.

Bug 41 - Distance and ETE calculations were not taking all waypoints into account.

Bug 42 - PMDG 737 cabin temps are not being properly reported.

Bug 47 - Errant Pushback calls that force OUT to be called at improper times and which reset flights (!).

Bug 49 - Revising any item in a PAX flight in the FCDU will force Service to be set to NONE.

Bug 55 - Winds Aloft Screen (#44) had problems displaying the speed adjustment.

Bug 56 - Leading or trailing whitespace on the license key line would cause the license check to fail.

Bug 60 - Flight Attendants always responded positively to a Start Service request, even if they couldn't start a service.

Bug 64 - Icing Pirep was falsely reported while on the ground.

Bug 65 - Safety announcement was not called after pushback or after de-icing.

Bug 67 - Profit calculation does not always consider PAX class.

Bug 74 - CTD on startup in FS9 & FSX.

Bug 79 - Admin fails to update dll.xml if FSCaptain not found.

Bug 80 - Looping sounds (boarding, pushback, de-icing) fail to stop when commanded.

Bug 84 - VA-exported flights not always logged as "Sent."

Bug 89 - Flight Attendant does not perform safety briefing after pushback.

Bug 92 - First Officer constantly repeats "Hard landing" audio.

Bug 95 - Substituted aircraft can have an incorrect load map.

Bug 103 - False "Gear Up" crashes with fixed gear aircraft. (Hello Islander Captains!)

Bug 108 - Minor tweaks to the METAR decoder.

Bug 109 - Emergencies not always recorded properly.

Bug 110 - Alternate airport's name not updated in Administrator.

Bug 112 - Dispatch not copied to the kneeboard when flight begins in FCDU.

Bug 113 - Ground Icing Rate of Change not calculated properly.

Bug 117 - Nearby airports not always found at FCDU start-up.

Bug 119 - Ghost FO makes comments.

Bug 124 - Fueler could try to overload a/c.

Bug 125 - Administrator could crash when scanning the aircraft directory.

Bug 126 - Faux "go arounds" due to complex terrain altitude on approach - or flying in a chopper.

Bug 127 - Some weather files not being read under certain circumstances.

Bug 130 - Flights can go OUT while not being recognized as such.



REVISION HISTORY
----------------



These enhancements were included with version 1.6.2:
---------------------------------------------------

- A new button on the FCDU, 'PLN', will allow you to access the waypoints of your flight plan, if and only if you planned your flight through the Administrator and loaded a flight plan in that process. On the view window, you can choose to change the active flight plan.


These problems were fixed in 1.6.2:
----------------------------------

ID#0327: Flight Attendant sometimes says safety briefing twice.
ID#0328: First Officer never compliments the Captain on a good landing.
ID#0329: Runways are too often considered to be contaminated.


These enhancements were included with version 1.6.1:
----------------------------------------------------

- FScaptain is now compatible with the FSX Steam Edition.

- More complete integration with GSX (Ground Services X from FS Dream Team). FSCaptain now recognizes the states of Catering, Fueling and De-Icing services. If you call GSX Catering or Fueling via the GSX menu, you must wait until their service has completed before you can being the FSCaptain load process. If your aircraft requires De-Icing, and if GSX offers their services to your aircraft, FSCaptain will give you an estimated HOT.

- A new option is available on the Aircraft Configuration: Maximum Takeoff Weight. Previously this was always Maximum Gross Weight. If omitted (less than 1) in the new option the default will be Maximum Gross Weight. But if specified it will be used instead. This cannot be less than the Landing Weight.

- FSCaptain now supports helicopters with a new option on the Aircraft configuration page of the Administrator.

- More variation in load numbers for flights using the Load Factor calculation, partly calculated based on size of departure and destination airports.

- A new option is available in Options.cfg: ENABLEOFFLINEFAULT. By default it is zero, which is the previous functionality. But set it to 1 and the FSCaptain random mechanical fault generator will work when you have the FCDU in Offline mode.

- A new built-in interface is provided for the Captain Sim L-1011.

- 'Active Frost' has been made less aggressive via an updated ice.cfg file.

- Runway Contamination can be inferred from an airport's SNOWTAM code within their METAR. Your Dispatch Release will indicate your Departure and Destination Airport's Runway status using METAR-derived data. (Which can be out of date, so you should always check with your company's Dispatch via the FCDU during your flight.)

- All FSCaptain options (along with either the default setting, or a Captain's own setting) are written to a file named options_current.cfg. Captains may - on their own prerogative - copy the contents from options_current.cfg to options.cfg. Doing so will not change a Captain's settings. It will only allow each Captain to see the full set of choices that are available.

- All relevant settings from the Options, Profile, Current Airline, and Current Aircraft will be written to the FCDU log at the start of each session. (The ADMIN log will contain details of all Currently Available Aircraft.) We feel this should assist in sorting out many issues. If you are not experiencing any issues and wish to not write these values out, the following options will suppress the writing:

DONT_DISPLAY_OPTIONS=0 ; 1 = Do not log option values (this file)
DONT_DISPLAY_AIRCRAFT=0 ; 1 = Do not log aircraft values
DONT_DISPLAY_AIRLINE=0 ; 1 = Do not log airline values

However, leaving these options in their default state of "off" (0) will better ensure that a future diagnosis could be completed in a shorter timeframe.

- Your Dispatch Release will now additionally list your flightplan in "ATS format." An option in the options.cfg file allows you to explicitly include the "DCT" token for direct waypoint connections:

EXPLICIT_DCT_IN_ATS=0 ; 1 = 'DCT' will be explicitly written to the ATS for each 'direct' waypoint


These problems were fixed in 1.6.1:
-----------------------------------

ID#0307: Messages truncated in Virtual Airline Export Window.
ID#0309: Scheduled flights to small airfields (actually very short flights) never assigned.
ID#0311: Coolsky DC-9 Rate of Climb and Window Heat not working.
ID#0312: Conversion from pounds to KG not always correct.
ID#0313: The First Officer mumbles on about icing hazards after the airplane has landed.
ID#0314: On the Arrival page the DETAILS and STATS selections do not work.
ID#0315: "Reason for rejection" list in Administrator does not list correct reason.
ID#0317: When no external weather is configured Flight Dispatch says Wx data is very, very old.
ID#0318: Max extra cargo capacity is negative.
ID#0319: Administrator planner will not allow access to the last leg of a multi-leg flight.
ID#0320: Administrator can't handle multi-leg flights with the same destination listed twice.
ID#0321: Administrator reports "Your chosen altitude is too high for that distance" without considering airport altitudes.
ID#0323: FO warns about belts not being on even if airplane has no belts in config.
ID#0324: Specify Flight Details allows flights to the Departure airport.
ID#0325: External FCDU limits payload stations to 160 rather than the 320 of the gauge version.
ID#0326: Seaplane bases always have a runway length of zero making them unusable.



These enhancements were included with version 1.6.0:
----------------------------------------------------

- A prototype "Economic Mode" is under development in this version. This is the first step in the development of a new product that will accurately and realistically simulate the operation of an airline and all FSCaptains are invited to participate in the testing. Preliminary documentation of these new options is in your FSCaptain\Documentation folder in a file named "EconomicMode.pdf." Do know that certain aspects of this can change before it's officially rolled out in a future version of FSCaptain. If you have any questions, comments, praise or criticism, either email us or visit our public forum and let us know!!

- Rules concerning transition altitude penalties have been relaxed, you now have to be over 2000 feet above transition altitude and with an altimeter setting over 10 millibars over/under standard to be charged with the penalty.

- All transition altitude values are included on the Dispatch Release, not just non-18000ft values.

- Older XML Interface files for aircraft with internal interfaces will be ignored - this feature ensures that only XML Interface files which are newer than internal interfaces will be processed. (The status is noted in your FCDU logs if you're unsure.)

- FCDU logging of many events & items has been increased. If you notice any issue with a flight, we strongly suggest that you send us the FCDU logs for the affected flights with all logging items enabled. Likewise if you have problems with the Administrator, send us the ADMIN logs for the affected sessions with all logging items enabled. (See NEW OPTION.CFG ITEMS below for details.)

- More and varied cargo items will be provided, depending on your aircraft size, and departure location. (See "NEW CARGO ITEMS" below for more information.)

- Administrator logging of events & items has been increased. If you notice any issue with setting up a flight with the Administrator, we strongly suggest that you send us the ADMIN logs for the affected flights with all logging items enabled.

- When first clicking on the "Airline Definitions" tab in each session within the Administrator, your current Airline will be pre-selected for you. If you change your Airline during an Administrator session, the selected Airline on the "Airline Definitions" tab will not change.

- The FCDU now sports a new key - EMER. This will allow direct access to the Emergency Declaration screen (where the Captain must still confirm that declaration).

- The Administrator's Flight Dispatch list now displays the bearing from the Departure airport to each Destination (in degrees True).

- The FCDU recognizes the pushback process from FSDreamTeam's GSX utility. When your ACARS has you Cleared for Departure, you can use the GSX menu to perform your pushback. If you use GSX as your pushback engine, your ETE clock will not start until the GSX ground crew has fully cleared you and wished you a good flight. This feature requires you to be running FSDreamTeam GSX Version 1.9.0 or greater.

In future versions of FSCaptain, we intend to offer more integration with other Ground Services, eventually culminating in a combined and coherent environment that supports proper "turnarounds."



//// NEW CARGO ITEMS

There is a file in the \FSCaptain\Config\ folder with the name of "NewItems.cfg". It is the original "Items.cfg" file with several new and special items added. If you have not changed your "Items.cfg" file, then you can rename "NewItems.cfg" to "Items.cfg" and enjoy the new cargo items to carry.

However if you have changed your "Items.cfg" file, then you can locate the commented lines in "NewItems.cfg" and copy them to your "Items.cfg"



//// NEW OPTION.CFG ITEMS

- Logging of certain events can be disabled. If you are not having problems and want to reduce the size of your FCDU/ADMIN log files, you can set these values in your OPTIONS.CFG file:

DISABLE_LOG_LOADING=1 ; 1 = Disables logging of ACARS aircraft loading events (fuel & payload)
DISABLE_LOG_WX=1 ; 1 = Disables logging of WX data
DISABLE_LOG_SAVEFILE=1 ; 1 = Disables logging of FSCaptain "Save Flight" (and "Restore Flight") events
DISABLE_LOG_SEARCH=1 ; 1 = Disables logging of Administrator Flight Search events
DISABLE_LOG_STAGE=1 ; 1 = Disables logging of Flight Stage Change events (Loading, OUT, OFF, ON, IN, etc.)
DISABLE_LOG_PUSHBACK=1 ; 1 = Disables logging of the ACARS Pushback stages (stages range from 1 to 8)
DISABLE_LOG_AUDIO=1 ; 1 = Disables logging of audio file loading and playback events


If you do not include these items, or if you set their value to "0," then the accompanying issues will be logged.

- For Captains who use PLN files to plot their flights, the FCDU tracking of the "distance to the next waypoint" would advance when the flight reached a 5NM distance from the current waypoint. For those Captains who fly very accurately, it is now possible to change that "waypoint detection radius" by setting this value in your OPTIONS.CFG file:

WAYPOINT_DISTANCE=5 ; NM distance from "next waypoint" to advance waypoint check (the minimum = 1, and the default = 5)

- For Captains who have small, yet detailed flight plans they like to follow, and who have an upper level winds source, you can create up to 16 "wind points" for each of your flights by setting this value:

WINDGAP_MAX=3 ; NM distance to exclude "wind points" if you have 16 or less waypoints (including DEP and ARR airports) in your flight plan.

- For Captains who want to fly with "strict" ground-deicing protocols, setting this value to 1 will apply a weather hold at departure with a minimal amount (10 lbs) of ground ice:

STRICT_DEICE_PROCS=1 ; 1 = Ground Hold begins with minimal detected ice (10 lbs).

- This will suppress the "Environmental value" of Ice Weight equal to or less than the stated value:

IGNORE_ICE=5 ; Minimum weight of ice on aircraft surface to trigger environmental messages (default = 0). If the value here is "5" then any Ice Weight of 5 or less will not appear as an environmental message.



//// New internal interfaces are supplied for these aircraft:

+ Aerosoft Twin Otter Extended
+ CaptainSim 757 / 767
+ feelThere EMB Series
+ feelThere ERJ Series
+ feelThere Phenom 100
+ iFly 747 V2
+ Majestic Q-400
+ PMDG 777
+ QualityWings BA46 (146 & Avro)
+ QualityWings 757
+ RAZBAM Metroliner III
+ RealAir Duke Turbine


These problems were fixed in 1.6.0:
-----------------------------------

ID#0246: "Test the Data Source" does not parse METAR information.
ID#0272: Minor touchups for Administrator tabs.
ID#0275: On subsequent leg of a multi-leg flight fuel is always zero.
ID#0277: Crash to Desktop in the Administrator when clicking on Weather Options.
ID#0282: Maximum Fuel Value in the Aircraft Characteristics is increased to 500,000.
ID#0283: Aircraft with blanks in their ATC_MODEL will now work as if the blanks were underscores. If you have configurations that contained blanks generated from previous versions of FSCaptain, rename them to change the blanks to underscores. There is a limit of 16 characters for the ATC_MODEL, anything past 16 characters will be truncated.
ID#0284: Path Separator can be missing. (This could cause the Dispatch Release to not be copied to the kneeboard, and for the ACARS to fail to find a parking spot.)
ID#0285: The airport you were last located at is tracked more intelligently.
ID#0286: Flight Plan in Dispatch Release can show unexpected altitudes & speeds.
ID#0287: Dispatchers now have daily shifts. (ACME's Iron Man in the booth - J B SMITH - now has a relief staff to give him some time off of work.)
ID#0288: Administrator Manifests never change after checking for new flights.
ID#0289: Administrator Load Maps truncates "Type" value when saving.
ID#0290: Administrator Load Map requires cargo to accommodate 50 lbs of baggage per PAX. The value has been reduced, and is less so for smaller aircraft.
ID#0291: PAXCOM settings did not always reflect 'smooth flight' or 'nice landing'. An automatic fix is included so that the next time you run the Admin for an airline, these scores will be updated and your overall score may improve.
ID#0292: Administrator will sometimes download weather when it has access to a valid local weather file.
ID#0293: Eliminate phantom "Gear damage" reports introduced in earlier 1.5.1 Beta versions.
ID#0294: "Nearest Airport" Bearing & Distance is incorrect.
ID#0295: Incorrect fuel weight conversion to liters.
ID#0296: Communicator allows orders to non-existent cabin crew.
ID#0297: There is no issue 0297 - duplicate.
ID#0298: Military airports can appear in schedules when not desired to.
ID#0299: There is no issue 0299 - duplicate.
ID#0300: Hypoxia threat not verbalized by FO.
ID#0301: Select Flight Details only allows 5-digits for Cargo Weight.
ID#0302: Details from Overrides configuration files not always used.
ID#0303: "Contaminated runways" aren't contaminated enough.
ID#0304: REX Upper Level Winds absent from Dispatch Release.
ID#0305: Administrator can crash when checking "Unlisted Types" of aircraft.
ID#0308: Light GA aircraft are assigned to gates for larger aircraft.


These enhancements were included with version 1.5.0:
-----------------------------------------------------


- External FCDU as a Windows application. The FSCaptain\bin folder now contains a new program, FCDU.exe, which you can place a shortcut on your desktop or start menu by using standard Windows procedures (navigate to the FCDU.exe program, right click on it, and select "Pin to Start Menu"). Executing this program will give you an FCDU that runs on your desktop outside of FSX. It operates exactly the same, and has exactly the same capabilities and limitations, as the gauge one. It is not necessary to install anything, or make any modifications to, in an aircraft's panel.cfg or any other configuration file to use this FCDU with the airplane. It is truly "out of the box". This external FCDU can also be run on another windows based PC by configuring SimConnect on the other PC to connect to the FSX machine.

- A major addition to the Hazard Package is a complete, detailed, realistic simulation of aircraft structural icing both on the ground and in the air. Turn on this option (it is off by default) on the Weather Options dialog of the Options for All Airlines where the other hazard options are located. Be sure to read the manual carefully because now, as never before, icing can be extremely nasty and ruin your day very quickly if you ignore it. It is a deadly enemy; just like in real life in wintertime! The applies to ALL aircraft on an FSCaptain flight, not only jets.

- FSCaptain is compatible with Prepar3d version 2. Simply point your installation folder to the root folder of Prepar3d. Earlier versions of Prepar3d will work also, but it may be necessary to install FSCaptain into the dll.xml file manually. We recommend version 2.

- FSCaptain is now compatible with FS Global Real Weather and REX Essential Plus as external weather sources. Compatibility with Opus and FSrealWX has been enhanced.

- If you are using an external weather source as your primary source, when you request weather information (either online or offline) and none is found for the airport you are looking for, a search of surrounding airports is made and if one is found you are given that Metar and TAF but with the addendum (sample) [FROM KGVL 22NM NE]. You can limit the range of this feature with the WEATHERRANGE=XX option in Options.cfg, the default is 40 miles.

- A new item on the airline definition, in the middle left, is "Load Factor". Leaving this zero (the default) does not change the random way FSCaptain computes loads for your flights. But if you put a factor in here, from 1 to 100, your flight loads (PAX and/or cargo) will be near this percentage, give or take a random factor per flight. If you place a -1 in this field, your flight loads will be computed based on your reputation, a number from zero to +99, computed by the way you fly as defined by the events in your logbook. See the User's Guide for a precise definition of how each event influences your reputation. Also considered in this load factor computation is a base percent, obtained from the [airline]_nodes.txt file (if there is one for your airline) plus an analysis of the route with flights to or from larger markets tending to make for larger load factors. When you view your available flights and have not left this zero for the default you'll be shown your average load factor for the flights listed.

- To aid in pilots understanding why a particular aircraft they have is not listed as selectable in the Dispatch list, you can click on and then on List Flights and a list of all rejected types and the reason they were rejected will appear in a dialog box.

- Selection of charter flight destinations can now be limited to the airline's node list (if there is one) with the entry in Options.cfg of the line "PERCENTNODE=nn" where nn is the percentage of time when the selection will be limited, valid values are 1 to 100. The default is 70 percent, if nodes are present.

- When assigned parking spaces are found to be occupied by an AI aircraft on landing, there is now an option to delete the offending AI aircraft rather than re-assign the gate. The option to trigger this is an entry in Options.cfg of PERCENTZAP=nn where nn is the percentage of time when the AI will be removed rather than the gate re-assigned, valid values are 1 to 100. Default is 70 which means most of the time the AI will be cleared for you, only 30 percent of the time will you be assigned another gate. This feature will only be effective if you have the FSUIPC utility installed.

- The sound system of FSCaptain has been substantially revamped. The visible result is a new dialog in the Administrator that will allow you to configure your sound (voices and music). To access this, go to the Options for All Airlines tab and click on the "Sound Config" button in the ACARS configuration section on the lower right quadrant of the page. A new option, "Monitor PA" will allow you to decide if you want to listen to your Flight Attendants making public announcements to the passengers or not. It is checked by default to preserve the functionality of previous versions, where this wasn't an option. If you check this you will still hear all FA communications with the cockpit over the intercom, but not the PA announcements (except, possibly, faintly through the door.)

- A new WARNINGS option appears on the weather selection page. If you see this it means there are significant weather hazards along your projected flight path. Click on RLSK1 to read the warning(s) and pay attention -- nothing is listed here that can be ignored!

- A new option in Options.cfg is FLIGHTGAP. Giving a number here will make sure the next assigned charter flight will be that number up from the last one, instead of the current random 1 through 20 assignment. FLIGHTGAP=1 means your charter numbers will increase by exactly 1 each time.

- A new option in Options.cfg is SHOWENVIRONMENT. If this is set to 1, then certain environment variables that in the real world would be seen or felt will be monitored and if abnormal a message will be shown on the FCDU under the header. This message will not be present if all are within normal range. The environment variables that are monitored are ice weight, cabin temperature, and cabin rate of climb and pressure altitude. The color of the message indicates severity: Cyan = abnormal but not dangerous; Yellow = Caution, potential danger; Red = immediate danger. Ice is shown in weight, temperature in degrees C, and rate/altitude in FPM and feet, respectively.

- Logs are now stored in the folder FSCaptain\Data\Logs and are not erased, each new log has a date and timestamp as part of the file name. If you wish you can delete the files from this folder anytime that you aren't running the Admin or the FCOM/FCDU, but please DO NOT delete the Logs folder itself.

- The interfaces for the Majestic Q-400, MilViz 737-200, Carenado C208B, and Carenado King Air B200 are now incorporated into the standard product and an internal interface is no longer required for these add-ons. We recommend you remove any external interface xml code you've installed into the panel.cfg for these airplanes.


These problems were fixed in 1.5.0:
------------------------------------

ID#0222: Scheduled arrival time calculation is incorrect for certain flights
ID#0230: Absurd numbers for cargo weight in flight scheduled in the FCDU using Select Destination.
ID#0231: Changing the airline maintenance option clears some other options buttons.
ID#0232: STAT key cannot be used on a ferry flight to get basic numbers at the cleared for departure page.
ID#0233: Switching flight types on Select Destination page does not result in PAX flight.
ID#0234: Use of the 'Get Assignment' feature could result in an overloaded flight generated.
ID#0235: Sounds/voice/music cannot be heard on some systems.
ID#0236: Maximum PAX in generated flights never is maximum.
ID#0237: External 2 fuel tank priority is always zero. Load Maps.
ID#0238: Specified flight number is ignored for a ferry flight in Admin. Not FCDU.
ID#0239: The DISABLEPROTECT=0 option does not turn off the ground protect system.
ID#0240: FSrealWx METAR format file does not parse correctly.
ID#0243: Remote FCDU has "divide by zero" exceptions.
ID#0245: Weather Source Name limited to 7 characters.
ID#0248: Load Maps - when Right Aux fuel is set to a priority other than 1, it reverts to 1 on the save.
ID#0249: Appeals are not being taken into consideration in "Areas of Concern" comments.
ID#0250: No Online Weather data in Admin.
ID#0253: Page displays for the Checkride (ID 50) are mis-formatted.
ID#0256: If you erase a flight from the log immediately after changing airlines the updated log will write to the OLD airline.
ID#0259: Tiny aircraft (less than 500LB fuel capacity) do not compute accurate fuel estimates.
ID#0261: When using Internet weather source Admin does redundant downloads.
ID#0263: The 'display fault code' feature doesn't work in the FCDU.
ID#0264: The recorded fuel burn numbers are incorrect for Ferry flights.
ID#0265: Weather advisory from dispatch sometimes too large to fit on one line in message page.
ID#0266: External FCDU closes without an "Are you sure?" message under certain conditions.
ID#0267: FO warning about gear up when landing on a fixed-gear airplane.
ID#0268: Holding pattern is being detected on a reverse course during climb phase.
ID#0270: In Admin if you specify details after canceling a previous flight list, the details are ignored.
ID#0271: In Admin the Specify Details and Get Assignment buttons are not disabled after selecting a flight.


These enhancements were included with version 1.4.5:
-----------------------------------------------------

- Support for many popular add-ons are now built-in as internal interfaces in the FCDU. Automatic support now includes the PMDG 737, 747, MD-11, and JS-4100; the CoolSky DC-9, Captain Sim 707, 727, and 737, Leonardo Maddog MD-80, and the iFly 737. More user-installable interfaces are provided in the FCOMPNL folder (in Gauges), see the README_Interfaces.txt there for more details. In particular interfaces for the Majestic Q-400 and the Milviz B737 are provided new in this release.

- A new set of loap map parameters will allow you to precisely configure the way any aircraft is loaded. The new features are shown on the load map. This feature is disabled by default in this version. To enable it, include this line in the Options.cfg file (in the FSCaptain\Config folder): NODETAILLOAD=0

- The scoring for certain flight types has been changed so that the base score will be the higher of either 85, or the minimum required score for the level you are currently on. This change applies to CARGO, ferry, check rides, and skills development type flights. The change will be retroactive and should result in higher average scores for many Captains currently at or above level 7. You'll see the change immediately when you view your log or achievements page in the Administrator.

- For those of you flying with a tan interior cockpit, a tan version of the FCDU is available. To implement it, edit your panel.cfg and replace the occurrences of 'FCDU!' with 'FCDU2!'. The functionality is the same, just the faceplate of this version is tan not gray.

- New interfaces are included for the Majestic Q-400 and the Milviz B737-200.

- New interface support for reading the airspeed bugs from the ASI of certain supported aircraft. This will result in V1, VR, and V2 callouts regardless of the presence or absence of the old SPEEDCALL table, provided the aircraft allows user-settable speed bugs.

- A new option supports true Combi aircraft by changing the rules so that if a load map is configured with flight attendants the attendants will take care of the PAX even if the flight type is a cargo flight. ENABLECOMBI=1 in FSCaptain\Config\Options.cfg turns this new feature on. It is off by default.

- In the "Flight Dispatch" tab, the "departure airport" will now default to the last airport you landed at, unless you are running the Administrator from inside the sim, in which case it will default to the one you are currently location nearest. DISABLEDEFAULT=1 in FSCaptain\Config\Options.cfg turns this new feature off. It is on by default.

- The mysterious white knob on the FCDU is now correctly labeled ON. This should help with the occasional support issue of "the FCDU screen is blank."


These problems were fixed in 1.4.5:
------------------------------------

ID#0208: Changing the airline maintenance option clears some other options buttons.
ID#0209: FA will say "Cleared for Takeoff" before the safety briefing if the switch is toggled.
ID#0210: Arrival sometimes misinterpreted as a 'refueling stop' if another airport is too close.
ID#0211: Fuel on release flight plan section is always pounds.
ID#0213: When a flight spans midnight (zulu) on the last day of a leap year the ETE calculation stops.
ID#0214: When FSUIPC Mouselook is selected and FSCaptain.dll is loaded control of the mouse cursor is lost.
ID#0215: It is very difficult if not impossible to match NGX Pax loads to the numbers FSCaptain generates.
ID#0216: Nonstandard transition altitudes are not printed on releases from the Admin.
ID#0217: FO reminding CAP about gear on a plane with no retractable gear.
ID#0218: Unable to enter -1 to mean 'no service' when revising a flight.'
ID#0220: "Winds Aloft" falsely reported as not available when data source is Active Sky product.
ID#0221: Ferry flights have a base score of 85 which makes it impossible to score over 92.
ID#0224: Planned landing weight calculated incorrectly resulting in overweight flights generated.
ID#0225: FO issues stern warning if you open doors before ending flight, even if shut down and not moving.
ID#0226: FCDU background is too bright at night.
ID#0227: Previous log file entries are overwritten with new ones on ferry or skill flights scheduled from the FCDU.
ID#0228: Specific flight numbers entered into the Ferry setup page do not "take".
ID#0229: Fuel calculated incorrectly on flight plan resulting in too-low "LANDING FOB" on release.

These problems were fixed in 1.4.4:
-----------------------------------

ID#0205: Sometimes after using the STAT key on the FCDU ID#0206: Admin displays a message 'Do you want to administer for FSX' when FS2004 is started, possibly hanging the sim.
ID#0207: Local Time of arrival is actually Zulu time.

These problems were fixed in 1.4.3:
-----------------------------------

ID#0193: Early time estimates based on plan are overly optimistic.
ID#0194: 'Prohibit Service' option being ignored - service happens anyway.
ID#0195: Overrides not seen and aircraft.cfg fails to import into properly load maps feature.
ID#0196: Weather incorrectly being considered below minimums.
ID#0197: Dispatch complaining about insufficient fuel even when the fuel-auto-load is suppressed.
ID#0198: Clock continues to count after official arrival.
ID#0199: Under certain circumstances winds aloft data is not retrieved when it is available.
ID#0201: Some edits on aircraft performance data are too low for some high performance aircraft.
ID#0202: Gate Change message keeps repeating same gate over and over.
ID#0203: The score reported for a promotion on the Career tab is incorrect.
ID#0204: Admin fails to get winds aloft data on download of Wx from Internet.


These enhancements were included with 1.4.2:
---------------------------------------------

- A beta of the new FSCaptain save/restore facility is included with this release. The save/restore currently will only work with the FCDU, not the FCOM. Documentation is in the included file README_Save.txt.


These problems were fixed in 1.4.2:
-----------------------------------

ID#0191: Incorrect minutes calculated on enroute ETE revision
ID#0192: FS Crashes during flight with 1.4 or higher but not with 1.3.1


These enhancements were included with 1.4.1:
---------------------------------------------

- A new button next to 'Find Flights' on the Administrator will look for a single flight from among those available for you to fly in the future and list only that one. The 'Find Flights' button has been renamed to 'List Flights' but it functions exactly the same as in previous releases. This new functionality replaces the old 'leave the airport blank' assignment, which still works, but this will give you an assignment from an airport of your choice.

- When you login to the FCDU (not the FCOM) and your current airport and airplane don't match any open flights in the log, but there is another commitment within a 5 mile radius of where you are, you'll be shown the details of that commitment and asked if that's the flight you want. If you say yes a series of questions will determine the problem and get you flying if possible. This could involve switching your airport and/or your airplane to the one you're currently in, if that airplane is close enough in specifications to the one that you were booked for. if not you'll be advised to switch airplanes.


These problems are fixed in 1.4.1:
-----------------------------------

ID#0183: FSX crashes when pilot attempts to 'Use Administrator' from the FSCaptain menu.
ID#0185: Phantom No Smoking Trigger
ID#0187: After landing at destination FDCU misreads the location and identifies landing as a refueling stop.
ID#0188: Page 63 Dispatch Request mis-identified as page 35 on display.
ID#0189: In-flight with ETE revision (FCDU only) results in wrong resultant ETE minutes.
ID#0190: Zero payloads being generated for cargo flights in FCOM/FCDU


These enhancements were included with 1.4.0:
---------------------------------------------

- A new ACARS gauge named the "FCDU" (as opposed to the traditional FCOM) can be installed and used anywhere the FCOM was used. To install in a new airplane simply use the Installer program. To install manually, follow the FCOM installation procedure (documented in an appendix in the User Guide) but substituting the letters FCDU for FCOM. To modify an existing panel.cfg, simply change the occurrences of the string '=FCOM' to '=FCDU'. The new gauge works in the style of a Boeing FMC/CDU. The pages displayed and the information on them should be familiar to veteran FCOM users. Pilots not familiar with the FCOM or those not experienced with the use of an FMC/CDU should continue to operate the simpler FCOM. There is no official documentation for the FCDU yet but there is a README_FCDU.txt file in this archive that will have to do for now.

- A new updated tutorial using the new FCDU ACARS device is include in the Documentation folder.

- A new "Appeals" process that will allow Captains to selectively remove penalties from flights in their logbook. This is accessed from the View Details function when working with your log in Administrator. If a flight contains score deductions a new 'Appeal' button will be enabled. This button will lead to a dialog where any of the penalties can be erased for a point cost which varies by the severity of the penalty. Total points available is the pilot's current Quality Point total, minus any points previously used to remove other penalties.

- The ability to enter all the details of a flight in addition to the destination airport so as to be able to schedule a flight meeting external requirements, such as a VA flight or one from a printed schedule. Items such as passenger count and cargo can be specified or left blank to be automatically generated. The old 'destination ICAO' field is replaced by a new button 'Specify Flight Details'. This provides at a minimum the old functionality of a destination, if you leave all the other fields blank. But now you can specify details even including times and service codes.

- When the aircraft is positioned at an airport and there are other airports within a 5 mile radius, a new F3 option on the FCOM Pre-login page will allow the pilot to select which airport he is considered located on. This will resolve most 'wrong airport' conflicts.

- A new menu option and key combination ( CTRL-[ ) will request that the last statement said by your FO be repeated. Using the function again with no intervening new statement by the FO will request that the FA repeat their last statement.

- When smoke is first reported in the passenger cabin, turning off the galley power (if your aircraft supports galley power through an interface) will increase the odds that the smoke will clear rather than get worse.

- An exit from page 13 (flight review) using F9 will now ask to confirm by pressing F1 before actually exiting.

- A new option on the aircraft configuration page (bottom left column) allows airplanes to be designated as water capable. These should no longer crash on FS9, or require a parking brake be set to unload on both simulator versions.

- Charter flight numbers greater than 9999 will not be generated. When the current ascending series is exhausted a new series will begin at the highest flight number in the airline's schedule (if any) plus 500.

- The Interface support for the PMDG 737NGX has been moved into the FCOM itself. It's no longer necessary to install a separate interface into the panel.cfg for the airplane. It's suggested that pilots who have one installed remove it when they start using FSCaptain 1.3.2 but it's not necessary to do this; the FCOM internal code will defer to an external interface in the panel if it's there. As of this release the external and internal are identical in function but in future releases the external XML gauge will be deprecated. In future releases more aircraft will have this built-in support.

- The Installer that modifies the panel.cfg to install the ACARS gauge has been greatly improved. It supports the new FCDU, installs more cleanly with less superfluous comments, adjusts the proportions of the gauge to your screen width and panel size, and detects and supports some special situations for the installation (e.g. the NGX).

- A wider selection of default airlines is provided in a zip file named "Airlines.zip" in the FSCaptain\Airlines folder. These are provided here so that any user-customized airlines or schedules are not overwritten. They contain updated worldwide schedules for the FS9/X boxes airlines, plus a selection of real airlines from around the world.


These problems were fixed in 1.4.0:
-----------------------------------

ID#0159: Landing bonus points not being awarded.
ID#0160: Landings on water by water aircraft are considered a crash. (see enhancement note)
ID#0161: Some waypoints parsed incorrectly when imported from an FSX flightplan built by FSBuild.
ID#0163: Flight Attendants will now start service as soon as possible after service altitude on shorter flights.
ID#0165: Charter flight numbers can exceed 9999, this may be undesirable.
ID#0167: Weight limits in aircraft config are not always being honored during payload generation.
ID#0168: Some aircraft types can be selected in FCOM but are not available in the Administrator.
ID#0171: Cabin service was started while a cabin emergency was ongoing.
ID#0172: Pilot had penalty deducted for "excess fuel on landing" when on a ferry flight.
ID#0173: Aircraft configuration page does not save pressure option or retractable gear option.
ID#0175: A false VA Flight number of 65536 is shown when you view flight details.
ID#0177: Populating the aircraft list for flight dispatch omits numbered variants and doesn't read overrides.
ID#0178: On some flights bags and cargo are missing from the manifest.
ID#0179: Message about service required on a scheduled cargo flight with no attendants.
ID#0180: When using multiple pilots in the same company log 'view details' shows wrong flight details.
ID#0181: When flying with 2nd or greater pilot, first pilot is shown as PIC on dispatch release.



These problems were fixed in 1.3.1:
-------------------------------------

ID#0136: Destination ICAO overwritten with departure ICAO during flight.
ID#0137: Missing or badly timed hazardous weather verbal comments.
ID#0138: Engine flameout due to icing happens too often and too quickly.
ID#0139: F7 option on the Dispatch Request page is always grayed out.
ID#0140: Dispatch release document not produced after first leg of a multi leg flight.
ID#0141: Does not update fuel calculations when alternate airport is changed.
ID#0144: Wrong ZFW is calculated on Dispatch Release document.
ID#0145: Dispatch time estimates not properly using winds aloft along route.
ID#0147: Airline-specific music files won't load.
ID#0148: Flight Attendant incorrectly says "go-around" during flight.
ID#0149: No "smooth landing" bonus w/o alerting the FAs.
ID#0150: AI-only airplanes appear on the aircraft select drop-down on the flight dispatch tab.
ID#0151: Update 'valid surface types' to include bituminous, gravel, and steel mats.
ID#0152: Load stations had their positions in the airplane changed during loading (FS9 only.)
ID#0153: Load Map station 5 saves as 0 weight
ID#0154: When the 'No Load' option is selected for an A/C the PAX count keeps changing after login.
ID#0156: When saving aircraft characteristics cruise PPH is saved with the descent PPH value.
ID#0157: Alternate airport must be entered in all caps or it is rejected.
ID#0158: Parking type RAMP incorrectly shown as GATE on FCOM.

Also some voice files missing from the 1.3.0 release are included.

These problems were fixed in 1.3.0:
-----------------------------------

ID#0113: ATC holds and delay vectors are sometimes not detected.
ID#0114: ATC ground delays are often detected when they did not occur.
ID#0115: Valid gates are often not selected when gates are being assigned.
ID#0116: FCOM crashes when brought up in offline mode with engines running.
ID#0117: Penalty for violation of the 250K speed limit is too sensitive.
ID#0118: When canceling a flight on the 2nd leg of a multi-leg trip, it cancels the first leg instead.
ID#0120: Some add-on airports are not included in the airports.cfg database.
ID#0121: Sometimes no baggage is included on passenger flights.
ID#0122: When no FO is aboard, the F7 signal to alert the cabin crew does not work.
ID#0123: The "Makerwys.exe" program was not included in the distribution. It is in the Fixpack.
ID#0124: A long TAF is allowed to overflow the page down into the blue Fkey help lines.
ID#0125: Pressing F9 from the weather hold page goes to the next page not the previous one.
ID#0126: METAR generated from FS weather data does not include precipitation codes.
ID#0127: "Max Range" on the Progress page is not computed - showing N/A.
ID#0128: FCOM will freeze up if a message is received while another message is being shown.
ID#0129: The auto-loader will load some small random amount of extra fuel, usually in the five percent range.
ID#0130: "Poor Service" penalty was received even though not service was allowed on a scheduled flight.
ID#0131: Load Map Import skips first station, station.

These problems were fixed in 1.2.0:
------------------------------------
ID#0052: Airport KVCV was omitted from the database after a rebuild.
ID#0089: Flights are offered for which runway is below minimum for aircraft.
ID#0090: "Disabled" buttons on the communications page are really active.
ID#0092: Occasionally, pilot is unable to proceed from load complete when all three lines read "READY".
ID#0093: Fuel autoloader is loading way too little fuel to the plane if unit is set to KG.
ID#0094: APU fuel burn makes "Proceed" option vanish immediately after fuel has dropped below initial level.
ID#0095: Once you Commit to a flight the "Commit" button again will keep adding the same flight.
ID#0097: Fuel changes not being reflected in the dispatch release.
ID#0098: Booking a flight in the Administrator could result in an overloaded aircraft.
ID#0100: If you press F1=Proceed before door is closed it will open and you will not be ready again.
ID#0102: Changes sometimes not saved in administrator.
ID#0106: If you book your first flight ever for an airline in the administrator it won't be written to the log.
ID#0108: When changing to an airline with no log, the log for the previous airline is shown.
ID#0109: Having zero jump seats on a cargo flight causes loop at departure.
ID#0110: When committed flights are changed sometimes they will be duplicated.
ID#0111: CvtLog does not convert log to .csv file.
ID#0112: F.O. will comment on belts when there are no PAX.

These problems were fixed in 1.1.6:
------------------------------------
ID#0083: PAX counts not random in successive invocations of the Admin program.
ID#0084: FCOM with 'Suppress Auto-Payload' does not pick up current payload.
ID#0085: Auto-loader will not access stations above 60 under FSX.
ID#0086: Max gross weight and empty weight not parsed correctly for some aircraft.
ID#0087: Unable to enter 3-character ICAO Airport code if 4-character already in field.
ID#0088: When fuel is calculated over 99,999 pounds only the first 5 digits are passed to FCOM.


These problems were fixed in 1.1.5:
------------------------------------
ID#0055: Sometimes duplicate flights from a schedule are not shown, correctly fixed in 1.1.5.
ID#0072: Multi-leg flight resume problem - F9 changes destination.
ID#0074: Flight service times do not adapt to sim rate.
ID#0075: Flight scheduled in Administrator won't start in FCOM.
ID#0078: Does not connect to a VA website.
ID#0079: On some aircraft the landing lights signal does not work properly.
ID#0080: Connection and parsing problems with some wind data from Jeppesen.
ID#0081: Too many "PAX Ear complaints" to be realistic.
ID#0082: Number of PAX on same flight to same destination not randomized between selections.


These problems were fixed in 01.1.4:
------------------------------------
ID#0047: FCOM not installed properly on the HJG 707 aircraft.
ID#0055: Sometimes duplicate flights from a schedule (but for different times) are not shown.
ID#0058: Times imported into a schedule not always converted from GMT to local.
ID#0059: Airport limiter feature on Manifest doesn't prevent cargo load outside limits.
ID#0060: Reports of missing airports in airport rebuild function.
ID#0063: Changing fuel in dispatch window -- change doesn't take.
ID#0065: Some fields not updating in the administrator.
ID#0067: Export does not report error message properly.
ID#0068: Experiencing hydraulic failure on non-hydraulic aircraft
ID#0073: Speed, weight, and altitude editing restrictions expanded in Administrator

This problem was fixed in 01.1.3:
----------------------------------

ID#0048: Airport database rebuild sometimes fails and leaves only a few airports rebuilt.


These Problems were fixed in 01.1.2:
--------------------------------------

ID#0050: Flight Attendants could announce go-arounds during a turbulent takeoff.
ID#0051: On short duration flights destination offered was sometimes same as departure airport.
ID#0053: Under Windows 7, log entries were not made.
ID#0054: On small aircraft (e.g. C-172) when required to fill tanks autoload sometimes stopped short of full.
ID#0056: FO Reminded about gear up on aircraft with no retractable gear.
ID#0057: ETE is shown as too low on single-leg flights with small/slow aircraft


These problems were fixed in 1.1.1:
-------------------------------------
ID#0046: Date is one or two days in the past on dispatch release and log.
ID#0049: Admin popup screen in FSX disappears behind black screen


These problems were fixed in 1.1.0:
-------------------------------------

ID#0029: "Do Not Play GPWS" option on Load Maps tab is not saved.
ID#0030: Import of load map from B707 aircraft.cfg is wrong.
ID#0031: After takeoff with belts switch off, FA advised PAX they could get up and move
about just after takeoff.
ID#0032: GPWS Callouts don't happen for some aircraft where they should.
ID#0033: Message "Autoload Failed Use Manual Load".
ID#0034: Does not change pilot preferences when changed from 1st screen.
ID#0035: Hotkeys and signals between Admin DLL and FCOM not working.
ID#0036: Many airports give runway overrun errors.
ID#0037: Not cleared because too little fuel using "Suppress Fuel Auto-load" option.
ID#0038: Suggestion to include fault triggers in FCOM log.
ID#0040: Some add-on airports are not built in the airports database.
ID#0041: Lift 20,000 pound limit on fuel flow CRZ.
ID#0042: "Poor Service" penalty on a flight with no FA's.
ID#0043: No GPWS callouts for some aircraft.
ID#0045: Cabin emergency occurred after descent started.


These problems were fixed in 1.0.4:
------------------------------------

ID#0023: AI Flight Plan import does not handle multileg flights properly.
ID#0025: False 'Lights not set properly' penalty.
ID#0026: Bogus seatbelt announcement on 2nd leg of multileg flight.
ID#0027: False report of engine failure during start sequence on Connie L1049G.
ID#0028: Crash on auto-load of aircraft with more than 20 payload stations.


These problems were fixed in 1.0.3:
------------------------------------

ID#0010: Not recalculating fuel when when ETE revised.
ID#0018: Report that POS report rejected for '0 minutes elapsed' but in fact 30 mins had elapsed.
ID#0021: Pushback distance not calculated correctly in all cases.
ID#0022: Dispatch is calculating payloads that overload the aircraft
ID#0024: Dispatch requested a position report after TOD was sent, docked pilot points for not sending.


These problems were fixed in 1.0.2:
------------------------------------

ID#0016: When creating a new aircraft the type code is not written to the file.
ID#0019: Points being added or deducted from score on a check ride for multiple causes.
ID#0020: False positive on fault code 203 "partial panel avionics" on some aircraft.


These problems were fixed in 1.0.1:
-------------------------------------

ID#0001: Some aircraft (including most Flight1 products) not seen by the Installer.
ID#0002: Error message "We didn't have enough room to process all the folders" using the Rebuild Airports function.
ID#0003: Documentation about Speed Calls and manually installing the FCOM is now in Appendix 4 of the User Guide.
ID#0007: Points were deducted from flight score for not reporting position - on a check ride.
ID#0012: The 'Has a First Officer' option on the Aircraft Characteristics tab was ignored.
ID#0013: New aircraft config file, based on an old one, had the old file preceding the new filename.