Improving edge-rendering quality with multisample antialiasing (MSAA)

At a glance

Project structure

Source bundle/
├── Application/
│   ├── AAPLViewController.m
│   ├── main.m
│   ├── WindowSceneDelegate.m
│   ├── AAPLAppDelegate.h
│   ├── AAPLAppDelegate.m
│   └── AAPLView.h
└── Renderer/
    ├── AAPLShaderCommon.metal
    ├── AAPLRenderer.m
    └── AAPLShaders.metal

Structure observations

• The entry/composition boundary and renderer or operation boundary are separate in the source; AAPLRenderer 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["AAPLViewController"]
    N2["AAPLRenderer"]
    N3["multisample target and resolve setup"]
    N4["MSAA rasterization and resolve"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Renderer/AAPLRenderer.m:405 — multisample store-and-resolve configuration

        MTLStoreAction storeAction = shouldResolve ? MTLStoreActionMultisampleResolve : MTLStoreActionStore;
        renderPassDescriptor.colorAttachments[0].storeAction = storeAction;
        renderPassDescriptor.colorAttachments[0].texture = _multisampleTexture;
        renderPassDescriptor.colorAttachments[0].resolveTexture = shouldResolve ? _resolveResultTexture : nil;

Interpretation

This is the dominant control/data path: platform code composes AAPLRenderer; that object controls multisample target and resolve setup; GPU-visible work ends in MSAA rasterization and resolve. The arrows summarize responsibility transfer, not a claim that every node directly calls the next.

Ownership and state

classDiagram
    AAPLViewController *-- AAPLRenderer : _renderer

Ownership evidence

Application/AAPLViewController.m:47 — AAPLViewController creates and stores _renderer

@implementation AAPLViewController
// ...
    _renderer = [[AAPLRenderer alloc] initWithMetalDevice:_view.device
                                      drawablePixelFormat:_view.colorPixelFormat];
// ...
@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/AAPLShaderCommon.metal:42 — representative GPU entry/helper

vertex CompositionVertexOut

Design patterns

Naming conventions

• Role suffixes make ownership visible: AAPLViewController, AAPLRenderer, AAPLView, AAPLAppDelegate, WindowSceneDelegate.
• Method names describe setup or encoding actions: application, applicationShouldTerminateAfterLastWindowClosed, acceptsFirstResponder, keyDown, toggleAntialiasing, updateAntialiasingSampleCount, updateAntialiasingResolve.
• Shader entry points use stage/operation names: averageResolveKernel, hdrResolveKernel, averageResolveTileKernel, hdrResolveTileKernel.
• AAPL is a sample namespace prefix, not a recommendation for production module naming; retain semantic suffixes such as Renderer, Manager, Scene, or Adapter.

Architecture takeaways

• Keep AAPLViewController focused on composition; AAPLRenderer is the owner of multisample target and resolve setup.
• Treat MSAA rasterization and resolve as a separate execution/compilation boundary with explicit resource and data-layout contracts.
• The verified ownership edge is AAPLViewController → _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