sceneform-android

In a glTF context, ModelAnimator updates matrices according to glTF animation and skin definitions. It performs two primary roles:

1. TransformManager: Updates matrices in components according to model animation definitions.
2. RenderableManager: Updates bone matrices.

Morph Targets: If a model has morph targets (e.g., facial expressions), ModelAnimator handles the tracks that define how the influence of each morph target changes over the animation clip.

Important Note on Time Modification: When creating a PropertyValuesHolder to modify the time position of an animation, you must use ModelAnimation.TIME_POSITION instead of a custom property. This ensures that the modification can correctly cancel any other ObjectAnimator currently operating on the time of that same ModelAnimation.

In a glTF context, ModelAnimator updates matrices according to glTF animation and skin definitions. It handles two primary tasks:

1. Updating matrices in TransformManager components based on model animation definitions.
2. Updating bone matrices in RenderableManager.

This includes animating skeleton tracks (position, rotation, or scale of bones) and morph targets (e.g., transitioning a face from 'friendly' to 'angry').

Important: When using PropertyValuesHolder to modify animation time, you must use ModelAnimation.TIME_POSITION instead of its own property to ensure it can correctly cancel other ObjectAnimator instances operating on the same ModelAnimation.

The DepthMode is automatically determined by the ARCore Session configuration. It defines how the depth information is processed by the session. The available modes are:

• NO_DEPTH: The default mode. The Session is not configured to use the Depth-API.
• DEPTH: The Session is configured to use Config.DepthMode.AUTOMATIC.
• RAW_DEPTH: The Session is configured to use Config.DepthMode.RAW_DEPTH_ONLY.

To ensure your app is only visible in the Google Play Store on devices that support ARCore, you must declare the app as 'AR Required'. This involves requesting camera permissions, declaring the AR hardware feature as required, and setting the ARCore metadata value to required in your AndroidManifest.xml.

<uses-permission android:name="android.permission.CAMERA" />
<uses-feature android:name="android.hardware.camera.ar" android:required="true"/>

<application>
    ...
    <meta-data android:name="com.google.ar.core" android:value="required" />
</application>

Depth occlusion allows virtual objects to be occluded by real-world objects. To enable it, first check if the session supports Config.DepthMode.AUTOMATIC via setOnSessionConfigurationListener. Then, set the depthOcclusionMode on the arSceneView.cameraStream to CameraStream.DepthOcclusionMode.DEPTH_OCCLUSION_ENABLED within the setOnViewCreatedListener.

arFragment.apply {
    setOnSessionConfigurationListener { session, config ->
        if (session.isDepthModeSupported(Config.DepthMode.AUTOMATIC)) {
            config.depthMode = Config.DepthMode.AUTOMATIC
        }
    }
    setOnViewCreatedListener { arSceneView ->
        // Available modes: DEPTH_OCCLUSION_DISABLED, DEPTH_OCCLUSION_ENABLED
        arSceneView.cameraStream.depthOcclusionMode =
            CameraStream.DepthOcclusionMode.DEPTH_OCCLUSION_ENABLED
    }
}

When using ARCore, you must prominently disclose to users that the app uses Google Play Services for AR and how it processes data. A recommended way to do this is by adding a notice on your main menu:

"This application runs on Google Play Services for AR (ARCore), which is provided by Google LLC and governed by the Google Privacy Policy".

To explicitly free up renderable resources associated with a node, call destroy() on its renderableInstance.

node.renderableInstance.destroy()