By Topic

Combining ARToolKit with scene graph libraries

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

4 Author(s)
M. Haller ; Univ. of Appl. Sci., Hagenberg, Austria ; W. Hartmann ; T. Luckeneder ; J. Zauner

Many Augmented and Mixed Reality applications are based on two libraries: OpenGL is used for rendering and ARToolKit is used for marker recognition. The ARToolkit library is great for rapid prototyping of AR/MR applications. The library is very easy to use and it hides the complexity of marker recognition. In the AMIRE (Authoring Mixed Reality) project, a European founded AR project, we follow up the aim of ARToolKit consistently: the AMIRE approach is to offer well-established gems (software solutions) and components for a faster prototyping of AR/MR applications. Each content user should be able to develop his/her own AR/MR application without any computer graphics skills. Therefore, one of the primary goals of AMIRE is to find well-established solutions of current AR/MR applications. One of the solution is the ARToolKit library, which is used in numberless AR/MR applications. But which library should be used for rendering? Can we use a high-level graphics AN together with ARToolKit? Which graphic library would be the best for farther AR/MR applications? Should developers use Direct3D/OpenGL or should we propose a high-level graphics API, like Open Inventor, OpenGL Performer, OpenSG, or Open SceneGraph? High-level graphics APIs have a number of advantages as opposed to low-level graphics APIs. They include: A set of loaders (e.g. model and texture loaders); A scenegraph concept; Modern object oriented design; High performance (optimized rendering, view frustum culling, small object culling, Level of Detail nodes, etc.). One problem still remains: How difficult is the usage of ARToolKit, originally based on OpenGL, in combination with a high-level graphics API like OpenSG? For the AMIRE project we tested two different APIs: Open SO and Open SceneGraph.

Published in:

Augmented Reality Toolkit, The First IEEE International Workshop

Date of Conference: