Dialectic

Dwemer Dynamics HomeOverviewInstallationConfigurationRoleplay SettingsFallout SettingsLarge Language ModelsText-to-SpeechSpeech-to-TextModders GuideFAQRemote Hosting GuideLinux Setup GuideLog Files

⬇️Beta DownloadDiscordDiscordYouTubeYouTubePatreonPatreon

Dialectic Log Files

Use the log closest to the failing phase instead of guessing across the complete dialogue pipeline.

Game Plugin Log

Documents\My Games\FalloutNV\NVSE\dialectic.log

This is the first log for hotkeys, target resolution, requests, streaming responses, queue state, TTS downloads, playback, subtitles, lip animation, rechat, actions, actor scans, menus, and task health.

JIP LN And Script Logs

Check jip_ln_nvse.log when the bootstrap, MCM callbacks, game event handlers, or user-defined Fallout scripts do not register. The exact physical path depends on the game and Mod Organizer setup.

DialecticServer Logs

DwemerDistro stores the current server logs under:

/var/www/html/DialecticServer/log

Open DialecticServer - Control Panel - Server Logs or the Dwemer Dashboard Distro Debugger to inspect them.

  • dialectic.log - main request, game data, pipeline, action, memory, rechat, and timing log.
  • apache_error.log or php_error.log - PHP warnings, fatal errors, and web failures.
  • output_from_llm.log - normal language-model output.
  • context_sent_to_llm.log - normal prompt context.
  • output_from_llm_fast.log - fast/background model output.
  • context_sent_to_llm_fast.log - fast/background prompt context.
  • output_to_plugin.log - response envelopes and commands sent to Fallout.
  • stt.log - microphone upload and transcription.
  • debugStream.log - streamed response diagnostics.
  • monitor.log - worker and service monitoring.
  • service.log and manager.log - background service management.
  • relationship_worker.log - asynchronous relationship updates.

Follow One Request

Dialectic logs a shared turn or request ID across the main request, game data, LLM, TTS, STT, plugin response, and delivery acknowledgement paths. Search that ID across files to reconstruct one conversation.

Useful timings include STT, player TTS, LLM first token, NPC TTS start and finish, delivery, playback start, and playback completion.

Response Queue And Audio Cache

The Control Panel Response Queue shows pending server responses. The cache browser shows generated audio and images. A response can exist in the event log but still fail later during TTS generation, cache download, stale-request cancellation, or playback.

Launcher Diagnostics

The DwemerDistro launcher diagnostic creator collects DialecticServer logs and the Windows-side plugin log when it can locate them. It writes the report to:

Desktop\DwemerDistro-Diagnostics\diagnostics-YYYYMMDD-HHMMSS.txt

Create the diagnostic report immediately after reproducing the issue so the relevant log tail has not rotated away.

Recommended Debug Order

  1. Check dialectic.log for input, target, server URL, and request ID.
  2. Check dialectic.log on the server for request acceptance and phase timings.
  3. Check LLM context and output.
  4. Check TTS or STT service logs when that phase is slow or fails.
  5. Check output_to_plugin.log and the game plugin queue/playback lines.
  6. Check Apache/PHP errors for web UI failures.