You must set up your Cluster Rendering network so that input to the Master Node is passed on to all Client nodes. To do this, you need to set up the Cluster Input Settings, and use a VRPN server to send that input to all Client nodes.
For all normal input, you must define input mapping in the Cluster Input Manager settings. This can be found in the Project setting > Cluster Input menu.
| 属性： | 功能： |
|---|---|
| Size | Number of cluster input entries |
| Name | Unique name for this entry. Used in script to identify each entry. |
| Device Name | The name of the device which registered to VRPN server. |
| Server URL | The URL to connect to VRPN. Usually “localhost” if server started locally. |
| Index | The index/channel of the device this input entry suppose to connect to. |
| Type | The type of input. |
| - Button | Device that return a binary result of pressed or not pressed. |
| - Axis | Device is an analog axis that provides continuous value represented by a float. |
| - Tracker | Device that provide position and orientation values. |
| - CustomProvidedInput | A user customized input. |
All the entries entered into the Cluster Input Manager settings can be accessed from script via the ClusterInput class. The usage is much alike to Unity’s regular Input class; you can read the state of the input every frame with the API and act on it. For examples, see the ClusterInput Script Reference.
Whenever you have a project which reads input from the ClusterInput class, a VRPN server has to be present and running with the correct device connected. A VRPN device is identified by it’s name and url. Typically, the fully formed URL is something like TrackerA@localhost. TrackerA being the Device Name, localhost being the Server URL defined in the VRPN settting.
For more information about VRPN, visit this website: http://www.cs.unc.edu/Research/vrpn/
If your project does not use the ClusterInput class, and uses only Custom Input (see below), then you do not need a VRPN server.
You may want to integrate your input devices directly using the device manufacturer’s SDK, by writing a Unity C++ plugin. This plugin will then pass the values to the C# side of your project using interop services. In such a scenario, the inputs will not be syncrhonized to the rest of the cluster. To bridge this, ClusterInput provides a set of commands that can capture these custom input values and replicate them across the entire cluster.
To do this, you must create and configure an Input in the Cluster Input inspector and set the Type to "User Provided Input". On the master node of the cluster, poll for input values from the integrated device as usual and send them into these inputs using one of these APIs:
These values will then be available to rest of the cluster and also the master node.