Changes between Version 2 and Version 3 of PlugIns/GenericEvents/VR-Applications


Ignore:
Timestamp:
10/04/17 16:07:54 (7 years ago)
Author:
pharms
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlugIns/GenericEvents/VR-Applications

    v2 v3  
    55The Generic Events Plugin has been used for monitoring VR applications. For this, the VR applications have been equipped with a monitoring component, that sends monitored events to the Generic Event Monitor as described [wiki:PlugIns/GenericEvents/generic-event-monitor here]. An example for a monitoring component are the scripts attached to this page. These scripts can be integrated into [https://unity3d.com/de Unity 3D] projects. Unity 3D is a game engine that, in addition to others, can be used to create VR applications. One of the scripts must be added to a game object in a VR scene. On initialization, the script starts to monitor head movements of users as well as grabbing and using objects. For this, they register with event handling mechanisms attached to other game objects in the scene to be notified about any interaction. One of the scripts, the one with VRTK in its name, is an extension to the other. It works with the [https://vrtoolkit.readme.io/ Virtual Reality Toolkit (VRTK)] and extends the functionality of the other script with framework specific monitoring capabilities. 
    66 
     7Both scripts need to be configured with a valid endpoint of a Generic Event Monitor instance. When correctly setup, the send JSON message as required to the monitor instance. The monitor in turn stores the data locally. 
     8 
     9Using AutoQUEST and the Generic Events Plugin, the data can be read and processed. For this, the command '''{{{parseDirGenericEvents}}}''' must be called first to load the data. Then other commands like '''{{{generateTaskTrees}}}''' and '''{{{evaluateUsability}}}''' can be used for further analysis.