Fix: Unity Mesh.CombineMeshes Vertex Stream Mismatch

CombineMeshes works for one batch and fails for another with “has different vertex layouts.” Some imported meshes have tangents, others don’t; some have color, others UV1. The combiner needs them all to look identical.

The Symptom

CombineMeshes throws or silently produces an empty mesh. Console message about layout, vertex count exceeded, or index format. Affected meshes look fine individually.

What Causes This

Mesh.SetVertexBufferParams declares which streams a mesh has. CombineMeshes requires matching layouts because the output is a single buffer with one consistent layout. Mismatched inputs can’t be packed together without padding the smaller layout up.

The Fix

Step 1: Group by layout, combine within group.

var groups = sources.GroupBy(m => VertexLayoutKey(m));
foreach (var g in groups)
{
    var combine = g.Select(m => new CombineInstance { mesh = m, transform = Matrix4x4.identity }).ToArray();
    var result = new Mesh { indexFormat = IndexFormat.UInt32 };
    result.CombineMeshes(combine, mergeSubMeshes: true, useMatrices: false);
}

string VertexLayoutKey(Mesh m)
{
    return $"{m.vertexBufferCount}|{(int)m.GetVertexAttributes()[0].format}|{m.HasVertexAttribute(VertexAttribute.Color)}|{m.HasVertexAttribute(VertexAttribute.Tangent)}|{m.HasVertexAttribute(VertexAttribute.TexCoord1)}";
}

Step 2: Or normalize all to one layout. Pre-process every input to have the union of streams, zero-fill missing ones:

void EnsureColors(Mesh m)
{
    if (!m.HasVertexAttribute(VertexAttribute.Color))
        m.colors = Enumerable.Repeat(Color.white, m.vertexCount).ToArray();
}

Step 3: 32-bit index format for big combines. 16-bit max 65,535 vertices. Above, set:

result.indexFormat = IndexFormat.UInt32;

Memory usage doubles for the index buffer; vertex buffer unchanged.

Combine Then Apply

For runtime mesh combination (procedural levels, batch optimization), call CombineMeshes once at scene load and assign the result to a single MeshFilter. Don’t recombine every frame; it’s slow.

Verifying

Combine; check vertex count and submesh count on the result. Visualize in Scene view; the merged mesh should look identical to the sum of inputs.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. 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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, 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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Match layouts. UInt32 for big combines. Group meshes that pair cleanly.”

Related Issues

For SRP Batcher, see SRP Batcher. For occlusion culling, see occlusion.

Layouts align. Indices grow. Combines succeed.