Quick answer: Use KeepWorld if you want the attached child to stay at its current visible position. Use KeepRelative if you want to apply an existing local offset. Use SnapToTarget only if you want the child exactly at the parent’s transform. Typoed socket names fall back silently to the root.

Here is how to fix Unreal AttachActorToComponent wrong transform. You pick up a weapon actor and attach it to your character’s right hand socket. The weapon appears at the character’s feet, or at world origin, or rotated 90 degrees off. You set the weapon’s transform before attaching — no help. The attachment rules in Unreal’s AttachToComponent are three-way decisions that interact non-obviously with socket positions.

The Symptom

After calling AttachToComponent (C++) or Attach Actor To Component (Blueprint), the attached actor’s visible position is wrong:

What Causes This

Attachment rule misunderstanding. Three options per component (Location, Rotation, Scale):

Choosing “SnapToTarget” for location when you wanted “KeepWorld” snaps the child into the parent’s pivot — usually not where you want it unless a socket is specified.

Socket name typo or missing. AttachToComponent takes a SocketName parameter. If the socket does not exist on the target (skeletal or static mesh), attachment falls back to the component’s root. Silent misplacement.

Non-uniform scale interaction. A parent component with scale (2, 1, 1) applies that scale to children attached with SnapToTarget. A weapon attached to a zoomed-in character becomes oversized.

Order of operations. Setting transform before attachment with KeepRelative uses that transform as the post-attachment relative. Setting after attachment with KeepWorld recomputes relative based on world position. Understanding order prevents surprises.

The Fix

Step 1: Use the right attachment rules.

// Weapon in character's hand: snap exactly to hand socket
void AWeapon::Equip(AActor* Wearer, FName SocketName)
{
    USkeletalMeshComponent* Mesh = Cast<ACharacter>(Wearer)->GetMesh();
    if (Mesh)
    {
        AttachToComponent(Mesh,
            FAttachmentTransformRules::SnapToTargetNotIncludingScale,
            SocketName);
    }
}

// Pickup item following player: preserve current world position
void APickup::Follow(AActor* Player)
{
    AttachToActor(Player,
        FAttachmentTransformRules::KeepWorldTransform);
}

// Child with existing authored local offset
void AAttachment::AttachWithOffset(USceneComponent* Parent)
{
    AttachToComponent(Parent,
        FAttachmentTransformRules::KeepRelativeTransform);
}

Predefined FAttachmentTransformRules constants save typing: KeepRelativeTransform, KeepWorldTransform, SnapToTargetNotIncludingScale, SnapToTargetIncludingScale.

Step 2: Verify socket names. Open the skeletal mesh asset. In the Skeleton editor, expand the skeleton tree and check sockets. Socket names are case-sensitive.

Test with a Blueprint breakpoint or log the result:

bool bSuccess = AttachToComponent(Mesh,
    FAttachmentTransformRules::SnapToTargetNotIncludingScale,
    TEXT("RightHandSocket"));

// Verify with:
FVector SocketPos = Mesh->GetSocketLocation(TEXT("RightHandSocket"));
UE_LOG(LogTemp, Log, TEXT("Socket at: %s, Actor at: %s"),
    *SocketPos.ToString(), *GetActorLocation().ToString());

If the socket location and actor location match, attachment worked. If they diverge, the socket name is wrong or the attachment rule snapped elsewhere.

Step 3: Choose SnapToTargetIncludingScale carefully. Use NotIncludingScale if your child has authored scale you want to preserve (a weapon at scale 1 should stay at scale 1 even if the hand socket has non-unit scale). Use IncludingScale for snap-exactly-to-parent behavior, including any zoom.

Step 4: Detach with matching rules. When detaching, use similarly symmetric rules:

void AWeapon::Drop()
{
    DetachFromActor(FDetachmentTransformRules::KeepWorldTransform);
    // Weapon now sits at its visible world location
}

KeepWorldTransform on detach keeps the weapon in place visually. KeepRelativeTransform would revert to whatever local transform it had before attachment, which is rarely what you want.

Blueprint Equivalents

In Blueprint, Attach Actor To Component node has three dropdowns (Location/Rotation/Scale Rule) with the same three options each. Set based on the patterns above.

Common Gotcha: Instigator Transform

When spawning an actor and immediately attaching, the SpawnActor’s transform is ignored if you then SnapToTarget. Use KeepWorld if you want the spawn position to be the attached position:

AActor* Spawned = GetWorld()->SpawnActor<AActor>(Class, SpawnTransform);
Spawned->AttachToActor(Parent, FAttachmentTransformRules::KeepWorldTransform);
// Spawned stays at SpawnTransform, parent tracks it

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

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

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

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.

“Attachment rules are a three-way choice times three axes. Pick intentionally, use the predefined constants, and verify with a log.”

Related Issues

For skeletal mesh issues, see Skeletal Mesh Merge Not Combining Materials. For UMG issues, UMG Widget Not Visible covers related Unreal setup gotchas.

KeepWorld for existing-position-is-good. SnapToTarget for snap-to-socket. KeepRelative for authored offset.