Fix: Godot 4 3D CSG Mesh Build Frozen in Editor

CSG is great for blocking out levels until it isn’t. Add the 25th cylinder window to a wall and the editor stops responding for 5 seconds on every move. Conversion to ArrayMesh is the long-term answer; structuring CSG into smaller trees is the short-term one.

The Symptom

Editor stalls or freezes for seconds after each CSG edit. Saving the scene takes long. Closing the scene cleans up but reopening is slow.

What Causes This

CSG (Constructive Solid Geometry) operates by performing boolean operations between meshes. Every property change — transform, parameter, child add/remove — triggers a full rebuild of the affected subtree. Cost grows with the number of operations and the polygon count of each.

The Fix

Step 1: Convert finalized regions. Once a CSG sub-region is final (you’re not iterating on it):

1. Select the root CSGCombiner or CSG primitive.
2. 3D viewport menu (top of viewport) → Mesh → Convert → ArrayMesh.
3. The node becomes a MeshInstance3D with the baked geometry. The CSG tree is gone.

Editor performance returns to normal for that region. You lose the ability to non-destructively edit the boolean operations — that’s the trade-off.

Step 2: Disable Use Collision while sketching. CSG nodes have Use Collision = true by default, which adds a collision generation step on top of the visual rebuild. Turn off while you’re iterating; turn on at conversion time.

Step 3: Split into small trees. A “wall with windows” can be one CSGCombiner3D. The whole building should be many CSGCombiners (one per wall, one per ceiling), each with maybe 20 children. Editing one tree only rebuilds that tree.

Runtime CSG

If your game uses runtime CSG (destructible terrain, procedural geometry), you can’t pre-convert. Limit live CSG trees to small areas and rely on caching. set_use_collision(true) only after the geometry is final — constant collision regeneration is expensive.

The Right Tool for Final Levels

For shipped game levels, do the rough block-out in CSG, then export the geometry to Blender (use the addon or just convert and export glTF), refine, re-import as a regular MeshInstance3D. Your finished level isn’t paying CSG rebuild cost ever again.

Verifying

Open the .tscn file. Count CSG-prefixed nodes. If it’s in the hundreds, conversion to ArrayMesh would speed every operation in the editor. After conversion, the equivalent ArrayMesh nodes are simple MeshInstance3D with embedded data — faster to load, faster to edit.

Understanding the issue

Build configurations multiply: debug vs release, per-platform, per-store. Each combination is a separate code path, and each is a separate place for bugs to live.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Convert when done. Smaller trees while iterating. CSG for sketches, ArrayMesh for ship.”

Related Issues

For Godot CSG to static, see CSG mesh collision. For editor performance, see editor slow scenes.

Convert. Split. The editor breathes.