Place virtual content on real-world surfaces, and enable the user to interact with virtual content by using gestures.
- iOS 13.0+
- Xcode 11.0+
The key facet of an AR experience is the ability to intermix virtual and real-world objects. A flat surface is the optimum location for setting a virtual object. To assist ARKit with finding surfaces, you tell the user to move their device in ways that help ARKit prepare the experience. ARKit provides a view that tailors its instructions to the user, guiding them to the surface that your app needs.
To enable the user to put a virtual item on the real-world surface when they tap the screen, ARKit incorporates ray casting, which provides a 3D location in physical space that corresponds to the screen’s touch location. When the user rotates or otherwise moves the virtual items they place, you respond to the respective touch gestures and correlate that input to the virtual content’s look in the physical environment.
Set a Goal to Coach the User’s Movement
To enable your app to detect real-world surfaces, you use a world tracking configuration. For ARKit to establish tracking, the user must physically move their device to allow ARKit to get a sense of perspective. To communicate this need to the user, you use a view provided by ARKit that presents the user with instructional diagrams and verbal guidance, called
ARCoaching. For example, when you start the app, the first thing the user sees is a message and animation from the coaching overlay telling them to move their device left and right, repeatedly, in order to get started.
To enable the user to place virtual content on a horizontal surface, you set the coaching overlay goal accordingly.
The coaching overlay then tailors its instructions according to the goal you choose. After ARKit gets a sense of perspective, the coaching overlay instructs the user to find a surface.
Respond to Coaching Events
To make sure the coaching overlay provides guidance to the user whenever ARKit determines it’s necessary, you set
The coaching overlay activates automatically when the app starts, or when tracking degrades past a certain threshold. In those situations, ARKit notifies your delegate by calling
coaching. In response to this event, hide your app’s UI to enable the user to focus on the instructions that the coaching overlay provides.
When the coaching overlay determines that the goal has been met, it disappears from the user’s view. ARKit notifies your delegate that the coaching process has ended, which is when you show your app’s main user interface.
Place Virtual Content
To give the user an idea of where they can place virtual content, annotate the environment to give them a preview. The sample app draws a square that gives the user visual confirmation of the shape and alignment of the surfaces that ARKit is aware of.
To figure out where to put the square in the real world, you use an
ARRaycast to ask ARKit where any surfaces exist in the real world. First, you create a ray-cast query that defines the 2D point on the screen you’re interested in. Because the focus square is aligned with the center of the screen, you create a query for the screen center.
Then, you execute the ray-cast query by asking the session to cast it.
ARKit returns a position in the
results parameter that includes the depth of where that point lies on a surface in the real world. To give the user a preview of where on the real-world surface a user can place their virtual content, update the focus square’s position using the ray-cast result’s
The ray-cast result also indicates how the surface is angled with respect to gravity. To preview the angle at which the user’s virtual content can be placed on the surface, update the focus square’s
simd with the result’s orientation.
If your app offers different types of virtual content, give the user an interface to choose from. The sample app exposes a selection menu when the user taps the plus button. When the user chooses an item from the list, you instantiate the corresponding 3D model and anchor it in the world at the focus square’s current position.
Refine the Position of Virtual Content Over Time
As the session runs, ARKit analyzes each camera image and learns more about the layout of the physical environment. When ARKit updates its estimated size and position of real-world surfaces, you may need to update the position of your app’s virtual content to match. To help make it easy, ARKit notifies you when it corrects its understanding of the scene by way of an
ARKit successively repeats the query you provide to a tracked ray cast, and it calls the closure you provide only when the results differ from prior results. The code you provide in the closure is your response to ARKit’s updated scene understanding. In this case, you check your ray-cast intersections against the updated planes and apply those positions to your app’s virtual content.
Manage Tracked Ray Casts
Because ARKit continues to call them, tracked ray casts can increasingly consume resources as the user places more virtual content. Stop the tracked ray cast when you no longer need refined positions over time, such as when a virtual balloon takes flight, or when you remove a virtual object from your scene.
To stop a tracked ray cast, you call its
Enable User Interaction with Virtual Content
To allow users to move virtual content in the world after they’ve placed it, implement a pan gesture recognizer.
When the user pans an object, you request its position along the object’s path across the plane. Because the object’s position is transitory, use a
raycast(_:) instead of using a tracked ray cast. In this case, a one-time hit test is appropriate because you don’t need refined position results over time for these requests.
Ray casting gives you orientation information about the surface at a given screen point. While dragging, you avoid quick changes in orientation by subtracting the gesture’s rotation from the current object rotation.
Handle Interruption in Tracking
In cases where tracking conditions are poor, ARKit invokes your delegate’s
session. In these circumstances, the positions of your app’s virtual content may be inaccurate with respect to the camera feed, so hide your virtual content.
Restore your app’s virtual content when tracking conditions improve. To notify you of improved conditions, ARKit calls your delegate’s
session(_: function, passing in a camera
tracking equal to
Restore an Interrupted AR Experience
When a session is interrupted, ARKit asks if you want to try to restore the AR experience. You do that by opting in to relocalization, by overriding
session and returning
During relocalization, the coaching overlay displays tailored instructions to the user. To allow the user to focus on the coaching process, hide your app’s UI when coaching is enabled.
When ARKit succeeds in restoring the experience, show your app’s UI again so everything appears the way it was before the interruption. When the coaching overlay disappears from the user’s view, ARKit invokes your
coaching callback, which is where you restore your app’s UI.
Enable the User to Start Over Rather Than Restore
If the user decides to give up on restoring the session, you restart the experience in your delegate’s
coaching function. ARKit invokes this callback when the user taps the coaching overlay’s Start Over button.