Environment Variables
Once the product installation is finished, it is always good to reboot the computer (although this might not be necessary on Windows 11). You need the environment variable %VSTASKER_DIR% to be defined as C:VirtualSimvsTasker7 and the user (or system) path to include: %VSTASKER_DIR%Bin;%VSTASKER_DIR%Binvc100;%VSTASKER_DIR%Binvc100osgPlugins;. These are normally set by the installer, unless the system has forbidden it. In such case, it must be done manually.

If any error or warning message appears at application launch, make sure the Path is correctly set (you can test the environment from a command console: Windows Key + cmd, enter. Then on the console: set vstasker_dir -> C:VirtualSimvsTasker7 and use set path to check its content).

What is vsTASKER
vsTASKER is a white box synthetic environment for real-time simulation. It is a framework and development toolkit for all kind of time stepped simulations.

It is divided into two parts:

  • The design environment, called GUI, which provides all tools and features to define a simulation project. It includes mapping capabilities (GIS), terrain elevation, state machine, grafcets, object oriented components and entities to be dropped on the terrain.
  • The simulation engine, called SIM, which is built by Visual Studio from the GUI generated code and vsTASKER libraries. The SIM engine is license free and can be deployed without constraint.
vsTASKER Demo Installation
Download the self extractor vstasker_7_demo.exe from the email you received from VirtualSim, after having requested the link. Note that if you did not receive the email (if may take 24h), it is likely the provided email address has been rejected. See the conditions on the request page.

Double-click the executable and let the installer run. The process should not take long. If you do not have VisualStudio 2010 installed, the community version will be installed. It is mandatory to have it in order to compile your own examples or recompile the demo ones (which you are free to modify).

You can then launch vsTASKER from the Start menu or from the directory:


(ps: see other FAQ in case of problems)

First Run
At start, the first scenario is suicide_attack. It is an OpenSceneGraph example showing a car exploding itself to harm some hummvee vehicles. In the main toolbar, use the button to launch the simulation (check the taskbar as the OSG window may not popup). You can then start the simulation using the button.

Note that all demo samples are precompiled. You can simply load the databases (file ending with .db) from the various directories under /Data/Db/Samples and launch the associated simulation ()

If any problem during the install or the try, please use the ticket system here

Application exits just after start
On Windows 10 (but not only), if the registry cannot be accessed for writing, vsTASKER will exit and this is a normal (license protection) behavior.
Make sure to run vsTASKER GUI in Administrative mode.

Method 1: Right click the vsTASKER icon on the Desktop and choose “Run as Administrator”
Method 2: Right click the vsTASKER icon, then Properties::Advanced… and check the option box “Run as Administrator”
Weird colors in text editors
This can happen when you just change the theme. To fix this, just go to Tools::Preferences::System then Editors, and in Source Code panel, click Reset and Save.
How to change the theme
In vsTASKER, select Tools::Preferences::Systems then Forms, and in Application Skin box, choose Dark Theme for the default v7 theme or Light Theme for the previous version Windows theme.
Save and restart vsTASKER.
Dongle Problems
1. Dongle not recognized
This is typically the case when driver is missing, not yet installed or conflicting with another one. In such case, remove the driver and reinstall it.

2. Removing the KeyLock Driver
Go to Start::Programs::vsTASKER::Licensing::Usb Dongle
Select: uninstall
Press: Begin Uninstall
Reboot then, re-install the driver!

3. Conflict with Pitch Dongle
If you are using Pitch Dongle, please, refer to the following documentation: