Networking with DI-Guy
Using DIS or HLA networking, DI-Guy is already being used to interoperate 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 (oftentimes the user already has a working solution).  DI-Guy SDK ships with an example of integrating with a 3rdparty network solution, in this case, MäK's VR-Link.

Meanwhile, DI-Guy Scenario can be purchased with the DIS or HLA option to immediately support networking.

DI-Guy Custom PDUS and DI-Guy Custom FOM
The amount of support for lifeforms can seem limited in DIS and HLA.  To increase the fidelity of human performance across a network using DIS, DI-Guy offers DIS Custom PDS and the DI-Custom FOM.  These serve 3 basic purposes:

1. Specify the exact DI-Guy character_type you would like your character to be,
2. Specify the exact DI-Guy appearance you would like your character to have, and
3. 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, so that systems that do not subscribe to these customizations will still have human performances.

Please consult the DI-Guy SDK User Manual Chapter 6, "Networking with DI-Guy", to learn more about DI-Guy networking, and find the specifications of DI-Guy custom PDUs and DI-Guy Custom FOM.  If you are broadcasting DIS or HLA traffic, we'd be delighted to see you adopt these formats.