Quick answer: Set the window stretch mode to canvas_items with a base resolution and an expand aspect, and apply a content scale factor so UI scales up on dense displays.
On a 4K monitor the menus and HUD become a small island in the corner. The stretch mode left UI at base pixels. Configure canvas_items stretch with a content scale factor.
How to fix it
1. Set the stretch mode
In Project Settings > Display > Window, set Stretch Mode to canvas_items with a base viewport size, so the UI scales to the actual window resolution.
2. Choose an aspect policy
Use the expand or keep aspect option so the layout adapts to different shapes instead of stretching or pillarboxing the whole UI.
3. Apply a content scale factor
Set content_scale_factor (or DisplayServer scale) for high-DPI so fonts and controls render larger and stay readable on dense panels.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.