The major issues found in v3.0.200, thanks to "mickael_a" from x-plane.org site, was that triggers that were based on elevation did not work (Thank you mickael).
What is coming down the pipe:
First - I believe I fixed the trigger bug, unfortunately it was a logic part that I did not finish implementing since I tested ground rules, and just return "false" for all rest of elevation evaluations - Oops.
Second - I decided to fix the trigger issue but also add the "visual cues" that were available in Mission-X v2.x. So, next updated version will include the Visual Cue Info lines so simmer will be able to see where are the "event" areas in x-plane world.
There are still coding to be done in terms of "when" to display those lines (right now it is in "always on" state, but I'll add it soon).
Here is an example:
For designers this should be a huge help when designing triggers, since they will be able to visualize where and when Mission-X plugin will fire them, so it will make mission debug a lot easier.
But not everything can be visualized, triggers that are based on scripts can not be visualized, this will be dealt in the future (maybe).
Other planned features
The next feature is not from me, yes yes, I finally started to open the plugin to anyone who wants to participate and contribute to the plugin, after all my time is limited and there are features that others can benefit while not on my list.
The first feature that might see the light after I'll upload the fixes and the Cue Info options will be: "MXPAD Options".
If you already tested Mission-X in its latest build, you should be familiar with the "MXPAD", a lame name for "last messages" window, that hovers at the upper right side of your screen (or where ever you want to place it).
This feature was designed and written by "Michel", I do not know his X-Plane Org nickname, so I'll just use his first name. To make long story short, Michel approach me with the idea that the plugin should have an "option" feature, so a mission path will be affected by simmer decision, this will probably be useful in "tutorials".
Michal also suggested to implement this feature, and I admit that this was the first time I let anyone access to my plugin source, I was concerned only from one thing, that we won't be able to manage our individual code without overriding each other work.
Fortunately, I found Michal a great team mate, who is willing to take the time, learn and dive to the plugin code, and I think I'm lucky to have him as a contributor.
I do not want to add more, since there is some work that needs to be done, basically he already implemented the code, but we still need to merge and see how it all feats together.
I hope to write about this feature and share how to use it in this blog, but if you will miss my explanation, you can always find it in the documentation.
Here is a sneak pick to the MXPAD Options feature:
Until next time