PERCEPT / TECHNICAL EVALUATION
3D object tracking for your physical product
Object tracking evaluation should begin with the real object and the task an overlay needs to support. Percept offers discussions around object-specific tracking and native engine customization for AR applications.
Recognition is not the same as tracking pose
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.
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. Model availability does not guarantee that a particular file format can be imported directly or that the object will track reliably. Data preparation, geometry differences and surface appearance must be reviewed before confirming a workflow.
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. These are evaluation conditions, not promises that a tracker can handle every case. A short recording of the intended interaction can be useful when planning tests.
Define a pose and recovery acceptance test
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.
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. Percept can be evaluated against a scoped requirement; SDK distribution, supported interfaces, tuning and support are agreed with Holoceive. No head-to-head performance results are currently published.
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 Percept engine team.