Post by Travis on Dec 7, 2014 18:15:26 GMT -5
We have spent a lot of time working on bugs within FSCaptain, to the point where we have included enough new features (we were bored) that we feel we should now give our release a new version number... so since FSCaptain 1.6.0 is releasing, I want to encourage all current Captains who wish to participate in our Public Beta to do two things:
1. Make a backup of your entire \FSCaptain\ folder - a simple Copy and Paste from Windows Explorer will be good enough. Doing this will ensure that your current Company History will remain intact should we have introduced an error into the logic.
2. Install the Fixpack to a test folder... something like C:\CheckOutFSC160\. The Fixpack would create three folders within the extract folder (\FSCaptain\, \Gauges\, and \Modules\), plus add the latest MakeRunways.exe and an uninstaller to the extract folder. The content of the extract folder could be copied into your flight simulator(s) root folder(s) as is, but you may want to check the files within the \FSCaptain\Aircraft\ folders to make sure they do not overwrite any special modifications that you may have made.
The reason for this caution is that we have modified several aircraft configuration & load map files used by some of the aircraft which now have internal-to-FSCaptain interfaces. We've greatly enhanced the logging, so after each flight take a look at the FCDU.log that was generated and if you see that you have an internal and an XML interface both running, you can safely disable the XML interface by removing it from your appropriate panel.cfg file.
Download the current public beta fixpack release of FSCaptain here.
Happy flying!!
Here is the updated area of the README file. (Items new to 1.6.0 are in bold.)
README for the Fixpack for FSCaptain version 01.06.00 DEC/08/2014
---------------------------------------------------------------------------------------------
This is a cumulative Fixpack that will upgrade any previous release version of FSCaptain to the latest version.
=====================================================================================
To be safe, always make a copy of your FSCaptain folder before installing any fixpack.
=====================================================================================
To install simply execute the enclosed FSCaptain_Fixpack_10600.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 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 create an \FSCaptain\ folder and the entire data structure for you in the folder that you specify.
WARNING. Configuration Replacement as of 1.5.0.
Starting with version 1.5.0, FSCaptain contains a changed sound.cfg file because the sound options have changed. It will replace the sound.cfg file in the FSCaptain\Config folder. If you have changed your sound.cfg to add any of your own MP3 music files, you may want to back up your sound.cfg, copy the section that lists your modified playlists, and paste it into the new sound config replacing the existing playlist. The format of the playlist is compatible with previous releases. This release also contains aircraft configurations and load maps for popular aircraft that have been added to the standard FSCaptain collection since release. If you have your own individual copy of any of these configurations or load maps another with the same name in this distribution could overwrite your custom one. Again, to be safe, make a copy of your FSCaptain folder before installing this release.
WARNING. Version match for Flights and Interfaces.
To insure that flights have the correct information to start and be monitored successfully, in this and all subsequent FSCaptain releases the FCDU/FCOM will only acknowledge flights booked in an Administrator at the same revision level. This means if you have any opened, booked flights on your log before you install this new revision, you should fly them with the previous revision, or erase and re-book them once you have installed this one.
Also, with 1.5.1, the external (XML) interfaces cannot override the internal (ACARS) interfaces unless the XML interfaces have a certain code which signifies the XML interface is newer than the ACARS interface. (This feature allows old XML interfaces to be ignored in lieu of newer ACARS interfaces.)
WARNING. FCOM to be depreciated.
The enhanced structural icing simulation will be ignored in aircraft equipped with the FCOM even if the option is checked in the Weather Options page. It will only function in the FCDU. In the future, new features which require major user interface changes WILL NOT be implemented in the older FCOM. We urge airlines using the ACME Dispatch System to upgrade to the newer equipment as soon as practical.
These enhancements are included with version 1.05.01:
-----------------------------------------------------
- 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".
- 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.
- More and varied cargo items will be provided, depending on your aircraft size, and departure location. (See "NEW 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 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 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 File" 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 follow strict ground de-icing procedures (not being able to go OUT with any ground ice on their aircraft), you can enable such by setting this value:
STRICT_DEICE_PROCS=1 ; 1 = Enables STRICT Ground De-Icing procedures *overriding HAZARDDEICE=0*
- 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
+ CaptainSim 777
+ feelThere EMB Series
+ feelThere ERJ Series
+ feelThere Phenom 100
+ Majestic Q-400
+ QualityWings BA46 (146 & Avro)
+ QualityWings 757
+ RAZBAM Metroliner III
+ RealAir Duke Turbine
These problems are fixed in 1.05.01:
------------------------------------
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 are currently 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 which should be used for larger aircraft.