Known issues / S1

Luduvo bug Worth knowing Windows unconfirmed

D3D12 used without trying Vulkan

No word yet

Your game went straight to D3D12 without trying Vulkan first. On build 45 every Windows log posted so far does this.

What you see

The log shows D3D12 starting up with no Vulkan lines before it.

Who's affected

Every build 45 log posted on 26 Sep, on NVIDIA, AMD and Intel. Before that, an AMD RX 9060 XT on builds 41 and 44.

Why it happens

An early release note said Windows users default to D3D12. If Settings.cfg says graphics_api=D3D12, Luduvo may skip Vulkan entirely. Build 45 seems to start every Windows PC on D3D12, and nobody has said yet whether the setting still changes that. unconfirmed

What to do

  1. Press Win + R, paste %APPDATA%\Luduvo\Client and press Enter. Copy Settings.cfg somewhere safe first.
  2. Open Settings.cfg in Notepad and find the graphics_api line.
  3. If it says D3D12 and your graphics card supports Vulkan 1.3, you could change it to Vulkan and save. Nobody on the forum has confirmed this fixes the client yet. unconfirmed

Don't bother with

  • Editing any other Luduvo file.

Status

No staff word on this one yet.

How the Doctor spots it

It looks for log lines like these (patterns, not exact text):

  • [d3d12] backend init begin

Sources

Credits

  • alaz, showed switching the API can help

unconfirmed means a player suggested it and nobody has confirmed it works yet.

Last checked 26 Sep 2026.