21-07-2005, 07:45 PM
So I purchased FSP and started flying with it. So far I like it a lot but when I wanted to start flying with my favorite plane (the DC-9) I realized 2
things:
1) The payload template for it does not exist
2) and while trying to make my own I ran into a problem...
Here you can see the weight and ballance section of the aircraft.cfg:
As you can see I'm not flying the normal freight or passenger version but I'm flying the combi which has front and aft belly cargo compartments, holds
passengers in the rear section of the cabin and the front section of the cabin is used for containers. Since in the payload editor we are limited to 6
station only
I realized that the payload editor is missing the option to declare the price class of one of the first four stations as "cargo" which
is needed for airplanes such as the combi DC-9. I would really love if FSP could use the station loads from the aircraft.cfg files and just to group
them internally to sections via the loadmanager ini files. Making payload templates would then be very easy. However I will survive even the fixed 6
station if the option for switching one/all of the first four to cargo as well.
Another thing that would make FSPs more realistic would be the option of selecting TA's (Transition Altitudes) for each airport individually. Right
now you have the option to select the default TA in the options but if you fly from USA to Europe and you fly online (IVAO/VATSIM/FPI) you will most
probably get your pilot's points deducted because you will not set your altimeter in the right TA either in the USA or in the Europe. What I'm
proposing here should not be that hard to implement because.....
- player selects default TA as it is possible at the moment
- when loading the flight and filling in the destination airfield's ICAO code and time of arrival there would be a box for entering the TA for that
airfield
- if thas field is left blank the default TA is used, if the field is filled in the filled value is used and the value gets also saved to the
Icao_db.cfg so the next time the pilot does fly to or from that airport this value is used overriding the global default setting
Well maybe it is just too much hassle but it would for sure made the FSP experience more enjoyable and much closer to reality actually since
especially in Europe the TA's although each country has some general default transition altitude there may be airports in the same country that have
different TA because of the geographical conditions (hills around the airfield etc.)
So what do you think? Am I simply asking too much? (yeah I'm a greedy one)
things:
1) The payload template for it does not exist
2) and while trying to make my own I ran into a problem...
Here you can see the weight and ballance section of the aircraft.cfg:
Quote:[WEIGHT_AND_BALANCE]
max_gross_weight = 114000
empty_weight = 56850
reference_datum_position = 0.0, 0.0, 0.0
empty_weight_CG_position = 0.0, 0.0, 0.0
station_load.0 = " 340, 43.000, 0.0, 2.0, Pilots (2)"
station_load.1 = " 340, 39.000, 0.0, 2.0, FAs (2)"
station_load.2 = " 680, 29.500, 0.0, 2.0, Row 1 F(4)"
station_load.3 = " 680, 26.600, 0.0, 2.0, Row 2 F(4)"
station_load.4 = " 680, 23.700, 0.0, 2.0, Row 3 F(4)"
station_load.5 = " 680, 20.800, 0.0, 2.0, Row 4 F(4)"
station_load.6 = " 680, 16.000, 0.0, 2.0, Row 5 C(4)"
station_load.7 = " 850, 13.600, 0.0, 2.0, Row 6 C(5)"
station_load.8 = " 850, 11.200, 0.0, 2.0, Row 7 C(5)"
station_load.9 = " 850, 9.800, 0.0, 2.0, Row 8 C(5)"
station_load.10 = " 850, 6.400, 0.0, 2.0, Row 9 C(5)"
station_load.11 = " 850, 4.000, 0.0, 2.0, Row 10 C(5)"
station_load.12 = " 850, 1.600, 0.0, 2.0, Row 11 C(5)"
station_load.13 = " 850, -0.800, 0.0, 2.0, Row 12 C(5)"
station_load.14 = " 850, -3.200, 0.0, 2.0, Row 13 C(5)"
station_load.15 = " 850, -5.600, 0.0, 2.0, Row 14 C(5)"
station_load.16 = " 850, -8.000, 0.0, 2.0, Row 15 C(5)"
station_load.17 = " 850, -10.400, 0.0, 2.0, Row 16 C(5)"
station_load.18 = " 850, -12.800, 0.0, 2.0, Row 17 C(5)"
station_load.19 = " 850, -15.200, 0.0, 2.0, Row 18 C(5)"
station_load.20 = " 850, -17.600, 0.0, 2.0, Row 19 C(5)"
station_load.21 = " 850, -20.000, 0.0, 2.0, Row 20 C(5)"
station_load.22 = " 850, -22.400, 0.0, 2.0, Row 21 C(5)"
station_load.23 = "1000, 23.500, 0.0, -1.5, Fwd Belly(6350)"
station_load.24 = " 740, -25.983, 0.0, -1.5, Aft Belly(2650)"
station_load.25 = " 0, 31.750, 0.0, 2.0, Cargo Row 01-02"
station_load.26 = " 0, 23.250, 0.0, 2.0, Cargo Row 03-04"
station_load.27 = " 0, 14.750, 0.0, 2.0, Cargo Row 05-07"
station_load.28 = " 0, 6.250, 0.0, 2.0, Cargo Row 08-11"
station_load.29 = " 0, -2.250, 0.0, 2.0, Cargo Row 12-14"
station_load.30 = " 0, -10.750, 0.0, 2.0, Cargo Row 15-18"
station_load.31 = " 0, -19.250, 0.0, 2.0, Cargo Row 19-21"
max_number_of_stations = 35
empty_weight_pitch_MOI = 495599
empty_weight_roll_MOI = 312457
empty_weight_yaw_MOI = 859048
empty_weight_coupled_MOI = 0
As you can see I'm not flying the normal freight or passenger version but I'm flying the combi which has front and aft belly cargo compartments, holds
passengers in the rear section of the cabin and the front section of the cabin is used for containers. Since in the payload editor we are limited to 6
station only

is needed for airplanes such as the combi DC-9. I would really love if FSP could use the station loads from the aircraft.cfg files and just to group
them internally to sections via the loadmanager ini files. Making payload templates would then be very easy. However I will survive even the fixed 6
station if the option for switching one/all of the first four to cargo as well.
Another thing that would make FSPs more realistic would be the option of selecting TA's (Transition Altitudes) for each airport individually. Right
now you have the option to select the default TA in the options but if you fly from USA to Europe and you fly online (IVAO/VATSIM/FPI) you will most
probably get your pilot's points deducted because you will not set your altimeter in the right TA either in the USA or in the Europe. What I'm
proposing here should not be that hard to implement because.....
- player selects default TA as it is possible at the moment
- when loading the flight and filling in the destination airfield's ICAO code and time of arrival there would be a box for entering the TA for that
airfield
- if thas field is left blank the default TA is used, if the field is filled in the filled value is used and the value gets also saved to the
Icao_db.cfg so the next time the pilot does fly to or from that airport this value is used overriding the global default setting
Well maybe it is just too much hassle but it would for sure made the FSP experience more enjoyable and much closer to reality actually since
especially in Europe the TA's although each country has some general default transition altitude there may be airports in the same country that have
different TA because of the geographical conditions (hills around the airfield etc.)
So what do you think? Am I simply asking too much? (yeah I'm a greedy one)

Zdenek Cizek