The latest build for mission-x has minor bug fixes and a nice feature addition which was asked by "xplaneuser" from x-plane.org.
But before I'll explain the new feature in this build here are some nice to know facts on this build:
- For OSX simmers: plugin was built under Yosemite and XCode 6.x which limits the OS version it can support. I only tested the plugin under OSX10.8.x and 10.10.x !
- Linux was built under VM, but should work (has an issue with my native Linux distro).
The idea behind this option, is to limit the plane refuel option. The refuel rules are:
- Step defined and not global (If the step has the flag, then it will force the rules.
- The restriction on fuel payload, is only on increasing and not decreasing weight. Meaning, simmer can decrease as much fuel as he/she wants, but once he/she wants to increase the fuel capacity the rules will be forced.
- Refuel can be done only around "refuel_zone"s.
This element behaves like "trigger_zone", but is dedicated to fuel.
- Mission designer needs to define the "refuel_locations" globally (just like store element).
Therefore we need to define "refuel_rules" under each "step_settings" element.
<refuel_rules restrict_refuel_location="1" />
This is done just like "store" element but with the flexibility of "trigger_zone" (in some aspects).
Here is an example:
<refuel_zone name="FBMN tank" type="rad" >
<point lat="-19.975357" long="23.428282" />
<radius length_mtr="80" />
<tank fuel_in_tank_kg fuel_in_tank_kgfuel_in_tank_kg="" max_fuel_capacity="" />
<msg repeat="0" mute_voice="0" ><![CDATA[You entered FBMN fuel area. Stop your plane to refuel.;]]></msg>
<!-- Refuel point does not mean mission will also prevent manual refuel. You need to set the "refuel_rules" element on each step_settings -->
This might look complicated at first, but I believe there is some logic in it that you will find plausible.
- All "refuel_zone" elements are children of "refuel_locations" element.
- All "refuel_zone"s should have unique name.
- All "refuel_zone"s must have coordination: "point" element. If we define the type of zone as "poly" then we need at least 3 points.
- "radius" is only relevant if type of zone is "rad". radius can be in meters: "length_mtr" or nautical miles: "length_nm". Default radius is: "50 meters".
- You can define External Fuel tank capacity: "fuel_in_tank_kg
", "max_fuel_capacity". If you won't then the tank level will default to "100kg".