Designer Guide v3.0.x
The latest designer guide for v3.0.x is published with the plugin. Designer Guide v2.1.29 (for Mission-X 2.1.29.8)
The following document is intended for mission/adventure designers. For any question, you can send me an e-mail to "snagar.dev@protonmail.com" The plugin is published on the "Plugins" page. Latest update 2017-jul-28
|
User Manual
The user manual is a short document that explains the basics of how to use Mission-X plugin.This documentation is for v2.1x
Last update 2016-aug-20
|
Tips for designers (for v2.x):
- If your plane is on sea, avoid changing the "Sea" element since it will cause the plane to automatically move to the nearest airport. This is an X-Plane limitation/Feature ( this will be added to v1.20.12 designer guide ).
- You can map three buttons/Keys to the "Briefer", "2D Map" & "Flight Gauge" widgets. This will allow for a much streamline mission flight
( See the latest User Guide ). - There is no flag to stop a playing sound file. The workaround is to trigger and play a silent track that can be very short ( 0.5sec for example), while setting soundMix attribute to zero ( see Tutorial 05 ).
- Use the <MISSION .... stage="test"/> with <designer force_step_name="{step name}" >, in order to make objective tests easier. Meaning, when you press the [start mission] button, the objective that will start will be the "{step name}".
This will work only in "** Designer Mode **" - You should treat a <step> element just like a checkpoint and not like the last Target the plane should reach.
Meaning, if your mission has two main airports, or even one, but the plane needs to travel through different coordination, therefore it will be much easier to control the locations by dividing the "Steps" into sub steps, just like checkpoints.
The other benefit is that there will be more save points which means that simmer will not need to restart the mission. - Always download the latest plugin build ( just had to add this one ;-)