Quick answer: Recreate or resize the swap-chain on the same frame you apply the setting instead of waiting for an OS resize message, and flush a present before reading back the new size.

Players pick 1080p, click Apply, and nothing happens until they alt-tab out and back. The render target was updated but the swap-chain was only rebuilt on the focus-driven resize. Drive the resize yourself when the setting changes.

How to fix it

1. Resize on apply

Call the swap-chain resize directly in your Apply handler rather than relying on the windowing system's resize callback. Tie the back-buffer and viewport update to that one code path.

2. Avoid double sources of truth

If both your Apply code and the OS resize callback set the buffer size, they can race. Make the callback re-read the window size and reconcile, not fight, the explicit change.

3. Present once after

Issue a present (or one render tick) immediately after the resize so the new dimensions are live before the next input frame reads them.

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 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.