Well, I decided to address this issue, and add simple, yet useful visual cues inside x-plane scenery. But I did not stop there, there is another element in the plugin that was more accessible to me then the others, and it is called "Log.txt" debug info. When I test features I regularly flush info to the Log.txt file so I can debug the plugins work. I decided to create a new widget that will reflect the most important info to the designer, so he/she could monitor their mission progress. The widget includes the following info:
- General info: your targets status - distance from plane and status.
- Area info: List of all your areas basic info about them and if your plane is in the: physical area, the correct elevation and if all logic tests were met.
- Dref info: simple dataref values displayed. All your Dataref elements you defined under the Logic element will be reflected here ( only: int,float,double values are handled ).
- Param Info: on v1.30 I added parameters and the ability to define simple expressions. Their names, expected values and other info will be displayed on this screen.
- Static Targets.
- Dynamic Targets - static type (new)
- Logical Targets (new)
- Moving Objects (they already have 3D representative visual objects )
Instead of writing one thousand more words, here are some screenshots (this is still work in progress):
- Yellow: EventZone (AreaZone).
If it is a 3D closed polygon then it represents minimum and maximum elevation in a polygonal area.
- Green: Static Target element.
If it is a cylinder then it represents tolerate elevation value.
- Blue: Location of Dynamic Target.
> The vertical line represent the connecting/relevance of the different height shapes. In these screenshots it represent the cylinder area around the static target which forms the area where the plane should enter to fulfill the target.
The area's vertical line, represents the cubic area formed by the min/max elevation the plane should fly, in order to fulfill the area target.
Since the drawing loop is not synch with the flight loop, you will notice a small lag between the time the plane enter the area until you receive success confirmation, though it is negligible, you still need to be aware of this behavior.
Until next time