README for the Fixpack for FSCaptain version 01.01.03 07/07/2010 ----------------------------------------------------------------------------------------- This is a cumulative Fixpack that will upgrade any previous release version of FSCaptain to the latest version. (It will not upgrade any beta version it is required that you install FSCaptain 1.00.00 (or a later version) before installing this Fixpack if you have a beta version.) To install, execute the inclosed FSCaptain_Fixpack_10103.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. Known Issues Still Awaiting Resolution -------------------------------------- * Under FSX, when the FCOM is located on a 2nd or 3rd screen in a multi-screen setup, the keyboard capture function does not work properly. Keys that should be blocked from getting through to FSX get through. This does not happen if you locate the FCOM on the main screen. * Under FSX, when you select "End Flight" from the FSX menu (or press escape) the FCOM does not stop all music and background sounds every time. You can work around this by stopping the sounds yourself if your passengers are de-planing by using the "F4=Stop Music" key which will stop all music and background sounds. You can also elect to uncheck the option "Enable Background Sounds" in the Options for All Airlines tab in the Administrator. This problem is 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 Enhancements were included in 1.01.00: -------------------------------------------- The Administrator has a new tab on it called "Flight Dispatch". On this tab you can browse available FSCaptain flights and select the one you want to fly, then enter a planning phase where you retrieve (or enter) weather information and optionally an MSFS flight plan, and the program will use these to determine a more accurate ETE and fuel burn than the older facilities in the FCOM (which are still there). You can commit the flight to the log from this dispatch planner and then enter Flight Simulator at the appropriate airport in the scheduled aircraft and when you login to the FCOM you'll see your flight all ready to go. From that point you fly normally as you usually do in FSCaptain. Note that this removes all timing considerations from scheduled flights. Once you commit to a scheduled flight with this system you can start it anytime you enter FS at the scheduled airport in the correct aircraft type. When you browse for flights you will be required to enter an aircraft type which will be selected from a drop-down list. A list of all your installed aircraft types is included on the list -- but ONLY if they have an FSCaptain aircraft characteristics file for their type code. The dispatch planner can't work with aircraft which aren't defined in FSCaptain. The weather information is obtained from two sources: 1) If flight simulator is running at the time you run the Administrator, and the program is run outside Flight Simulator (not from the FSCaptain menu item) then current weather information can be retrieved from the current simulator weather. (This will not work from within the sim, and it won't work if you are running FS2004 without a registered copy of FSUIPC.) 2) The second source is the internet, with the first choice being the Jeppeson onlien weather website and a second choice being weather.noaa.gov. If attempts to retrieve current weather from a running copy of flight simulator fail metars and winds aloft will be downloaded from the internet sources. The new tab is fully documented in the User's Guide and there is some new information there in appendix 4. Also, a new description of the Cruise Speed data item on the aircraft characteristics tab which you should read if you set up aircraft characteristics -- the definition of this item has changed somewhat due to the new way ETE is calculated. The formulas used to compute ETE and fuel burn are now more comprehensive and sophisticated. They include adjustments for altitude flown as well as extrapolation of winds data figured on each leg of a flight plan. Part of the beta testing is to see how accurate they really are. Please report all issues on the forums on in an email to me. The forums are preferable since everyone can see and benefit from things discussed there. 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 Enhancements were included in 1.00.04: ------------------------------------------- 1) The number of payload stations accessible for auto-loading in the Administrator has be increased from 20 to 60. This is the maximum number of stations that can be loaded using the FSUIPC program. 2) A group of new options on both the 'Options for All Airlines' tab in the Administrator and the 'Load Maps' tab allow for parts of the FSCaptain system to be suppressed or modified for greater compatibility with other add-ons such as aircraft-specific payload and fuel loader programs, FS2Crew, and FSPassengers. Documentation for the new options is in the User's Guide and the FCOM Reference Manual. 3) A new set of options on the 'Options for All Airlines' tab of the Administrator allow you to specify how fast or slow passengers board any aircraft. Again documentation is in the User's Guide. 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.