🛰️Advanced Topics

Learn how to optimize URT3D performance, structure your assets for scale, and deploy interactive experiences across web, mobile, and desktop platforms.

📘 Looking for low-level SDK reference? View the full URT3D Unity SDK documentation: https://github.com/URT3D/urt3d-sdk_unity/blob/main/Documentation/index.md

This page brings together power-user guidance for performance, deployment, and asset structuring when using .urta files and the URT3D SDK at scale.

---

🔧 Performance Optimization

Performance starts with how you load and reuse assets and how often you run logic in scripts or traits.

Use Object Pooling

Don’t repeatedly load/destroy assets. Instead, keep a pool of inactive instances and activate as needed.

In Unity:

• Store deactivated assets in a dictionary of queues

• When needed, reuse from the pool

• Only load a new asset when none are available

👉 Unity’s Object Pooling Docs

Minimize OnUpdate Scripts

Use OnUpdate sparingly. Logic in this trigger runs every frame. Avoid:

• Heavy math inside Update()

• Spawning/despawning logic per frame

• Expensive raycasts or nested loops

Optimize Traits

• Only include traits you plan to use • Avoid setting values every frame unless needed • For static objects, set traits once on load

Reduce Model Complexity

• Keep .glb files under ~100K polygons • Use compressed textures (WebP or power-of-two JPG/PNG) • Consider baking animations • Use LODs only if your scene is performance-bottlenecked

---

📦 Asset Structuring & Reuse

URT3D works best when your content is modular and predictable.

Use Versioning in Filenames

Examples:

• robot_arm_v1.2.urta

• futuristic_shelf_FINAL.glb

This makes debugging and scene restoration much easier across teams.

Keep Traits Modular

Instead of deeply customizing each asset, use shared traits and assign values differently. You can:

• Reuse position/animation traits

• Send external triggers for variation

• Script unique behaviors via MiniScript instead of duplicating assets

Create Prefab Templates in Unity

Once an asset loads and looks right:

1. Add to a Unity scene

2. Assign default values

3. Convert to a prefab

4. Reuse this prefab in other projects or scenes

Use Consistent Foldering

• Assets/URT3D/Prefabs/

• Assets/URT3D/Scripts/

• Assets/URT3D/Samples/

• Assets/URT3D/ConvertedAssets/

Helps avoid confusion during large project collaboration.

---

🚀 Deployment Strategies

Deploying URT3D content effectively depends on platform.

Web (WebGL)

• Use Unity’s WebGL template to remove overhead UI

• Compress assets using gzip or Brotli

• Preload .urta files via UnityWebRequest

• Stream or batch load from remote servers with App Keys

👉 Unity WebGL Build Optimizations

Mobile (iOS / Android)

• Keep .urta files under 20MB for fast load

• Use compressed textures like ETC2

• Avoid OnUpdate-heavy scripts for battery efficiency

• Test scripts on-device to identify frame rate drops

👉 Unity Mobile Best Practices

Desktop / VR

• Use full resolution models with baked lighting

• Combine .urta with other Unity packages

• Great for training simulations and large digital twins

• Stream assets dynamically using App Key auth and remote loading

---

💬 Have feedback or want to contribute advanced tips? 🗨️ Join our Discord creator community 📩 Email us at [e-mail]