UE4: Guidebook
Search…
4.24
Iterators
Object & Actor Iterators, Optional Class Scope For Faster Search
Overview
Dear Community,
In the UE4 engine two of the most powerful tools I use constantly are the Object and the Actor Iterators.
You can use these functions to search for all Run-Time instances of actors and objects, or only specific classes!
The advantage of using the UE4 iterators is that they are always accurate!
You dont have to maintain dynamic arrays of actors, and then remember to remove actors when they are destroyed!
The Actor and Object Iterators always give you the real and accurate list of all actors / objects currently still active in your game world
Yay!
Include
#include "EngineUtils.h"
Controller Class
You dont have to use these functions in the Controller Class,
I was just doing this for the sake of ClientMessage and easy testing on your part :)
Object Iterator
1
void AYourControllerClass::PrintAllObjectsNamesAndClasses()
2
{
3
for ( TObjectIterator<UObject> Itr; Itr; ++Itr )
4
{
5
ClientMessage(Itr->GetName());
6
ClientMessage(Itr->GetClass()->GetDesc());
7
}
8
}
Copied!
Actor Iterator
1
void AYourControllerClass::PrintAllActorsLocations()
2
{
3
//EngineUtils.h
4
for (TActorIterator<AActor> ActorItr(GetWorld()); ActorItr; ++ActorItr )
5
{
6
ClientMessage(ActorItr->GetName());
7
ClientMessage(ActorItr->GetActorLocation().ToString());
8
}
9
}
Copied!
Object Iterator & Actor Iterator Comparison
Disadvantage of Object Iterator
Unlike the Actor Iterator, the Object iterator is going to iterate over objects in the Pre-PIE world / the Editor World.
This can lead to unexpected results.
This is not an issue if you are running your game as an independent Game Instance / the editor is closed :)
Critical Advantage of Object Iterator
A critically important advantage of the Object Iterator is that it does not require a UWorld* Context!
Notice how all the uses of Actor Iterator involve GetWorld()
1
TActorIterator ActorItr<AStaticMeshActor>(GetWorld());
Copied!
If you need to find an object in the game world from a static context, where you cannot obtain the UWorld via some other means,
then the Object Iterator is the way to get the proper context and access the entire living game world!
Object Iterator Can Search for AActors
Because AActor extends UObject, the Object Iterator can search for AActors!
But the AActor Iterator cannot search for instances of UObjects that do not extend AActor at some point.
So the Object Iterator can do a search for all UStaticMeshComponents, as well as all ACharacters!
1
TObjectIterator<UStaticMeshComponent> Itr;
Copied!
1
TObjectIterator<ACharacter> Itr;
Copied!
Specifying Classes & Subclasses To Search For
Perhaps the most powerful feature of the Actor and Object Iterators is the ability to limit the scope of the search to a chosen base class and its subclasses!
This makes the iterator run faster and helps you gather only the data you really want from the game world!
Object Iterator, Specific Base Class
1
void AYourControllerClass::PrintAllSkeletalMeshComponentsNames()
2
{
3
for ( TObjectIterator<USkeletalMeshComponent> Itr; Itr; ++Itr )
4
{
5
ClientMessage(Itr->GetName());
6
}
7
}
Copied!
Actor Iterator, Specific Base Class
1
void AYourControllerClass::PrintAllStaticMeshActorsLocations()
2
{
3
//EngineUtils.h
4
for (TActorIterator<AStaticMeshActor> ActorItr(GetWorld()); ActorItr; ++ActorItr)
5
{
6
ClientMessage(ActorItr->GetName());
7
ClientMessage(ActorItr->GetActorLocation().ToString());
8
}
9
}
Copied!
Using a World-Filter with ObjectIterator
ObjectIterator can and will return editor-instance / default object objects that simply should not be edited at runtime!
To filter out objects that you should not be editing at runtime, you can do a world check with an object that you know is part of the correct world (not the editor world)!
1
UWorld* YourGameWorld = //set this somehow, from another UObject or pass it in as parameter
2
​
3
for(TObjectIterator<UYourObject> Itr; Itr; ++Itr)
4
{
5
//World Check
6
if(Itr->GetWorld() != YourGameWorld)
7
{
8
continue;
9
}
10
//now do stuff
11
}
Copied!
In-Engine Example ~ Get All Widgets Of Class
The above is the code structure that I used for my Get All Widgets of Class node, pull request that Epic accepted that is now live in 4.7 !
Github Link
I avoid getting the UMG widget default objects /editor objects by passing in the world using the Blueprint method of setting a WorldContextObject!
Enjoy!
Authors
Original author: Rama <3
Ported from wiki by Firefly74940
Previous
Interfaces in C++
Next
String Conversions: FString to FName, FString to Int32, Float to FString
Last modified 1yr ago