Welcome 2018.
Cheer
Snagar Development Site |
|
Just wanted to drop by and congratulate all who are celebrating the new year.
Welcome 2018. Cheer
0 Comments
Hi all, There is always a sense of excitement before releasing a new version or major one, to say the list, but there is always a short list of "what I would have like to fix or enhance after this build" too. After publishing the first Alpha build: v3.0.160 I started working on:
This is a short list, but it can consume a lot of time to make it right. Currently I'm working on fixing some aspects of the documentation, mainly the script part. Version v3.0.160 was not ready for script writing, from documentation point of view. I believe I nailed most of the issues, and I'm also working on a short scripting guide to make it easier to understand, unfortunately that does not mean that scripting is easy nor hard, it just a feature that needs to be approached carefully at first (it won't bite though). I strongly suggest to first work with the examples I'll upload, and then try your own. The other big change I would like to implement in the next alpha build, is how the plugin reads missions and how many mission files can be defined in one folder, mainly: "{xp install}/Custom Scenery/missionx/{my mission folder}/briefer" Currently you can only set one mission file per mission folder. The next build will solve this, by reading ALL xml files in the "briefer" folder, and any valid file with a briefer image will be registered and displayed. The benefits:
Bugs - There are always bugs that need to be squashed, and in the next build some major ones, related mainly to scripts, were fixed.
Some words on scripting Since scripting is based on MY-BASIC interpreter, it is advisable to read the reference guide. But, please do remember that we only need to write a short script to handle logic, and not to build a whole application using MY-BASIC. The "MY-BASIC" scripting should only enhance the "Logic" part of the mission. We should use scripting for, but it is not limited to:
Some functionality might not be achieved without exposing the capability in the plugin (like modifying Dataref value). In such cases, contact me and send me a direct e-mail with request/suggestion for enhancement. Until next time Cheers Saar Hi All,
After weeks, well more like months, of work and sweat, the first build of the next version of Mission-X will be uploaded. It is not backward compatible with previous versions, but it try to retain the framework it was built on, but with the ability to execute scripts as part of the flow of the mission. Unfortunately, many features that are present in Mission-X v2 were not implemented and might not be implemented directly into the plugin. Some can be just scripted with enough experience. The main goal of this build, is to introduce the plugin and the new concepts in it. It will have only one mission as an example, and it won't have the scripting part demo yet, since there is some work to be done, mainly documentation. This build demonstrate the:
* The Nuklear library is being used since it solved me the True Type Font implementation. My personal preference is to always use LR XPSDK even for UI and even if it won't look sexy. This might not seem much, but since it is a complete re-write of the code, there was much effort invested in it and I hope the result will be acceptable by Mission designers. What kind of mission can you expect to create This alpha build aims to introduce XML mission creation. Simple "to and from" locations, with few messages. In 75% of these missions, this kind of interaction should be enough What about embedded scripts I already have a demo for the embedded scripting, but I think it is too early and documentation is not ready yet (you will see what I mean if you would get the chance to read the new designer guide). In the future build, I will add embedded examples to the demo mission. My problem is mainly time and the desire to implement more features, I want to implement the 3D Object feature, which is a large component from programming side, which come at the expense of writing documentation and preparing tutorials. I will have to decide though. Once the alpha build will be published, if you are designer then please go over the documentation first. Take your time, and go over the mission file and the packaging rules (location of mission files and folders). The demo mission is a simple implementation of one of v2 missions. Please do remember that this is an early bird build, so changes might take place. Until next time Cheers Saar |
AuthorCreation is something I always wanted to do. Since I'm not that good in painting/writing, I decided to contribute in programming. Archives
March 2024
|