> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/polygon-streaming/integrations-and-plugins/polygon-streaming-unity-sdk/streaming-model-component.md).

# Streaming Model Component

The ***`StreamingModel`*** component represents a single model streamed into your scene. It requires a reference to a ***`StreamController`*** and a source URL. Loading starts automatically when the component is enabled.

### Key Inspector Fields

| Field                 | Default | Description                                                            |
| --------------------- | ------- | ---------------------------------------------------------------------- |
| **Stream Controller** | —       | Reference to the scene's `StreamController`. Required.                 |
| **Source Url**        | —       | URL of the XRG model to stream.                                        |
| **Light Probe Usage** | `false` | Enable Unity light probe sampling.                                     |
| **Custom Materials**  | `false` | Override default materials with your own opaque/transparent materials. |
| **Quality Priority**  | 1       | Prioritize this model's quality relative to others in the scene.       |

### Animation Fields

| Field                          | Default | Description                                                                       |
| ------------------------------ | ------- | --------------------------------------------------------------------------------- |
| **Animation Mode**             | `Auto`  | Which animation system to use. See Animated GLB Models and VRM Avatar Streaming.  |
| **Custom Animator Controller** | —       | `RuntimeAnimatorController` for Mecanim animation.                                |
| **Auto Play Loop**             | `true`  | Auto-play embedded clips. Disabled automatically when a custom controller is set. |

### VRM Settings

Only take effect on VRM avatars:

| Field                   | Default | Description                                  |
| ----------------------- | ------- | -------------------------------------------- |
| **Enable Spring Bones** | `false` | Enable spring bone physics (hair, clothing). |
| **Enable Look At**      | `false` | Enable eye tracking.                         |
| **Look At Target**      | —       | Transform the avatar's eyes follow.          |

> For full VRM settings (physics multipliers, override options), see `USAGE_VRM_STREAMING.md` in the SDK package.

### Callbacks

```csharp
streamingModel.SetLoadedCallback(() => Debug.Log("Ready!"));
streamingModel.SetLoadFailedCallback(ex => Debug.LogError(ex.Message));
```

### Scene Preview

The `StreamingModelPreview` component renders a lightweight preview in the Scene View while in Edit Mode. Toggle it on/off in the Inspector.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.viverse.com/polygon-streaming/integrations-and-plugins/polygon-streaming-unity-sdk/streaming-model-component.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.