---
type: source-digest
topic: ue-mcp-strategy
status: active
created: 2026-06-16
updated: 2026-06-16
source_notes:
  - external
derived_from:
  - web-research
confidence: high
source_url: https://aousd.org/news/pixar-adobe-apple-autodesk-and-nvidia-form-alliance-for-openusd-to-drive-open-standards-for-3d-content/
---
# interchange-and-lock-in

## Why This Matters

The bull thesis ("open the MCP, every generated asset deepens UE content gravity") rests on assets being *engine-native and non-portable*. This digest grounds the facts that decide that question: how Epic actually captures value (the runtime royalty test), which UE artifacts are truly engine-bound (Verse, Blueprints) versus portable (USD, glTF, FBX), and that **Epic itself is a founding backer of the open interchange standard (OpenUSD) that erodes the very lock-in the thesis depends on.** That tension is the heart of the bear case.

## Key Takeaways

- **Value capture is literally defined by the runtime.** Epic's royalty (historically 5%, reduced to 3.5% for Epic-Games-Store-co-launched titles from 1 Jan 2025) triggers on lifetime gross >$1M *per title*, and the test for owing a royalty is whether the shipped product "relies on Unreal Engine code at runtime." Non-runtime use (VFX, archviz) falls under a seat fee (~$1,850/yr). So "value sits at the runtime" is not a slogan — it is the contractual mechanism. (FACT)
- **Verse and Blueprints are engine-bound.** Both are Epic-developed and run only inside UE/UEFN; there is no export path to another engine. This is the strongest content-lock-in surface. (FACT)
- **But the heavy assets are portable.** OpenUSD (Pixar, open-sourced 2016), glTF 2.0 (Khronos, royalty-free, the "JPEG of 3D"), and FBX (Autodesk) all move meshes/materials/scenes across engines. UE 5.4+ unified FBX/glTF/USD import under the **Interchange framework**; UE has native USD Stage workflow. (FACT)
- **Epic is a founding general member of the Alliance for OpenUSD (AOUSD)**, alongside Pixar, NVIDIA, Adobe, Apple, Autodesk — and notably Unity. Epic is actively investing in making 3D content *more* portable, not less. (FACT — this is the load-bearing one for the bear case.)
- **Portability is imperfect.** Materials/shaders often don't survive interchange cleanly; glTF is a "publish" format, weak for round-trip editing. So lock-in is partial, not zero. (FACT)
- **No engine-agnostic "intent compiler" exists yet** that targets UE *and* Unity *and* Godot interchangeably; the market is engine-specific agents (Unity Muse, Summer Engine for Godot) + engine-agnostic *asset* generators (Meshy, Scenario, Anything World) + cross-engine code LLMs (Claude, Copilot). The agnostic layer is plausible, not present. (FACT + REASONING)
- **AI slop is already measurable.** Steam AI disclosures up ~800% in 2025 (~8,000 games, ~7% of catalog); 1 in 5 new 2025 titles report generative AI. "Slop" = Merriam-Webster 2025 word of the year. (FACT)
- **MCP exposes tool schemas by design**; "Agentic Tool Extraction" reconnaissance can reconstruct full tool/function signatures. Training-data-to-competitor leakage specifically is *not* documented — it is inference. (FACT for schema exposure; REASONING for the competitor-training claim.)
- **Frontier-lab dependence is real and worsening.** Model lifecycles compressed to 6-12 months; silent re-pricing on deprecated endpoints (e.g., xAI bills deprecated slugs at the newer model's rate); Copilot dropped multiple Claude/OpenAI/Gemini models. (FACT)

## Entities

- **Epic Games / Unreal Engine** — runtime owner; royalty value-capture; AOUSD member.
- **AOUSD / OpenUSD** — Pixar-origin open 3D interchange standard; Linux Foundation JDF; Epic + Unity both members.
- **Khronos Group / glTF 2.0** — open royalty-free runtime 3D delivery format.
- **Autodesk / FBX** — incumbent DCC interchange format.
- **Verse / Blueprints / UEFN** — Epic's engine-bound authoring/scripting surfaces (the real lock-in).
- **Frontier labs (Anthropic, OpenAI, Google, xAI)** — the rented intelligence behind any MCP; pricing/deprecation risk.
- **Asset generators (Meshy, Scenario, Anything World)** — engine-agnostic, feed the "swappable backend" risk.

## Sources (all URLs)

- AOUSD founding announcement — https://aousd.org/news/pixar-adobe-apple-autodesk-and-nvidia-form-alliance-for-openusd-to-drive-open-standards-for-3d-content/
- NVIDIA on AOUSD (lists Epic + Unity as general members) — https://nvidianews.nvidia.com/news/aousd-to-drive-open-standards-for-3d-content
- USD in Unreal Engine docs — https://dev.epicgames.com/documentation/unreal-engine/universal-scene-description-in-unreal-engine
- Interchange OpenUSD plugin — https://dev.epicgames.com/documentation/en-us/unreal-engine/API/PluginIndex/InterchangeOpenUSD
- Universal Scene Description (overview) — https://en.wikipedia.org/wiki/Universal_Scene_Description
- UE licensing / royalty terms — https://www.unrealengine.com/license
- Royalty cut to 3.5% (Launch Everywhere with Epic) — https://www.cgchannel.com/2024/10/epic-games-to-cut-royalty-rate-on-unreal-engine-games/
- glTF 2.0 as standard exchange format (Godot) — https://godotengine.org/article/we-should-all-use-gltf-20-export-3d-assets-game-engines/
- glTF vs FBX — https://www.threekit.com/blog/gltf-vs-fbx-which-format-should-i-use
- AI game tools across engines (2026) — https://www.summerengine.com/blog/best-ai-tools-game-development
- AI slop flooding storefronts — https://vgtimes.com/tech-and-hardware/153162-ai-slop-what-is-it.html
- AI slop on storefronts (Steam data) — https://outrungaming.com/ai-slop-digital-storefronts/
- MCP security / Agentic Tool Extraction — https://arxiv.org/html/2511.20920v1
- MCP safety audit (exploits) — https://arxiv.org/abs/2504.03767
- Model deprecation calendar 2025-2026 — https://presenc.ai/research/ai-model-deprecation-tracker-2026
- xAI deprecated-slug re-pricing policy — https://docs.x.ai/developers/migration/may-15-retirement
- Copilot dropping Claude/OpenAI/Gemini models — https://www.itpro.com/software/development/github-copilot-ai-model-deprecation-openai-anthropic-google

## Open Questions

- What share of an AI-generated UE project's *value* lives in non-portable surfaces (Verse logic, Blueprint graphs, Nanite/Lumen-tuned setups) vs. portable USD/glTF meshes? That ratio is the real gravity coefficient.
- Does Epic's own AOUSD membership mean it has already conceded asset-layer portability and is betting gravity on the *runtime + UEFN economy*, not assets? If so, the bull thesis is half-wrong by Epic's own actions.
- Is there a public case of an MCP's tool schema being used to train or clone a competitor's capability? (None found — keep this claim at low confidence.)