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 Actor Compare panel and pre-populates it with the row preset as Primary 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.

Purpose

Actor Compare lets you pick a primary actor and compare it against a list of other actors — all in one view. For each actor you add, the panel evaluates every collision-capable component on that actor and shows how it resolves against the primary, so you can see the full collision surface without jumping between presets.

A practical example: set your Projectile actor as the primary, then add a range of enemy and player actor types. You'll see in one glance exactly what the projectile blocks, overlaps, or ignores across your entire cast — and catch any mismatches before they show up in play.

Adding actors to the compare list

• Click and drag any actor from the level viewport or Content Browser directly into the compare list panel
• Click the import button (folder icon) to browse and select an actor asset from the Content Browser
• Both methods support adding multiple actors — build the list as large as you need
• Remove any entry using the × button on its row
• Use the Refresh button to re-evaluate after a Project Settings change

Reading a result row

Each row shows: the comparison preset name, a color-coded BLOCK / OVERLAP / IGNORE badge, A→B raw response, B→A raw response, and an optional overlap event warning.

Overlap event warning (⚠)

When a resolved result is OVERLAP, a warning indicator appears. This is a reminder that for the BeginOverlap event to fire at runtime, both actors must have Generate Overlap Events enabled on their collision component — not just one. A resolved OVERLAP result is a necessary but not sufficient condition for the event to fire.

What it is

Experiment Mode is a what-if sandbox. You temporarily override channel response values and the matrix updates live to show how those changes would affect all interactions — without touching your actual Project Settings.

Active experiment indicator

When any override is set, a prominent banner at the top of the Experiment panel reads "Experiment Mode Active". The Matrix panel also reflects this state. This visual indicator ensures you never confuse experimental values with your real project state.

Setting overrides

Each channel has Query and Physics override dropdowns. Set either to Ignore, Overlap, or Block. The matrix updates immediately — no evaluate button needed.

Diff highlighting

Cells in the Matrix that differ from the project baseline are highlighted with a distinct border, making it easy to see at a glance exactly what your override changes.

Committing an experiment

When you're satisfied with an experiment, press Commit to Project Settings. This writes your overrides to the project's collision configuration. This is the only place in Collision Commander where data is written back — and it requires an explicit button press. There is no auto-commit.

Resetting

Press Reset to clear all overrides instantly and return the matrix to its baseline state. Closing the panel without committing also discards all overrides.

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.

Triggering an export

Click Export… in the Collision Commander toolbar. A file-save dialog opens — choose a location and filename. The plugin writes a .xlsx workbook and shows a confirmation toast. There is no auto-save.

What's in the workbook

• Sheet 1 — Preset Definitions: Every preset with its Object Type, Collision Enabled state, and per-channel Query responses. Blue rows for UE built-ins, green rows for custom presets.
• Sheet 2 — Collision Matrix: The full N×N grid with BLOCK / OVERLAP / IGNORE fills and the built-in / custom separator border.
• Sheet 3 — Actor Compare: Your current Actor Compare session, if one is active. "No active comparison" note otherwise.
• Sheet 4 — Validation Report: All active validation warnings at export time, with severity colors, rule IDs, and suggested fixes.
• Sheet 5 — Snapshot Info: Project name, engine version, export timestamp, plugin version, and preset / channel counts.

Compatibility

The workbook uses no formulas — all values are pre-computed at export time. Compatible with Microsoft Excel 2013+, LibreOffice Calc, and Google Sheets.