Course contentsShow
← Unreal Engine Game Development
Lesson 25 of 8801. Foundations and Editor WorkflowFree lesson

Debugging Actor and Component Hierarchies

Utilize the World Outliner and visual debugging tools to inspect and troubleshoot complex component structures during active gameplay sessions.

In this lesson, you will learn how to leverage the World Outliner and visual debugging tools to inspect and troubleshoot complex component structures while your game is running.

As your projects grow, you will often find that an Actor isn't behaving as expected—perhaps a SceneComponent has the wrong transform, or a child component isn't spawning at all. Debugging these relationships in code can be difficult, but Unreal provides powerful "live" inspection tools.

The World Outliner as a Live Debugger

When you press Play in the editor, your World Outliner transitions into "PIE" (Play-In-Editor) mode. By default, it shows the active instances of your Actors. If you click on an Actor in the viewport while the game is running, the Details Panel will show you the exact state of all its components at that specific frame.

If you don't see your components, look at the top-right corner of the Details Panel. You can toggle the "Show Inherited Variables" or filter by component name to quickly isolate a specific part of your hierarchy.

Visualizing Transforms

If you are struggling with a complex hierarchy of nested SceneComponents, you can use the "Visualize" options. By selecting an Actor, you can see the white "gizmo" lines connecting parent components to their children. If an Actor is moving but its child component is staying still, checking this visual hierarchy will immediately reveal if you have forgotten to "Attach" the component to a parent or if the relative transform is incorrectly offset.

Debugging via Console

You can also inspect these hierarchies without clicking. Press the tilde key (~) to open the console and type: ShowDebug Hierarchy

This command overlays text on your screen, listing the Actor you are currently possessing and the entire tree of its attached components. It displays their class names, registration status, and current world locations. This is invaluable when you suspect a component has failed to register during the game's lifecycle.

By combining the Details Panel (for deep inspection of variables) and the ShowDebug command (for structural oversight), you can trace hierarchy bugs in real-time.

Key Takeaway: Use the PIE-mode World Outliner and the ShowDebug Hierarchy console command to inspect component state and parent-child attachment live, saving you hours of hunting through C++ headers.