Customizing DI-Guy

DI-Guy is designed to be easy to customize because we use industry standards for our data formats.

Models
DI-Guy uses Collada files for skinned character content. All other character content uses OpenFlight (.FLT) as well as all of our vehicles, props, animals, and terrains.

Texture Maps
DI-Guy uses RGB files (.rgb) for the images used as textures on our models.

Sound
DI-Guy uses WAVE (.wav) and Ogg files.

Motions
While DI-Guy uses our own proprietary format for motions, you can import your own motions using the Bio-Vision Heirarchical (.bvh) format and integrate them directly into the DI-Guy motion engine using the DI-Guy Motion Editor
.
Graphics
DI-Guy works out of the box with OpenGL, OSG, DirectX, and Vega Prime. Using the DI-Guy Graphics API, DI-Guy can be customized to any renderer including both scene graph and immediate mode style renderers.

Plug-ins to DI-Guy Scenario
You can customize the DI-Guy Scenario application using the DI-Guy Plugin interface. Your code is compiled as a .DLL file and dynamically linked at runtime.

The DI-Guy Custom Directory: Making your customizations portable
DI-Guy makes keeping your customizations organized easy by providing a directory called "custom" that masks our default content with your user-created content.  This makes sharing your custom work with other users a breeze, simply zip up the custom directory and send it to a colleague; once he unzips it, he'll have a customized version of DI-Guy exactly like yours.