j.foucher
c2ca2e3dbb
Networked clients could hear the agent but the agent never replied to them (worked in standalone/listen-server host). Root causes, client-only paths that never run on the authority: 1. Deferred StartListening was never retried once the conversation went live. OnRep_ConversationState now (re)starts listening when bNetIsConversing replicates and the local player is in the conversation — closes the RPC/replication ordering race so bIsListening reliably opens the uplink. 2. The client stripped ALL silent mic chunks to save bandwidth, but ElevenLabs Server VAD needs the trailing silence to detect end-of-turn — so the agent heard the words but never the pause and never responded. Replaced the hard silence drop with a silence "tail": keep streaming for MicSilenceTailSeconds (default 2s, tunable) after the last voiced chunk, then drop during idle. The authority path is unchanged (always streams the full mic). Also: debug HUD now shows "CONNECTED (via server)" on clients instead of a misleading "DISCONNECTED" (clients have no local WebSocket; IsConnected() is always false there). [MIC-DBG] temporary diagnostics are kept in this commit to validate the fix on another machine; they will be removed in a follow-up once confirmed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>