FSCaptain Release 1.4.5 BETA is now available

[Dutch Owen]

Greetings Captains,

FSCaptain 1.4.5 BETA is now available at this link:

www.fscaptain.net/downloads/FSCaptain_Fixpack_145B1.zip

Install it like any Fixpack. This is BETA software so use caution! The official README is below, but here are some notes for you.

The new release contains new support for the Majestic Q-400, which required extensive additions to the FSCaptain interface to accomplish. The new interface is in the usual place, FCOMPNL as "InterfaceMJQ400.xml", install it like any interface and it should simply work. This new version must be used, replace any previous version you may have been trying - it will not work.

Support for many popular add-ons has been brought into the system, and so an external interface is no longer required for the following aircraft simulations: PMDG 737, 747, MD-11, and JS-4100; the CoolSky DC-9, Captain Sim 707, 727, and 737, Leonardo Maddog MD-80, and the iFly 737. If you are using an external interface for one of these, we recommend you remove it from panel.cfg. If you don't you'll get a message reminding you that the internal interface is overridden by an external one. The old external xml interfaces for these aircraft are still included in FCOMPNL but are no longer supported and will not be updated. Any official changes will be made to the internal versions only.

A major new feature is included but disabled by default: "Precision loading". This is the ability to define load stations with much more precision. The feature is disabled by default because we don't have a ton of confidence in it yet. If you are the adventurous type you can enable it and test it for us. To enable it, include the line NODETAILLOAD=0 in your Options.cfg file (in the FSCaptain\Config folder.)

To see an example of the new coding, take a look at the load map for the Q-400, named mjc8q400.cfg. You will see four new fields on the load stations: type, unit, size and name. The type codes are: C for Crew, Y or J for passengers, G for General Cargo. The unit field contains the unit size in pounds, and the units field contains the maximum number of units allowable in the station. The name describes what each unit is.

There are some rules to follow if you choose to include these new fields on your airplane. First, if you code any of the new fields on a row you must code all rows with the new fields. Another common gotcha is for passenger configurations you must allow enough cargo space (type G) to accommodate at least 50 pounds per passenger with all PAX loaded.

Hope you enjoy the new release.

Dutch



From the official README:


These enhancements are included with version 1.04.05:
-----------------------------------------------------

- Support for many popular add-ons are now built-in as internal interfaces in the FCDU. Automatic support now includes the PMDG 737, 747, MD-11, and JS-4100; the CoolSky DC-9, Captain Sim 707, 727, and 737, Leonardo Maddog MD-80, and the iFly 737. More user-installable interfaces are provided in the FCOMPNL folder (in Gauges), see the README_Interfaces.txt there for more details.

- A new set of loap map parameters will allow you to precisely configure the way any aircraft is loaded. The new features are shown on the load map. This feature is disabled by default in this version. To enable it, include this line in the Options.cfg file (in the FSCaptain\Config folder): NODETAILLOAD=0


These problems are fixed in 1.04.05:
------------------------------------

ID#0208: Changing the airline maintenance option clears some other options buttons.
ID#0209: FA will say "Cleared for Takeoff" before the safety briefing if the switch is toggled.
ID#0210: Arrival sometimes misinterpreted as a 'refueling stop' if another airport is too close.
ID#0211: Fuel on release flight plan section is always pounds.
ID#0213: When a flight spans midnight (zulu) on the last day of a leap year the ETE calculation stops.
ID#0214: When FSUIPC Mouselook is selected and FSCaptain.dll is loaded control of the mouse cursor is lost.
ID#0215: It is very difficult if not impossible to match NGX Pax loads to the numbers FSCaptain generates.
ID#0218: Unable to enter -1 to mean 'no service' when revising a flight.'
ID#0220: "Winds Aloft" falsely reported as not available when data source is Active Sky product.

[alpha117]

Many Thanks

Clive

[antonmorse]

Many thanks for this update

Keith

[Travis]

The "Detailed Load Maps" can be tricky, that's why they're off by default. But when they work... they work a treat.

I keep thinking of piddling around with the old BAC 1-11, but since they only have one station by default... yeesh, the CoG really can get off with that one....

[Aviator992]

I'm having issues whenever I have jumpseaters on my cargo runs. When theres not a jump seater, everything works great! As soon as I get a PAX though (can only hold 1), things get screwy... Even though I have the captain seat set to "C" with a weight of 165 (which its supposed to load every flight), it loads things evenly across stations with the same priority. This means its not loading that 165 in the captain seat, but instead an amount divided by my other stations with that same priority. I think the absolute best thing would be to specify a seat as being a jumpseat, rather than it just dividing the weight of that jumpseater between all the "G" stations as mentioned in the user guide. Any ideas on what could be going on here? Looking forward to this working!!

[Travis]

The funny (non ha-ha) thing is by the time we read your post, both Dutch and I had independently began thinking about how to better address multiple "versions" of load maps, and a revised set of load maps will be rolled out soon. (If not in 1.4.5β2, then by β3.) As it is in the planning stage, the maps should cover Pax, Cargo, and Cargo-with-people-in-dedicated-stations load types.

Now I'll return to thinking on "What type of load map should ferry flights default to?"  Decisions, decisions....

[Aviator992]

Thats pretty interesting! Glad we're all on the save wavelength I look forward to having my jump seater in one spot rather than scattered throughout the plane... that sounds a bit brutal but we know that thats the truth right now!

[Travis]

Sept 5, 2013 20:09:00 GMT -5 Aviator992 said:

I look forward to having my jump seater in one spot rather than scattered throughout the plane... that sounds a bit brutal but we know that thats the truth right now!

Heh, you sound like old Doctor McCoy.

The scheme that I'm pulling the remainder of my hair out on goes like this. You can now have three different load maps for each aircraft/folder: one for Pax, one for Cargo, one for a Combo.

The benefit of this is if you have an aircraft with only one folder but which might have several models - a Pax and Cargo model let's say - then you can have three load maps that reference the same stations but with different loadouts. For a Pax flight, the Administrator will choose the Pax load map, for a Cargo-only flight, the Cargo load map. The Combo type is a mixture of Pax and Cargo which can accommodate pax seat as a Jumpseat. Voila!

I'm currently tinkering with my beloved PC-12, the default FSX C208B, the PMDG JS4100, and the default DC-3 to get good load plans for all types. There's a significant difference in what I'm seeing than what Dutch is seeing (his looks better, mine's... ok but not as good). So there needs to either be more work on Dutch's part, or possibly a lightbulb may go off over m'head and I'll see the light.

The latter is the outcome that should occur, but I've got a thick noggin so it may take time before should becomes will.

[Travis]

Here's three different flights in the J41 that I just ran up for demo purposes. In my J41 load maps, I started with the Pax version that has an attendant w/seat, and made an all cargo version that uses the "boxes in seats" load method.  I then took my Cargo version and converted the "extra boxes in the FA's seat" into a Jumpseat.

I also converted the Aft Cargo area to hold "bags" for PAX flights and a single "Pallet" for cargo.

The formatting's atrocious, but that's me....


PAX

LOAD MANIFEST:
1) 3 Units   CREW           490LB
2) 6 PAX     Passengers    1020LB
3) 1 Lot     Baggage        180LB
4) 1 Box     Misc. Items    290LB
********
TOTAL PAYLOAD              1980LB



J41 LOAD PLAN:
STN TYPE UNITS WEIGHT DESCRIPTION
------------------------------------------------------------
001 C 2/Seat   340LB   Flight Crew
002 C 1/Seat   150LB   Attendant
003 Y 3/Seat   510LB   For Cabin
004 Y 3/Seat   510LB   Aft Cabin
005 G 1/Box    110LB   Low Cargo
006 G 10/Bag   360LB   Aft Cargo

SUMMARY:
C Crew     3  490LB
Y PAX/Y    6 1020LB
G CARGO   11  470LB   






CARGO

LOAD MANIFEST:
1) 2  Units    CREW                340LB
2) 21 Boxes    Misc. Items        4070LB
3) 1  Box      Documents           440LB
4) 1  Box      Medical Supplies    450LB
********
TOTAL PAYLOAD                     5300LB



J41 LOAD PLAN:
STN TYPE UNITS WEIGHT DESCRIPTION
------------------------------------------------------------
001 C 2/Seat    340LB   Flight Crew
002 G 3/Box     115LB   Extra boxes
003 G 16/Box   1824LB   Forward Cargo
004 G 19/Box   1900LB   Mid Cargo
005 G 3/Box     262LB   Low Cargo
006 G 1/Pallet  859LB   Aft Cargo

SUMMARY:
C Crew   2      340LB
G CARGO 64     4960LB





COMBI (w/jumpseat)

LOAD MANIFEST:
1) 2  Units      CREW               340LB
2) 1  PAX        Passengers         170LB
3) 15 Boxes      Misc. Items       3110LB
4) 1  Box        Documents          480LB
********
TOTAL PAYLOAD                      4100LB



J41 LOAD PLAN:
STN TYPE UNITS WEIGHT DESCRIPTION
------------------------------------------------------------
001 C 2/Seat    340LB   Flight Crew
002 J 1/Seat    170LB   Jumpseat
003 G 12/Box   1352LB   Forward Cargo
004 G 15/Box   1408LB   Mid Cargo
005 G 2/Box     194LB   Low Cargo
006 G 1/Pallet  636LB   Aft Cargo

SUMMARY:
C Crew   2      340LB
J PAX/J  1      170LB
G CARGO 46     3590LB

[rick deckard]

Hi, any plans for the new released pmdg 777 interface/cfg files?

[joeporter2]

Dutch,

I am unable to have FSCAPTAIN recognize the doors (open/closed) on the T7. As such, I can not get the program to board passengers. It is not able to run thereafter, or unusable.

[joeporter2]

Figured it out, sorry.

Joe

[Dutch Owen]

We are investigating the interface for the 777 - further news when we have it. We'll get it done.

Dutch