Available devices

In CVE device interface is defined as a meta-model. Several meta-models are proposed by default. Usually almost one agent defines the dynamic behavior of the device. Observing sensors and updating a cve instance of the meta-model, or changing device actuators when a specific state is changed.

CVE could be used to create interactions about any kind of agents, but the initial focus concerned XR device and tools. For every XR device, we expect to use, we developped a meta-model and in parallel an agent synchronizing a meta-model instance and the real state of the device.œ

Viewer meta-model and cveogl agent

The viewer meta-model creates the information model of a complete viewer, including the complete 3D scenes with imported files or basic objects but also with various widgets. It describes the interaction modes.

This model is executed within the cveogl agent and may be controlled by one or several external agents.

Haptic meta-model and cvehappy agent

The haptic meta model is very basic since an haptic arm mainly control a transformation matrix and a force torsor. The cvehappy agent manage the Virtuose haption haptic arm to reflect this meta model.

Interaction meta-model and cvevrpn agent

VRPN is the virtual private network which is used by many interaction device to publish the device state. The vrpn meta model describes vrpn client connexion to a vrpn server and translate the events from the server into basic states of cve objects. Devices are mainly controled by transformation matrix (to track positions) and boolean to follow binary events (button state). Sometimes integers or float can be also controlled.

The cvevrpn agent executes this model as a vrpn client towards various vrpn server, and thus various vrpn devices.

Leapmotion interaction and agent cveleap

The leapmotion metamodel replicates the behaviour of the leapmotion device. It is associated with the cveleap agent which replicates the hand tracking and gesture recognition from the leapmotion as cve objects.

Steamvr meta-model

the steamvr metamodel allows the connexion of a steamvr device (mainly hmds). It has no specific agent but is managed directly by cveogl.