tomkrikorian/visionosagents/realitykit-rendering-materials

RealityKit Rendering Materials

Quick Start

1. Confirm the issue is visual: mesh display, material assignment, camera

projection, lighting, shadows, post-processing, splats, decals, LOD, occlusion, or probes.

1. Load the narrowest rendering reference that matches the feature.
2. Route ShaderGraph or USDA material graph editing to shadergraph-editor.
3. Route local USD stage rendering through

realitykit-visionos-developer; route USD authoring to usd-editor.

1. Validate on device or simulator with concrete visual checks, because many

rendering issues are asset-, lighting-, or hardware-dependent.

Load References When

Cross-Routing

• Use realitykit-visionos-developer for entity loading, input, attachments,

anchoring, portals, synchronization, and local USDStageComponent.

• Use realitykit-animation-physics when the visual issue is caused by

animation, blendshape, particle, cloth, collision, or physics state.

• Use realitykit-ecs-systems when rendering state is driven by a custom

component or per-frame system.

• Use shadergraph-editor for material graph source edits.

Guardrails

• Treat visionOS 27 rendering additions as beta API; re-verify symbols against

the installed SDK before shipping.

• Keep expensive material, mesh, and texture loading asynchronous.
• Validate visual changes with screenshots or simulator/device inspection when

possible.

• Prefer documented RealityKit components before custom draw or update logic.

Output Expectations

Provide:

• the rendering category
• which rendering reference files were used
• the chosen component or asset path
• the visual/performance constraint
• the next screenshot, simulator, or device validation step