Fix: Unreal Async Load Asset Returns Null in Shipping

Your inventory system loads item icons by soft path string at runtime — FSoftObjectPath(“/Game/Items/Icons/IconSword.IconSword”). It works in PIE. The shipping build returns null for every load. Player inventories render as missing-icon placeholders.

Why Cooking Excludes Dynamic References

The cooker walks the dependency graph from a set of roots (maps in the build, asset manager primary assets, anything in Always-Cook directories) and includes only what it discovers. A soft path constructed at runtime from a string has no compile-time presence in any referencing asset; the cooker doesn’t see it and doesn’t include the target.

In PIE, the editor loads from the uncooked content tree, so missing “cook” coverage is invisible. Only the packaged build exposes the problem.

Fix 1: Asset Manager Primary Asset Type

Define a category for the dynamically-loaded assets:

1. Open Project Settings → Game → Asset Manager.
2. Add a Primary Asset Type:
   • Primary Asset Type: Icon
   • Asset Base Class: Texture2D (or your custom DataAsset)
   • Directories: /Game/Items/Icons
   • Rules → Cook Rule: Always Cook
3. Save and re-cook.

At runtime, request the asset through the Asset Manager:

auto& AM = UAssetManager::Get();
FPrimaryAssetId Id("Icon", "IconSword");
AM.LoadPrimaryAsset(Id, {}, FStreamableDelegate::CreateUObject(this, &ThisClass::OnLoaded));

The Asset Manager handles streaming, refcounting, and unload — better than raw FStreamableManager for content libraries.

Fix 2: Always Cook Directory

Quicker if you don’t want the full Asset Manager treatment:

// DefaultGame.ini
[/Script/UnrealEd.ProjectPackagingSettings]
+DirectoriesToAlwaysCook=(Path="/Game/Items/Icons")

The directory is included unconditionally. Loads still happen through your existing soft-path code path; nothing else changes. The downside is no streaming intelligence — assets are in the .pak whether anyone references them or not.

Fix 3: Soft Object Reference UPROPERTY

If you have a finite set of dynamic assets, declare them as soft references on a config or data asset:

UCLASS(Blueprintable)
class UIconLibrary : public UDataAsset
{
    GENERATED_BODY()
public:
    UPROPERTY(EditAnywhere)
    TMap<FName, TSoftObjectPtr<UTexture2D>> Icons;
};

Populate in the editor by dragging icons into the map. The soft references are visible to the cooker (via the DataAsset reference chain) and get included. Load at runtime by name:

auto IconRef = Library->Icons.FindRef("Sword");
StreamableManager.RequestAsyncLoad(IconRef.ToSoftObjectPath(), Callback);

Diagnosing in a Build

Run with -log to capture the Output Log. Look for “LogStreaming: Async loading from a string path” followed by “Asset doesn’t exist”. The path is your culprit. Search the cooked content folder (Saved/Cooked/PLATFORM/Project/Content/...) for a .uasset matching the name; if it’s missing, the cooker skipped it.

For a definitive list of what got cooked:

# Linux/macOS terminal:
find Saved/Cooked -name "*.uasset" | grep -i Icon

Verifying

After applying one of the fixes, rebuild the package. Confirm via find or the .pak inspection that your assets are present. Run on target and observe the icons load. Output Log should show successful streaming with no “couldn’t find” warnings.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

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

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

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.

“PIE finds anything. Shipping finds what you cooked. Tell the cooker what to cook.”

Asset Manager looks heavy at first but pays off the moment you have more than a few dynamic asset types.