What causes a UI layout not rescaling after a resolution change?

Your UI computed its anchors and font sizes once at startup and never recomputed them when the viewport size changed, so it stays pinned to the old resolution.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix UI That Stays the Wrong Size After Changing Resolution Mid-Game

Quick answer: Hook the resize/size-changed signal and force a layout pass, and base sizes on viewport-relative units rather than absolute pixels captured at load.

Switch from 1080p to 4K in the options menu and the HUD shrinks into a corner or buttons overlap. The layout cached old dimensions. Recompute it whenever the viewport size changes.

How to fix it

1. Listen for the resize

Connect to the viewport size_changed signal (or the engine's equivalent) and re-run your layout logic when it fires, not only at startup.

2. Use relative anchoring

Anchor controls with percentage-based anchors and stretch settings so the engine reflows them automatically instead of you positioning by absolute pixels.

3. Refresh dynamic fonts

Font atlases and dynamic font sizes derived from screen height must be recomputed on resize, or text will look tiny or huge at the new resolution.

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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.