How to debug Motion with Visual Logger and Rewind Debugger

Use this guide when you need to inspect Motion movement state, GAS state, component registration, or timing problems during gameplay.

Open Visual Logger

Use the console command:

VisLog

Or open Window > Developer Tools > Visual Logger.

Record a session

1. Open Visual Logger.
2. Click the red Record button.
3. Play the scenario you want to inspect.
4. Stop recording.
5. Select the character actor.
6. Scrub the timeline.

Filter by LogMotionVisual when you only want Motion entries.

Track specific attributes

Motion logs general movement state automatically. Add attributes when you need histograms for values such as stamina or walk speed.

UMotionSubsystem* Subsystem = GetLocalPlayer()->GetSubsystem<UMotionSubsystem>();
Subsystem->TrackedAttributes.Add(UMotionAttributeSet::GetStaminaAttribute());
Subsystem->TrackedAttributes.Add(UMotionAttributeSet::GetWalkSpeedAttribute());

Tracked attributes appear as histograms in the Visual Logger graph panel.

Add custom logs

Use Motion subsystem logging helpers for custom Blueprint or C++ debugging:

Subsystem->LogFloat(FName("CustomSpeed"), MyCustomSpeed);
Subsystem->LogText(FName("AI"), TEXT("Started chase behavior"));

Use custom logs for temporary investigation data, not permanent gameplay state.

Use Rewind Debugger

1. Enable Rewind Debugger in Edit > Editor Preferences > Rewind Debugger.
2. Record gameplay with Visual Logger.
3. Open the Rewind Debugger panel.
4. Scrub through the timeline.
5. Inspect Motion's actor summary, component count, movement speed, and movement mode.

Troubleshooting

Symptom	Check
No Motion logs appear	UMotionSubsystem is active, build is not Shipping, and LogMotionVisual is visible
Logs appear only on server	Simulated proxies are filtered to avoid duplicate logs
Histograms do not appear	Recording is active and the character actor is selected
Attribute values are missing	The attribute was added to TrackedAttributes before recording

Next steps

Visual Logger is disabled in Shipping builds. Motion logging functions remain available for API compatibility but do not add runtime cost there.

UMotionSubsystem referenceLook up the subsystem functions that centralize Motion logging.Use UMotionSubsystemCoordinate components and debugging through the local player subsystem.Networking commandsUse console commands for network and GAS debugging alongside Visual Logger.