vsTASKER is divided into two parts:
-
The GUI that allows user to define visually the entire simulation, from behavior definitions to scenario edition;
-
The Simulation Engine that loads and run the scenario.
Both parts are connected using Shared Memory or LAN.
vsTASKER needs a compiler like Microsoft Visual C++ in order to build simulation engines.
Without MS Studio, you will only be able to load and run already compiled sample databases (*.rt) that are provided with their associated sim-engine.
If you have Studio (2008 or 2010) installed, check that the configuration is correct. Go to Tools::Options, select Compilation panel and chose the version you have installed. You must change the location if your compiler is installed on a different directory.
Compiler needs “cl.exe” and Linker needs “link.exe”.
Select Tools::Preferences::Environment
|
|
Microsoft Visual C++ 2003 (vc71) 2005 (vc80) and 2009 (vc90) are no more supported since v7
|
In order to run the simulation engine, vsTASKER must built it using the database definition.
Use the toolbar
button or the menu
Tools::Compile or Tools::Recompile All (F7 or Ctrl F7) to do so:
If the compilation fails, you will get the following window:
Click on the button to open the Build Output window:
The display is the cl.exe or link.exe output. Nevertheless, you can double click on the error word to directly jump to the line of the faulty code:
From here (xx is the problem, line 210), you must correct the code in the object itself (vsTASKER does not yet opens the object automatically).
To find the faulty object, the name of the function is always a good help.
Here: E3A_logic_ActDef::_inform_all()
That means the code is inside the Action named inform_all of the Logic named E3A_logic.
Once the compilation, link and build all succeed, the following window invites you to load the simulation engine (you can also use the
toolbar button)
