Diagnostics

Why a prop does not break, answered in four places - the Rejection Reason of every hit, the Diagnose this object panel, asset validation with its SDF-DATA codes, and the development console commands - plus the PIECES report and the settings shown only when they act.

Why does this prop not break? SDF 2.0 answers in four places: the result of every hit, the Diagnose this object panel, the validation of your assets, and the development console commands. None of them changes your data.

Why a hit did not break the prop

Every hit returns an FSDFDestructionResult. Next to its Outcome, RejectionReason (ESDFRejectionReason) says why the prop did not break, or None when it did. Each reason’s tooltip, in Blueprint and in the panel below, says what to do.

Rejection ReasonThe prop did not break because…
LockedSetDestructionEnabled(false) locked it.
Already BrokenIt is broken already.
Not StartedA script tried to break it before its BeginPlay.
No ProfileIt has no Destruction Profile.
Invalid Debris SettingsIts debris settings are not valid numbers; the log names the field.
Refused By ActorIts actor’s CanReceiveDestructionHit refused the hit.
Projectile PolicyThe hit came from a projectile and its projectile policy refuses projectile damage.
Too SlowThe hit’s Impact Speed is below Minimum Impact Speed.
IndestructibleIt is indestructible.
Power Too LowThe hit’s Destruction Power is below Minimum Destruction Power.
Below DefenseDamage Threshold Blocks Break is on and the hit’s Damage is below Minimum Damage Threshold.
No DamageThe hit did no damage to a prop that breaks when its health runs out.
Health RemainsThe hit did damage, but the prop has health left.
Break Refused By ActorIts actor’s CanDestroyFromHit refused the break.
Cannot Show BreakNothing could show the break (no collection, no debris): the hit was rolled back. In a networked game the break commits instead: the server decided it.
Destruction OffSDF.Debug.Destruction is off (development builds).
Not Allowed BreakerWhoever dealt the hit may not break it: its Allowed Breakers, the SDF.CannotBreak tag, the attacker’s SDF Breaker interface or the world’s breaker filter said no.
Partly BrokenPartial Break is on: the hit broke off only the pieces it reached. The prop collapses once Collapse At of its pieces have fallen or its health is gone.
Server DecidesA networked game: on a client a hit breaks nothing; the server decides, and its break arrives.

To show it in game, three pure Blueprint nodes under Souls Destruction > Diagnosis turn a result into one localizable sentence, in packaged games too: Describe SDF Result, Describe SDF Radial Result and Describe SDF Rejection Reason (empty for None). See Integration examples and Who may break a prop, and how hard.

Diagnose this object

Select a placed destructible’s SDF component, in the editor or while playing in the editor, and open Diagnose this object in its Details. The panel answers in plain words, on the values the prop really plays — its setup, Behavior and Material, with both levels of exceptions:

  • Why it does not break (or It can break): the answer, in the order a hit is decided, then what to do after the arrow. For example: The last hit was too weak: Medium. This prop needs Heavy.
  • What breaks it: one hit of a given power or more, or hits until its health runs out (Hits of Light power or more, until its health runs out (40 of 100 left)); for a prop whose Health Mode is Number of Hits, the hits left (3 hits of Light power or more, whatever their damage (2 of 3 left)); the speed and damage a hit needs, when it needs them; whether projectiles, body contact and falls can break it; and whether this prop has its own exceptions.
  • Last hits: the last 8 hits in a few words — where the hit came from, its power, its damage and what happened, such as Melee, Medium, 20 damage → too weak. The same hit several times in a row shows once, with its count. Hit it in Play In Editor and the panel follows within half a second.
  • Advanced, closed by default: the technical side — setup, Behavior and Material, every effective value, each hit with its time, speed and rejection reason, and what the validation says about these values.

From code:

  • Diagnose() (Blueprint pure) returns the same data as an FSDFDiagnosis: state, setup, Behavior and Material names, whether exceptions apply, the health (CurrentHealth, MaxHealth - its starting health: Max Health, or Hits To Break when it counts hits - and HealthMode), power, speed and damage gates, whether projectiles and body contact can break it, the destruction mode and fallback, the per-frame break budget, whether SDF.Debug.Destruction is on, and the last hits as FSDFDiagnosedDecision entries, oldest first.
  • In C++, DescribeDiagnosis() returns the plain text of the panel and DescribeDiagnosisDetails() its Advanced part. They are C++ functions of USDFDestructibleComponent, not Blueprint nodes.
  • While playing, SDF.Debug.Diagnose Name=<text> writes both parts for every prop whose name contains the text to the Output Log.

Last hits in development builds only

The last hits are kept in development builds only. A Shipping build returns the values without them, and the SDF.Debug commands are not available in Shipping.

Validating assets

SDF profiles, Behaviors, Materials, authoring presets and placed SDF components validate themselves through Unreal’s Data Validation, enabled by default:

  • right-click assets and choose Validate Assets;
  • right-click a folder and choose Validate Assets in Folder;
  • or let your project validate on save.

SDF.Validate [Root=/Game] checks every SDF asset under a folder and lists what it found; without Root it checks /Game and /SoulsDestructionFramework. Validation only reads: it never corrects anything.

What is checked depends on what the asset is for:

  • A template — a profile an authoring preset starts new setups from (its Runtime Profile Template) — carries no model of its own and takes its reaction and look from the Behavior and Material given at generation. Only its numbers and references are checked.
  • A setup must carry everything its break needs. What its shared Behavior or Material does on its own is reported once, on that asset, not on every setup that uses it.
  • A placed prop reports a missing profile, a template used as its profile, and what its own exceptions change. A Blueprint’s class default is not asked for a profile.

A field greyed out by its condition does nothing and is not reported. Errors make the asset invalid; warnings point at settings that have no effect.

CodeMeans
SDF-DATA-001A number is not finite.
SDF-DATA-002A number is outside its allowed range: it came from a script, an import or an older asset.
SDF-DATA-003A value is none of its choices.
SDF-DATA-004A reference points to an asset that no longer exists.
SDF-DATA-010Geometry Collection mode without a collection and without fallback debris: every break fails.
SDF-DATA-011Geometry Collection mode without a collection: every break uses the fallback debris.
SDF-DATA-012The Geometry Collection Asset is not a Geometry Collection.
SDF-DATA-013Swap And Scatter without any debris that can spawn: every break fails.
SDF-DATA-014Destruction Mode None: the prop disappears and nothing replaces it.
SDF-DATA-016, 018, 019A debris entry without mesh, or a minimum above its maximum.
SDF-DATA-020 to 027Health, single hit, power override, damage threshold or launch range settings with no effect.
SDF-DATA-030, 031, 033Sounds, decals or effects switched on with nothing to play.
SDF-DATA-032Spawn Loot without a loot actor.
SDF-DATA-034 to 038Propagation, body contact, fall, pawn contact or body contact breaks that can never break the prop.
SDF-DATA-040 to 042Preset fragment counts the ceiling cuts down, out of order, or a ceiling above what the cutter places.
SDF-DATA-050, 051An empty Behavior module slot, or two modules of the same kind.
SDF-DATA-060, 062A placed prop without a profile, or with an authoring template as its profile.
SDF-DATA-070Allowed Breakers is Tagged Attackers Only with no Breaker Tag: no attacker may break the prop.
SDF-DATA-080Destruction Mode Animated with a Break Animation missing: a break that picks it fails.
SDF-PHYS-001Precise debris collision needs the project physics step described in Debris: keep, remove, budget and rest.

Authoring issues (SDF-AUTH-..., SDF-BATCH-..., SDF-REGEN-...) are listed in Troubleshooting.

Development console commands

Available in every build except Shipping, while playing:

CommandDoes
SDF.Debug.Destruction 0 / 1Switches every break off or back on. Off, hits are still heard and seen and return Destruction Off.
SDF.Debug.BreakAll [Radius=<cm>]Breaks every intact or damaged prop through the normal break, budgets applied; within the radius around the player when given. Locked and indestructible props are left alone.
SDF.Debug.RestoreAllPuts every broken or damaged prop back as placed. Locks are kept.
SDF.Debug.ClearDebrisRemoves every piece of debris; broken props stay broken.
SDF.Debug.StatsCounts intact, damaged, broken and locked props, debris, and the budgets in use, including the moving debris pieces against Max Active Debris Pieces, the last collision level and how many pieces were set apart.
SDF.Debug.Diagnose Name=<text>Writes Diagnose this object for the matching props to the Output Log.

SDF.Debug.BreakAll is also the quickest way to see a freshly generated prop break with no code: play, open the console and type it; SDF.Debug.BreakAll Radius=500 breaks only the props within 500 cm of the player, and SDF.Debug.RestoreAll puts them back.

The remembered props have three cheat commands of their own (not in Shipping), for the world they are typed in: SDF.ResetAll restores every zone as a rest at a checkpoint would, SDF.ResetZone <ZoneId> restores one zone, SDF.ListBroken lists the props remembered broken. In a networked game, type them on the server. See Broken props remembered.

Two debris commands turn SDF’s Geometry Collection corrections off for comparison: SDF.Debris.ContactRefinement 0 and SDF.Debris.RestFreeze 0. See Debris: keep, remove, budget and rest.

Pieces: what was aimed for and what came out

Validate Destructible ends with a PIECES paragraph, in plain words:

  • The recipe aimed for: what the density or Custom Fragment Count asked for. For wood and barrels it is only a guide: the mesh’s own parts decide.
  • It made: every piece of geometry in the Geometry Collection, then how many fly apart when it breaks. Bigger parts that were cut again never show as pieces of their own, and pieces that never move on their own are counted apart.
  • Limits: the aim goes up to the preset’s Maximum Allowed Fragment Count, never above the 150 cuts the cutter places. It does not cap the whole output of a structured recipe: a table of 30 boards gives at least 30 pieces. The project’s Maximum Fragment Count (Project Settings > Souls Destruction Authoring, 400 by default) caps the total.

The supplied Barrel 01 aims for 10 pieces and makes 92: 69 fly apart, 23 are bigger parts cut again. The supplied table aims for 16 and makes 168: 136 fly apart, 32 are bigger parts cut again.

Two authoring codes name the fragment rules: SDF-AUTH-VAL-010 reports a cut recipe that produced more than 4 times its target, and SDF-AUTH-VAL-005 a collection above Maximum Fragment Count. See Troubleshooting.

Settings shown only when they act

Max Health, Health Mode, Damage Multiplier, Impact Damage Multiplier and Allow Power Override are greyed out unless Use Health is on and Destroy On Single Valid Hit is off: a prop that breaks on one valid hit, or has no health, never reads them. Hits To Break is greyed out also unless Health Mode is Number of Hits. Nothing saved changed: every setting keeps its name and its default value.

Asking for support

For a prop that does not break, include what Diagnose this object reports, with the SDF version, the engine patch, the platform, the relevant logs and minimal reproduction steps. See Support.

Last updated: 2026-10-29

Type to search titles, sections and keywords.