FAQ

Fix the most common D4LF and Diablo 4 loot filter problems.

Start here for the issues players hit most often, especially if you searched by the exact D4LF error text.

Exact D4LF error strings this page covers

  • TTS connection has not been made yet
  • D4LF GUI crashes immediately with no error message
  • D4LF mouse control does not work
  • D4LF Paragon overlay does not appear
D4LF GUI crashes immediately with no error message.

This usually points to a broken params.ini file. Delete params.ini, reopen the GUI, and reconfigure the settings there so the file is regenerated correctly.

D4LF mouse control does not work.

Run D4LF as administrator. If you prefer not to, set vision_mode_only to true in params.ini to disable mouse-driven actions.

Steam users see "TTS connection has not been made yet." in D4LF.

Set Diablo IV.exe to Run this program as an administrator. If the issue remains, also run Steam as administrator and launch Diablo IV through Steam again.

D4LF Paragon overlay does not appear.

Use borderless windowed mode, make sure your profiles include a top-level Paragon section, and verify that toggle_paragon_overlay is not conflicting with another hotkey.

Source D4LF README Common problems section Last verified 2026-05-11 Drift medium

After troubleshooting

Retry the right setup branch

Use the recovery branch that matches the root cause you found, or escalate to upstream when you have already exhausted the documented fixes.

Install

Install guide

Return to the install steps when the failure points to TTS, DLL setup, or first-run game settings.

Open install steps

Config

Profiles and configs

Jump back to params.ini, YAML profiles, or hotkey settings when the app launches but the behavior is still wrong.

Inspect config layout

Escalate

Upstream issues

Escalate reproducible D4LF bugs to the official issue tracker after you have confirmed the local setup path.

Open GitHub issues

If your issue still falls outside these cases, check the Discord server or GitHub issues.