VR-Forces has built-in support for DI-Guy models.

It publishes DI-Guy animations and appearances, which 3D visualization applications such as the VR-Forces front-end and VR-Vantage Stealth can use to control lifeform models. The DI-Guy representation of the simulation object is stored in its state repository in the container class DtRwDIGuyCharacterInfo. This holds DI-Character, the current appearance, and the animation of the simulation object.

The DtDiGuyController class handles changes to the DI-Guy representation of the character and keeps the DI-Guy animation the simulation object is currently performing synchronized with the actual simulation of the simulation object. It responds to the Set DI-Guy Appearance set data request and updates the DI-Guy appearance in the simulation object's state repository. It responds to any DI-Guy Animation tasks and updates the simulation object's DI-Guy animation.

It maintains the synchronization between the DI-Guy animation that is being performed visually and where the enity is in the simulation by reading the data file, character_digest.xml. This file is produced by the DI-Guy application. It lists:

The appearances available to DI-Guy characters
The animations available
For each animation, it specifies:
- The time it takes to perform one cycle of the animation.
- the distance it covers.
- Posture changes it makes.
- Any directional changes it makes.

When a simulation object is not doing a tasked animation, the DtDiGuyController uses the simulation object's current posture, speed, and weapon state to determine the best default intrinsic animation. For example if a simulation object is in a prone position and moving toward a waypoint, the controller queries the available intrinsic animations in the character data for an animation that is in a prone position and has a speed close to the speed of the simulation object. If the simulation object has no prone animations than it gives up and the simulation object finds the closest animation for its default posture.