Using object capture assets in RealityKit

At a glance

Project structure

Source bundle/
└── CaptureChess/
    ├── CaptureChessApp.swift
    ├── SplashScreenView.swift
    ├── ContentView.swift
    ├── Game.swift
    ├── GameManager.swift
    ├── AnimationSystem.swift
    ├── MetalLibLoader.swift
    ├── Components.swift
    ├── ChessViewport.swift
    ├── ARViewContainer.swift
    ├── ChessPieceData.swift
    └── Entities/
        └── BoardGame.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Metal, Swift.
• The verified tree contains 4 project/configuration file(s) and 30 source declaration(s).

Overall architecture

flowchart LR
    N1["CaptureChessApp"]
    N2["ContentView"]
    N3["GameManager"]
    N4["MetalLibLoader"]
    N5["RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

CaptureChess/CaptureChessApp.swift:10 — architecture anchor

@main
struct ObjectCaptureSampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into RealityKit.

Ownership and state

classDiagram
    OverlayView o-- GameManager : gameManager
    Piece o-- Player : player
    Piece o-- PieceType : type
    Move o-- Coordinate : from

Ownership evidence

CaptureChess/ContentView.swift:38 — stored dependency or nearest verified ownership anchor

struct OverlayView: View {
    // ...
    @ObservedObject var gameManager: GameManager
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

CaptureChess/ChessViewport.swift:70 — representative execution boundary

class ChessViewport: ARView {
    // ...
            .receive(on: RunLoop.main)
    // ...
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

CaptureChess/Components.swift:10 — representative type boundary

protocol HasChessPiece: Entity { }

The source explicitly defines local protocol relationships: ChessPiece → HasChessPiece.

Access control

Reference code

CaptureChess/ChessViewport+Bloom.swift:46 — representative boundary

    fileprivate func prepareTexture(_ texture: inout MTLTexture?, format pixelFormat: MTLPixelFormat = .rgba8Unorm) {
        if texture?.width != self.sourceColorTexture.width
        // ...
    }

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: ObjectCaptureSampleApp; Component: CheckerComponent, ChessPieceComponent; Loader: MetalLibLoader; Manager: GameManager; Player: Player; System: AnimationSystem; View: ContentView, GestureView, OverlayView, SplashScreenView.
• Protocols: HasChessPiece.
• Methods: validateMove, toggle, piece, setPiece, removePiece, makeMove, kingCoordinate, coordinates.
• Files: CaptureChess/SplashScreenView.swift, CaptureChess/ContentView.swift, CaptureChess/GameManager.swift, CaptureChess/AnimationSystem.swift, CaptureChess/MetalLibLoader.swift, CaptureChess/ChessViewport.swift.

Architecture takeaways

• CaptureChessApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches RealityKit, SwiftUI, metal_stdlib, UIKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation