Control the ray tracing process using intersection queries

At a glance

Project structure

Source bundle/
├── Application/
│   ├── ViewController.mm
│   ├── main.m
│   ├── AppDelegate.h
│   └── AppDelegate.m
└── Renderer/
    ├── Shaders.metal
    ├── Renderer.mm
    ├── Scene.mm
    ├── ShaderTypes.h
    └── Scene.h

Structure observations

• The entry/composition boundary and renderer or operation boundary are separate in the source; Renderer is the principal feature coordinator.
• GPU-specific logic stays in Metal shader files; shared headers bridge host/shader layouts where present.
• The tree above is intentionally pruned to composition, resource, and shader files.

Overall architecture

flowchart LR
    N1["ViewController"]
    N2["Renderer"]
    N3["intersection-query configuration"]
    N4["inline ray queries in a Metal kernel"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Application/ViewController.mm:32 — feature handoff or setup anchor

@implementation ViewController
// ...
        if(device.supportsRaytracing)
// ...
@end

Interpretation

This is the dominant control/data path: platform code composes Renderer; that object controls intersection-query configuration; GPU-visible work ends in inline ray queries in a Metal kernel. The arrows summarize responsibility transfer, not a claim that every node directly calls the next.

Ownership and state

classDiagram
    ViewController *-- Renderer : _renderer

Ownership evidence

Application/ViewController.mm:57 — ViewController creates and stores _renderer

@implementation ViewController
// ...
    _renderer = [[Renderer alloc] initWithDevice:_view.device
                                           scene:scene];
// ...
@end

Class and protocol design

Framework delegate conformance is a callback seam; the source does not justify calling the whole app protocol-oriented.

Access control

This sample does not use Swift private, fileprivate, or public for its native boundary. Objective-C/Objective-C++ use header versus implementation placement, C++ uses access specifiers/linkage, Python uses module conventions, and Metal entry points cross a compiled-library boundary; these are not Swift access levels.

Logic ownership and placement

Shader boundary reference

Renderer/Shaders.metal:331 — ray-tracing kernel with a visible-function table

kernel void raytracingKernel(uint2 tid [[thread_position_in_grid]],
                             constant Uniforms & uniforms,
                             texture2d<unsigned int> randomTex,
                             texture2d<float> prevTex,
                             texture2d<float, access::write> dstTex,
                             device void *resources,
                             device MTLAccelerationStructureInstanceDescriptor *instances,
                             device AreaLight *areaLights,
                             instance_acceleration_structure accelerationStructure,
                             visible_function_table<IntersectionFunction> intersectionFunctionTable)

Design patterns

Naming conventions

• Role suffixes make ownership visible: ViewController, Renderer, Scene, AppDelegate, WindowSceneDelegate.
• Method names describe setup or encoding actions: initWithDevice, clear, uploadToBuffers, geometryDescriptor, resources, addCubeWithFaces, addSphereWithOrigin.
• Shader entry points use stage/operation names: raytracingKernel, copyVertex, copyFragment.
• Names favor concrete domain roles and target-local types; no broad public library namespace is introduced.

Architecture takeaways

• Keep ViewController focused on composition; Renderer is the owner of intersection-query configuration.
• Treat inline ray queries in a Metal kernel as a separate execution/compilation boundary with explicit resource and data-layout contracts.
• The verified ownership edge is ViewController → _renderer; broader exclusive ownership is not inferred.
• Access-control rationale follows concrete language boundaries rather than translating every header or shader symbol into Swift terms.

Source map

• Official Apple documentation