I\'m currently doing some experiments with RealityKit.
I\'ve been looking at some sample code, and I\'m a bit confused about the differences between ARAnchor
Updated: July 11, 2020.
ARAnchor
class and AnchorEntity
class were both made for the same divine purpose – to tether a 3D content to your real-world objects.
RealityKit AnchorEntity
greatly extends the capabilities of ARKit ARAnchor
. The most important difference between these two is that AnchorEntity
automatically tracks a real world target, but ARAnchor
needs renderer(...)
or session(...)
instance methods to accomplish this. Also take into consideration that the collection of ARAnchors
is stored in the ARSession and the collection of AnchorEntities
is stored in the Scene.
Here are hierarchical differences:
Apple Developer documentation says:
In RealityKit framework you use an
AnchorEntity
instance as the root of an entity hierarchy, and add it to theanchors collection
for a Scene instance. This enables ARKit to place the anchor entity, along with all of its hierarchical descendants, into the real world. In addition to the components the anchor entity inherits from theEntity
class, the anchor entity also conforms to theHasAnchoring
protocol, giving it anAnchoringComponent
instance.
AnchorEntity
has three building blocks:
world
, body
or image
)All entities have Synchronization component
that helps organise collaborative sessions.
AnchorEntity
has nine specific anchor types for nine different purposes:
You can simultaneously use both classes ARAnchor
and AnchorEntity
in your app. Or you can use just AnchorEntity
class because it's all-sufficient one.
For additional info about
ARAnchor
andAnchorEntity
, please look at THIS POST.