Jump to: navigation, search

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


Line 1: Line 1:
__TOC__
 
 
= Introduction =
 
= Introduction =
 +
__TOC__
 
The Dynamic AR Content feature allows the user to see different content according to a marker configuration.
 
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.
 
The configurable content are 3D objects, movies and {{UBIK}} objects. Currently this feature is enabled for ID Markers and Markerless scanning, meaning image tracking.

Revision as of 09:07, 11 February 2015

[edit]

Introduction

Contents

 [hide
  • 1 ® 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.

    Setup

    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

    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

    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.

    Tracking Setup

    The first step is to configure the tracking data xml in order for UBIK® to recognize scanned pictures and ID's. In case the marker is a picture (image), the location of the pictures must also be provided. In the example it's ../res/pic_name.(png, jpeg). The id located in the tracking data xml should be the same as the order of the id in the list of ids.

    • This example below the configuration of the location of the image:
      <SensorCOS>
        <SensorCOSID>1</SensorCosID>
        <Parameters>
             <referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
        </Parameters>
      </SensorCOS>
    IC Attention.pngThe ID must be an integer number and it is not allowed to leave gaps, otherwise tracking wont work!