The 3D model content type is probably the most appealing one for augmented reality experiences. genARate offers a basic pipeline for the integration and use of 3D- models.

What's the benefit?

This feature enables you to place an interactive 3D model in the user’s environment. Users can tap a 3D-thumbnail button to view the model in augmented reality.

Once decided to add a 3D-model overlay to your AR.Create WonderPage follow the explanation below.

Here you can find out how to

How to add a 3D model:

Step 1: Click on the 3D icon inside the toolbar to start the upload dialogue.

Step 2: Upload a 3D model. Choose between your own model or insert from the Library.

  • To use 3D models from the library click the insert button on the right

  • A new window will open with available 3D-assets

  • The Green section shows the type of the 3D model (animated/static)

  • Click on the 3D model to insert it into your target image

  • After the upload has completed the 3D model will appear in the scenario editor

  • Click on the 3D model inside the scenario editor to move/position the element via drag & drop and to access the settings

Pro tip: If you want more information on how to create, export and convert 3D content have a look at our 3D-model article in the Best Practice collection.

Settings

ATTRIBUTES

Name: Select a unique name for your 3D element.

Source: Name of uploaded source file and button to replace uploaded 3D-model “on the fly”.

Size: Set the individual size of 3D model (by width and height of ground plane – the aspect ratio is fixed).

Position: Set the individual position of the model (by x and y – z not available, yet).

Rotation: Set rotation of model (by ° for 3 axis x,y,z).

Hidden: Makes model invisible at the start of AR experience (to e.g. let it appear by a Button interaction at a later time).

Unique ID: Internal ID of the content element, mostly used for referencing inside HTML fragments.

Access 3D-model from HTML Fragment: Unique link to 3D-model, mostly used for referencing inside HTML fragments.

CONTENT

Auto play: The animation of the 3D model (which has to be provided inside the model) starts playing automatically when it appears in AR (if not, the user needs to click 3D- model to start, etc.)

Continue playing: 3D-model stays visible, also when image tracking is lost (target image is not visible in camera view anymore), the 3D-model will be displayed centered to the screen and user can rotate/scale it by touch interaction

ANIMATIONS

Animations make your WonderPage more appealing as they add some motion to static content. For each content element, you can easily define how it should appear/disappear as soon as a target image is scanned or lost.

See how to animate your AR elements here.

Formats & Restrictions:

genARate currently supports the following formats: GLTF (GLB), Subset of FBX (FBX Binary 2012). The genARate 3D engine is compatible with Three.js.

In terms of the size/complexity of 3D models, the technical limit of possible polygons is 500.000. The recommendation is to not go over 50.000 polygons in order to guarantee a smooth experience on most smartphones. In practice, you can find many good 3D- models offering an appealing mobile experience with around 10.000 polygons already.

Material Support

GLTF: Bump Maps, Reflective Materials, Matte Materials, Alpha Materials = GOOD.

FBX: Bump Maps, Reflective Materials, Matte Materials, Alpha Materials = GOOD.

Animation Support

GLTF: Bones = GOOD, Blend Shapes = Limited-GOOD, Transform Animation = GOOD.

FBX: Bones = Limited, Blend Shapes = No, Transform Animation = GOOD.

Not supported:

  • Import of complete scenes

  • Import of lighting

  • Custom Shaders

  • File size restriction: max 20 MB

Creation Pipeline:

  • Link Doc IR

  • Link Description Zan

  • Use of 3D Paint for conversion


Maybe interesting too:

Feel free to use different overlays in a single AR.Create WonderPage.

Further AR.Create overlay types are:

Image

Video

Audio

Text Box

Social Media

Buttons

Contact

Calendar Event

HTML

Did this answer your question?