Quick answer: Set the Blender install path in Editor Settings, enable .blend import, and trigger a reimport so Godot re-exports the file through Blender on save.

Editing a .blend and seeing no change in Godot means the native Blender import is not running. Godot imports .blend by calling Blender headlessly, so a missing executable path or disabled import setting leaves the scene frozen at its last state.

How to fix it

1. Set the Blender path

In Editor Settings under filesystem/import/blender, set the Blender 3 executable path and enable the importer. Godot needs this to run Blender and convert the .blend on import.

2. Reimport from the FileSystem dock

Select the .blend, open the Import tab, and click Reimport. Confirm it regenerates the scene rather than using a cached version.

3. Use .glb if headless import is unavailable

On CI or constrained machines without Blender, export to .glb from Blender and import that instead, so the pipeline does not depend on a Blender install.

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 bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.