Core contract
Flag unsupported materials early.
Material graphs are validated up front — unsupported setups get flagged in Blender, before they silently break downstream.
Open Source
BlenderToRCP
Export Blender scenes to RealityKit without guesswork — stricter validation, MaterialX rewriting, and USD output that Reality Composer Pro actually understands.
Key areas
How BlenderToRCP organizes the handoff.
Each stage of the pipeline — validation, material rewriting, export, and packaging — is handled separately so problems surface early and fixes stay local.
Export surface
Export USD that stays editable.
Export .usda, .usdc, or .usdz, with supported Blender shaders rewritten into RealityKit-compatible Shadergraph output.
Asset package
Keep the handoff portable.
Textures and sidecar assets travel with the scene, so nothing breaks when the folder moves between machines, review, or app integration.
Artist workflow
Work for RealityKit inside Blender.
Validate materials, preview RealityKit-ready node groups, and kick off exports in the background — all without leaving Blender.
Developer workflow
Inspect more, guess less.
Rich diagnostics, granular USD export controls, and animation tooling let you review and diff output before it ships.
Animation library
Turn actions into reusable clips.
Blender actions are baked into an Animation Library layout that Reality Composer Pro can consume directly.
Agent workflows
Ready for the agentic world.
BlenderToRCP isn't just a UI add-on — agents can inspect scenes, trigger exports, and patch USD as part of a larger content pipeline.
CLI + Skills
Automate exports from the command line.
Use the CLI for validation and export flows, with two dedicated skills to help agents inspect scenes and run the right commands.
LLM Ready
ASCII .usda works well with agents.
Because .usda is plain ASCII USD, agents can read the scene, reason about it, and patch details such as shaders directly.
Client adoption
Used by our clients
We use BlenderToRCP to deliver spatial work for our clients.
