Jump to: navigation, search

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

(→‎Example)
 
(58 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
== Introduction ==
 
 
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.
 
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.
 
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 ==
+
= Prerequisites =
−
In order to be able to use the feature properly, a setup folder is required and can be found at the following link [http://wiki.augmensys.com/images/6/66/Dynamic_AR_Content_Folder_Structure.rar Folder Structure]. The setup folder contains:
+
In order to be able to use the feature properly, a certain folder structure is required and can be found at the following link {{FileLink|Dynamic_AR_Content_Folder_Structure.rar|Dynamic_AR_Content_Folder_Structure.rar}}. Since version 2.4.4, the schema changed slightly (downwards compatible). The updated example package can be found here: {{FileLink|Dynamic_AR_Content_Folder_Structure_244.zip|Dynamic_AR_Content_Folder_Structure_244.zip}}
 +
The setup folder contains:
 
# A root folder, named ''UBIK''
 
# A root folder, named ''UBIK''
 
# The ''UBIK'' root folder contains a child folder, named ''ARConfig''
 
# The ''UBIK'' root folder contains a child folder, named ''ARConfig''
 
# The ''ARConfig'' contains two child folders named ''IDMarker'' and ''Markerless''
 
# The ''ARConfig'' contains two child folders named ''IDMarker'' and ''Markerless''
−
## ''IDMarker'' folder contains the resources and configuration files needed for scanning an id marker
+
## ''IDMarker'' folder contains the resources and configuration files needed for scanning an ID marker
 
## ''Markerless'' folder contains the resources and configuration files needed for scanning a picture
 
## ''Markerless'' folder contains the resources and configuration files needed for scanning a picture
 
# ''IDMarker'' and ''Markerless'' folder contain a ''res'' and a ''conf'' folder
 
# ''IDMarker'' and ''Markerless'' folder contain a ''res'' and a ''conf'' folder
Line 15: Line 15:
 
## The ''conf'' folder contains all the configuration files
 
## The ''conf'' folder contains all the configuration files
  
−
The following picture shows an exemplary sketch of the folder structure:
+
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.
−
:[[File:folder_structure.png]]
+
  
 +
The following shows an exemplary sketch of the folder structure:
  
−
== Action Mapping XML Setup ==
+
<source lang="xml">
 +
/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
 +
</source>
 +
 
 +
= 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 picture must also be provided. In the example it is '''../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.
 +
 
 +
The example below show the configuration of the location of the image:
 +
<source lang="xml">
 +
  <SensorCOS>
 +
    <SensorCOSID>1</SensorCosID>
 +
    <Parameters>
 +
        <referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
 +
    </Parameters>
 +
  </SensorCOS>
 +
</source>
 +
 
 +
{{Attention|The ID must be an integer number and it is not allowed to leave gaps, otherwise tracking wont work!}}
 +
 
 +
= Action Setup =
  
−
After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can be found inside the ''UBIK'' Folder and is named ''xsd_schema_validation''.
+
After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can be found inside the example package provided in the prerequisites section (xml_schema_xsd).
 +
Since version 2.4.4, GeometryAction derives from UBIKObjectAction. When a geometry is clicked, it will try to find the respective UBIK object and show a dialog for it.
  
−
The action mapping xml contains different actions such as GeometryAction, MovieAction and UBIKObjectAction.
+
The action mapping Xml contains different actions such as
 +
* GeometryAction (3D Object)
 +
* MovieAction
 +
* UBIKObjectAction
  
−
* The following xml shows an example configuration:
+
The following Xml shows an example configuration:
 
<source lang="xml">
 
<source lang="xml">
 
<TrackingActionMapping>
 
<TrackingActionMapping>
−
<GeometryAction TrackingID="1">
+
  <GeometryAction TrackingID="1">
−
  <GeometryResource>
+
    <!-- Since 2.4.4, you can use a UBIK-UID for linking an POI dialog to the geometry. -->
−
    <ResourcePath>pump.obj</ResourcePath>
+
    <!-- Alternatively, you can configure (by customizing) an object with Marker Classification and its Marker ID set to the Tracking ID of this action. -->
−
    <Scale>100</Scale>
+
    <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
−
  </GeometryResource>
+
    <GeometryResource>
−
</GeometryAction>  
+
      <ResourcePath>pump.obj</ResourcePath>
 +
      <Scale>100</Scale>
 +
    </GeometryResource>
 +
  </GeometryAction>  
  
−
<UBIKObjectAction TrackingID="2"/>
+
  <GeometryAction TrackingID="2">
−
<GeometryAction TrackingID="5">
+
    <GeometryResource>
−
  <GeometryResource>
+
      <ResourcePath>pump.obj</ResourcePath>
−
    <ResourcePath>pump.obj</ResourcePath>
+
      <Scale>100</Scale>
−
    <Scale>100</Scale>
+
      <RotationDegrees>
−
    <RotationDegrees>
+
 
         <Z>90</Z>
 
         <Z>90</Z>
−
    </RotationDegrees>
+
      </RotationDegrees>
−
  </GeometryResource>
+
    </GeometryResource>
−
</GeometryAction>
+
  </GeometryAction>
 +
 
 +
  <UBIKObjectAction TrackingID="3">
 +
    <!-- Alternatively, you can configure (by customizing) an object with Marker Classification and its Marker ID set to the Tracking ID of this action. -->
 +
    <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
 +
  </UBIKObjectAction>
  
−
<UBIKObjectAction TrackingID="6">
 
−
  <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
 
−
</UBIKObjectAction>
 
−
 
 
</TrackingActionMapping>
 
</TrackingActionMapping>
 
</source>
 
</source>
  
−
All Action tags must specify a Tracking id, as an attribute. The Tracking id must exist in the tracking xml.
+
All Action tags must specify a TrackingID attribute, where ID value must exist in the corresponding tracking Xml within a ''<SensorCOSID>'' tag.
  
 
{{Attention|If a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.}}
 
{{Attention|If a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.}}
  
−
=== GeometryAction Tag ===
+
=== Displaying 3D objects ===
  
−
Inside the ''GeometryAction'' tag there can be a GeometryResource tag that defines the type of resource required for the GeometryAction.
+
3D objects can be displayed using the ''<GeometryAction>'' tag. The sub-tag ''<GeometryResource>'' defines the content and the parameters for displaying the 3D object.
 +
 
 +
==== UBIK-UID Tag ====
 +
 
 +
Available since version 2.4.4:
 +
Just like the UBIKObjectAction, this action allows the usage of a optional UBIK-UID tag, specifying the ID of a UBIK object.
 +
If it is specified, the respective object is linked to this geometry; else, it is tried to find an object with a marker classification and the geometry action's tracking ID for it's marker id value.
 +
When the user clicks on the geometry, a dialog is opened for the linked object (if found).
  
 
==== GeometryResource Tag ====
 
==== GeometryResource Tag ====
Line 69: Line 124:
 
# '''RotationDegrees'''. if specified, the 3D object will be rotated by this value against the detected marker.
 
# '''RotationDegrees'''. if specified, the 3D object will be rotated by this value against the detected marker.
  
−
* ''Resource path example''. pump/pump.obj.
+
* ''Resource path example''
 +
<source lang="xml">
 +
pump/pump.obj
 +
</source>
  
 
* ''OffsetMillimeters example''.
 
* ''OffsetMillimeters example''.
Line 78: Line 136:
 
</source>
 
</source>
  
 +
In the following rotation example the user must see the 3D object rotated around X axis and around Z axis 90 degrees.
 +
Note that the angle is in radians.
 +
* ''RotationDegrees example''.
 +
<source lang="xml">
 +
  <Rotation>
 +
    <X>0.5707</X>
 +
    <Z>0.5705</Z>
 +
  </Rotation>
 +
</source>
  
−
=== MovieAction Tag ===
+
=== 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 ====
+
==== MovieResource Tag====
  
−
The ''MovieResource'' Tag contains the same values as the ''GeometryResource'' except the rotation vector.
+
Movies can be displayed using the ''<MovieResource>'' tag, which basically contains the same values as the ''GeometryResource'', except the rotation vector.
  
−
==== PlayButton Tag ====
+
==== PlayButton Tag====
 +
By using the ''<PlayButton>'' tag, the movie will not start immediately but there will be a geometry shown in between which basically contains the same values as the ''GeometryResource'' tag. Its purpose is to start the video only when this intermediate geometry is touched.
  
−
The ''PlayButton'' Tag, if it is defined, contains the same values as the ''GeometryResource'' tag. Its purpose is to start a video, if the geometry is touched.
 
−
 
−
=== UBIKObjectAction Tag ===
 
−
 
−
The ''UBIKObjectAction'' tag should enable handling of the {{UBIK}} objects when scanning either a picture or an id marker. The tag must contain the tracking id attribute and, optional, the ubik-uid tag.
 
−
# Example. When configuring a tag without the ubik-uid tag the object is searched based on its MarkerID property which is the value inside TrackingID attribute. If the ubik-uid tag exists the object is searched based on the value inside the ubik-uid tag.
 
−
== Tracking Data XML ==
 
−
 
−
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:
 
 
<source lang="xml">
 
<source lang="xml">
−
   <SensorCOS>
+
<MovieAction>
−
     <SensorCOSID>1</SensorCosID>
+
   <MovieResource>
−
    <Parameters>
+
     ...
−
        <referenceImage widthMM="420" heightMM="297">../res/img_pic.png</referenceImage>
+
  </MovieResource>
−
    </Parameters>
+
  <PlayButton>
−
   </SensorCOS>
+
      <Scale>150</Scale>
 +
      <ResourcePath>plane/plane.obj</ResourcePath>
 +
      <RotationDegrees>
 +
        <Z>3.14</Z>
 +
      </RotationDegrees>
 +
   </PlayButton>
 +
</MovieAction>
 
</source>
 
</source>
  
−
== '''Usage''' ==
+
=== Displaying an UBIK object dialog ===
−
In order to use the previously configured xmls, you can use either the ID Marker activity or the Markerless activity on the {{UBIK}} Android Client.
+
 
 +
The ''<UBIKObjectAction>'' allows to bring up a popup to navigate to an {{UBIK}} object when scanning either a picture or an ID marker. The tag must contain the tracking ID attribute and, optional, the ''<UBIK-UID>'' tag.
 +
When configuring a tag without the ''UBIK-UID'' sub-tag, the object is searched based on the value of its ''MarkerID'' property, which is compared to the value of the ''TrackingID'' attribute. If the ''UBIK-UID' tag exists the object is searched based on the value inside the ''UBIK-UID' tag.
  
 +
= Example =
 +
In order to use the previously configured xml's, you can use either the ID Marker activity or the Markerless activity on the {{UBIK}} Android Client.
  
 
=== ID Marker Activity ===
 
=== ID Marker Activity ===
  
−
The id markers used can be found at the following link [http://wiki.augmensys.com/index.php/File:ID_Marker_Example_1_6.pdf ID Marker Example Ids 1-6]
+
The ID markers used can be found at the following link {{FileLink|ID_Marker_Example_1_6.pdf|ID Marker Example Ids 1-6}}.<br>
−
Having in mind the setup tracking ids, you can now scan id markers.  
+
Having in mind the setup tracking IDs, you can now scan ID markers.  
−
* For an id that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.  
+
* For an ID that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.  
−
* If the id has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button.
+
* If the ID has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button. Clicking the play button starts the video.
−
* If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, the movie will be shown immediately.
+
* If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, a movie preview image will be shown. Clicking the image starts the video.
  
 
=== Markerless Activity ===
 
=== Markerless Activity ===
  
−
The scenario is very similar with the id marker activity with the only difference that instead of ids you have to scan your tracking images.
+
The markerless photos used in this example can be found at the following link {{FileLink|Markerless_Examples._Pics_1-7.pdf|Markerless example pictures}}.<br>
 +
The scenario is very similar with the ID marker activity with the only difference that instead of IDs you have to scan your tracking images.
  
−
=== Examples ===
+
=== Results ===
  
−
With the existent configuration from the zip file, you should see the following picture when scanning the first id or the first picture:
+
With the existent configuration from the .zip file, you should see the following picture when scanning the first ID or the first picture:
−
:[[File:scanning_id1.png]] <br>
+
:[[File:scanning_id1.png|border]] <br>
  
−
When scanning the second id or the second picture, you should see the following:
+
When scanning the second ID or the second picture, you should see the following:
−
:[[File:scanning_id2.png]] <br>
+
:[[File:scanning_id2.png|border]] <br>
  
−
When scanning the sixth id, using the Markerless activity, you should see a play button and, if pressed, a movie.
+
When scanning the sixth ID, using the Markerless activity, you should see a play button and, if pressed, a movie.
 
* Play button:
 
* Play button:
−
:[[File:scanning_id3_play_button.png]] <br>
+
:[[File:scanning_id3_play_button.png|border]] <br>
 
* Movie:
 
* Movie:
−
:[[File:scanning_id3_movie.png]] <br>
+
:[[File:scanning_id3_movie.png|border]] <br>
  
−
When scanning the sixth id using the IdMarker Activity you should see a play button also and, if pressed, a movie too.
+
When scanning the sixth ID using the IdMarker Activity you should see a play button also and, if pressed, a movie too.
 
* Play button:
 
* Play button:
−
:[[File:scanning_id6_play_button.png]] <br>
+
:[[File:scanning_id6_play_button.png|border]] <br>
 
* Movie:
 
* Movie:
−
:[[File:scanning_id6_movie.png]] <br>
+
:[[File:scanning_id6_movie.png|border]] <br>
  
−
[[Category:How-To]]
+
[[Category:Client|Configure Dynamic AR Content]]
−
[[Category:UBIK Client]]
+
[[Category:How-To|Configure Dynamic AR Content]]
 +
[[Category:POI|Configure Dynamic AR Content]]

Latest revision as of 09:28, 20 May 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 IC FileLink Download.png Dynamic_AR_Content_Folder_Structure.rar. Since version 2.4.4, the schema changed slightly (downwards compatible). The updated example package can be found here: IC FileLink Download.png Dynamic_AR_Content_Folder_Structure_244.zip 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

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 picture must also be provided. In the example it is ../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.

The example below show 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!

Action Setup

After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at Online XML Schema Validator. The schema used to validate against can be found inside the example package provided in the prerequisites section (xml_schema_xsd). Since version 2.4.4, GeometryAction derives from UBIKObjectAction. When a geometry is clicked, it will try to find the respective UBIK object and show a dialog for it.

The action mapping Xml contains different actions such as

  • GeometryAction (3D Object)
  • MovieAction
  • UBIKObjectAction

The following Xml shows an example configuration:

<TrackingActionMapping>
  <GeometryAction TrackingID="1">
    <!-- Since 2.4.4, you can use a UBIK-UID for linking an POI dialog to the geometry. -->
    <!-- Alternatively, you can configure (by customizing) an object with Marker Classification and its Marker ID set to the Tracking ID of this action. -->
    <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
    <GeometryResource>
      <ResourcePath>pump.obj</ResourcePath>
      <Scale>100</Scale>
    </GeometryResource>
  </GeometryAction>

  <GeometryAction TrackingID="2">
    <GeometryResource>
      <ResourcePath>pump.obj</ResourcePath>                                    
      <Scale>100</Scale>
      <RotationDegrees>
        <Z>90</Z>
      </RotationDegrees>
    </GeometryResource>
  </GeometryAction>

  <UBIKObjectAction TrackingID="3">
    <!-- Alternatively, you can configure (by customizing) an object with Marker Classification and its Marker ID set to the Tracking ID of this action. -->
    <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
  </UBIKObjectAction>

</TrackingActionMapping>

All Action tags must specify a TrackingID attribute, where ID value must exist in the corresponding tracking Xml within a <SensorCOSID> tag.

IC Attention.pngIf a texture is used for a geometry, the material (*.mtl file) and the texture (picture) must all exist in the same place in order for to have the 3D object displayed properly, Only the geometry has to be specified as a resource in the Action Mapping, though.

Displaying 3D objects

3D objects can be displayed using the <GeometryAction> tag. The sub-tag <GeometryResource> defines the content and the parameters for displaying the 3D object.

UBIK-UID Tag

Available since version 2.4.4: Just like the UBIKObjectAction, this action allows the usage of a optional UBIK-UID tag, specifying the ID of a UBIK object. If it is specified, the respective object is linked to this geometry; else, it is tried to find an object with a marker classification and the geometry action's tracking ID for it's marker id value. When the user clicks on the geometry, a dialog is opened for the linked object (if found).

GeometryResource Tag

The GeometryResource contains:

  1. Resource path: the resource path of the 3D object or video to be displayed.
  2. Scale: if specified, the 3D object will be scaled to this size.
  3. OffsetMillimeters: if specified, this value will be added to the position of the detected marker when displaying the 3D object. The offset can be defined along the X, Y and Z axis.
  4. RotationDegrees. if specified, the 3D object will be rotated by this value against the detected marker.
  • Resource path example
pump/pump.obj
  • OffsetMillimeters example.
  <OffsetMillimeter>
    <X>10</X>
  </OffsetMillimeter>

In the following rotation example the user must see the 3D object rotated around X axis and around Z axis 90 degrees. Note that the angle is in radians.

  • RotationDegrees example.
  <Rotation>
    <X>0.5707</X>
    <Z>0.5705</Z>
  </Rotation>

Displaying movies

Inside the MovieAction tag there can be two possible resources defined, a MovieResource and a PlayButton resource.

MovieResource Tag

Movies can be displayed using the <MovieResource> tag, which basically contains the same values as the GeometryResource, except the rotation vector.

PlayButton Tag

By using the <PlayButton> tag, the movie will not start immediately but there will be a geometry shown in between which basically contains the same values as the GeometryResource tag. Its purpose is to start the video only when this intermediate geometry is touched.

<MovieAction>
  <MovieResource>
    ...
  </MovieResource>
  <PlayButton>
      <Scale>150</Scale>
      <ResourcePath>plane/plane.obj</ResourcePath>
      <RotationDegrees>
        <Z>3.14</Z>
      </RotationDegrees>
  </PlayButton>
</MovieAction>

Displaying an UBIK object dialog

The <UBIKObjectAction> allows to bring up a popup to navigate to an UBIK® object when scanning either a picture or an ID marker. The tag must contain the tracking ID attribute and, optional, the <UBIK-UID> tag. When configuring a tag without the UBIK-UID sub-tag, the object is searched based on the value of its MarkerID property, which is compared to the value of the TrackingID attribute. If the UBIK-UID' tag exists the object is searched based on the value inside the UBIK-UID' tag.

Example

In order to use the previously configured xml's, you can use either the ID Marker activity or the Markerless activity on the UBIK® Android Client.

ID Marker Activity

The ID markers used can be found at the following link IC FileLink Download.png ID Marker Example Ids 1-6.
Having in mind the setup tracking IDs, you can now scan ID markers.

  • For an ID that has a 3D object mapped in the action xml, the object should be displayed on the screen as shown in the next picture.
  • If the ID has a video object mapped in the action xml, you should see a video object on the screen, depending on the existence of the play button. Clicking the play button starts the video.
  • If the play button exist you should see first see the play button, and after it's clicked the mapped video. If the play button doesn't exist, a movie preview image will be shown. Clicking the image starts the video.

Markerless Activity

The markerless photos used in this example can be found at the following link IC FileLink Download.png Markerless example pictures.
The scenario is very similar with the ID marker activity with the only difference that instead of IDs you have to scan your tracking images.

Results

With the existent configuration from the .zip file, you should see the following picture when scanning the first ID or the first picture:

Scanning id1.png

When scanning the second ID or the second picture, you should see the following:

Scanning id2.png

When scanning the sixth ID, using the Markerless activity, you should see a play button and, if pressed, a movie.

  • Play button:
Scanning id3 play button.png
  • Movie:
Scanning id3 movie.png

When scanning the sixth ID using the IdMarker Activity you should see a play button also and, if pressed, a movie too.

  • Play button:
Scanning id6 play button.png
  • Movie:
Scanning id6 movie.png
Retrieved from "https://wiki.augmensys.com/index.php?title=HowTo:Configure_Dynamic_AR_Content&oldid=15649"