What causes a dynamic object ignoring baked GI in Godot?

LightmapGI only feeds dynamic objects when they are set to GI Mode Dynamic and the LightmapGI is configured to capture dynamic-object lighting, so a default mesh gets no baked bounce while moving.

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 a Dynamic Object Ignoring Baked GI Because of GI Mode in Godot

Quick answer: Set the moving mesh's GI Mode to Dynamic, enable the LightmapGI's dynamic-object capture (Use Texture for Bounces / interior capture), and rebake.

In Godot, static meshes get baked lightmaps but moving meshes need GI Mode Dynamic to read the bake's captured probe data. Setting that mode and enabling dynamic capture lights moving objects from the bake.

How to fix it

1. Set GI Mode to Dynamic

On the moving MeshInstance3D, set GI Mode to Dynamic so it samples the LightmapGI's captured probe data instead of being skipped.

2. Enable dynamic capture on LightmapGI

Configure the LightmapGI so it stores the data dynamic objects read (the captured grid for dynamic GI), not only static lightmaps.

3. Place the object inside the baked bounds

Ensure the dynamic object moves within the LightmapGI's captured region; outside the bounds it receives only environment ambient.

4. Rebake the LightmapGI

Re-run Bake Lightmaps after changing GI modes so the dynamic capture data is generated; without a rebake the dynamic mesh still has nothing to sample.

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.