LORKHAN

Home Overview Installation Configuration Roleplay Settings Morrowind Settings Large Language Models Local LLM Guide Text-to-Speech Speech-to-Text Modders Guide FAQ Remote Hosting Logs and Debugging

Beta downloads Discord Patreon Mod Code Server Code

Logs and Debugging

Collect evidence from the same failed conversation before changing settings.

First checks

  1. Confirm DwemerDistro and LorkhanServer are running.
  2. Open the server webpage through the launcher.
  3. Check the target in Text Chat and Interact and send a short typed message.
  4. Note the time and whether text, NPC speech or microphone transcription failed.

Server logs

Open the Dwemer Dashboard, enter its debugger and select LORKHAN. Use the server log views there to inspect errors around your test time.

The server’s AI responses and event history are useful for checking what was recorded, but a recorded response alone does not prove audio played in game.

Client logs

Use Open LORKHAN Logs in the launcher to find the client logs. The in-game Diagnostics menu can help identify a missing bridge or connection.

For a bridge error, first confirm you launched Play-LORKHAN.cmd from the intended beta profile and did not mix files from different builds.

Create a support report

  1. Open the launcher’s LOGS tab.
  2. Select Generate Distro Debugging Logs and confirm the prompt.
  3. Review the diagnostic archive before sharing it. Do not include API keys, pairing keys or private configuration files.
  4. Report the beta version, what you tried, NPC name, approximate time and whether typed chat also fails.

Share the report through Discord. Do not reinstall or clear your history just to collect logs.

Collect a Useful Reproduction

  1. Note the time, NPC name/reference ID, profile, LLM slot and voice service.
  2. Send one short typed message to exclude microphone transcription from the test.
  3. If it works, repeat with Voice Chat. Note whether recording, transcription, generated text or playback is the first missing stage.
  4. Collect dashboard logs around that time, together with client/server versions and whether the issue began after an update or save load.

Do not reset connectors or clear history before gathering evidence. Remove keys, tokens and private prompt text before sharing logs publicly.