Important notes / considerations for achieving the best AR-experience possible

→Return to Getting Started

3D-content preparation

Besides the information below, please also refer to the general content preparation section.

• further information regarding VRML http://www.web3d.org/x3d/specifications/vrml/ISO-IEC-14772-VRML97/part1/nodesRef.html
• supports models up to 2 million polygons (maximum count highly depends on the used hardware)
• for texturing, UV-mapping is required
• "power of 2" - textures recommended (e.g 512x512)
• textures not bigger than 2048x2048 (1024x1024 recommended, depending on the graphics card memory-size)
• format: JPG .jpg and PNG .png (with alpha channel)
• due to VRML-format limitations avoid using any dynamics and particles

Renderer

Besides the information below, please also refer to the Renderer section.

• Bitmanagement BS Contact: http://www.bitmanagement.com/
• no advanced Shading possibilities (eg. Specular-, Normal-, Bump-Maps etc.) using standard VRML-Rendering. Such advanced Shading can be done using Direct X in combination with HLSL (.fx).

Videos

• correct video-playback is only possible using VRML-visibility sensors and Timers (as described here: UnifeyeDesignFAQs -> VRML)

Tracking

Besides the information below, please also refer to the tracking configuration section and the planar markerless tracking configuration tool.

• not every image is suitable for tracking - get instant feedback from the tracking quality test within the planar markerless tracking configuration tool.
• avoid shiny/glossy surfaces as tracking-reference because it may disturb/reduce the tracking quality significantly.
• choose your tracking reference according to its later screen-size in the camera image (e.g camera resolution: 640x480 pixel -> tracking reference should have a smaller resolution e.g. 400x400 pixel).
• best tracking performance can be reached when your reference image resolution corresponds with the following formula (for the smallest number of your resolution): 25*power(2,n).
• keep in mind that the smaller you design/print out the marker, the closer it has to get to the camera for recognition.

Camera

• use small exposure times (e.g 1/50s or 1/100s) and appropriate sensitivity (gain) values to assure that the camera response is fast enough to follow all your movement in real-time without delay.
• HD-Imaging (HD-Cameras) needs a fast PC-system to handle the big amount of image-data and is only recommended up to 720p (1280x720).
• be Aware that USB-Cameras are limited in terms of bandwidth and may do some unpleasant image-compression/up-scaling to reach HD-Resolution (which normally would exceed USB bandwidth capacities)
• correct any lense-distortions by doing a camera calibration using our Sextant Camera Calibration Tool

Display Devices

• Make sure that the aspect ratio of your display device and the camera resolution match.
• To assure the best possible viewing quality, always adapt the camera resolution to your screen size (small screen - lower resolution possible, big screen - higher resolution recommended)

Workflow-Engine

Besides the information below, please also refer to the Workflow-Engine and Authoring GUI overview section or move directly to the detailed Workflow Authoring GUI documentation.

• Workflows are limited to a total of 100 action-nodes

→Return to Getting Started

-- SupportMetaio - 2010-07-15