Troubleshooting

Start with the visible symptom and check the graph, runtime UI, input module, or imported asset involved before changing project settings.

The dialogue does not start

• The DialogManager has a usable DialogUIManager reference or prefab, or a valid DialogUIController is already in the scene. The old uiPanel field is not the current setup.
• If you use PlayDialogByID, check that dialogGraphs contains exactly one matching ID and a graph reference. IDs are matched as registered keys.
• In the Graphs workspace, show the graph sidebar, select Validate, and click Validate Graph. Review its issues and inspect Start’s outgoing route to a valid next node or End.
• Check the Console for a specific refusal, such as a missing UI manager, invalid graph, or ambiguous ID.

The UI appears but choices do not work

• Open the active DialogUIController and check its choice prefab and choicesContainer bindings. The current controller also supports its configured fallback choice prefab.
• Check the choice prefab’s expected view/button components and that the container belongs to a live scene UI, not a Project prefab asset.
• Confirm an active EventSystem has an input module compatible with the project’s Active Input Handling. DGS includes an optional bridge for the Input System UI module; the Input System package itself is not required for the core runtime.
• Check the choice’s requirements and outgoing link in the graph. A visible choice does not guarantee that its authored destination or requirements are valid.

History panel is empty

• Check that a DialogueHistory component is initialized against the active manager. It can resolve the manager’s current UI history view when one is available.
• Verify the history panel is enabled in the effective runtime UI settings and the view’s required panel, list/viewport, and row prefab references are assigned.
• Check the retention policy: CurrentConversation starts a fresh visible session for a new conversation, while broader retention keeps entries within the configured cap.
• Open the panel only after at least one line or choice has been committed. It records runtime presentations, not graph nodes merely selected in the editor.

Transcript comes back empty

• Use PlayDialogByID if you need branch-path lookup by ID; a direct StartDialog(graph) call does not provide that registry ID.
• Check that the requested ID still maps to one graph and that the conversation recorded a branch path.
• Call GetLastPlayedDialogTranscript after a run that reached a terminal point, and check the returned text rather than assuming every run has a transcript.
• Rebuild after graph edits. A stored path is a sequence of branch indices and cannot always be replayed against a structurally changed graph.

JSON import fails

• Use Production > Import / Export in Tools > Beka Forge > Dialogue Graph System > Open Editor. Select a TextAsset or external JSON file and choose Load & Validate JSON before importing.
• Read the preview and refusal message. DGS validates identities, node data, choice requirements, references, and supported branch/condition structures before creating the graph.
• Import as a new independent copy for ordinary reuse. Choose overwrite only when you intend to replace an existing target and have reviewed the exact target.
• Keep external JSON untrusted and review the imported graph in the editor before use.

Contextual Banter does not appear

• Check that the Banter host finished initialization before it submitted a request.
• Compare the submitted trigger and category with enabled exchanges in the configured collections, then run the Exchange and Catalog validators.
• Check the exact registered ActorIds and character-role bindings. See Set up Banter.

Graph sound is assigned but silent

• Graph authoring data and playback are separate: prepare a fresh runtime binding from the graph’s sound sidecar, then use a scene bridge with the correct manager, binding, and distinct ambience/local players.
• Check the AudioClip, AudioListener, mixer and active output device. See Set up Walla sound.

For AI-provider setup and authoring diagnostics, use the AI authoring guide; provider details are maintained separately from this core troubleshooting page.