Copyright VirtualSim 2004-2020 - All rights reserved
Directories
Bin
Here as stored some DLL needed by vsTASKER GUI and some generated simulation engines, according to the libraries used.
You will also find the vst2008_pro.msi and vst2010_pro.msi redistributable package normally called at installation time. They are requested if you do not have Visual Studio installed.
This directory contains all the databases needed by vsTASKER for design and runtime.
3DS
Contains some 3DS Max models to use for OpenGL perspective mode or OSG viewer
4586
Editions 2 and 3 of the STANAG 4586 definitions
ArcInfo
vsTerrainBuilder converted .geo terrain data from .shp files
Coast
vsTerrainBuilder converted coast line terrain data from .dat or .lin files
Db
Contains all design database vsTASKER loads at design time. The database node file .db is inside a directory holding the same name.
Elev
vsTerrainBuilder converted elevation terrain data from .dem or .dted files
Fom
Contains HLS federation files in 1.3 (.fed) or 1516 (.xml) format needed by the HLA module
HMI
Contains all textures needed by the Sprites. Files are going by pair. One is the .tga with alpha-channel for transparency. The second one is the .bmp for display in the File selection window (as .tga cannot appear as bitmap)
Log
Directory used to store Record & Playback files from the Logger
Map
Contains all the image terrain files used for Raster maps and the tiled-map databases (x.map file and associated x directory)
Contains all scenarios Features available. User can modify any of them, add his own using the template provided or rebuild the corresponding .lib (need of Visual Studio) and .dll (need of C++ Builder 2010 or higher) to resolve some problems that might occur on some systems at dll load time.
features.lst lists all built-in Features. features_user.lst lists all user added Features (if any).
Because of the first file, it is for now advisable to mind the name given to the database (a database named windows for example will conflict the system windows.h header file).
db_config.h/cpp contains the latest generated header file.
Contains some samples on how to create a custom GUI replacing vsTASKER GUI for runtime environment.
chinese and simple are two basic applications written in Visual C++ to load a scenario, control some entities and run it, from inside a specific panel and using some vsTASKER dll map plugins (see below).
Contains the vsTASKER User Manual (this document, that also includes the online help), the Reference Manual (automatically generated using Doxygen), the TerrainBuilder User Manual and the deprecated Tutorial document.
Contains all Components and DataModels used as built-in items in vsTASKER GUI and linked against the simulation engine.
The user can add his own Components and DataModels in specific directories (to avoid mixing built-in with his own) either by using the template_cpt.h/cpp, template_dml.h/cpp (see src/user and include/user) or by using the button of the Component or DataModel object. See Models.
built-in items:
default_cp.lst lists all default components
military_cp.lst lists all defense related components
vrvantage_cp.lst lists some vrVantage components used to integrate vsTASKER Sim engine with the MAK 3D Viewer (use them as an example)
satellite_cp.lst lists all components used with the Satellite version, like orbit propagators
stk_cp.lst lists all STK components (used with STK software or to replace some STK capabilities, after scenario import)
default_dm.lst lists all default built-in data-models
military_dm.lst lists all military data-models, mostly used by military components
User items:
user_cp.lst template for user components
user_dm.lst template for user data-models
Built-in lists must not be modified as each new release/update will replace them with a new version.
Contains directories per Viewer or third party software.
It is not mandatory for a user to keep these directories for his own database development but all vsTASKER samples are using them.
So, in each directory, you will find the corresponding vc10 (Visual Studio 2010) or vc14 (Visual Studio 2017/19) .sln project file to debug the generated simulation engine. Each project has already libraries and include path set, ready to compile, link and run.
If you need to create a specific target environment for your simulation engines, it is advisable to create your own directory under Runtime, set the path in Database Runtime setup and include there the Visual Studio project file and relocate here all models or directory the environment will need at runtime.
Contains all Sprites available to build HMI. User can modify any of them and rebuild the corresponding .lib (need of Visual Studio) and .dll (need of C++ Builder 2010 or higher).
sprites.lst lists all built-in Sprites.
sprites_user.lst lists all user-added Sprites. Use this file to add/remove your own Sprites (you will need C++ Builder 2009 or higher)
Built-in lists must not be modified as each new release/update will replace them with a new version.
Contains the HLA ambassador class file needed to link with the respective RTI (1.3, 1516 or Evolved)
Template directory has some template.cpp files needed as #include if used by the code.
OSG directory contains the layer vsTASKER is adding to provide some visual effect for the user (to be used from logics). SilverLining and Triton source files are also provided.
4586 directory has some glue modules for Edition 2 or Edition 3. These files are automatically built.
Contains some subroutines that are attached to a specific Dyn-UI and are called every time a change is made by the user on any of the Dyn-UI variables.
validation.lst lists all built-in validation functions.
validation_user.lst lists all user-added validation functions. Use this file to add/remove your own validation.
Built-in lists must not be modified as each new release/update will replace them with a new version.
button of the 
