Jump to: navigation, search

Changes


HowTo:Configure Dynamic AR Content

612 bytes added, 07:22, 9 May 2014
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''.
The action mapping xml contains different actions such as GeometryAction(3D Object), MovieAction and UBIKObjectAction.
* The following xml shows an example configuration:
<source lang="xml">
<TrackingActionMapping>
<GeometryAction TrackingID="1"> <GeometryResource> <ResourcePath>pump.obj</ResourcePath> <Scale>100</Scale> </GeometryResource> </GeometryAction>
<UBIKObjectAction GeometryAction TrackingID="2"/><GeometryAction TrackingID="5"> <GeometryResource> <ResourcePath>pump.obj</ResourcePath> <Scale>100</Scale> <RotationDegrees>
<Z>90</Z>
</RotationDegrees> </GeometryResource> </GeometryAction>  <UBIKObjectAction TrackingID="3"> <UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID> </UBIKObjectAction>
<UBIKObjectAction TrackingID="6">
<UBIK-UID>a5aa5a70-591f-11e3-949a-0800200c9a66</UBIK-UID>
</UBIKObjectAction>
</TrackingActionMapping>
</source>
All Action tags must specify a Tracking id, as an attribute. The Tracking id must exist in the corresponding tracking xmlwithin 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.}}
=== GeometryAction Tag Displaying 3D objects ===
Inside 3D objects can be displayed using the ''<GeometryAction>'' tag there can be a GeometryResource . The sub-tag that ''<GeometryResource>'' defines the type of resource required content and the parameters for displaying the GeometryAction3D object.
==== GeometryResource Tag ====
</source>
In the following rotation example the user must see the 3d 3D object rotated around X axis and around Z axis 90 degrees.
Note that the angle is in radians.
* ''RotationDegrees example''.
</source>
=== MovieAction Tag Displaying movies ===
Inside the ''MovieAction'' tag there can be two possible resources defined, a MovieResource and a PlayButton resource.
==== MovieResource Tag====
The Movies can be displayed using the ''<MovieResource>'' Tag 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.
The ''<source lang="xml"><MovieAction> <MovieResource> ... </MovieResource> <PlayButton'' Tag, if it is defined, contains the same values as the ''GeometryResource'' tag> <Scale>150</Scale> <ResourcePath>plane/plane. Its purpose is to start a video, if the geometry is touchedobj</ResourcePath> <RotationDegrees> <Z>3.14</Z> </RotationDegrees>=== UBIKObjectAction Tag === </PlayButton> </MovieAction></source>
The ''UBIKObjectAction'' tag should enable handling of the {{=== Displaying a 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.dialog ===
== The ''<UBIKObjectAction>'Usage'allows to bring up a popup to navigate to a {{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.In order to use When configuring a tag without the previously configured xmls''UBIK-UID'' sub-tag, you can use either the ID Marker activity or object is searched based on the value of its ''MarkerID'' property, which is the compared to the value of the ''TrackingID'' attribute. If the ''UBIK-UID' tag exists the Markerless activity object is searched based on the {{value inside the ''UBIK}} Android Client-UID' tag.
== '''Examples''' ==
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 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: