Fix: Unreal MetaSound Not Playing in Packaged Build

Here is how to fix Unreal MetaSound not playing in packaged build. You build an adaptive music system or procedural SFX generator using MetaSounds. In PIE, everything sounds perfect — layered audio, parameter-driven synthesis, reactive music. You package the game, launch it, and hear silence. No audio plays from any MetaSound source. Legacy SoundCue assets still work. Only MetaSounds are affected.

The Symptom

MetaSound assets play correctly in Play In Editor mode but produce no audio in Development or Shipping packaged builds. The game runs without errors, gameplay works, but MetaSound-driven audio is completely silent. SoundCue and SoundWave assets may still work normally.

What Causes This

MetaSound asset not cooked. PIE has access to all project assets regardless of references. Packaged builds only include assets reachable through the cook dependency graph (hard references from maps, Blueprints, or data assets). If your MetaSound is only referenced via soft pointers or loaded by string path, the cooker may skip it.

Referenced wave files not cooked. A MetaSound graph references SoundWave assets as inputs. If those wave files are in a directory not scanned by the cooker and have no other hard references, they are excluded. The MetaSound cooks but its audio sources are missing.

MetaSound module not linked in C++. C++ projects that interact with MetaSound programmatically need MetasoundEngine in their module dependencies. Without it, MetaSound runtime initialization may be incomplete in packaged builds even though the editor initializes it automatically.

Audio Component not using correct sound class. If you assign a MetaSound to a UAudioComponent via SetSound at runtime with a soft reference that has not loaded, the component plays nothing. Unlike SoundCues, MetaSounds loaded async may not be ready when Play is called.

Platform audio format mismatch. MetaSound wave table inputs may reference formats not supported on the target platform. The cooker converts them, but if conversion fails, the cooked MetaSound has silent inputs.

The Fix

Step 1: Add MetaSound directories to Always Cook.

// In DefaultGame.ini:
[/Script/UnrealEd.ProjectPackagingSettings]
+DirectoriesToAlwaysCook=(Path="/Game/Audio/MetaSounds")
+DirectoriesToAlwaysCook=(Path="/Game/Audio/Waves")

This ensures all MetaSound assets and their source wave files are included in the cook regardless of reference chains.

Step 2: Use hard references for critical audio.

// Hard reference ensures cooking:
UPROPERTY(EditDefaultsOnly, Category = "Audio")
USoundBase* FootstepSound;  // Assign MetaSound in Blueprint defaults

// Avoid soft references for audio that must play immediately:
// TSoftObjectPtr<USoundBase> - may not be loaded when needed

// Playing with hard reference:
UGameplayStatics::PlaySoundAtLocation(
    this, FootstepSound, GetActorLocation());

Hard UPROPERTY references in Blueprints or C++ classes that exist in cooked maps automatically include the MetaSound in the cook.

Step 3: Add module dependencies in Build.cs.

// YourProject.Build.cs
PublicDependencyModuleNames.AddRange(new string[]
{
    "Core",
    "CoreUObject",
    "Engine",
    "MetasoundEngine",      // Required for MetaSound runtime
    "MetasoundFrontend",    // Required for parameter interfaces
    "AudioExtensions"
});

Without these modules, MetaSound graph execution may silently fail in packaged builds. The editor includes them implicitly but packaged games do not.

Step 4: Ensure async loading completes before playback.

// If using soft references, load before playing:
TSoftObjectPtr<USoundBase> MetaSoundRef;

void AMyActor::PlayMetaSound()
{
    if (!MetaSoundRef.IsValid())
    {
        // Request synchronous load
        MetaSoundRef.LoadSynchronous();
    }

    if (USoundBase* Sound = MetaSoundRef.Get())
    {
        AudioComponent->SetSound(Sound);
        AudioComponent->Play();
    }
}

Verifying Cook Output

After packaging, check the cook log for MetaSound assets. Search for “LogCook” entries mentioning your MetaSound paths. Missing assets show as warnings or are absent from the cooked asset registry. Use -log launch parameter to see runtime asset loading:

// Launch with logging:
// MyGame.exe -log
// Search output for: LogAudio, LogMetaSound
// Missing assets show: "Failed to find MetaSound asset"

Understanding the issue

Build pipelines transform development assets into shipping packages. Each transformation can introduce subtle changes: compression, stripping, format conversion, code generation. A bug that only appears in the cooked build is usually one of these transformations doing something the author didn't expect.

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

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

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unreal-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 Unreal, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“PIE lies about asset availability. It loads everything. Packaged builds only load what the cooker included. Hard references or explicit cook paths are the only guarantees.”

Related Issues

For level content not loading in packaged builds, see Level Instance Not Loading. For GameplayCue audio not firing on clients, see GameplayCue Not Firing on Client.

Always Cook directory, hard references, MetasoundEngine module, sync load before play. Audio ships correctly.