FSCaptain 1.7.3 Public Beta 1 is released

[Travis]

Captains,

FSCaptain version 1.7.3 Beta 1 has been released for public download and testing.

If you wish to participate in the Public Beta, feel free - we would like to have as many Captains as we can find to give this their attention. The first thing you should do is check the README that's in the ZIP files, and then make a backup of your current \FSCaptain\ folder (if you have one). Then you can install either the Full version (if you have not tested FSCaptain before) or the Fixpack version (if you have already installed FSCaptain).

The Full version can be found here:

174MB
www.fscaptain.net/downloads/FSCaptain_173_B1.zip

It includes all audio files.

If you have an existing copy of FSCaptain the Full installer will overwrite your Airline and Airplane files, as well as many configuration files.  So we recommend that current Captains use the Fixpack installer below.

The Fixpack version (for users who have already installed FSCaptian and merely wish to update) can be found here:

32.6MB
www.fscaptain.net/downloads/FSCaptain_Fixpack_173_B1.zip

The Fixpack does not include the full audio packages - just additions from 2016.  The Fixpack installer will also not overwrite any of your \config\_user.txt files.

You will be asked if you want to overwrite existing files!  Just say Yes when asked.

After updating, when you first run your simulator you will be asked the "Do you trust..." questions for both FSCaptain.dll and the FCDU / FCOM gauge (if you use the gauge).  Again, just say Yes when asked.

Development and other notes follow....

=============
General Notes
=============

• 1.7.3 was intended to only contain bug fixes and minor adjustments - although a few new features have found their way in due to the length of development.
• FSCaptain 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: 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.)
• The Administrator is now built in a manner which should allow it to be used by Captains using Windows XP.
• The FCDU.EXE is currently not able to run under Windows XP - those Captains will need to use the FCDU gauge.
• Windows XP users are advised to check whether or not they have the Microsoft .Net Framework version 3.5 installed on their PCs which is necessary in order for the FSCaptain Scenery Scanner to operate. If you do not have Framework 3.5 installed, you can download the installer from Microsoft at: www.microsoft.com/en-us/download/details.aspx?id=21
• The "User Guide and "Configuration How-To" documents have been updated to reflect recent changes in FSCaptain.
• The "Load Station Calculator" spreadsheet referenced in the "Configuration How-To" document is included in OpenDocument Spreadsheet format.

============================
Testing Notes on New Options
============================

• A new variant to the SIM_AUTOSAVE_ON_GROUND option (4) allows auto-saves to only occur when on ground. This works well with other add-ons which only auto-save when in air.
• The global options SERVICE_MAX_TURBULENCE and SERVICE_MAX_BANK_ANGLE allows you to define the maximum turbulence level and maximum aircraft bank angle that are permitted before cabin service is suspended.
• The airline option HOURS_BETWEEN_MEALS allows you to define a timespan for additional meal services during a (long) flight. The default value is 8 hours, but you may choose anywhere from 3 to 12 hour intervals.
• FSX and P3D turbine aircraft that don't have an explicit interface for "continuous ignition" can now optionally use the default simulator signal by setting ENABLE_DEFAULT_IGNITION=1.  This will bring the responsibility of keeping "continuous ignition" during precipitation (and optionally during turbulence).
• Yes - optionally, excessive flight in moderate to severe turbulence without an active ignition can cause an engine failure in turbine aircraft. Reducing the amount of being bounced around the sky (such as by reducing your airspeed) will dampen this effect. This feature is controlled by the new option ENABLE_ENGINE_FAILURE_IN_CAT. The engine should "un-fail" within 30 seconds, allowing you to restart it.
  
• Therefore, Aircraft Ignition systems can be flagged as INOP - just in case a favorite turbine aircraft doesn't have a mechanism to manage them.
• For testing purposes, you can set ENABLE_ENGINE_FAILURE_IN_CAT anywhere from 0 to 10.  0 is disabled, and for each increase in value you can risk failure after each 1 minute of Moderate CAT or 25 seconds of Heavy CAT or 10 seconds of Severe CAT.
• QP_MINIMUM_TO_APPEAL and QP_PER_PENALTY_POINT were not being written to options.cfg if left at default values.
• A new option - DEFAULT_CAN_BE_OPEN=1 - allows the most recent Open flight's departure airport (where you last wanted to fly from, but haven't yet flown) to be the default departure airport in the Administrator's Flights tab.  So if you last flew to EDDM but have since created a new Dispatch Flight from LSZH to LIML, LSZH would be your default departure airport if you reopen your Administrator before taking that flight.
• If you're in a helicopter, the "AI Freeze Ray" will function below a Captain-specified AGL height - set PROTECTION_HEIGHT in your options.cfg anywhere from 0 (disabled by default) to 200.  (More testing that we could afford for 1.7.3 would be needed to adjust the "Gate Detector" and parking routines.)

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

• The presence of Airline Code and Aircraft Type safety announcements will override the standard SAFJET and SAFPROP announcement from your FA and FO. (Currently undocumented....)
• A new airline (Surfair) is included with full Economic Mode details. It is limited to PC12 aircraft flying from a select list of Northern California airports to an equally select list in Southern California.
• "Exit Mapping" - which involves both assigning exit numbers to exit “types” and allowing control of these types - is a new feature of FSCaptain. A description follows:

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

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

• When the "AI Freeze Ray" is active, the FCDU screen number will be presented in red.
• The "AI Freeze Ray" can only be activated when your Landing / Taxi lights are on. (Your Systems' screen will tell you if your Landing Lights signal is active when using your Taxi Lights.) If you find yourself blocking another aircraft from taking off, switch off your Landing (and Taxi Lights if needed) until the aircraft moves out of range.
• What was known as the Interface screen on the FCDU is now referred to as the Systems screen.
• The Administrator's Load Maps tab can now be used to edit aircrafts' exit maps.
• Landing pitch and bank values will be reported on the Statistics page, but not logged until version 1.8.0. (They have been recorded in the FCDU log since version 1.7.0.)
• The Systems screen can now be reached before Loading by clicking on the PROG key of the FCDU. SIGNALS cannot be set before loading.
• The Aircraft Data screen now displays the path & filenames for the currently loaded aircraft configuration file and aircraft loadmap.
• There is an addition to the customs_fsc.txt file, giving full Customs Services to LIMC.
• There are updates to the customs_exceptions.txt file to account for differences in the form which United States airports' "country name" is used.
• GForce values are no longer noted when on the ground. This may be the cause of recent GForce damages when landing.
• Having a "Complainer PAX" onboard now reduces the max & min GForce values for a FLTBAD penalty.
• Simulator autosaves no longer will occur when the sim is paused.
• In case of a diversion, the flight will be noted as being to the original destination (together with the original alternate airport). However the actual point of landing will be noted in the flight details.
• Aircraft exits can also now be flagged as INOP, relieving a need to properly open/close them.
• The aircraft battery switch can also now be flagged as INOP, in case someone makes an aircraft that doesn't use the standard battery switch! EDIT - there is an interface since at least one aircraft has already done this.
• INOP systems (including aircraft without retractable gear) are now recorded as INOP on the Systems screen, with the system reported as "on."
• On the four SYSTEMS screens, INOP systems are presented in grey - active systems are presented in green.
• On the Administrator's Specify Flight Details screen, you can now enter Cargo Weight in kilograms by appending "kg" to the weight value.
• Parking Brakes can now be flagged as INOP, relieving a need to properly set them.
• Flights with a Block Time of less than 45 minutes, as well as the initial Service for any Meal Service flights, will have their Cabin Service defined as "Drinks Service."
• The minimum runway length for takeoff and landing has been reduced to 100 feet. Piper Cub Captains can rejoice.
• For unregistered users, if an attempt is made to take off from an un-allowed airport, an option to go OFFLINE is available - previously, such Captains would be stuck on the "Please Register" screen.
• For P3D users, FSUIPC interactivity has been restored.
• When the airport database is rebuilt, you will not need to restart the Administrator to see any changes you may have made.
• Piston aircraft will have flap & landing gear callouts made at slightly lower AGL levels.
• The function that should "un-fail" an engine less than one half minute after failing due to chilled precipitation did not work properly.
• A new reason (CAPT DISCRETION) can now be used in any circumstance to divert to any alternate airport without immediate penalty.  (This has been proven useful if you arrive at an airport that - due to scenery changes - has "sunken" into the ground.)  However repeated use of this diversion type will incur a reprimand from the Airline.
• Scoring for unauthorized diversion requests are now uniform - a loss of 20 points.
• Diverted flights are now eligible for "correct position reporting" bonuses.
• Administrator Flight Dispatch type now considers preferred Airline flight type and then the preferred Captain's flight type to assign the default search type.
• Engine failures due to Chilled Precipitation Intake are now cause for a post-flight inspection due to the Captain's Error.
• The amount of Chilled Precipitation Intake when only flying through clouds has been halved.
• The Administrator's Aircraft configuration editor has a textbox to enter how many engines are on an aircraft. This shouldn't be needed for most aircraft, but we do know of one or two aircraft which do not report the correct number of engines. If in doubt, leave this blank. If you load an aircraft and see an incorrect number here, change it!
• The odds of hearing a cargo-loading noise has increased from 30% per item to 50%.
• Taxi music will no longer play on cargo or ferry flights. (There's no constructive way to signal that takeoff is imminent, and you may be in dialog with ATC.)
• An updated HOT.cfg file is included.
• An updated transitions.cfg file built off of AIRAC 1609 is included.
• PLN waypoints with IDs up to nine characters are supported in the FCDU and Dispatch Release.

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

• A bug which would report a false "belly landing with gear up" has been corrected.
• A CTD bug which could occur at an airport without fuel locations has been fixed.
• A fix to reduce (not eliminate!) the possibility of "negative pax" being listed on certain Economic Mode flights.
• Flight Type not always correctly considered when loading aircraft loadmaps in Administrator.
• Two CTDs that occurred when a flight was going out and when a manifest was generated were found and eliminated.
• Fuel display formatting in the Dispatch Release's Flight Plan list has been corrected.

===========================
Testing Notes on Interfaces
===========================

• There is a new interface for the FSLabs A320. Its exits can not be controlled by your crew.
• There is a new interface for the Carenado Phenom 300.
• There is a new interface for the CLS BAe-146.
• The FSDS Hawker Siddley 748 now includes a continuous ignition signal via an expansion of its interface. (Use the Relight L & R switches on the pop-up panel.)
• The PMDG 777-200 now accepts input from the aircraft's exits to indicate when they are open or closed.
• The CLS BAe-146 and Carenado C208EX are the first exit-mapped aircraft types supported in FSCaptain. Captains of these aircraft can use signals from the Systems Screen Page 4 to test opening and closing their exit types.
• An interface for the Lionheart Quest Kodiak has been included (it covers only one item - the Engine Igniter signal).