📐Transforming Content
Learn how to move, scale, and rotate 3D content in Scene Viewer.
Last updated
Learn how to move, scale, and rotate 3D content in Scene Viewer.
Last updated
Move the model by tapping the screen with one finger and moving the finger around the screen.
Scale the model by pinching the screen with two fingers.
You can use metadata to persistently transform 3D content.
If the content is too big or too small, go back to the console and add metadata to affect its transformation. After adding or changing metadata refresh the browser and relaunch the experiences for the changes to take effect.
The following keys are words the system uses as pre-defined metadata keys to control transformations:
scale
float
Any positive number. Default value is 1.
Grows or shrinks the hologram uniformly
Refresh the browser and relaunch the experiences after adding metadata with WebAR experiences for the changes to take effect.
Rotate the model by placing two fingers on the screen and moving them in a circular motion.
You can also use two thumbs and move them up and down, each thumb in the opposite direction.
You can use metadata to persistently transform 3D content.
If you can add metadata to further adjust the starting rotation of the model. After adding or changing metadata refresh the browser and relaunch the experiences for the changes to take effect.
The following keys are words the system uses as pre-defined metadata keys to control transformations:
xAngle
float
Any positive or negative number.
Default value is 0.
Rotates the model on the x-axis
yAngle
float
Any positive or negative number.
Default value is 0.
Rotates the model on the y-axis
zAngle
float
Any positive or negative number.
Default value is 0.
Rotates the model on the z-axis
Remember to relaunch the experience after adding metadata with Scene Viewer experiences for the changes to take effect.
If you'd like to annotate the content, go back to the console and add metadata to add text. After adding metadata, relaunch the experience.
The following keys are words the system uses as pre-defined metadata keys to add and design text:
Keyword
Type
Options
Description
annotation<NAME>_content
string
Any string.
Text to appear with the 3D content
annotation<NAME>_position
float,float,float
Any triplet of positive or negative numbers.
Position of the text relative to the 3D content
annotation<NAME>_normal
float,float,float
Any triplet of positive or negative numbers.
Normal vector defining the "front" of text relative to the 3D content
For example:
Key
Value
annotationName1_content
Empire State
annotationName1_position
1,1,1
annotationName1_normal
-0.1,0.5,0
Remember to relaunch the experience after adding metadata with Scene Viewer experiences for the changes to take effect.
Can't see the text? The original size of the model might affect the annotations' coordinate system and displace the location of text. We recommend placing your annotations at 0,0,0 first and then fine tuning the coordinate of each axis.
Controlling animations requires that you to upload pre-animated 3D assets that have a built-in animations list.
If you'd like to control built-in animations of the content, go back to the console and add metadata to control animations. After adding metadata, relaunch the experience.
The following keys are words the system uses as pre-defined metadata keys to control built-in animations:
Keyword
Type
Options
Description
autoplay
boolean
Either 'true' or 'false'.
Default value 'true'.
Play the default animation automatically.
animationsTrigger
string
Either 'click' or 'after'. Default value 'click'.
Play the next animation by clicking the model or automatically after the previous animation.
animation<X>_name
string
Any string that matches a name of an existing built-in animation in the asset's pre-defined animations list.
The animation's place in the sequence of the animations that is presented.
animation_loop
boolean
Either 'true' or 'false'.
Default value 'false'.
Play the animation once or in a loop. This option is available only if 'animationsTrigger' is not set to 'after'.
For example:
Key
Value
animation1_name
walking
animation2_name
running
Remember to relaunch the experience after adding metadata with Scene Viewer experiences for the changes to take effect.
