README for the Fixpack for FSCaptain version 01.03.00 12/19/2011 -------------------------------------------------------------------------------------------- This is a cumulative Fixpack that will upgrade any previous release version of FSCaptain to the latest version. (It will not upgrade any pre-1.00 beta version it is required that you install FSCaptain 1.00.00 (or a later version) before installing this Fixpack if you have a pre-1.00 beta version.) To install simply execute the inclosed FSCaptain_Fixpack_10300.exe. It will locate your FS9 folder for you but you may browse to another folder if you wish. This also works for the FSX version of FSCaptain as well -- simply browse to your FSX root folder before installing. VERY IMPORTANT WARNING!!! 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 create an FSCaptain folder and the entire data structure for you in the FS root folder. Note: The FCOM reference manual is still being updated and will be distributed in a Fixpack in the near future. Extra Installation Steps - PLEASE READ. -------------------------------------- In order for FSCaptain to recognize gates at your airports, you must use the "Rebuild Airports Database" option on the Options for All Airlines tab of the Administrator. If you change or add or remove Airports from your scenery database you must again rebuild the databases if the gate configuration of any airport has changed, otherwise FSCaptain will believe the gates are in the positions they were when the databases were last built. This version of FSCaptain uses the external program "MakeRwys.exe" to build part of the Parking database. As a part of the installation a copy of this program is placed in your Flight Simulator folder. It will, when it is run, built its database files there. This same program and the same data files are used as a part of the Radar Contact product and others. There is no conflict between these two, FSCaptain will use (and rebuild) the same text files that Radar Contact does. These enhancements are included with 1.03.00: --------------------------------------------- - The "Hazard Package" is included which will detect certain dangerous conditions and make the consequences realistic in ways that Flight Simulator failed to do. Specifically, wet or icy runways and taxiways are now slippery. Icing can flameout a jet engine. Thunderstorms can now invoke extreme turbulence. None of these will happen without warning from either Dispatch or your First Officer, or both. The runway conditions are invoked from the reported weather in your Weather Source and may or may not match the visuals in FS. Thunderstorms and engine icing are detected from present conditions and should match the visuals. A new section of the "Weather Options" dialog available from the Options for All Airlines in the Administrator will allow you to switch these danger enhancements on or off. They are ON by default. - The loading philosophy of the FCOM has been modified such that it no longer will hold up the progress of the flight until the payload in the aircraft matches the expected weight from the manifest. You may proceed to a new "Reconciliation" page where you can made adjustments and specify whether the manifest or the aircraft are correct if they differ. - Several FSCaptain interfaces for popular add-on airplanes are available in the FCOMPNL folder that's loaded into your Gauges folder by the installer. Check out the README_Interfaces.txt for more information. The FCOMPNL folder is full of extras you can add to panels to enhance your FSCaptain experience. - You may now interrupt the auto-loading process at any time and proceed with the flight, or return to the start page. - You may enter the number of passengers at any time during a non-autoload operation, regardless of whether you selected the "PAX Prompt" option in the Administrator. - Your First Officer is now much more involved in any flight made in Offline Mode. If you are flying a jet he will now make the 60 knots call on landing and remind you to stow the reversers if they are still down. Some other new cautions are also included. - An option to suspend the 250 knot speed limit under 10,000 feet is included. - A new "Dispatch Request" page is accessible from the Communications page, which allows the above request and seven others. - The time beween the Flight Attendants' welcome message and the safety briefing has been reduced. - The verbiage associated with the F9 key is now consistently "Return" to return to the previous page, and "Cancel" to cancel some request, or the whole flight. - A new "start time" option is available in the Flight Dispatch tab of the Administrator. To invoke this option put the time in as a 4 digit local time in the "Time Constraint" field with a dash in front of it, like this: -1130 for 11:30 local time. When you do this, but leave the departure airport blank in order to receive an assignment from the airline, your assignment will be within 2 hours of the time specified in the Time Constraint. You cannot use this feature unless you leave the departure airport field blank. - A new FCOM (#66) page will allow the user to test certain important Flight Simulator signals (passenger signs, NAV and landing lights, and the anti- and de-icing systems) to see if they are compatible with the aircraft the FCOM is installed in. The new page is accessible using F1 from the Interface page. - A new option on the Aircraft configuration will allow you to specify that an airplane does not have working Engine Anti-Ice. There problems are fixed in 1.03.00: ----------------------------------- 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 cancelling 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 weatehr 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.0 These problems were fixed in 1.02.00: ------------------------------------ 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 jumpeats 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.01.06: ------------------------------------ ID#0083: PAX counts not random in successive invocations of the Admin program. ID#0084: FCOM with 'Supress 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.01.05: ------------------------------------ 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.01.04: ------------------------------------ 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.01.03: ---------------------------------- ID#0048: Airport database rebuild sometimes fails and leaves only a few airports rebuilt. These Problems were fixed in 01.01.02: -------------------------------------- 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.01.01: ------------------------------------- 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.01.00: ------------------------------------- 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.00.04: ------------------------------------ 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.00.03: ------------------------------------ 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.00.02: ------------------------------------ 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.00.01: ------------------------------------- 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.