In this demo, we want to test various configuration delays for detonating IED when passing a convoy.
Open the /VBS-3/ied database:
In the scenario map, we can see the two vehicles (Brdm1 & Brdm2) and the two IEDs (ied1 & ied2).
The colored rectangles are trigger zones.
Prior to compile and run, select the scenario Player and check the settings of the VbsProxy component. Values should be as follow:
They are defined in Runtime/VBS-3/vsTaskerPlugin.cpp in hard (for the moment). If you change these values (and must recompile), do not forget to update the VbsProxy component settings.
|
#define IN_PORT 9930 // vsTASKER -> VBS
#define OUT_PORT 9931 // VBS -> vsTASKER
#define CLIENT_IP "127.0.0.1"
|
Now, start VBS 3 and load the database. Make sure the plugin is correctly loaded.
Start the simulation.
You should see on the vsTASKER map that both vehicles are starting to move along the planned path.
Click on one of them.
On VBS 3 window, the camera should jump to track the selected entity (otherwise, select it on the object list)
When the first or second or even third colored area will be entered by the first vehicle, the attached IED will explode, according to the following logic (belonging to the Player):
You can connect the NoDelay1 exit point to the action explodeIED1 (then disconnect NoDelay2) or even add some delay time in each Delay object and see the result in the damages.
Below, the explosion of the IED1 located in front of a parked car, at proximity of the Brdm:
After the explosion of the to IEDs, you may have destruction of both Brdm or just the second one, depending on the delay, speed of each vehicle and lethality of each IED.
