Collision debugging,
finally visible.

What it shows

An N×N grid where every row is a preset (Actor A) and every column is a preset (Actor B). Each cell shows the resolved interaction between that pair using UE's pairwise resolution rule.

Visual separator

A thick border divides UE's 14 built-in presets (top-left block) from your custom presets (bottom-right block). This helps you spot when a custom preset is misconfigured relative to the built-ins.

Hover tooltip

Hovering any non-diagonal cell shows:

• PresetA's response to PresetB's Object Type channel
• PresetB's response to PresetA's Object Type channel
• The resolved result (the minimum of both)

Clicking a cell

Left-clicking any non-diagonal cell switches to the Collision Compare panel and pre-populates it with the row preset as the focus and the column preset as the first comparison entry.

Refreshing

Click the Refresh button to re-read UCollisionProfile and rebuild the matrix. The matrix also auto-refreshes when Project Settings change during your editor session.

What it's for

The Matrix gives you the full picture, but hunting down a specific pairing in a large grid gets old fast. Collision Compare gives you a focused view: pick one preset as your focus, then add however many others you want to compare against. One table, all the pairings you care about.

Good example: set your Projectile preset as the focus and add all your character and enemy presets. You'll see in one shot what it blocks, overlaps, or ignores across the board.

Building your compare list

• Select a focus preset from the dropdown at the top
• Add comparison presets to the list below it
• Remove any entry with the × button on its row
• Hit Refresh after a Project Settings change to re-evaluate

Reading a result row

Each row shows the comparison preset name, a color-coded BLOCK / OVERLAP / IGNORE badge, the A→B raw response, and the B→A raw response. Hover any row for the full tooltip.

Overlap event warning (⚠)

When a pairing resolves to OVERLAP, a warning icon appears on that row. This is a reminder that for BeginOverlap to actually fire at runtime, both actors need Generate Overlap Events enabled. A resolved OVERLAP result is necessary but not sufficient.

What it's for

A single actor can have a capsule, a skeletal mesh, a hitbox sphere, and a weapon trace component, each with its own preset and settings. Checking them individually in the Details panel is slow and gives you no combined view.

There's also a hidden problem worth knowing about: if you manually edit a component's collision responses in the Details panel without assigning a named preset, it gets set to Custom. That bypasses the preset system entirely and makes that component's collision harder to audit. The Actor Inspector calls that out explicitly.

How to use it

• Pick a Blueprint actor from the level or the Content Browser
• The panel lists every collision-capable component with its preset, enabled mode, and object type
• Build a list of target presets or channels below, and the panel renders a per-component interaction table
• Hover any cell for the tooltip with both contributing responses and the resolved result
• Hit Refresh after loading a new actor or changing Project Settings

Custom preset warning

Any component using a Custom profile gets a ⚠ icon with a tooltip explaining the issue. These warnings are also forwarded to the Validation tab automatically when you refresh.

What it's for

When you're thinking about adding a new preset or changing how an existing one behaves, there's no safe way to preview that in vanilla UE without actually editing Project Settings and then undoing if it's wrong. Experiment is a sandbox for that. Design a preset, tweak its channel responses, and see exactly how it would interact with everything else in your project before you commit to anything.

How to use it

• Load an existing preset as a starting point, or start from scratch
• Set a name, object type, collision enabled mode, and per-channel responses
• The interaction table at the bottom updates live as you change values
• Nothing is saved anywhere until you hit Create Preset

Committing

When you're happy with the result, press Create Preset. You'll get a confirmation dialog before anything writes. If you loaded from an existing preset and kept the same name, you'll be asked to confirm an overwrite. That's the only point in Collision Commander where data gets written back to Project Settings.

Visual indicator

When an experiment is in progress the panel shows a visible indicator so you always know you're in a modified state. Close without committing and everything is discarded.

When it runs

Validation runs automatically every time you refresh the matrix and every time you commit an experiment. Results are shown in the Validation panel and summarised as a badge count on the toolbar.

Severity levels

• Error: configuration that will likely cause bugs or is known to cause incorrect behaviour. Fix before shipping.
• Warning: potential misconfiguration worth reviewing. May be intentional.
• Info: non-critical observation, such as unused channels. Worth knowing, not urgent.

All 10 validation rules

• CS_CHAN_BUDGET_WARN: 14+ of 18 custom channel slots in use. Audit before adding more.
• CS_CHAN_BUDGET_CRIT: 17+ slots used. Consolidate immediately, you're near the limit.
• CS_CHAN_UNUSED: Custom channel defined but no preset responds non-Ignore. Remove or reserve.
• CS_PRESET_DUPLICATE: Two presets with identical ObjectType and response arrays. Consolidate.
• CS_PRESET_ALL_IGNORE: A preset ignores every channel. Likely misconfiguration.
• CS_STATIC_IGNORED: Dynamic ObjectType preset ignores WorldStatic. Actor will fall through the floor.
• CS_OVERLAP_MISMATCH: A wants to Block B, but B ignores A. The Block is silently overridden to Ignore.
• CS_NAME_CONFLICT: Custom preset name matches a UE built-in exactly. Rename to avoid lookup ambiguity.
• CS_OVERLAP_EVENT: Two presets resolve to Overlap but Generate Overlap Events may not be enabled.
• CS_VISIBILITY_BLOCK: A preset blocks the Visibility channel. This affects AI sight, shooting traces, and camera.