Skip to main content

Features

Frequently asked questions about SPECS Lens features, including Marker Tracking, audio, Connected Lenses, and Face Tracking.

These are common questions about Lens features and how they behave on SPECS, including tracking, audio, and Connected Lenses.

Marker Tracking


Marker Tracking works on SPECS. If the tracking result is misaligned with the target, check the size of the marker: in the Image Tracker asset in Lens Studio, set the real size of the printed or displayed image, in centimeters.

Audio Component


SPECS has no fixed limit on how many audio tracks a Lens can play at once. Each track that plays costs CPU time and memory, though, so a Lens that plays many tracks at the same time can run out of resources. Play only the tracks you need at any moment, and stop tracks you no longer need.

Connected Lens


When a user joins a Connected Lens session that uses SyncKit, the setup runs in this order:

  1. The session is created and the user connects to it.
  2. The session's shared stores are created.
  3. For a colocated session, the Lens maps the space or relocalizes in it.
  4. The session is ready: SessionController.notifyOnReady() callbacks run, and SessionController APIs can be called.
  5. Each SyncEntity finishes setting up and runs its notifyOnReady() callbacks. Its storage properties can now be set and read.
  6. Each Instantiator finishes setting up and runs its notifyOnReady() callbacks.

For the full flow and a flowchart, see Lifecycle for SyncKit.

Face Tracking


Yes, with some limitations:

  1. Use the Head Binding component to attach 3D objects to the head.
  2. Set Attachment Point Type to Candide Center, Right Eyeball, or Left Eyeball only.