Event Manager TCP Connection (Event Manager Gui)

Table of Contents

• Implementing a DtNetworkEventManager override
  • Classes
  • Plugin Entry Points

This example will show how to replace the sending of events from using the VR-Link exercise connection to send VR-Forces data interactions to using a TCP socket to send these data interactions.

This example only will allow usage on port 6000 and connect to local host. It will also only have the front-end connect to a single back-end. The intent of this example is to show how you can replace the DtNetworkEventManager with one of your own to deal with events before they get sent out over the normal DIS/HLA network.

The Event Manager Sim example demonstrates the following:

• How to create a new event manager based on an existing event manager
• How to use a socket to send/receive messages once a back-end is discovered
• How to recreate a DtDataInteraction from a memory buffer sent over a TCP network
• How to post events to the event manager

Implementing a DtNetworkEventManager override

In the Launcher, click the Plug-ins button to bring up the Plug-ins Selection dialog. Enable the eventManagerTCP plugin for this example to work.

1. Start vrfGui.
2. Run VR-Forces as normal. You should notice no difference in the operation of VR-Forces other than netDump or vrfMsgDump will no longer show VR-Forces data interactions being sent over the network.

Classes

DtEventManagerTCP	The class that overrides the DtNetworkEventManager. This class will provide basic functionality for sending/receiving a DtDataInteraction on the TCP network.
DtClientEventManagerTCP	The class that overrides the DtEventManagerTCP. This class will create the socket socket to connect to the network and send information to the back-end
DtEventManagerAccessory	This class will make sure there is a back-end to connect to, and, connect it it over the TCP network if it exists. If it does not it will wait for back-end to be discovered.

---

Plugin Entry Points