Upcoming 1.6.3 Beta trial

[Travis]

Captains,

The development of the next version of FSCaptain (referred to as "1.6.3") has been held up for the past few months due mostly to a Great Big Huge Whopping CTD Bug (#74); Or as normal humans would say, "@*%^?  !&#@!  ;*#@*%#@!!"

The bug manifested itself in a spectacular way - if the aircraft used in your FSX default flight had an FCDU or FCOM gauge installed, FSX would crash before the start-up screen appeared.  P3D was unaffected.  And Peter discovered two weeks ago that good old FS9 would crash after exiting the start up screen. (Which finally gave us a way to see what was happening.)

We had cautioned early Alpha testers to remove the gauge from their default FSX flight aircraft, while we tried attaching debuggers to FSX after it had started.  That led to miserable failures which lasted since late February....

That's behind us now: since Peter found a way for Dutch to finally figure out what was happening... which allowed Dutch to fix it last week... we have been busy tidying up small things....

Since I (again, not a primary C++ coder) was fairly useless in the Great Bug Hunt, I decided to add a few new things to FSCaptain while Dutch searched for the Great Big Huge Whopping CTD Bug.

What follows is a list of new and changed things that I was able to slip into FSCaptain while Dutch & Peter were otherwise occupied.  (Shhh... don't tell them.)

This version of FSCaptain, while designated as 1.6.3, includes elements that we had deemed to appear in 1.7.0 or 1.8.0, so please feel free to think of this version as comparable to what we had intended to be available for FSCaptain 1.8.0.

We anticipate the Beta Test phase to begin May 25th or 26th.    As of 1506 PDT on the 25th, there's only one audio issue left to check....

Starting points

If you have an existing career that you wish to retain, it is strongly advised that you make a backup copy of your 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 new to Beta Testing, please test things with short flights at first to ensure the simple things are working for you. There's no need to book a ten-hour flight to only find out that it wasn't recorded [for some dog-gone able technical reason]!

New GaugeSound.dll

FSCaptain 1.6.3 uses a new gaugesound.dll - it plays through the simulator, not through Windows.
  

• Advantage - will offer better performance, "panning" for future voicepacks, as well as layered tracks.
• Disadvantage - will need FS9, FSX or P3D to be "the foreground window" to hear sound.

New Airport Database Format

FSCaptain now 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," "military," "Customs status," and "re-IDed" airports. (An airport which has changed its identifiers.)

Trying to use an old airport database with this version will cause FSCaptain to ask to rebuild your database. Trying to use a new airport database with older versions... will likely confuse older versions. So don't do that.

FSCaptain now uses a new utility program called "SceneryScanner" to build this new database. This program uses 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 us with your system's specifications!)

Results from earlier in the 1.6.3 Alpha testing has us reluctant to deny takeoff for any reason tied to the Departure Airport's layout (runway length, type, etc.)  As currently is, if an airport does not have a runway of sufficient length - and of an appropriate type - no Captain would be allowed to take off.  We are currently debating an optional value which would bypass such a restriction....

As mentioned earlier, the Administrator will offer to auto-rebuild the Airports Database if it cannot find a database that's properly configured.

SceneryScanner will also output extra files that aren't currently 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.

The airport.cfg file that is in the Beta release download represents the default sceneries from P3D 2.5. We suggest that you run the Rebuild Airports Database function once you've installed the Beta files.

You can do so like this: Run the Admin.exe program, go to the "Options for All Airlines" tab and click the "Rebuild Airport Database" button - you will see a new checkbox that is labeled "Run Makerwys as part of Rebuild".  Leave that box checked for your first rebuild.  Makerwys will run, taking a few moments to build data files, and you will be prompted to close Makerwys when it has finished.  At that point, SceneryScanner will auto-run in a "Command Prompt" window.  SceneryScanner will automatically close when it is finished.

VC++ 2013 Libraries

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: 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 Beta 1, go back and download the x64 version.)

But if we distribute them with Dutch as the builder... then anyone who can run 1.6.2 should have no problem.

Dutch has build the Beta Package, but I'll leave this qualification in place just in case some Captains would experience this.

Testing Notes on New Optional Items

There are several new features that require each Captain to modify various options file to enable the feature in question.

• 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.
• A new Hazard Pack option allows brakes to be monitored for abuse.  In 1.6.3, engaging the parking brakes while at a groundspeed of over 20kts will fail the brakes and cause gear damage.  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.
• 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.
• A new option will prohibit international flights to airports that are known not to have Customs capabilities.  Our dataset for US airports is very comprehensive.  Our dataset for other airports may 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.
• 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.

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.6.3, 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.
• NOTAMs that 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's audio files will be included with the full release of 1.6.3.  She is a no-nonsense American English FA.  (Please!... don't get on her bad side!)
• FA_Regina - Regina's audio files will be included with the full release of 1.6.3.  She is a multi-lingual FA (English and German).
• FO_Peter - Peters audio files will be included with the full release of 1.6.3.  He's Canadian, but speaks German.  That makes for some interesting times in the crew lounges.
• 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.

Four of these new features (private-use airports, closed airports, airports with new IDs, et aéroports sans Douanes) are controlled by new data files in the \FSCaptain\Config\ folder.  These files will appear in pairs, one ending in "_fsc.txt" and the other in "_user.txt".  The _fsc.txt files represent our best information, and will be distributed as read-only.  The _user.txt files are supplied for each Captain to customize to their own specifications.  So if you were to discover that airport "WXYZ" has closed and if you want to represent such in your FSCaptain instance, you could enter that into your "closed_user.txt" and then use the Administrator to Rebuild your Airport Database, and airport WXYZ would then be "closed" for operations.

Testing Notes on Changed Items

• Multi-leg flights now have variable payloads & manifest items.
• Opus TAF is supported.  Opus upper winds will be supported in a future version.
• 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.  (This is known as "The Travis Rule" as commercial flights are conducted at KSUU - Travis AFB.)
• 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.
• 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 rarer 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.  Improvements will continue as time progresses.
• Lots of changes to logging.
• "Oil-treated" runways on third-party airports are now considered as "hard surfaces."  This will mostly affect Orbx sceneries which sometimes substitute "oil-treated" runways for what are in real life "asphalt" runways.
• Ground ice accumulation from "cold soaked wings" is recognized more effectively.

Testing Notes on Interface Changes

• The GSX interface will 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 interface.
• The Majestic Q-400 now reports cabin and brake temperatures. Engage the parking brake and the temps will hold at 180C.  Otherwise the brakes will cool down to the ambient temperature.  There is no fault in abusing these brakes - yet. :-)
• There is a built-in interface for the Carenado Citation.
• There is a built-in interface for the Digital Aviation Fokker.
• There is a built-in interface for the Flight One ATR-72.
• There is a correction and an addition to the QualityWings BA46 interface.
• There is a correction to the CaptainSim 707 interface.
• The Carenado C208EX 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 remove them when you start your engines....
  

Testing Notes on Bugs

• 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. (Dutch to test and vett.)
• 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.  (The Great Big Huge Whopping CTD Bug.)
• Bug 79 - Administrator fails to update dll.xml if FSCaptain is 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."