Why does TSoftClassPtr LoadSynchronous return null after cook?

The Blueprint class was not packaged because no hard reference reached it. Soft refs do not force inclusion. Register the class in Asset Manager Primary Asset Types with Has Blueprint Classes = true, or add the directory to Additional Asset Directories To Cook.

How do I async-load a Blueprint class in C++?

Use FStreamableManager::RequestAsyncLoad with the SoftObjectPath. In the callback, call ResolveObject and Cast to UClass. Spawn actors using the loaded UClass. Always check IsValid before spawning to handle failed loads gracefully.

Why does my soft class work in PIE but not in standalone?

PIE uses the editor's asset registry which sees all assets. Standalone packaged builds only ship cooked assets. If your soft class was not registered with Asset Manager and no scene hard-referenced it, the cook excluded it. Add it to Asset Manager Primary Asset Types and rebuild.

Fix: Unreal TSoftClassPtr Async Load Returns Null

Quick answer: Soft class pointers do not force the Blueprint to be cooked. If no hard reference exists, the cook excludes it and runtime loads return null. Register the class type with Asset Manager (set Has Blueprint Classes = true), or add the directory to Additional Asset Directories To Cook.

Here is how to fix Unreal TSoftClassPtr<UMyClass> loads that succeed in PIE but return null in packaged builds. Soft references are designed to allow on-demand loading without ballooning the cook size, but they require explicit Asset Manager registration to ensure the targets ship at all. Without it, your enemy classes, weapon archetypes, or whatever you store as soft refs simply are not in the build.

The Symptom

A TSoftClassPtr field references a Blueprint class. PIE works fine. Packaged build fails to spawn the class — SpawnActor with the loaded UClass returns null, or LoadSynchronous on the soft pointer returns null.

What Causes This

Soft class refs do not create cook dependencies. Same as soft object refs. The cooker only includes assets that are reachable through hard references or registered in Asset Manager.

No Asset Manager entry. Without registering the class type, the cook does not know to scan a directory for matching Blueprint classes.

Has Blueprint Classes flag off. When configuring an Asset Manager primary type, this flag must be true for Blueprint subclasses to be discovered (vs DataAssets which are not classes).

Class compiled but not in any redirector chain. Renaming a Blueprint can break soft refs if redirectors are missing. Open the Asset Audit window to find broken references.

The Fix

Step 1: Register the class in Asset Manager. Open Project Settings → Asset Manager → Primary Asset Types To Scan:

Primary Asset Type:    Enemy
Asset Base Class:      AEnemyBase
Has Blueprint Classes: true
Directories:           [/Game/Enemies]
Cook Rule:             AlwaysCook

This makes the cooker include every Blueprint subclass of AEnemyBase under /Game/Enemies, even if no scene hard-references them.

Step 2: Async load via FStreamableManager.

void USpawnSubsystem::SpawnEnemy(TSoftClassPtr<AEnemyBase> enemyClass, FVector loc)
{
    UAssetManager& AM = UAssetManager::Get();
    FStreamableManager& SM = AM.GetStreamableManager();

    SM.RequestAsyncLoad(enemyClass.ToSoftObjectPath(),
        FStreamableDelegate::CreateLambda([enemyClass, loc, this]()
        {
            UClass* loaded = enemyClass.Get();
            if (loaded)
            {
                GetWorld()->SpawnActor(loaded, &loc);
            }
            else
            {
                UE_LOG(LogTemp, Warning, TEXT("Class not loaded: %s"),
                       *enemyClass.ToString());
            }
        }));
}

Step 3: Verify in the cooked build. After packaging, list the .pak contents:

UnrealPak.exe MyGame-Pak.pak -List | grep Goblin

If your Blueprint does not appear, Asset Manager registration is wrong or the directory does not match.

Step 4: Add fallback handling. If a soft class fails to load (corrupted asset, missing redirector), fail gracefully:

if (UClass* C = enemyClass.Get())
{
    GetWorld()->SpawnActor<AActor>(C, loc, FRotator::ZeroRotator);
}
else
{
    // substitute a default fallback class shipped hard-referenced
    GetWorld()->SpawnActor<AActor>(DefaultEnemyClass, loc, FRotator::ZeroRotator);
}

Step 5: Use TAssetSubclassOf or alias if migrating. Older code uses TAssetSubclassOf; modern UE uses TSoftClassPtr. They are equivalent for cook semantics. Update old code for clarity.

Hard vs Soft Class

Hard class references (TSubclassOf<AEnemyBase>) force the class to be cooked. Use them for archetypes always loaded with the level. Soft class references are for on-demand: large variety of enemies, modular DLC content, runtime-selected variants.

Understanding the issue

AI bugs are emergent. The code is correct in isolation; the behavior emerges from interaction with other systems. Reproducing means controlling the interaction; fixing means deciding which interaction was wrong.

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

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

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.

“Soft refs ship on demand only. Asset Manager fills the gap. Without it, the cook leaves your classes behind.”

Related Issues

For data asset soft refs, see Data Asset Soft Ref Null. For multicast RPC issues, see Multicast RPC.

Has Blueprint Classes = true. Directory listed. Cook rule AlwaysCook. The class survives the cook.