The world reacting to a break
How the rest of the game hears and sees a break — break noise for the AI, world-wide break events and queries, navigation, weapon recoil on props that hold, breaking what rests on a prop, debris pushed by characters, and props that let the camera and characters through.
A prop that breaks is more than a mesh coming apart. The guards in the next room hear the crate smash. A barricade that blocked the way opens a path for the enemies. A sword that strikes an indestructible gate bounces back. The pots on a shelf shatter with the shelf. Pieces at a character’s feet are kicked aside, and a pillar between the camera and the player gets out of the view. This page covers these reactions. Every new option here is off by default unless the page says otherwise, and the defaults that are on keep SDF 1.0’s behaviour.
Break noise for the AI
Add the Break Noise module to a Behavior, or tick the Break Noise exception on one setup or one placed copy, and the prop’s break makes a noise through Unreal’s AI Hearing sense. Off by default; no prop in the demo map turns it on.
| Setting | Default | What it does |
|---|---|---|
| Break Noise Loudness | 1 | Scales both the listener’s hearing range and Break Noise Range |
| Break Noise Range | 1500 cm | The farthest a listener hears it, before Loudness. 0 leaves only the listener’s own hearing range |
| Break Noise Tag | SDF.Break | Carried by the noise, so a listener can tell a break from footsteps or combat. Module only |
- The noise is made at the prop’s break point: its Break Presentation Socket, else the centre of its intact bounds. See Explosions, break point and cover.
- It is credited to whoever broke the prop: the pawn of the hit’s Instigator, else its Damage Causer. When nobody did — a fall, a chain — it is the prop’s own, because Unreal drops a noise with no instigator. Set your listeners’ Detection By Affiliation to match: a noise credited to the player has the player’s team.
AIModuleis an engine module: there is nothing to enable.
Every break, world-wide
USDFDestructionSubsystem::OnDestructibleBroken(Destructible, Hit, Result) fires once for every prop
that breaks in the world, after that prop’s own OnDestroyed. Bind it once — on your AI manager, a
quest system or telemetry — instead of binding every prop:
- an AI that watches its surroundings can investigate where a prop broke, using
Hit.ImpactLocationor the destructible’sGetIntactCentre(); - quest logic can count the barrels a player smashed, filtering on the hit’s tags;
- telemetry can record which props break, how and by whom.
Breakables around a point
USDFDestructionSubsystem::FindDestructiblesInRadius(Origin, Radius, bIncludeBroken) returns the
destructibles in play whose intact centre lies within Radius of Origin, nearest first. Broken
props are left out unless bIncludeBroken is set; they are then found where they stood.
GetIntactCentre() on a destructible returns the point it is measured from. Use it for an AI that
looks for something to smash, or a spell that needs the props around its target.
For props a character touches, see OnDestructibleTouched in
Bodies against props.
Navigation
What the AI’s paths do when a prop breaks, on the Behavior or as the Navigation exception on one setup or one placed copy:
- Navigation On Break:
- Follow NavMesh (the default, as in SDF 1.0) leaves it to the navmesh’s own Runtime Generation. With Dynamic, the way opens once the prop breaks; with Static or Dynamic Modifiers Only, it stays closed.
- Obstacle Until Broken: the standing prop marks its area as an obstacle, lifted at the break. The way opens with a Dynamic or a Dynamic Modifiers Only navmesh. It needs a box, sphere or capsule intact collision (SDF’s own actors have one), and then keeps the intact’s own mesh out of the navmesh geometry.
- Debris Affects Navigation (on by default, as in SDF 1.0): with a dynamic navmesh, the debris cut it where they lie, and may close a way the prop opened. Off, the AI walks through them.
A Static navmesh never changes while the game runs, whatever the prop says. Measured on a two-metre gap plugged by a prop, with a dynamic navmesh: closed while it stands, a ten-metre path straight through once it breaks.
Weapon Recoils When Held
With Weapon Recoils When Held on — on the Behavior, or as an exception on one setup or one placed copy — a melee blow the prop holds makes the weapon bounce back. A prop holds a blow when it is indestructible or locked; a prop that breaks, or only loses health, never sends the weapon back. Off by default; no prop in the demo map turns it on.
USDFMeleeHitSenderComponentsetsbShouldRecoilin the melee result (FSDFMeleeDeliveryResult) and fires On Melee Recoil (OnMeleeRecoil).- At most once per swing: a blade that bounces off a wall and then touches a pillar in the same swing recoils once.
- SDF plays nothing. Your character plays its rebound from On Melee Recoil.
The demo character (ASDFDemoCharacter) shows one way to play it. Its values, under SDF Demo >
Combat:
| Setting | Value | What it does |
|---|---|---|
| Recoil Freeze Seconds | 0.08 s | The swing first freezes at the contact: the blow lands |
| Recoil Seconds | 0.3 s | Then the swing runs backward this long, fast at first and slowing down |
| Recoil Start Speed | 1.5 | How fast it runs back when the rebound starts, as a share of the attack’s own speed |
| Recoil End Speed | 0.2 | How fast it runs back when the rebound ends |
| Recoil Step Back | 40 cm | How far the character steps back during the rebound |
| Recoil Blend Out Seconds | 0.35 s | How long the character takes to blend back to standing |
| Recoil Shake Amplitude | 4 cm | Camera shake at the contact; 0 for none |
| Recoil Shake Seconds | 0.2 s | How long the shake takes to fade |
See Melee integration for the sender itself.
Break What Rests On It
With Break What Rests On It on — on the Behavior, or as an exception on one setup or one placed copy — the props resting on the prop break with it when it breaks: the pots on a shelf shatter with the shelf.
- One wave only: the props it breaks carry
SDF.Source.Chainand pass nothing on, even if they have the option themselves. - An indestructible or locked prop on top still holds.
- Off by default: what rests on a broken prop falls instead, into the wreck. See Intact physics and fall damage.
To damage everything around a broken prop rather than only what rests on it, see Chain reactions.
Debris Pushed By Characters
Debris Pushed By Characters, on the Behavior or as an exception on one setup or one placed copy, is off by default: characters pass through debris, as in SDF 1.0. On, a character walking or rolling through the prop’s debris nudges the pieces at its feet away from it and along its way. It is one way only: debris still ignore pawns, so they never block, lift or trip the character, whose path stays the same as on an empty floor.
- Every character counts, player or enemy, moving at 30 cm/s or more; the lower 70 cm of its capsule is its feet. A pushed piece is left alone for 0.3 s, then may be pushed again.
- Max Debris Pushes Per Second, in the budget limits (40 by default), bounds how many pieces are
nudged each second; 0 pushes none.
GetBudgetStats()reportsTotalDebrisPushes,TotalDebrisPushesRefusedand the time spent,DebrisPushSeconds. - The check runs 30 times a second, and only while such debris exist.
- Chaos and Swap And Scatter pieces are pushed; glass shards are not. Pieces that settled with their collision reduced (Reduce Collision After Settling) are left where they are: woken, they would fall through the floor.
See Debris: keep, remove, budget and rest.
Camera and characters
On the Behavior, or as the Camera And Characters exception on one setup or one placed copy:
| Setting | Default | What it does |
|---|---|---|
| Intact Blocks Camera | On, as in SDF 1.0 | The standing prop stops the camera like a wall. Off, the camera passes through it |
| Intact Blocks Characters | On | The standing prop stops characters. Off, they walk through it: small decor, grass-high bones |
| Hide When Blocking View | Off | The standing prop is hidden while it stands between the player’s camera and the player, and shown again once out of the way |
- Debris never stop the camera.
- A prop characters walk through cannot be broken by body contact: contact breaks need the body to meet it. See Bodies against props.
- Hide When Blocking View checks 10 times a second with the first local player’s camera and pawn,
only while such props exist. A game with its own camera can call
USDFDestructionSubsystem::UpdateViewBlockers(View, Target)itself, from C++. - The prop is hidden, not faded: a gradual fade needs a dithered material.
Networked games
The break noise, OnDestructibleBroken, Break What Rests On It and the navigation changes happen
on the server only. Each client shows the debris, sounds and effects. A dedicated server spawns no
debris, so Debris Affects Navigation has no effect there. See
Networked games.
Last updated: 2026-10-27