Why this exists

I kept seeing the same few errors in the bug threads. Someone posts a screenshot of the popup, staff ask for client.log, and a week later someone else posts the same thing. The biggest thread, "I cant play luduvo because of this bug", passed 190 posts.

The four most common failures have no fix on your end yet. People were reinstalling drivers and deleting folders for nothing. So I made this: drop your log in, and it tells you what's wrong, whose problem it is, and what's worth trying. If there's nothing you can do yet, it says so.

It has nothing to do with trading or the Luduvo API. It doesn't log in, doesn't talk to Luduvo's servers, and doesn't know who you are.

-Tippy

How your logs stay private

Your logs are read by code running in this browser tab. Nothing is uploaded, ever.
The page's security policy sets connect-src 'none'. That tells your browser to block every network request the page tries to make. You can check: open your browser's developer tools, go to the Network tab, and drop a log. Nothing new appears.
Fonts are served from this site. There are no analytics, no cookies, no ads and no third-party scripts.
Before you copy or download a bug report, usernames in file paths, install ids, tokens, email addresses and launch links are replaced, and the preview shows exactly what was taken out.
The IP: line in client.log is Luduvo's server, not your connection, so it stays unless you tick the box. matt explained this on the forum.
The code is public, so anyone can check all of this: github.com/tippythetaidum/duvodoctor.

What "unconfirmed" means

Some advice here came from players rather than staff, and nobody has confirmed it works. Those bits carry an unconfirmed label. Try them if you like, but don't expect miracles.

Credits

Most of what the Doctor knows was worked out by players on the forum. Thank you.

matt: traced the failure to a D3D12 shader; worked out that the AMD driver is what crashes; the Windows debug guide; showing the IP: line is Luduvo’s server
Jediweirdo: the clearest build 44 report; reported it with the full log; the bug report layout the report builder uses
Starte: suggested checking for a newer driver; pointed at the update lock file; suggested the Test-NetConnection check
Evrayne: credited in the build 40 notes for the cache fix; passed on the hosting explanation
tunics: explained the token expiry; worked out why the handler times out
0v3r5e3r: found the fullscreen=0 workaround
1sam: first reported the publish error on build 45
666: the thread that got crash.log added
alaz: showed switching the API can help
AntE: suggested the Vulkan Runtime
Box: said it cleared after about an hour
dan: reported it
delvern: found Luduvo works on Linux on the same PC
eeviika: found it worked on another network
Epik: confirmed the Linux workaround
ferry: reported it with steps
Kitty-kitkat: credited in the build 44 notes for the fallback fix
Milk: worked out the VPN link
PlushPersik: confirmed the fix works
radio: warned against DLL download sites
rek: posted screenshots of the Studio and website errors
Roxubo: showed what happens with the override on
silo: reported it; credited in the build 44 notes
skrubbed: found the Bandicam file was the cause
Wind: noticed it happens on their own game
zxenowc: confirmed it

Staff replies quoted here:

Isaac: 24 Sep 2026, 23 Sep 2026, 23 Sep 2026, 13 Sep 2026, 25 Sep 2026, 25 Sep 2026
Nikhil: 14 Sep 2026, 14 Sep 2026, 14 Sep 2026, 14 Sep 2026, 14 Sep 2026, 14 Sep 2026, 14 Sep 2026, 14 Sep 2026
IgorAlexey: 11 Jun 2026, 14 Sep 2026, 15 Sep 2026

Seen an error it doesn't know?

Use the report builder on the Doctor page, then either post it in the forum's Bug Reports section or open an issue on GitHub with the redacted excerpt. Each known issue is one entry in a data file, so adding one takes a few minutes and no code. The contributing guide explains how.

Changelog

26 Sep 2026: New look

A new doctor, built from the same blocky shapes as a Luduvo avatar: white coat, red scrubs, stethoscope and a head mirror. Luduvo doesn't sell doctor clothes, so I drew one. His head is the new logo.
Status tags are square now, and the colours are our own instead of stock ones.
The front page is shorter. The how-it-works box repeated what was already above it, so it's gone.
In the log view, errors that only follow on from a problem it recognised are greyed out, so they don't look like extra problems.
On phones, the menu fits on one row now.

26 Sep 2026: Plainer words

I went through every page as if I'd never heard of Vulkan. There are fewer tech words, the log folder is on the front page with a copy button, and the paste box looks like something you can press.
Statuses now say "Not fixed yet" and "Has a workaround" instead of Open and Workaround.
What your PC needs starts with a short version. The Vulkan feature list is tucked away for the technically minded.
The sidebar shows the newest Luduvo build, and the site says so if a build comes out before I've checked the known issues against it.

26 Sep 2026: Build 45

Build 45 came out today with no release notes. It starts Windows PCs on D3D12 without trying Vulkan, and the D3D12 startup failure is now hitting NVIDIA, AMD and Intel cards. I've added the five build 45 logs players posted today and updated that issue.
Build 45 changed the first line of client.log, so the Doctor was losing the build number. It reads both layouts now.
New issue: publishing from Studio fails with "scene check failed" since the update.
Every status is now checked against build 45.

26 Sep 2026: First version

Reads client.log, crash.log, launcher.log, app.log, studio.log, state.json and Settings.cfg in your browser.
Knows 35 issues from forum reports and staff replies, checked against build 44. Build 45 hasn't shipped yet, so every status is as of 44.
Tested against 50 real logs, 44 from the forum and 6 of my own, plus a few nasty made-up ones.