Why does my TSoftObjectPtr return null in a packaged Unreal build?

Soft references do not force the target asset to be cooked. If no hard reference exists and the asset is not registered with the Asset Manager, the cooker excludes it. Either add the path to Project Settings > Packaging > Additional Asset Directories To Cook, or register the asset type with the Asset Manager.

How do I add data assets to the Asset Manager?

Open Project Settings > Asset Manager > Primary Asset Types To Scan. Add a new type with your DataAsset class as the Asset Base Class and the directory containing your assets as the Directory. The Asset Manager scans this directory at startup and includes all matching assets in the cook.

Why does LoadSynchronous on a soft pointer block the game thread?

LoadSynchronous reads the asset and any dependencies from disk on the calling thread. For a single small asset it is acceptable; for chains of references it can hitch. Prefer FStreamableManager::RequestAsyncLoad with a callback for non-blocking loads.

Fix: Unreal Data Asset Soft Reference Null After Cook

Quick answer: Soft references (TSoftObjectPtr) do not force the target asset to be cooked. Either register the data asset type with the Asset Manager (Project Settings → Asset Manager) or add the directory to Additional Asset Directories To Cook. Without one of these, soft refs to uncooked assets resolve to null in builds.

Here is how to fix Unreal soft references and data assets that resolve to null in shipping builds even though the editor sees them fine. You design abilities or item definitions as DataAssets, store them in DataTables or as TSoftObjectPtr arrays, and the cooker silently excludes them. Players see no enemies, no pickups, no abilities — only fail-fast nullptr crashes.

The Symptom

A TSoftObjectPtr<UAbilityDataAsset> works in PIE. After packaging, the pointer’s LoadSynchronous returns null. The cook log shows the asset is not in the package. Hard-coding a hard reference fixes the issue but is impractical for hundreds of assets.

What Causes This

Soft refs do not create cook dependencies. By design. Otherwise the cooker would pull every potentially referenced asset, defeating the point of soft refs.

No hard reference and no Asset Manager registration. Without either, the asset is not in any cooker reachability path. The cooker excludes it from the build.

DataTable references are sometimes also soft. FDataTableRowHandle stores a soft reference to the table. If only the table itself is hard-referenced but the rows reference assets via soft pointers, those assets may be missed.

Editor-only references. Asset references created in editor utility widgets do not survive packaging.

The Fix

Step 1: Register the data asset type with Asset Manager.

Open Project Settings → Game → Asset Manager. Under Primary Asset Types To Scan, add a new entry:

Primary Asset Type:    Ability
Asset Base Class:      UAbilityDataAsset
Directories:           [/Game/Abilities]
Has Blueprint Classes: false
Is Editor Only:        false
Cook Rule:             AlwaysCook

This makes the Asset Manager scan the directory at startup and pull in every matching asset. The cooker honors this list.

Step 2: Use Asset Manager APIs to query.

void UMySubsystem::LoadAllAbilities()
{
    UAssetManager& AM = UAssetManager::Get();
    TArray<FAssetData> assets;
    AM.GetPrimaryAssetDataList(FPrimaryAssetType("Ability"), assets);

    for (const FAssetData& data : assets)
    {
        if (UAbilityDataAsset* a = Cast<UAbilityDataAsset>(data.GetAsset()))
        {
            AllAbilities.Add(a);
        }
    }
}

Step 3: Or add to Additional Asset Directories To Cook. If you do not want to use Asset Manager, open Project Settings → Packaging and add directories to Additional Asset Directories To Cook. Everything inside is cooked unconditionally.

Step 4: Async load with FStreamableManager.

void AItem::EquipAsync(TSoftObjectPtr<UItemDefinition> itemSoft)
{
    UAssetManager& AM = UAssetManager::Get();
    FStreamableManager& SM = AM.GetStreamableManager();

    SM.RequestAsyncLoad(itemSoft.ToSoftObjectPath(),
        FStreamableDelegate::CreateUObject(this, &AItem::OnItemLoaded, itemSoft));
}

void AItem::OnItemLoaded(TSoftObjectPtr<UItemDefinition> itemSoft)
{
    if (UItemDefinition* def = itemSoft.Get())
    {
        ApplyDefinition(def);
    }
}

Step 5: Verify the cook. After packaging, open the build folder and look at the .pak content list:

UnrealPak.exe MyGame-Pak.pak -List

Search for your asset name. If absent, registration or directory inclusion is still wrong.

Hard vs Soft Reference Cheat Sheet

// Hard - always cooked, always loaded with owner
UPROPERTY(EditAnywhere)
UItemDefinition* HardItem;

// Soft - cooked only if reachable through Asset Manager or hard ref chain
UPROPERTY(EditAnywhere)
TSoftObjectPtr<UItemDefinition> SoftItem;

// Soft class - same rules but for UClass references
UPROPERTY(EditAnywhere)
TSoftClassPtr<UItemDefinition> SoftClass;

Use hard for small assets always loaded with the owner. Use soft for large content (textures, meshes) you load on demand. Always pair soft refs with Asset Manager registration when the data is not also referenced by something else hard.

Understanding the issue

Asset pipelines transform source content into runtime data. Each stage can lose information, change behavior, or introduce platform-specific variations. Bugs at this layer are often invisible until the cooked build runs.

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

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

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

“Soft refs save memory but break cook reachability. Asset Manager fills the gap. Without it, the cooker leaves your data behind.”

Related Issues

For DataAsset save issues, see Data Asset Changes Not Saving. For Niagara cook issues, see Niagara Not Rendering.

Asset Manager primary type. Or Additional Directories To Cook. Either way the cooker keeps the file.