--- title: Rendering Gaussian splats with RealityKit framework: visionos role: sampleCode role_heading: Sample Code platforms: [iOS 27.0+, iPadOS 27.0+, Mac Catalyst 27.0+, macOS 27.0+, visionOS 27.0+, xcode 27.0+] path: visionos/rendering-gaussian-splats-with-realitykit --- # Rendering Gaussian splats with RealityKit Bring a real-world scan into an app by loading splat data from a USD or PLY file. ## Overview Overview A Gaussian splat asset represents a scene as a large collection of colored, oriented ellipsoids instead of a mesh, so a real-world capture keeps details that are hard to model by hand, like soil texture or the fine edges of leaves. Each splat carries position, scale, rotation, opacity, and a set of spherical harmonic coefficients that let its color shift depending on the viewing angle. This reproduces specular highlights and reflections that were present in the original capture. The capture bakes that color in, so scene lighting doesn’t change how a splat looks, and a splat won’t cast a shadow the way mesh-based content does. This sample uses RealityKit to add a scan of a potted plant to a scene. The app loads the same plant from either a USD file or a PLY file, and the code that gets that data onto the GPU is shared across every platform the sample runs on. A scene can only render a limited number of splat entities at once. When an asset costs more than the renderer can afford, RealityKit reduces its own splat rendering work and reports the change by sending a GaussianSplatEvents.RenderingChanged event on the entity that owns the splat. The event’s isRenderingLimited property tells the app whether RealityKit is currently limiting the entity’s splat rendering, and renderingStatus indicates which rendering quality the system selected. RealityKit sends the event after it applies that mitigation, so the event reports a decision rather than asking the app to make one. The sample subscribes to the event so the app’s window can report when RealityKit limits splat rendering. Reducing the asset’s splat count gives the renderer less to do and brings back full-quality rendering. note: This sample code project is associated with WWDC26 session 287: Build next generation experiences with visionOS 27, and session 279: Explore advances in RealityKit. Configure the sample code project Because Gaussian splats don’t render in Simulator, choose a destination from the scheme menu in Xcode and run the app on Apple Vision Pro, iPhone, iPad, or Mac. The sample shares its loading code for each platform to provide a native environment on launch. For example, on visionOS, the plant appears in a mixed immersive space where a person can pick it up, move it, and anchor it to a nearby table or floor. On macOS and iOS it appears in the app’s window, where dragging turns it. Load a splat from a USD file The sample’s bundled USD asset stores its splat data in a primitive whose schema type is ParticleField3DGaussianSplat. This primitive isn’t defined by RealityKit or USDKit, and is instead created by the tool that authored the asset. loadUSDEntity(assetName:) opens the stage with open(_:loadingPayloads:), searches the stage’s descendants for the primitive with that schema using isSchema(_:), and reads the attributes of that USDPrim into a GaussianSplatBuffers: func loadUSDEntity(assetName: String) async throws -> Entity { let url = try bundleUSDURL(assetName: assetName) let buffers = try await Task.detached(priority: .userInitiated) { let stage = try USDStage.open(url) guard let splatPrim = stage.descendants.first(where: { $0.isSchema("ParticleField3DGaussianSplat") }) else { throw GaussianSplatError.invalidData("No ParticleField3DGaussianSplat prim found in \(url.lastPathComponent)") } return try buildBuffers(from: splatPrim) }.value return try makeSplatEntity(from: buffers, isLinear: true) } RealityKit expects each rotation as four contiguous floats in w, x, y, z order. USDValue.Quatf exposes its parts through the real and imaginary accessors rather than as raw fields in that layout, so the loop reads each component through its accessor and writes it into the matching slot of the LowLevelBuffer instead of copying the structure’s bytes directly: private nonisolated func fillRotationBuffer(_ buffer: LowLevelBuffer?, quatArray: [USDValue.Quatf], count: Int) { buffer?.withUnsafeMutableBytes { dst in let out = dst.bindMemory(to: Float.self) for idx in 0.. Entity { let url = try bundlePLYURL(assetName: assetName) let buffers = try await Task.detached(priority: .userInitiated) { let splatData = try readGaussianSplatFile(url) return try deinterleaveGaussianSplatData(splatData) }.value return try makeSplatEntity(from: buffers) } The deinterleaveGaussianSplatData(_:) method also sanitizes every value it copies, replacing any NaN or infinite float with 0. RealityKit rejects a splat buffer that contains a non-finite value, so the loader cleans up the capture data before building the buffer. Prepare buffers for splat assets Whichever format the sample starts from, it fills the same GPU buffers for position, scale, rotation, opacity, and spherical harmonics. This sample defines a custom structure, GaussianSplatBuffers, that holds those buffers, and a helper turns a filled-in structure into something the app can add to a scene. assembleSplatComponent(from:isLinear:) packages the buffers into a GaussianSplatResource.BufferResource, describing where each per-splat property lives with a GaussianSplatResource.BufferDescriptor, wraps that in a GaussianSplatResource, and builds a GaussianSplatComponent from it. assembleSplatComponent(from:isLinear:) also sets the resource’s scaleActivation and opacityActivation, which tell RealityKit how to interpret the raw numbers in the buffers: func assembleSplatComponent(from buffers: GaussianSplatBuffers, isLinear: Bool = false) throws -> GaussianSplatComponent { guard let pos = buffers.positionBuffer, let scale = buffers.scaleBuffer, let rotation = buffers.rotationBuffer, let opacity = buffers.opacityBuffer, let shBuf = buffers.shBuffer else { throw GaussianSplatError.invalidData("One or more GPU buffers failed to allocate") } let degree = GaussianSplatResource.SphericalHarmonicDegree(rawValue: buffers.degreeSH) ?? .zero let bufferResource = try GaussianSplatResource.BufferResource( count: Int(buffers.splatCount), position: makeDescriptor(buffer: pos, format: .float3, stride: 3 * 4), scale: makeDescriptor(buffer: scale, format: .float3, stride: 3 * 4), rotation: makeDescriptor(buffer: rotation, format: .float4, stride: 4 * 4), opacity: makeDescriptor(buffer: opacity, format: .float, stride: 1 * 4), sphericalHarmonics: (makeSHDescriptor(buffer: shBuf, tupleSH: buffers.tupleSH), degree) ) let splatResource = GaussianSplatResource(bufferResource) if isLinear { splatResource.scaleActivation = .identity splatResource.opacityActivation = .identity } else { splatResource.scaleActivation = .exponential splatResource.opacityActivation = .sigmoid } return GaussianSplatComponent(splatResource) } This sample passes isLinear: true for data that’s already in linear space, like the USD version of the plant asset. For the PLY asset, the sample leaves it false, allowing RealityKit to apply the GaussianSplatResource.ActivationFunction.exponential and GaussianSplatResource.ActivationFunction.sigmoid conversions for splat data. Add interactivity to a splat entity A splat entity is an Entity like any other, so it takes the same components. The sample’s visionOS view adds a GroundingShadowComponent and a ManipulationComponent so a person can pick up the plant and move it. Because a splat asset has no mesh to derive collision geometry from, the call to configureEntity(_:hoverEffect:allowedInputTypes:collisionShapes:) passes an explicit box from generateBox(size:). private func configureManipulableObject(_ entity: Entity) { ManipulationComponent.configureEntity( entity, collisionShapes: [ShapeResource.generateBox(size: SIMD3(repeating: 0.5))] ) var manipulation = entity.components[ManipulationComponent.self] ?? ManipulationComponent() // ... entity.components.set(manipulation) entity.components.set(GroundingShadowComponent(castsShadow: true)) } ## See Also ### RealityKit and Reality Composer Pro - [Reality Composer Pro](realitycomposerpro.md) - [Chaparral Village: Building an immersive visionOS adventure game](visionos/chaparral-village-building-an-immersive-visionos-adventure-game.md) - [Designing no-code games with Reality Composer Pro 3](visionos/designing-no-code-games-in-reality-composer-pro-3.md) - [Petite Asteroids: Building a volumetric visionOS game](visionos/petite-asteroids-building-a-volumetric-visionos-game.md) - [BOT-anist](visionos/bot-anist.md) - [Swift Splash](visionos/swift-splash.md) - [Diorama](visionos/diorama.md) - [Building an immersive media viewing experience](visionos/building-an-immersive-media-viewing-experience.md) - [Enabling video reflections in an immersive environment](visionos/enabling-video-reflections-in-an-immersive-environment.md) - [Combining 2D and 3D views in an immersive app](realitykit/combining-2d-and-3d-views-in-an-immersive-app.md) - [Understanding the modular architecture of RealityKit](visionos/understanding-the-realitykit-modular-architecture.md) - [Using transforms to move, scale, and rotate entities](visionos/understanding-transforms.md) - [Capturing screenshots and video from Apple Vision Pro for 2D viewing](visionos/capturing-screenshots-and-video-from-your-apple-vision-pro-for-2d-viewing.md) - [Implementing object tracking in your app](visionos/implementing-object-tracking-in-your-app.md) - [Placing entities using head and device transform](visionos/placing-entities-using-head-and-device-transform.md)