Fix: Unity UI TextMeshPro Falling Back to Default Font

A UI mockup uses a custom display font. In Unity TextMeshPro renders LiberationSans everywhere — the default packaged with TMP. Dragging your TTF into the Font Asset slot doesn’t work; TMP wants a Font Asset, not raw TTF.

TTF vs TMP_FontAsset

The legacy UI Text component accepts a TTF directly. TextMeshPro doesn’t. TMP needs:

1. A baked atlas containing every glyph you’ll display.
2. Distance field information for the SDF rendering technique.
3. Kerning tables and per-glyph metadata.

The TMP_FontAsset is a precomputed resource holding all of this.

Generate the Font Asset

1. Import your TTF/OTF into the project (Assets/Fonts/).
2. Open Window → TextMeshPro → Font Asset Creator.
3. Set Source Font File to your TTF.
4. Sampling Point Size: 90 (good balance of quality vs atlas size).
5. Padding: 5 (for SDF spread).
6. Character Set: choose ASCII for English-only, or Unicode Range Hex with a wider range for international.
7. Click Generate Font Atlas, then Save.

You get a .asset file. Drag it into the Font Asset slot on your TextMeshProUGUI component.

Set the Default for the Project

In Project Settings → TextMesh Pro → Settings, set Default Font Asset to your generated asset. New TextMeshProUGUI components default to this.

Fallback Fonts for Multilingual Support

If you support English + Japanese, generate one asset per script. On the main asset:

1. Inspector → Fallback Font Assets.
2. Add Element.
3. Drag the Japanese asset in.

When TMP encounters a glyph not in the main atlas, it cascades through fallbacks. The user-visible text mixes scripts seamlessly.

Dynamic SDF Atlas

For user-generated content where you can’t pre-bake every glyph, set Atlas Population Mode = Dynamic. Glyphs are baked on-demand at runtime. Costs more first-render time per new glyph; eliminates “missing glyph box” for unexpected characters.

Verifying

Run the scene. Text should render in your custom font. Inspector on a TMP component should show your asset in the Font Asset slot (not LiberationSans). Switch language at runtime — fallback glyphs should appear in their correct script font, not as missing-character boxes.

Understanding the issue

UI frameworks have their own lifecycle (mount, update, unmount). When game state changes faster than the UI can respond, you get either stale displays or visible flicker.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“TMP doesn’t accept raw TTFs. Generate a Font Asset, then assign it. Two minutes the first time, saves the ‘why LiberationSans’ surprise.”

Use Dynamic Atlas mode for fonts with hundreds of glyphs (CJK) — pre-baking everything bloats memory unnecessarily.