Post by Travis on Dec 27, 2019 12:29:24 GMT -5
Captains,
Reporting Problems
================
We're not self-important enough not to think there may be new problems in this build, or old problems may have taken on a new shape. If something goes wrong and you want to continue testing, make the notes you feel would help us find the problem, take any screenshots that would help illuminate things, and supply any new Admin, FCDU and FSCaptain logfiles. The logs are a key element in our ability to triage problems.
You can either post here in the forum, or by email (see the link in my signature below for clues on how to email us).
Our log files capture such things as your "username on your computer" as well as your "computer's name" and the names of all of your Captains. So if you don't want that to appear in public, we're happy to receive bug reports by email. (Most of our support is done via email, for whatever reason.)
This is a Refresh Build
==================
You MUST also install this on top of the most recent public release of FSCaptain - that's 1.8.1 SP2 - or on top of one of the earlier 1.8.2 Alpha builds. This Alpha Release build only contains the files which have changed since the prior public release.
A Full Backup is Highly Recommended
===============================
For your own convenience, we strongly urge Captains to back up your entire FSCaptain installation prior to installing this! It takes less than a minute, and can guarantee you a stress-free ability to 'roll back' the changes.
I recommend going into Windows Explorer and copying your entire FSCaptain folder from your simulator and pasting it on your Desktop. That's what I do, because it keeps my backup in my "line of sight" in case I need to revert to a previous version.
If something contained in this Alpha Release build is "unhelpful" to your flying habits, you will need to restore your backup over your simulator's FSCaptain folder. (Don't bother with the "Uninstall Program." I've never used it, and I likely never will....)
First, delete everything in your active \FSCaptain\ folder, and copy the contents of your backup \FSCaptain\ folder into the active folder.
If you use the FCDU or FCOM gauges, look inside your restored \FSCaptain\ folder for a folder named \Simulator-Gauges\. Copy the GAU files from that folder into your simulator's \Gauges\ folder.
If you are an FS9/FS2004 Captain, look inside the \FSCaptain\ folder for a folder named \Simulator-Modules\. Copy the FSCaptain.DLL from that folder into your simulator's \Modules\ folder.
Okay... let's look at the new stuff!
Airport DB changes... and running the Installer
======================================
When you first run any of the FSCaptain 1.8.2 Installers, you will get the prompt to update your airport database. Please have all of your airport sceneries ready to be scanned by MakeRunways and SceneryScanner!! This is a one-time update, all future Beta and Public releases will not need further updates.
The new SceneryScanner supports changes in MakeRunways 4.873 - which is also included in these Installers - and will note all airports in Australia, Canada, New Zealand, and the US with default TA and TL levels - unless specified otherwise in Navdata.
If you are asked by the Installer to overwrite any files, you must allow that to occur. We've updated some Config files, and the "Sound Files" files, and some of these are normally read-only.
Administrator UI changes
======================
We have all but committed to some changes to the appearance of the Administrator during the 1.8.2 Beta timeframe, which is why we're giving any Captain until early January to point out any problems in our intended changes.
So please run your Admin.exe to see the base changes first. Buttons and backgrounds should have changed appearance... looking not so much "Windows 98"... and there is an "empty for now" space between the "OK Cancel Apply" buttons at the bottom of the dialog, and the rest of the dialog.
This is how it appears on my Windows 7 system:
If there is anything on your system that doesn't look "right" (except for the empty space at the bottom of the Administrator dialog) please email us a screenshot, and include your PC's OS version, along with any display options that you feel might be relevant! If we don't hear anything from a test Captain before the end of 2019, we will begin adding new fields to certain configuration tabs.
If our changes are not usable for you, then after you have sent us a screenshot, go to your Install ZIP file and open the file named "Admin - Old UI.zip" and extract the "Admin.exe" file from within. Copy that file into your "\FSCaptain\bin\" folder, overwriting the "Admin.exe" file therein. The code inside is the same, except for the "new UI" bits.
If our initial changes are usable for you, feel free to ignore the "Admin - Old UI.zip" folder.
==================================================
//// CHANGELIST FOR FSCAPTAIN 1.8.2 Alpha Releases
==================================================
Each item below begins with an numeric indicator of the its release version: "-1" is Alpha 1, "-2" is Alpha 2, etc. (Alpha 4 items are also bolded for easier visual scanning.)
New Features
-2 An option to alter the acceptable landing vertical speed rate for a "PAX Nice Landing" bonus has been added.
The option's name is LANDING_RATE_NICE and currently accepts four values. You can choose to maintain the 0-200 fpm range, or use 100-300, 200-400, or 200-500.
-1 After reports of FS9 company logs not updating after a flight, a set of checks have been added to both the FCDU and the Administrator. If a write command for the company log (and for the ADMIN and FCDU process logs) fails, a message will appear on screen. This would allow those affected to pause the simulator and check their PC systems for any unexpected system change, such as an anti-virus program that has "woken from a sleeping state."
-1 In addition, company logs are now copied in place before a write command executes. For example, "ACME.log" will be copied to "Acme.log_backup" before it is rewritten.
-1 There is a new option - ALLOW_BYPASS_OF_READYTO - which will enable the FCDU's LSK1R to act as an 'emergency bypass' if you become stuck on the Load Confirm (#42), Ready to Load (#20), Load Progress (#21), Load Complete (#22), or Arrival (#29) screens with any balky exit, engine, or parking brake. After this is enabled, when you come across a 'guarded against condition' LSK1R will have a command caret ">" to denote a bypass is available.
"RTL>" for Ready to Load.
"RTF>" for Ready to Fly.
"RTU>" for Ready to Unload.
-1 There is a new option AUTOSCAN_AIRCRAFT_ON_START which can be used to bypass the "SimObjects check" that the Administrator normally does when it is launched. If "autoscan" is disabled, your aircraft data will be read from our new database located in "\FSCaptain\Aircraft\MyAircraft.bin".
-1 If you choose that option, you need a way to have the Administrator rescan your aircraft. Look on the Options for All Airlines tab of the Administrator to "Rescan Aircraft". Clicking this button will perform a scan of SimObject folders for flyable aircraft, and create/update a local database in your \FSCaptain\Aircraft\ folder.
-1 A new file is generated when your aircraft are scanned to give you a list of all your aircraft liveries - divided into "Aircraft.cfg locations" and "Aircraft Type" values. Look for "MyLiveries.csv" in your FSCaptain\Aircraft folder.
The file names are "new-name_fsc.txt" and "new-name_user.txt". The "_fsc" file contains a few entries which we have verified and will update throughout Full, Refresh and Fixpack files. Do note that the "_user" file is intended for your use and will not be updated - you can add entires for airports which you want used. Any entry in the "_user" file will override any entry in the "_fsc" file. Empty "_user" entries, such as "KBUR:", will negate any entry in "_fsc" files.
-1 There is a new set of configuration files to support specified Airline Parking Codes at any Parking Spot in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
-1 There is a new set of configuration files to support General or Airline-specific Preferred Alternate airports for any Destination Airport in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
-1 There is a new set of configuration files to support specific taxi-out and taxi-in times for any Airport in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
If you have questions about any of these new Config files, please email us, or post your questions in the FSCaptain forum!!
Changes
If in excess of the calculated safe speed, the current turbulence level is 'none' the line will display in cyan. If in 'light' to 'heavy' the line will be white. If 'severe' the line will be in red.
-3 METAR parsing now ignores "FMhhmm" values noticed in some Australian METARs. In the past this has led to incorrect station weather reporting!
-2 The PLN Waypoints screen will now display "Expected Altitudes" for waypoints on the first page if they are substantially different from your current altitude (so only in Climb and Descent). This can greatly help you "hit your targets" on SIDs and STARs.
-2 Fuel values in Gallons can now be entered using either "....GA" or "....GL" as the type designator.
-2 If PAX see Ground Ice on the aircraft frame before takeoff, you will no longer be eligible for a "PAX Smooth Flight" bonus. (Because they would be worried during the flight.)
-2 If you've received Approach Clearance, the TL value on the FCDU will remain green - indicating you're not violating company policy.
-2 The "<REQUEST" LSK on the FCDU's Communication screen has been changed to "<DISPATCH" to better indicate *to* *whom* you are making the request.
-1 If an FSLabs A320 series aircraft is detected in use, FSCaptain will not set the GSX Passengers and Crew values, since the aircraft does that itself.
-1 The FCDU.EXE should now remotely play all audios without "stepping on" already playing audios!
-1 If you set the option ALLOW_UNPROFESSIONAL_AUDIOS=1, some of FO_Trav's colorful audios will not play.
You still may hear him make the comment "Smooth Like Butter" on a very nice landing since that's what his CFI said on Trav's first landing.
-1 Captains who make PAX flights outside of Economic Mode with a Load Factor of 90 to 100 should see a marked increase of PAX - a 100 Load Factor should see nearly all seats full! (This does require testing and tweaks during the Alpha Testing process.)
-1 The Dispatch Release now indicates both the Field Elevation and current Density Altitude for your flight's airports.
-1 The Upper Winds display in the FCDU will now indicate levels in grey which are below you when you are climbing, or above you when you are in descent.
-1 The option TAXIOUT_FAILURES_ALLOWED has been renamed and several 'sibling' options have been added so you can disable a/c system failures in these modes:
FAILURES_ALLOWED_CLIMBOUT=1 ; 1 = Failures are allowed to occur during climbout (default). 0 = No failures can occur while climbing to TOC.
FAILURES_ALLOWED_DESCENT=1 ; 1 = Failures are allowed to occur during descent (default). 0 = No failures can occur after TOD.
FAILURES_ALLOWED_ENROUTE=1 ; 1 = Failures are allowed to occur while enroute (default). 0 = No failures can occur between TOC and TOD.
FAILURES_ALLOWED_TAXIIN=1 ; 1 = Failures are allowed to occur after landing (default). 0 = No failures can occur after landing.
FAILURES_ALLOWED_TAXIOUT=1 ; 1 = Failures are allowed to occur during taxiout (default). 0 = No failures can occur before any takeoff.
These options only apply to aircraft system failures. Other incidents - such as a cabin emergency, bird strike, cargo shift, and blown tires - remain unchanged.
-1 The DIVERT option in the FCDU has a new option. While you can easily end a flight by Diverting to your Alternate Airport (or to any other Airport you wish), doing so will end your flight.
Now you can choose to DIVERT for a REFUEL STOP and all TOC/TOD TA/TL LANDL values will be expected. (Needs full testing of all "cases".)
-1 If the MakeRunways data (or your Parking Codes data) has captured an airport's jetway-equipped parking spots, they will be flagged as "/J" on the Administrator's Parking Selector.
-1 Aircraft can now have their Cabin Temperature, Galley Power, and Window Heat systems marked as INOP. (This will give Captains the ability to ignore these systems in case of an aircraft developers' update breaking the current FSCaptain interface.)
-1 When using the Windows' File Selector to pick a PLN file in the Administrator, new "filters" have been added to allow you to easily filter these types [Examples given for a KSEA to KATL flight.]
All Departure airport (ICAO) --> Destination airport (ICAO) PLN files. [*KSEA*KATL*.PLN]
All Departure airport (ICAO) PLN files. [*KSEA*.PLN] -- These are all files which contain the Departure ICAO... including as Destination!
All Destination airport (ICAO) PLN files. [*KATL*.PLN] -- These are all files which contain the Destination ICAO... including as Departure!
All PLN files. [*.PLN] -- This was the previous (and only) filter used by the Administrator.
All files. [*.*]
-1 Minor speed improvements when searching for flights in the Administrator.
-1 "Standing Lenticular clouds" (METAR codes "ACSL" "SCSL" "CCSL") are now noted as "Significant Weather - CAUTION" for an airport. Their presence - usually in mountainous areas - is indicative of turbulent air.
-1 "Official" Private and Military airports in Australia and New Zealand have been updated.
Bugs
=====
-4 A PAX flight with a 'no service' rule called could render a 'bad service' penalty when going IN. (Very rarely, but still....)
-2 A coding error would flood your FCDU log with "Transition Level" notices if your TA was below your Landing Light Altitude, and while you were below the Landing Light Altitude.
-2 Two errors in reading "non-pound Fuel values" in the Administrator's Flight Dispatch screen has been fixed.
-1 A second "Snack Service" would begin earlier than expected.
-1 When the Administrator is used to Dispatch multi-leg flights, the Load Plan from the first leg would be copied to subsequent legs. When flown, those legs would generate correct Load Plans at the time of loading, so this was only a "cosmetic bug."
-1 When dispatching multi-leg flights, the "Latest Dispatch Release" will now be for the 'first flight leg' and not the 'last flight leg.'
-1 Airline / Aircraft specific safety announcements were being played by the FCDU.EXE opposite to the REMOTE_VOICES option setting.
-1 The "Autopilot INOP" option might be ignored.
-1 Conditions gleaned from new METAR types could induce a SKID on a dry runway(!).
-1 Ground Deicing might enter a "loop" that might not have an easy exit.
-1 The final entry in the no_scan_folders.txt file was being ignored!
Interfaces
-2 The PMDG 737NGXu is supported for SimConnect-64 simulators.
=================
//// Future Plans
=================
We anticipate the next FSCaptain Build (Beta 1) to be released mid-January.
With luck, after a few Beta Releases we should have the Final Release of 1.8.2 in February or March of 2020.
Once that happens, we can look for the status of any upcoming simulator releases from either Lockheed Martin or Microsoft.
Finally, I will be updating my PC to run Windows 10 just before the last minute (tick tock), so I may be offline or otherwise aggravated during January 2020....
===================
//// Download Links
===================
If you skipped any section of this post just to get to the links, please reconsider and read everything before installing!
You only need one of these downloads for your simulator:
-- Prepar3D 4 takes the SimConnect 64 download.
-- FS2004/FS9 takes the FS2004 download.
-- All others (FSX, P3D2 & P3D3) take the SimConnect 32 download.
{links removed}
One substantial (but fortunately rare!) bug has been addressed (we hope) so that and a few tweaks are the main changes for Alpha 5 - the last Alpha build for FSCaptain 1.8.2.
----We realize that some Captains are hesitant to install "Alpha Test" software, and while we understand the hesitation, do know that this is the version that we (and dozens of other Captains) are now flying.
If you're worried that a change might break things for you, this is actually the best time to test things - there will be a much faster turnaround time for bugs! After you've read the instructions which follow, make a backup of your FSCaptain folder - you must be running nothing older than version 1.8.1 - and install this. If you find a problem, report it (along with log files and any other file we may request) and we should be able to address your report in the next Build of FSCaptain.
That's one reason we wanted to make the Alpha Test phase open to the public. Any problems can be found much easier with more of a testing group participating, and we can then fix those problems quicker.
With new simulators possibly arriving in 2020, we will need to focus on what needs to happen to ensure FSCaptain can run with whatever makes it to market. So FSCaptain 1.8.3 or 1.9.0 or whatever we call it will have new simulator support (plus new features) uppermost.
So let's try and find as many bugs in the next month, so we can look to the future with a solid final release behind us.
Current 1.8.1 Alpha Captains
========================
If you've already installed any of the Alpha releases, you can skip down to the Changelist, Future Plans, and Download Links sections - AFTER you've made another backup of your FSCaptain folder.
You don't need multiple backups... just a backup of your Last Known Good build!
Once you have chosen the Installer for your simulator, just download it, check the README file, and install over your current (and backed-up) FSCaptain!
Reporting Problems
================
We're not self-important enough not to think there may be new problems in this build, or old problems may have taken on a new shape. If something goes wrong and you want to continue testing, make the notes you feel would help us find the problem, take any screenshots that would help illuminate things, and supply any new Admin, FCDU and FSCaptain logfiles. The logs are a key element in our ability to triage problems.
You can either post here in the forum, or by email (see the link in my signature below for clues on how to email us).
Our log files capture such things as your "username on your computer" as well as your "computer's name" and the names of all of your Captains. So if you don't want that to appear in public, we're happy to receive bug reports by email. (Most of our support is done via email, for whatever reason.)
This is a Refresh Build
==================
You MUST also install this on top of the most recent public release of FSCaptain - that's 1.8.1 SP2 - or on top of one of the earlier 1.8.2 Alpha builds. This Alpha Release build only contains the files which have changed since the prior public release.
A Full Backup is Highly Recommended
===============================
For your own convenience, we strongly urge Captains to back up your entire FSCaptain installation prior to installing this! It takes less than a minute, and can guarantee you a stress-free ability to 'roll back' the changes.
I recommend going into Windows Explorer and copying your entire FSCaptain folder from your simulator and pasting it on your Desktop. That's what I do, because it keeps my backup in my "line of sight" in case I need to revert to a previous version.
If something contained in this Alpha Release build is "unhelpful" to your flying habits, you will need to restore your backup over your simulator's FSCaptain folder. (Don't bother with the "Uninstall Program." I've never used it, and I likely never will....)
First, delete everything in your active \FSCaptain\ folder, and copy the contents of your backup \FSCaptain\ folder into the active folder.
If you use the FCDU or FCOM gauges, look inside your restored \FSCaptain\ folder for a folder named \Simulator-Gauges\. Copy the GAU files from that folder into your simulator's \Gauges\ folder.
If you are an FS9/FS2004 Captain, look inside the \FSCaptain\ folder for a folder named \Simulator-Modules\. Copy the FSCaptain.DLL from that folder into your simulator's \Modules\ folder.
HOWEVER, we strongly urge you to remain with the Testing program, even if there are really annoying things. Every bit of feedback that you provide can help us in fixing things. Also, if you're still running Alpha software, it will be much easier for you to upgrade to a newer Alpha / Beta build.
Okay... let's look at the new stuff!
Airport DB changes... and running the Installer
======================================
When you first run any of the FSCaptain 1.8.2 Installers, you will get the prompt to update your airport database. Please have all of your airport sceneries ready to be scanned by MakeRunways and SceneryScanner!! This is a one-time update, all future Beta and Public releases will not need further updates.
The new SceneryScanner supports changes in MakeRunways 4.873 - which is also included in these Installers - and will note all airports in Australia, Canada, New Zealand, and the US with default TA and TL levels - unless specified otherwise in Navdata.
If you are asked by the Installer to overwrite any files, you must allow that to occur. We've updated some Config files, and the "Sound Files" files, and some of these are normally read-only.
Administrator UI changes
======================
We have all but committed to some changes to the appearance of the Administrator during the 1.8.2 Beta timeframe, which is why we're giving any Captain until early January to point out any problems in our intended changes.
So please run your Admin.exe to see the base changes first. Buttons and backgrounds should have changed appearance... looking not so much "Windows 98"... and there is an "empty for now" space between the "OK Cancel Apply" buttons at the bottom of the dialog, and the rest of the dialog.
This is how it appears on my Windows 7 system:
If there is anything on your system that doesn't look "right" (except for the empty space at the bottom of the Administrator dialog) please email us a screenshot, and include your PC's OS version, along with any display options that you feel might be relevant! If we don't hear anything from a test Captain before the end of 2019, we will begin adding new fields to certain configuration tabs.
If our changes are not usable for you, then after you have sent us a screenshot, go to your Install ZIP file and open the file named "Admin - Old UI.zip" and extract the "Admin.exe" file from within. Copy that file into your "\FSCaptain\bin\" folder, overwriting the "Admin.exe" file therein. The code inside is the same, except for the "new UI" bits.
If our initial changes are usable for you, feel free to ignore the "Admin - Old UI.zip" folder.
==================================================
//// CHANGELIST FOR FSCAPTAIN 1.8.2 Alpha Releases
==================================================
Each item below begins with an numeric indicator of the its release version: "-1" is Alpha 1, "-2" is Alpha 2, etc. (Alpha 4 items are also bolded for easier visual scanning.)
New Features
=============
-4 A new option - DISPATCH_REQUIRES_MIN_FUEL - can be set to prevent you from Dispatching a flight in the Administrator with less fuel than is needed for:
= 1: Aircraft Minimum + Taxi + Trip + Reserve + Holding.
= 2: Aircraft Minimum + Taxi + Trip.
= 1: Aircraft Minimum + Taxi + Trip + Reserve + Holding.
= 2: Aircraft Minimum + Taxi + Trip.
The default value is 0, which will not try to impose minimum fuel restrictions.
-3 During your 'rollout' phase, the FCDU will display both your vertical landing speed and the associated GForce. For a good landing this line will be in green; in yellow for an 'okay but not hard' landing; and in red should either value be deemed as 'too hard.'
-2 An option to alter the acceptable landing vertical speed rate for a "PAX Nice Landing" bonus has been added.
The option's name is LANDING_RATE_NICE and currently accepts four values. You can choose to maintain the 0-200 fpm range, or use 100-300, 200-400, or 200-500.
-1 After reports of FS9 company logs not updating after a flight, a set of checks have been added to both the FCDU and the Administrator. If a write command for the company log (and for the ADMIN and FCDU process logs) fails, a message will appear on screen. This would allow those affected to pause the simulator and check their PC systems for any unexpected system change, such as an anti-virus program that has "woken from a sleeping state."
-1 In addition, company logs are now copied in place before a write command executes. For example, "ACME.log" will be copied to "Acme.log_backup" before it is rewritten.
-1 There is a new option - ALLOW_BYPASS_OF_READYTO - which will enable the FCDU's LSK1R to act as an 'emergency bypass' if you become stuck on the Load Confirm (#42), Ready to Load (#20), Load Progress (#21), Load Complete (#22), or Arrival (#29) screens with any balky exit, engine, or parking brake. After this is enabled, when you come across a 'guarded against condition' LSK1R will have a command caret ">" to denote a bypass is available.
"RTL>" for Ready to Load.
"RTF>" for Ready to Fly.
"RTU>" for Ready to Unload.
-1 There is a new option AUTOSCAN_AIRCRAFT_ON_START which can be used to bypass the "SimObjects check" that the Administrator normally does when it is launched. If "autoscan" is disabled, your aircraft data will be read from our new database located in "\FSCaptain\Aircraft\MyAircraft.bin".
-1 If you choose that option, you need a way to have the Administrator rescan your aircraft. Look on the Options for All Airlines tab of the Administrator to "Rescan Aircraft". Clicking this button will perform a scan of SimObject folders for flyable aircraft, and create/update a local database in your \FSCaptain\Aircraft\ folder.
-1 A new file is generated when your aircraft are scanned to give you a list of all your aircraft liveries - divided into "Aircraft.cfg locations" and "Aircraft Type" values. Look for "MyLiveries.csv" in your FSCaptain\Aircraft folder.
-1 There is a new set of configuration files to support airports whose airport names have changed from BGL-derived names. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of both files.
The file names are "new-name_fsc.txt" and "new-name_user.txt". The "_fsc" file contains a few entries which we have verified and will update throughout Full, Refresh and Fixpack files. Do note that the "_user" file is intended for your use and will not be updated - you can add entires for airports which you want used. Any entry in the "_user" file will override any entry in the "_fsc" file. Empty "_user" entries, such as "KBUR:", will negate any entry in "_fsc" files.
-1 There is a new set of configuration files to support specified Airline Parking Codes at any Parking Spot in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
The General file is located at \FSCaptain\Config\Preferred_Parking.txt, and Airline-specific files can be placed in \FSCaptain\Airlines\ using the airline's short name followed by "_Parking.txt". (E.g., "ACME_Parking.txt")
Please check the General file for the schema/format of the data.-1 There is a new set of configuration files to support General or Airline-specific Preferred Alternate airports for any Destination Airport in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
The General file is located at \FSCaptain\Config\Preferred_Alternates.txt, and Airline-specific files can be placed in \FSCaptain\Airlines\ using the airline's short name followed by "_Alternates.txt". (E.g., "ACME_Alternates.txt")
Please check the General file for the schema/format of the data.-1 There is a new set of configuration files to support specific taxi-out and taxi-in times for any Airport in your simulator. A full description of this is in the User Guide - in Appendix 5. The schema of the configuration data is located in the header of the General file.
The General file is located at \FSCaptain\Config\Ground_Times.txt, and Airline-specific files can be placed in \FSCaptain\Airlines\ using the airline's short name followed by "_Ground_Times.txt". (E.g., "ACME_Ground_Times.txt")
Please check the General file for the schema/format of the data.If you have questions about any of these new Config files, please email us, or post your questions in the FSCaptain forum!!
Changes
=========
-5 The "Nearest DME" value in the Airport and Runway Data section of your Dispatch Release now excludes NDB navaids. Also, the distance from the Airport Reference Point to the DME source is now listed.
-5 The Airport and Runway Data section of your Dispatch Release now contains the "Flight Rules" for each airport - VFR, MVFR, IFR, LIFR, CAT I, CAT II, or CAT III.
-3 The current turbulence value on the Flight Progress display will now only appear in green if you are 10% below the current "barber pole" speed and/or your flight phase's default speed.-5 The Airport and Runway Data section of your Dispatch Release now contains the "Flight Rules" for each airport - VFR, MVFR, IFR, LIFR, CAT I, CAT II, or CAT III.
If in excess of the calculated safe speed, the current turbulence level is 'none' the line will display in cyan. If in 'light' to 'heavy' the line will be white. If 'severe' the line will be in red.
If your flight encounters 'light' or greater turbulence, lower your IAS until this value is displayed in green to maintain your chance for a 'smooth flight' PAX comment, and to reduce possible aircraft frame damage!
In our next release, you should notice the ability to apply actual Vra values for aircraft.
-3 METAR parsing now ignores "FMhhmm" values noticed in some Australian METARs. In the past this has led to incorrect station weather reporting!
-2 The PLN Waypoints screen will now display "Expected Altitudes" for waypoints on the first page if they are substantially different from your current altitude (so only in Climb and Descent). This can greatly help you "hit your targets" on SIDs and STARs.
-2 Fuel values in Gallons can now be entered using either "....GA" or "....GL" as the type designator.
-2 If PAX see Ground Ice on the aircraft frame before takeoff, you will no longer be eligible for a "PAX Smooth Flight" bonus. (Because they would be worried during the flight.)
-2 If you've received Approach Clearance, the TL value on the FCDU will remain green - indicating you're not violating company policy.
-2 The "<REQUEST" LSK on the FCDU's Communication screen has been changed to "<DISPATCH" to better indicate *to* *whom* you are making the request.
-1 If an FSLabs A320 series aircraft is detected in use, FSCaptain will not set the GSX Passengers and Crew values, since the aircraft does that itself.
-1 The FCDU.EXE should now remotely play all audios without "stepping on" already playing audios!
-1 If you set the option ALLOW_UNPROFESSIONAL_AUDIOS=1, some of FO_Trav's colorful audios will not play.
You still may hear him make the comment "Smooth Like Butter" on a very nice landing since that's what his CFI said on Trav's first landing.-1 Captains who make PAX flights outside of Economic Mode with a Load Factor of 90 to 100 should see a marked increase of PAX - a 100 Load Factor should see nearly all seats full! (This does require testing and tweaks during the Alpha Testing process.)
-1 The Dispatch Release now indicates both the Field Elevation and current Density Altitude for your flight's airports.
-1 The Upper Winds display in the FCDU will now indicate levels in grey which are below you when you are climbing, or above you when you are in descent.
-1 The option TAXIOUT_FAILURES_ALLOWED has been renamed and several 'sibling' options have been added so you can disable a/c system failures in these modes:
FAILURES_ALLOWED_CLIMBOUT=1 ; 1 = Failures are allowed to occur during climbout (default). 0 = No failures can occur while climbing to TOC.
FAILURES_ALLOWED_DESCENT=1 ; 1 = Failures are allowed to occur during descent (default). 0 = No failures can occur after TOD.
FAILURES_ALLOWED_ENROUTE=1 ; 1 = Failures are allowed to occur while enroute (default). 0 = No failures can occur between TOC and TOD.
FAILURES_ALLOWED_TAXIIN=1 ; 1 = Failures are allowed to occur after landing (default). 0 = No failures can occur after landing.
FAILURES_ALLOWED_TAXIOUT=1 ; 1 = Failures are allowed to occur during taxiout (default). 0 = No failures can occur before any takeoff.
By default, all of these options are enabled (unless you have previously disabled "TAXIOUT_FAILURES").
These options only apply to aircraft system failures. Other incidents - such as a cabin emergency, bird strike, cargo shift, and blown tires - remain unchanged.
-1 The DIVERT option in the FCDU has a new option. While you can easily end a flight by Diverting to your Alternate Airport (or to any other Airport you wish), doing so will end your flight.
Now you can choose to DIVERT for a REFUEL STOP and all TOC/TOD TA/TL LANDL values will be expected. (Needs full testing of all "cases".)
-1 If the MakeRunways data (or your Parking Codes data) has captured an airport's jetway-equipped parking spots, they will be flagged as "/J" on the Administrator's Parking Selector.
-1 Aircraft can now have their Cabin Temperature, Galley Power, and Window Heat systems marked as INOP. (This will give Captains the ability to ignore these systems in case of an aircraft developers' update breaking the current FSCaptain interface.)
-1 When using the Windows' File Selector to pick a PLN file in the Administrator, new "filters" have been added to allow you to easily filter these types [Examples given for a KSEA to KATL flight.]
All Departure airport (ICAO) --> Destination airport (ICAO) PLN files. [*KSEA*KATL*.PLN]
All Departure airport (ICAO) PLN files. [*KSEA*.PLN] -- These are all files which contain the Departure ICAO... including as Destination!
All Destination airport (ICAO) PLN files. [*KATL*.PLN] -- These are all files which contain the Destination ICAO... including as Departure!
All PLN files. [*.PLN] -- This was the previous (and only) filter used by the Administrator.
All files. [*.*]
-1 Minor speed improvements when searching for flights in the Administrator.
-1 "Standing Lenticular clouds" (METAR codes "ACSL" "SCSL" "CCSL") are now noted as "Significant Weather - CAUTION" for an airport. Their presence - usually in mountainous areas - is indicative of turbulent air.
-1 "Official" Private and Military airports in Australia and New Zealand have been updated.
Bugs
=====
-5 Earlier Alpha Builds may have not written a correct "_preflight" file containing important flight information.
-4 GSX L2 was not noticed in earlier Alpha Releases!!
-4 A PAX flight with a 'no service' rule called could render a 'bad service' penalty when going IN. (Very rarely, but still....)
-2 An airport without a METAR would give a incorrect Density Altitude value, as well as incorrect Takeoff Roll and Landing Distance values.
-2 A coding error would flood your FCDU log with "Transition Level" notices if your TA was below your Landing Light Altitude, and while you were below the Landing Light Altitude.
-2 Two errors in reading "non-pound Fuel values" in the Administrator's Flight Dispatch screen has been fixed.
-1 A second "Snack Service" would begin earlier than expected.
-1 When the Administrator is used to Dispatch multi-leg flights, the Load Plan from the first leg would be copied to subsequent legs. When flown, those legs would generate correct Load Plans at the time of loading, so this was only a "cosmetic bug."
-1 When dispatching multi-leg flights, the "Latest Dispatch Release" will now be for the 'first flight leg' and not the 'last flight leg.'
-1 Airline / Aircraft specific safety announcements were being played by the FCDU.EXE opposite to the REMOTE_VOICES option setting.
-1 The "Autopilot INOP" option might be ignored.
-1 Conditions gleaned from new METAR types could induce a SKID on a dry runway(!).
-1 Ground Deicing might enter a "loop" that might not have an easy exit.
-1 The final entry in the no_scan_folders.txt file was being ignored!
Interfaces
=========
-5 The Aerosoft A300 Professional is supported for SimConnect-64 simulators.
-5 The Aerosoft CRJ Professional is supported for SimConnect-64 simulators.
-5 The VirtualCol Embraer Version 4 series is now supported.
-4 The Simcheck A300 is now supported.
-2 The VirtualCol A220 is now supported.
-2 The PMDG 737NGXu is supported for SimConnect-64 simulators.
-1 The JustFlight 757 "Freemium" is now supported for SimConnect-32 simulators.
-1 The QualityWings 787-10 model is now supported for SimConnect-32 and -64 simulators.
=================
//// Future Plans
=================
Unless a new bug is discovered, we are in a 'code freeze' and our efforts will soon turn to updating documentation and preparing for new Full and Fixpack Installers.
We have not heard any negative feedback to the Administrator UI changes, so we are almost ready to proceed with the initial "baked-in changes" that a slightly larger footprint allows us. But since the holiday season always sees an influx of new Captains, we've decided to hold off for a few more weeks to ensure a larger pool of testers.
We anticipate the next FSCaptain Build (Beta 1) to be released mid-January.
With luck, after a few Beta Releases we should have the Final Release of 1.8.2 in February or March of 2020.
Once that happens, we can look for the status of any upcoming simulator releases from either Lockheed Martin or Microsoft.
Finally, I will be updating my PC to run Windows 10 just before the last minute (tick tock), so I may be offline or otherwise aggravated during January 2020....
===================
//// Download Links
===================
If you skipped any section of this post just to get to the links, please reconsider and read everything before installing!
You only need one of these downloads for your simulator:
-- Prepar3D 4 takes the SimConnect 64 download.
-- FS2004/FS9 takes the FS2004 download.
-- All others (FSX, P3D2 & P3D3) take the SimConnect 32 download.
{links removed}
That's all for now. Happy flying with ACME!
Best regards,