Jump to: navigation, search

Difference between revisions of "HowTo:Configure Dynamic AR Content"


(PlayButton Tag)
(Displaying movies)
Line 129: Line 129:
 
=== Displaying movies ===
 
=== Displaying movies ===
  
Inside the ''MovieAction'' tag there can be two possible resources defined, a MovieResource and a PlayButton resource.
+
Inside the ''MovieAction'' tag there can be two possible resources defined, a '''MovieResource''' and a '''PlayButton''' resource.
  
 
==== MovieResource Tag====
 
==== MovieResource Tag====

Revision as of 02:42, 31 March 2015

The Dynamic AR Content feature allows the user to see different content according to a marker configuration. The configurable content are 3D objects, movies and UBIK® objects. Currently this feature is enabled for ID Markers and Markerless scanning, meaning image tracking. Therefore, every time the user has scanned an ID marker or a picture, the corresponding object (3D object, movie or UBIK® object) will be processed and, according to the configuration, displayed on the screen.

[edit]

Prerequisites

In order to be able to use the feature properly, a certain folder structure is required and can be found at the following link FolderStructure. The setup folder contains:

  1. A root folder, named UBIK
  2. The UBIK root folder contains a child folder, named ARConfig
  3. The ARConfig contains two child folders named IDMarker and Markerless
    1. IDMarker folder contains the resources and configuration files needed for scanning an ID marker
    2. Markerless folder contains the resources and configuration files needed for scanning a picture
  4. IDMarker and Markerless folder contain a res and a conf folder
    1. The res folder contains all the resources to be shown, like 3D objects, videos and links to UBIK® objects
    2. The conf folder contains all the configuration files

A senseful configuration always consists of a tracking configuration (in one of the TrackingData.xml) and a corresponding action configuration (in the parallel ActionMapping.xml). So when the pattern, configured in tracking, is recognized by the camera, the configured action is triggered.

The following shows an exemplary sketch of the folder structure:

/UBIK/ARConfig/
  IDMarker
    conf
      TrackingData_Marker.xml
      Action_Mapping.xml
    res
      .obj
      .png
      .jpg
      .mtl
      .3g2
      .md2
  Markerless
    conf
      TrackingData_Game.xml
      Action_Mapping.xml
    res
      .obj
      .png
      .jpg
      .mtl
      .3g2
      .md2