elkraneo Blog

TLDR: MeshResource.contents, three passes, one PostProcessEffect Rasterize the selected mesh into an offscreen R8Unorm silhouette mask Dilate the mask into a pixel-wide edge ring, suppressing the interior Composite the outline color over the source frame…

This latest wave of fixture work extended the reverse-engineering effort across Reality Composer Pro’s built-in components.

The previous inspector series parts explored attributes that map cleanly to USD: transforms, material bindings, and variant sets.

The next level of functionality in the RCP inspector offers deeper control over model linking, looks, and variations Screenshots of RCP displaying various options for both the model selector and the hierarchy.

A continually growing list of interesting things found during exploration that have not yet been featured in the "Deconstructing Reality Composer Pro" series entries.

The Inspector in RCP focuses on context-sensitive information, precise input, and the management of components (as in ECS).

To implement the Scene navigator, we will need to handle .usd manipulation, and the best approach I have found is to use Apple's SwiftUsd project.

Viewport is deep (modes, debug views, presets/history).

Part of what makes Reality Composer Pro a composer is asset management.

First, let's lay down and establish some sensible defaults to prepare for the absolute certain complexities to come.

Reality Composer Pro is positioned at the intersection of complex and evolving file format definitions.

TLDR: Xcode runs a verified two-pass process to compile .reality files, and understanding this unlocks the possibility of custom build pipelines, enables automation, and reveals Apple's USD-based spatial computing strategy.

...and there are strong reasons against it.

Explore On February 27th, 2025, from 10:00 AM to 5:00 PM (PST), Apple ran a hybrid session at Apple Developer Center Cupertino.

Just updated the data source to include WWDC25 contents and recompiled for Tahoe because it is nicer...