To reduce eye strain, Dark Theme has been setup as default mode for v7.
Users can always come back to the normal light Windows theme by going to Preferences, Forms, selecting Light Theme and restarting vsTASKER.
This first version does not cover yet Sprites (HMI) and Feature windows. Both will come in next v7.1 version.
Automatic Code Updater
With earlier version of vsTASKER, the code generated to build the simulation engine was only intended for the compiler. It was possible to run in debug and do some local changes, but any modification of the generated code had to be manually retrofitted into the vsTASKER database.
With v7, this update process is automatic. Although the built-in code editor of vsTASKER is good enough for simple edition, it does not reach the level of Intellisense nor the debugging capability of Visual Studio. So, with v7, it is more efficient to define structures in vsTASKER and write the code in Visual Studio while keeping both parts synchronized.
Titan Vanguard Integration
Since the game engine of Calytrix/Titan.IM provides a C++ API, embedding vsTASKER engine inside the simulation core is now plug and play. vsTASKER generates a DLL which is loaded by Titan engine at startup. The Sim DLL takes control of the 3D engine to create entities, position and control any object in real-time, from start to end.
CIGI Interface Redesigned
A big effort has been carried out to provide easy CIGI setup. While other CGF provide black box CIGI capabilities, vsTASKER delivers an open mechanism to control all exchanged messages. It becomes easy to build a customized solution compatible any IG, even if this latest has expended the standard with proprietary messages.
CIGI in Design Mode
vsTASKER GUI can now connect to an IG during design time to position entities on the terrain. This feature is very useful when preparing a scenario with requirement for fine positioning or when line of sight is crucial. Two screens are required for best experience, as the 2D map of vsTASKER is used for moving entities with instant feed back on the remote 3D screen.
Elevation Data using CIGI
Since the external IG has loaded the terrain database, it can be useful to request elevation data in order to build a DTED or HGT representation of the terrain. Such local elevation data is much simpler to use and very efficient for pre-processing LoS before requesting a more CPU/GPU consuming request using CIGI messages.
vsTASKER provides an easy way to automatically generate the terrain height database, with various layers of accuracy. As the process can be time consuming, the result will be saved on disk to be reused offline.
To ease the use of VBS-IG from Bohemia with vsTASKER, special menus have been added to the scenario interface, to select visually entities to drop into the database.
CIGI has been extended with some VBS-IG bespoke messages:
Several categories in vsTASKER have now the capability to use folders to store likewise elements. Folders can embed other folders. When a lot of logics or objects are created, the display area can become saturated and messy. This feature will help the user to cleanse and better organize its working environment and be more productive.
64 bits Libraries
In addition to the x86 libraries for Visual Studio 2010 and 2015, some libraries have been ported to 64 bits for vc100 (2010), vc140 (2015) and vc141 (2017). The 64 version of the simulation does not include yet all libraries. Future versions or v7 will provide more features. Console and OpenGL output are supported (mainly for Qt and HMI). Visual Studio 2017 x64 will soon support OpenSceneGraph and OsgEarth.
Dynamic User Interface redesign
The old style parameter/value table for user defined data interface has been redesigned to offer mode dynamic widgets. It will be extended in new versions.
Freetypes can now be used for entity and HMI labeling as well as Qt OpenGL map. This will improve the quality of the display.
Single Terrain Mode
Since some terrains can take a lot a memory, the user has the choice between several scenarios over different terrains (old way) or several scenario over the same terrain (new way).
Since the ASI interface of VBS-3 from Bohemia allows a communication with a third party software, vsTASKER is using it to control the VBS3 engine from remote. This can be useful for some small project as the ASI interface of VBS3 is not efficient performance wise.
The way the integration was done is extendable by the user as the source code is provided. One of the best use of this integration is populating the VBS3 scenario with entities coming from vsTASKER. Updates from VBS3 to vsTASKER is acceptable when very few entities are concerned.