Quick answer: Set the Camera3D Keep Aspect to Keep Height (or Keep Width) to match your design intent and configure the project stretch mode so resizing does not distort geometry.

If resizing your Godot window squashes or stretches the 3D view, the keep-aspect setting is wrong. Matching it to your stretch mode fixes it. Here is how.

How to fix it

1. Pick the right Keep Aspect

On the Camera3D set keep_aspect to Keep Height if FOV is the vertical angle you tuned, or Keep Width if you designed around horizontal extent.

2. Set the project stretch mode

In Project Settings under Display > Window, choose a Stretch Mode (canvas_items or viewport) and Aspect (keep, expand) consistent with the camera's keep mode.

3. Test extreme aspects

Resize to very wide and very tall windows to confirm the view reveals or hides extra scene gracefully instead of stretching the rendered image.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.