Networking with DI-Guy

Using DIS or HLA networking, DI-Guy interoperates with third party applications such as:

• OneSAF
  
• DI-SAF
  
• JSAF
  
• ExportCGF
  
• MÄK VR-Forces
  
• LMIS ModStealth
  
• LMIS TopScene
• Vega Prime / vpNet

When working with DI-Guy SDK, the user needs to supply his own networking software (this is because oftentimes the user already has a working network solution to which he wants to connect his DI-Guys).  DI-Guy SDK ships with an example of integrating with a 3rdparty network solution, in this case, MäK's VR-Link.

DI-Guy Custom PDUS and DI-Guy Custom FOM
Support for lifeforms is limited in DIS and HLA.  To increase both the visual and motion fidelity of human performance across a network using DIS or HLA, DI-Guy supports DI-Guy Custom PDUs for DIS and the DI-Guy Custom FOM for HLA. 

DI-Guy Custom PDUS / DI-Guy Custom FOM perform 3 important tasks when networking DI-Guy:

1. They specify the exact DI-Guy character_type you would like your character to be,
2. They specify the exact DI-Guy appearance you would like your character to have, and
3. They specify the exact DI-Guy action you would like your character to perform.
   

Note that this information is supplemental to standard DIS and HLA information. Systems that do not implement these customizations will still have good but lower fidelity "standard" DIS/HLA human performances.

Please consult the DI-Guy SDK User Manual Chapter 6, "Networking with DI-Guy", to learn more about DI-Guy networking. The specifications for DI-Guy Custom PDUs and DI-Guy Custom FOM are clearly listed there and ready to use. If you are broadcasting DIS or HLA traffic, we'd be delighted to see you adopt these formats. Ask DI-Guy support for the DI-Guy Digest, an XML based text document that details all the character types, appearances, and motions in DI-Guy. The DI-Guy Digest is free and can be used on a system that does not install DI-Guy.