> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/conversation-targeting/troubleshooting.md). # Troubleshoot conversation targeting Fix a conversation target that will not switch, flickers between characters, or never moves in a Convai multi-character room. Diagnose why conversation targeting is not choosing the character you expect in a multi-character room. Each entry below covers one symptom you can observe in Play mode. ### Before you start * Select `ConvaiManager` in the Inspector during Play mode and open the Live section. It names the character currently addressed, whether the player can talk to them, and the verdict behind the last targeting decision. * Open **Convai → Troubleshooter** for a one-shot report covering targeting alongside the rest of the conversation state. If you work with a coding assistant, the `Convai.DiagnoseConversation` tool reports the same thing, including the targeting rule with its values and whether they are still the shipped defaults. * Confirm the scene has two or more `ConvaiCharacter` components registered — targeting logic never runs for a single-character room. ### Looking at a character does not switch the conversation to them **Symptom:** The player's view is clearly on a character, but the conversation stays with a different one, or with nobody. **Cause:** The character's distance or angle falls outside `MaxDistance` or `MaxAngle`, so it is not eligible to be addressed. **Fix:** 1. Open `ConvaiManager` → **Who The Player Talks To** and check **Range (Metres)** and **Look Angle (Degrees)**. 2. Widen whichever value is excluding the character. See [Tune conversation targeting](/api-docs/plugins-and-integrations/convai-unity-sdk/features/conversation-targeting/tune-targeting.md). **Verify:** The Live section reports the character as addressed once the player's view is within range and angle. ### The conversation flickers between two characters **Symptom:** The addressed character keeps switching back and forth between two candidates without the player's view or position changing meaningfully. **Cause:** `SwitchMargin` or `SwitchDelaySeconds` is too low for how close together the characters are standing, so small camera movements are enough to trigger a switch. **Fix:** 1. Raise `SwitchMargin` first — it is measured in degrees under `LookAt`. 2. If flickering continues, raise `SwitchDelaySeconds` as well. **Verify:** The addressed character in the Live section holds steady while the player's view stays roughly on one candidate. ### Nothing switches at all **Symptom:** The conversation never moves to a different character, no matter where the player looks or moves. **Cause:** `ConversationTargeting.Mode` is set to `Manual`, so nothing changes the target except a call to `TalkTo`. **Fix:** Confirm the **Chosen By** field in **Who The Player Talks To**. If `Manual` is intentional, drive the target with `TalkTo` — see [Script the conversation target](/api-docs/plugins-and-integrations/convai-unity-sdk/features/conversation-targeting/script-the-conversation-target.md). If it is not intentional, switch to `LookAt` or `Proximity`. **Verify:** The Live section's addressed character changes when the player looks at or approaches a different character. ### `TalkTo` appears to do nothing **Symptom:** Calling `manager.TalkTo(character)` does not move the conversation, and the Console logs `[ConvaiManager] Cannot talk to '': it is not in the current room. Only characters that joined this connection can be addressed.` **Cause:** The character passed to `TalkTo` is not a member of the current room — it either was never registered, or it left the room since the room connected. **Fix:** Confirm the character is one of the `ConvaiCharacter` components that joined the current connection. `manager.ConversationTarget` and the room roster confirm current membership. **Verify:** The warning stops appearing and the Live section reports the requested character as addressed. ### The conversation seems stuck holding one character **Symptom:** The addressed character does not change even though the player is clearly not looking at or near them anymore. **Cause:** This can be correct behavior rather than a fault. The target never clears itself — when nobody currently qualifies as eligible, the last character addressed keeps the conversation rather than the conversation going silent. **Fix:** Check `ConvaiManager.ConversationTargetingStatus` (or the Live section's verdict) to tell a held target apart from a stuck one — `AlreadyActive` or `HeldForDelay` mean targeting is working as designed. If the verdict never changes even when the player is clearly addressing someone new, check whether that character is eligible under the current `MaxDistance` and `MaxAngle`. **Verify:** Moving a genuinely eligible character into range and angle changes the addressed character. ### Related pages {% content-ref url="/pages/zzX2LcsbroZhIMpddTMg" %} [How conversation targeting works](/api-docs/plugins-and-integrations/convai-unity-sdk/features/conversation-targeting/how-conversation-targeting-works.md) {% endcontent-ref %} {% content-ref url="/pages/WU9yfXg75LQp4e4UXSZS" %} [Troubleshoot multi-character sessions](/api-docs/plugins-and-integrations/convai-unity-sdk/features/multi-character-sessions/troubleshooting.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/conversation-targeting/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.