10.2 - Architectural Overview

VR-Link C# is composed of several layers.

The bulk of the work is accomplished in a C++ library called ManagedInterface, which we use to manage how information gets pushed to and from C#. Above the C++ ManagedInterface library is a set of C# bindings called ManagedInterfaceCS, which allows the C# application to access the power of VR-Link and ManagedInterface directly from C#. ManagedInterfaceCS communicates with the underlying C++ libraries through a simple message-passing API.

The ManagedInterfaceCS layer is responsible for passing messages between VR-Link C# and VR-Link C++.

For messages coming from DIS/HLA, ManagedInterfaceCS receives messages from VR-Link and stores current state in VR-Link C# reflected objects. It automatically updates objects with the same VR-Link dead-reckoning and smoothing algorithms. Users can extend the built-in message handler to fit the needs of their simulation design. For events (for example, Fire and Detonate), ManagedInterfaceCS provides a mechanism to register callbacks or custom handlers.

For objects owned by the C# application, ManagedInterfaceCS provides a "Publish" component, which is responsible for passing current state across the language boundary to VR-Link. VR-Link then publishes objects to the DIS/HLA network. For events/interactions, ManagedInterfaceCS provides a C# API to fill out and send the appropriate messages.

[<< Introduction to VR-Link for C#] [Home] [Top of Page] [ManagedInterface Class >>]