# ActorComponents registered with wrong world from UWorldPartition::ApplyRuntimeCellsTransformerStack 

**URL:** <https://forums.unrealengine.com/t/actorcomponents-registered-with-wrong-world-from-uworldpartition-applyruntimecellstransformerstack/2692632>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [December 16, 2025, 12:11pm UTC](https://forums.unrealengine.com/t/actorcomponents-registered-with-wrong-world-from-uworldpartition-applyruntimecellstransformerstack/2692632 "2025-12-16T12:11:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [December 16, 2025, 12:11pm UTC](https://forums.unrealengine.com/t/actorcomponents-registered-with-wrong-world-from-uworldpartition-applyruntimecellstransformerstack/2692632/1 "2025-12-16T12:11:57Z")

</div>

There is a risk of actor components registering with the wrong world when reconstructed from UWorldPartition::ApplyRuntimeCellsTransformerStack. The repro case is arguably a bad usage, but it was the easiest way I found to showcase the issue.

Components registered during the construction phase can have the temporal world assigned and cached. I believe this is not an issue in most cases, but I think it is something worth flagging as it might be the only (and a new case) where the actors are constructed with a temporal world, and it could cause hard to find issues.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [December 16, 2025, 12:12pm UTC](https://forums.unrealengine.com/t/actorcomponents-registered-with-wrong-world-from-uworldpartition-applyruntimecellstransformerstack/2692632/2 "2025-12-16T12:12:01Z")

</div>

**Steps to Reproduce**

- In the ThirdPersonCharacter project, create a default open world level and add a UWorldPartitionRuntimeCellTransformerISM to the stack
- In C++, create an actor with the following code

```auto
AMyActor::AMyActor()
{
    RootComponent = CreateDefaultSubobject<USceneComponent>(TEXT("Root"));
}

// Called when the game starts or when spawned
void AMyActor::BeginPlay()
{
    Super::BeginPlay();
    ensureAlways(IsValid(RootComponent->GetWorld()->GetGameInstance()));
}

void AMyActor::OnConstruction(const FTransform& Transform)
{
    Super::OnConstruction(Transform);
    MySceneComponent = NewObject<USceneComponent>(this);
    AddInstanceComponent(MySceneComponent);
    RegisterAllComponents();
}

```

- See ensure trigger  
[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![RyanBickell](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@RyanBickell](https://forums.unrealengine.com/u/RyanBickell)\
**Post date:** [December 17, 2025, 1:00pm UTC](https://forums.unrealengine.com/t/actorcomponents-registered-with-wrong-world-from-uworldpartition-applyruntimecellstransformerstack/2692632/3 "2025-12-17T13:00:56Z")

</div>

Hi,

I created a JIRA for this issue, which can be tracked here: [https://issues.unrealengine.com/issue/UE-358403](https://issues.unrealengine.com/issue/UE-358403). I don’t have an ETA, as priorities for bugs and features can shift at any time.

Thanks,

Ryan

[Attachment Removed]
