HOLOCEIVE / AR TRACKING SDK
3D object tracking SDK for Unity, iOS and Android
Holoceive SDK is a native 3D object tracking SDK for aligning digital content with physical products, equipment and components. Integrate object position and orientation into Unity, iOS or Android apps, with target preparation and engine customization by Holoceive. Bring your CAD model, mesh or physical sample to discuss an evaluation.
Discuss your target and integration ↗CAD-based object tracking: from model to AR pose
A CAD-based tracking workflow uses a model of a known object to prepare a target, then estimates the object’s 3D position and rotation from camera images. This six-degree-of-freedom (6DoF) pose lets an app align instructions or highlights with the object. For Holoceive SDK, we review the model, physical dimensions and visible surfaces together, then agree on target preparation and test the actual part. CAD geometry alone does not establish tracking accuracy.
Object recognition and pose tracking
Identifying which object is in an image does not by itself establish a stable position and orientation for an AR overlay. Specify what the application needs after recognition: a label near the object, an overlay aligned with a component, or a sequence of instructions. The required alignment and failure behavior determine how the tracking evaluation should be designed.
Unity object tracking: connect poses to your scene
Unity object tracking for AR estimates the position and rotation of a real object so your app can align a GameObject with it. Holoceive SDK supports Unity integration through its native engine. Start with one representative object and scene, then define camera access, target data, coordinate conversion and how content responds when tracking is lost.
A practical Unity integration plan
Identify the Unity version, iOS or Android build target, rendering pipeline and camera owner. Agree on the target origin, physical scale and transform into Unity coordinates. Validate an anchored label or model while the camera and object move, including pause, resume and reacquisition. The integration scope defines who prepares target data, implements the adapter and tests the scene.
Anchor product labels and assembly guidance to an object
Define which physical feature a label, highlight or instruction should stay aligned with. Use object tracking when the overlay must follow the product itself; placing content at a fixed world position solves a different problem. For an assembly or inspection workflow, agree on what to display if a hand covers the part or the target leaves the camera view. Test that behavior on the actual object before expanding the integration.
CAD models, meshes and physical samples
Tell us what you have: CAD, a mesh, photographs, a physical sample or only a concept. Include units, dimensions and the relevant configuration of the object. We review file compatibility, differences between the model and the physical object, and surface appearance to determine how to prepare the tracking data.
Test difficult surfaces and object configurations
For an equipment or product application, describe reflective or transparent surfaces, repeating parts, moving assemblies and removable components. Specify whether the object itself can move and whether hands or tools cover it during use. Include these conditions in the evaluation scope. A short recording of the intended interaction can be useful when planning tests.
Test alignment and tracking recovery
Agree on the coordinate origin, units and the reference used to measure alignment. Record initialization success across viewpoints, tracking loss during the task and recovery after occlusion. Test representative devices for sustained operation, not only a short launch sequence. If several engines are compared, keep the object, camera path, lighting, devices and scoring method consistent.
Figurines, product models and components
For a figurine, identify the surfaces visible from the intended viewing angles and whether users rotate the object. For a product model, define the reference origin so annotations line up with the correct part. For components, include hands, tools and configuration changes in the test. These use cases share a tracking pipeline but require different target preparation and acceptance criteria.
Discuss industrial AR integration before implementation
An inspection or assembly guide may need different update rates, alignment tolerances and fallback UI from a product visualization. Describe what a user should see when confidence is insufficient or tracking is lost. We define an evaluation for your requirements and agree on SDK delivery, interfaces, tuning and support. Use the agreed acceptance test to decide whether the integration is ready for your application.
What to include in your evaluation request
- Object dimensions, material, moving parts and relevant variants
- Available CAD, mesh, photos or access to a physical sample
- The exact task the aligned overlay should support
- Target devices, camera access and Unity or native application stack
- Acceptance criteria, test conditions and deployment constraints
Project-based integration with the Holoceive SDK engine team.