🏗️Core Concepts & Architecture

Understand how URT3D is structured under the hood — from assets and actors to traits, scripts, and the wrapper that ties it all together in Unity.

▶️ Watch the Video Guide: Step 5 – Launch Your First URT3D Asset in Unity

📘 Looking for detailed implementation docs? This page gives you a high-level overview, but you can always dive deeper in the official SDK documentation on GitHub: urt3d-sdk_unity › Documentation

---

🧱 What Makes Up a URT3D Asset?

At runtime, a .urta file is loaded as a URT3D Asset — a structured object that brings together a 3D model, behaviors, and metadata.

Here are the key components of the SDK and how they work together:

---

🔹 Asset (Urt3d.Asset)

The central object that represents everything inside a .urta file.

Includes:

• Actor – the 3D model itself (GLB/GLTF)

• Preview – thumbnail image for UI display

• Metadata – GUIDs, type, and names

• Traits – modular behaviors (movement, interaction, animation)

• Scripts – MiniScript behavior blocks

public abstract class Asset
{
    public Actor Actor { get; }
    public Preview Preview { get; }
    public Metadata Metadata { get; }

    public ReadOnlyCollection<Trait> Traits { get; }
    public ReadOnlyCollection<Script> Scripts { get; }

    public static Task<Asset> Construct(string pathToAsset);
}

🔹 Actor (Urt3d.Actor)

This is the actual visual representation of your asset — loaded from a .glb file.

Responsibilities:

• Load mesh and materials

• Manage transforms and rendering

• Can be constructed independently if needed:

var actor = await Actor.Construct("path/to/model.glb");

🔹 Wrapper (Urt3d.Wrapper)

A Unity MonoBehaviour that connects the asset to your scene. Use this to load .urta files via drag-and-drop or through code.

Also handles:

• Local file vs. remote asset loading

• Script execution modes

• Inspector integration for login, key, and settings

---

🔹 Metadata (Urt3d.Metadata)

Tracks identity, naming, and asset categorization.

csharpCopyEditpublic class Metadata
{
    public Guid GuidInstance { get; set; }
    public string NameInstance { get; set; }
    public Type TypeInstance { get; set; }
}

This enables asset versioning, display, and filtering logic at runtime.

---

🔹 Traits & Scripts

URT3D assets are modular. Each Trait provides a layer of behavior (position, animation, interactivity), while Scripts allow you to author dynamic logic using MiniScript.

These components are explained in depth here:

→ Traits System → Scripting with MiniScript

---

🧠 How It All Fits Together

When you load a .urta file:

1. Asset.Construct(path) loads the data

2. An Actor is created and displayed

3. Traits are attached and initialized

4. MiniScripts begin executing if present

5. The Wrapper handles runtime settings and updates

URT3D enables this all with minimal setup — no need to manually wire up GameObjects, triggers, or logic files.

---

💬 Need Help?

🗨️ Join our Discord creator community 📩 Email: [e-mail]