Skip to content

Troubleshooting

Symptom Check
No dialogue UI Widget created, added to viewport and bound before Start Dialogue?
Name/text not populated Correct widget parent, exact optional binding names and matching types?
Choices missing ChoicesPanel and Choice Widget Class set? Conditions hiding all responses?
Wrong response selected Using stale or authored indices instead of the current visible list?
Double press skips too much Is the same input routed to widget confirmation and component Continue?
Continue never appears Runtime policy, pause/choice state, visibility mode and typewriter progress?
Panel shrinks during choices Use Hidden instead of Collapsed for Continue Button Hidden Layout
Speaker color ignored Use Speaker Color for Name enabled? SpeakerNameText actually bound?
Expression validation fails Default/requested tag defined in that speaker’s Expressions array?
Voice silent Default Game Managed mode requires your playback; choose Built In for automatic 2D
Voice plays twice Both built-in and external handlers playing the same request?
After Voice stalls Captured request ID reported correctly? Playback unavailable/failing? Inspect fallback
External condition always false Selected object exists and implements Condition Provider? Exact role registered?
Event happens twice Same effect handled in both provider and event delegate?
Signal ignored Correct component/tag, wait active, dialogue not paused, no early send?
Camera does not move Provider instance assigned, local controller available, linked Speaker Actor/custom target valid?
Camera framing looks wrong Offset is relative to Actor rotation; look-at aims at Actor origin
Restore rejected Existing dialogue still active? Unsupported snapshot? Missing asset/node/entry? Read Failure Reason
Resume has no character/UI Restore was called before level, Speaker Actor links, widget or providers were ready
Works in editor, missing in package Assets included in cook? Runtime free from editor dependencies?
Build ends with code 6 Read the first C++/UHT error above MSB3073, not just the wrapper

When reporting a problem, include engine/plugin version, first actionable error, expected behavior, minimal graph and whether it occurs in PIE or the packaged game. Do not regenerate GUIDs as a generic repair for a saved conversation.