Install HCP VBS
Before you start
- Windows 10 or 11 x64.
- VBS4 25.1 or later, with Gears Studio installed for component management and deployment.
- HEAT Capture running and reachable from this workstation.
VRAI distributes HCP VBS to customers as a built Gears Studio component package; it is not published as a GitHub release. Building it yourself from source is only needed for development - see Build from source below.
Install the supplied package
-
Obtain the HCP VBS component package from VRAI for the
hcp-VBSversion you are deploying. -
In Gears Studio, use component management to import or copy the supplied
HCPVBScomponent into VBS4. -
Confirm the four configuration files are present next to the deployed DLL, in VBS4’s
mycomponents/HCPVBS/folder:File Purpose HCPVBSConfig.jsonTransport, session endpoints and collection settings DISMappings.jsonFallback VBS object type to DIS type mapping DISConfigNameMappings.jsonPrimary VBS config-class-name to DIS type mapping EntityDenyList.jsonEntities to exclude from tracking -
Edit
HCPVBSConfig.jsonbefore first launch - see Configure; the values shipped in the package are not usable against current HEAT Capture as they stand. -
Start VBS4. The component loads automatically through the Gears component system.
Verify the install
Start a mission with HEAT Capture running and a user signed in. Check the VBS4 / Gears log for:
HCPVBS loaded
HCPVBS ConnectingWith a working WebSocket configuration (see Configure), the console
log shows onopen once the connection to HEAT Capture succeeds. Confirm entities are arriving by
checking HEAT Capture’s own session view for the workstation VBS4 is running on.
HCPVBS loaded and HCPVBS Connecting appear even when nothing on the other end is listening.
Neither line is proof that HEAT Capture is receiving data - see
Troubleshooting.
Build from source
Only needed for development against hcp-VBS itself, not for deploying the VRAI-supplied
package above.
-
In Gears Studio, create a new project named
HCPVBSwith the project folder set toHCPVBS-dev. -
Inside that project folder, clone or copy the
hcp-VBSrepository into a subdirectory namedHCPVBS- this is the repository root Gears Studio expects. -
In Gears Studio, select Import Component and point it at the
HCPVBSrepository folder. -
Generate the solution in Gears Studio, then open
build/vs2022/HCPVBS.slnin Visual Studio 2022 (v143 toolset, C++20). -
Select the ReleaseWithSymbols | x64 configuration and build the solution. Gears Studio deploys the output DLL into VBS4’s component folder; the four configuration files still need editing per Configure before first launch.
Uninstall
Remove the HCPVBS folder from VBS4’s mycomponents/ directory, or use Gears Studio’s component
management to unload it. No credentials or session data are stored outside that folder; the four
JSON configuration files are the only state left behind.