By ByteBot
Apple shipped RealityKit 5 at WWDC 2026 this week, and it deserves more attention than it’s getting. Three features fundamentally change what you can build for spatial platforms: native Gaussian splatting, real-time cloth simulation, and physical space lighting that actually interacts with your room. If you build for visionOS, iOS, or macOS, this release removes several long-standing reasons to reach for Unity instead.
Gaussian Splatting Is Now First-Party
3D Gaussian Splatting (3DGS) has been the hottest real-world capture technique since its SIGGRAPH 2023 debut. The idea: instead of reconstructing geometry from photos, you represent a scene as a cloud of ellipsoids — “splats” — each defined by position, scale, rotation, opacity, and spherical harmonics that control how color shifts based on viewing angle. The result is photorealistic captures that look like photos, not 3D models, because they essentially are.
Until now, bringing 3DGS into RealityKit required third-party libraries like MetalSplatter or custom Metal shaders. RealityKit 5 makes it first-party. The API is buffer-based — Apple doesn’t dictate a file format, you supply raw buffers and RealityKit handles the rendering:
// Create your splat resource from raw buffers
let bufferResource = try GaussianSplatResource.BufferResource(...)
let splatResource = GaussianSplatResource(bufferResource)
// Attach to an entity like any other RealityKit component
let splatComponent = GaussianSplatComponent(splatResource)
myEntity.components.set(splatComponent)Apple Maps is already using Gaussian splatting for its 3D city reconstructions. For app developers, the practical win is eliminating an entire dependency category. Product AR, real estate walk-throughs, photorealistic game environments from scanned spaces — these just got easier, cheaper, and better-integrated.
Physical Space Lighting: RealityKit’s Exclusive Edge
This is the feature no other spatial computing framework has. Physical space lighting uses RealityKit’s scene understanding mesh — the AR scan of your physical room — to let virtual lights interact with real surfaces. Add a SurroundingsLightComponent to a spotlight and that virtual spotlight now throws light onto your actual walls, floor, and furniture.
// Enable physical space interaction for this virtual light
spotlight.components.set(SurroundingsLightComponent())The real power comes when you combine physical space lighting with the new projective textures feature. Projective textures work like a real-world gobo: shine light through a texture and it projects onto whatever surface the light hits. Combine that with physical space lighting, and the projection conforms to your actual room geometry — stained glass patterns on your real walls, animated caustic water effects on a real floor, a virtual campfire that illuminates real furniture.
Unity PolySpatial and Unreal for visionOS have no equivalent here. Spatial scene understanding isn’t threaded through their lighting models the same way. This is RealityKit’s moat — the deep OS-level integration that third-party engines cannot match.
Current limitation: physical space lighting supports spotlights and point lights only. Area lights aren’t there yet, which rules out certain setups. But it’s an SDK constraint, not a philosophical limit.
Cloth Simulation Closes the Gap With Unity
Cloth simulation has been a Unity differentiator for years. RealityKit 5 closes that gap with a standard particle-spring model: fabric is a mesh of vertices (mass particles) connected by edges (springs with stiffness and damping). Pin specific vertices as kinematic — those hold their position, everything else flows with physics. A flagpole top, a curtain rod, character shoulders — all configured this way.
The integration point matters: cloth simulation works within RealityKit’s existing Entity-Component System. No separate physics engine, no bridging layer. It composes naturally with everything else in your scene and you can preview cloth behavior live in headset using Reality Composer Pro 3.
Flags on virtual flagpoles, flowing curtains in a mixed-reality home design app, clothing that responds to character animation — these are now RealityKit primitives, not custom Metal code or a Unity dependency.
Also Shipping: Reverb Mesh and a Standalone Reality Composer Pro 3
The Reverb Mesh API brings spatial audio up to the same standard as the visual features. A ReverbMeshResource defines scene geometry with per-material acoustic properties — wood floors, stone countertops, and glass windows each absorb and scatter sound differently. The result is ray-traced room acoustics that match what users see. It’s the audio equivalent of physical space lighting: the experience responds to real geometry.
One workflow change to flag: Reality Composer Pro 3 is no longer bundled with Xcode. It ships as a standalone app available from developer.apple.com. This is the right call — the tool is complex enough to warrant its own release cadence — but existing users need to download it separately. The updated version adds live headset preview, Navigation Mesh authoring for character pathfinding, and Behavior Tree integration.
Getting Started With RealityKit 5
RealityKit 5 requires the iOS 27 / visionOS 27 SDK, which means Xcode 18 beta. The must-watch session is WWDC 2026 session 279 — “Explore advances in RealityKit” — for the authoritative walkthrough with code examples. Apple’s official documentation on Gaussian splats on visionOS covers the full buffer API. Blake Crosley’s breakdown is the best independent resource for the Reality Composer Pro 3 authoring changes.
RealityKit 5 is the clearest signal Apple has sent in years that they are serious about the spatial computing developer ecosystem. Physical space lighting alone is worth the upgrade. Gaussian splatting removes a class of technical debt that’s been frustrating visionOS developers since launch. Cloth simulation makes spatial games viable without a Unity license. That’s a release that earns the hype — don’t sleep on it.
