LCM Nav3D - Mass Entity Trait Reference

How to build a Mass crowd/agent with LCM Nav3D. Add these traits to a Mass Entity Config asset (Create → Miscellaneous → Mass Entity Config) and use it on an AMassSpawner.

One rule: every agent needs exactly one movement trait. Everything else is an orthogonal add-on. The editor validator (below) enforces this.

The anatomy of a config

A Mass Entity Config is a list of traits. A working Nav3D agent needs one from each of three categories, and no more than one from the movement category.

Figure 1 - A three-trait config, one per category.

Things the screenshot shows that are easy to miss:

• Validate Entity Config at the top runs the trait-combination check on demand. It also runs on save and on cook.
• Compute - leave it on Auto. This release solves on the CPU, so Auto and CPU behave identically; the selector is kept for forward compatibility.
• Greyed rows are not disabled features. Goal Location is greyed because Goal Mode is Tagged Actor, and Lead Seconds Cap because Enable Goal Prediction is off. The panel hides what the current configuration will ignore.

⛔ This config is also the worked example of the one rule

Look at [1] and [2] together. The Agent's Nav Mode is Flow Field, but LCM Nav3D Goal is a Path Following add-on - it drives the path-request fragment, and a Flow Field agent never issues one.

So this combination fails validation, with:

LCM Nav3D Goal only works with a Path Following agent (it drives the path-request fragment). For a Flow Field agent, set the goal on the 'LCM Nav3D Agent' trait's Goal / Goal Mode properties instead.

The fix is one of two things, and which one depends on what you want:

You want	Change
A 10K-scale crowd sharing a goal	Remove the Goal trait. Set the goal on the Agent trait's own Goal Mode properties.
Per-agent precise routes	Set Nav Mode to Path Following. The Goal trait is then correct as it stands.

Press Validate Entity Config on any config you build. It catches this, the duplicate-movement-trait case, and the mixed Path+Flow case - all three of which are silent at runtime and present as "my agents do not move".

The traits

🟢 LCM Nav3D Agent - the one movement trait (start here)

The single authoring entry point. Pick a Navigation Mode:

Mode-specific properties hide automatically via EditCondition. Common movement knobs (radius, speed, accel, turn-rate, avoidance style, flight style, lane bias) apply to both.

➕ LCM Nav3D Goal - auto-pathing (Path Following only)

Points a Path Following agent at a fixed location or a tagged actor and keeps it pathed there (re-pathing on drift, optional lead-prediction for moving targets). Not for Flow Field - set the goal on the Agent trait's Goal Mode properties instead. The validator warns if you get this wrong.

➕ LCM Nav3D Perception - SVO-LOS sight (either mode)

Makes an agent both a senser and perceivable (faction-based, true-3D SVO line-of-sight). Writes a per-agent "closest visible threat" surface read by EQS, StateTree, or steering. Opt-in avoidance: r.LcmNav.Mass.PerceptionAvoid 1 makes Flow Field agents veer from their own perceived threat.

🎨 Rendering - pick ONE

Combination matrix

• ❌ conflict - two movement stacks; the editor validator errors and (at runtime) the two steerers mutually exclude → the entity would not move. Keep one.
• ⚠️ - allowed but pointless; the validator explains.

The editor validator

ULcmMassConfigValidator runs on every UMassEntityConfigAsset (right-click → Validate, or on save/cook). It errors on:

1. Two movement stacks (Path + Flow, in any mix of unified/legacy traits).
2. Goal without a Path Following agent.

So a broken config can't ship. Requires the Data Validation plugin (bundled).

Migration from the old traits

The pre-2026-07 traits still work (byte-identical archetypes) but are marked (Legacy) and superseded by the unified trait:

Existing content (e.g. DA_MassAgent_Apex) keeps working - no forced migration.

Default-value deltas when migrating (the unified trait has ONE default per property; the two legacy traits differed): ArriveRadius is now 100 (legacy path 80 / legacy flow 150) and AvoidanceStyle defaults to Reactive (the legacy Flow Steer defaulted to Predictive/ORCA). If your config relied on a legacy default, set the value explicitly after switching traits. TargetActorTag defaults to ApexGoal (matches legacy).

World Partition / large-world (City Sample scale) - REQUIRED READING

The vanishing-crowd trap (stock engine behavior)

AMassSpawner::BeginDestroy calls DoDespawning - the spawner destroys every entity it spawned when the spawner actor is destroyed (engine MassSpawner.cpp). In a World Partition map a placed spawner is spatially loaded by default, so when the player leaves the spawner's cell, the spawner streams out and silently deletes the entire crowd. Symptom: agents work near the spawn area, then all disappear when the player walks away.

Fix (pick one):

1. Use LCM Nav3D Crowd Spawner instead of the stock Mass Spawner - identical (EQS generators etc. all inherited) but defaults to not spatially loaded, so its crowd's lifetime is never tied to the player's position.
2. On a stock AMassSpawner: Details → World Partition → Is Spatially Loaded = false.

This follows the AAA rule: population lifetime must be owned by something persistent (an always-loaded actor/subsystem), never by a streamed actor. Distance-based despawning should be an explicit population policy (an ambient ring, à la City Sample's crowd), not a streaming side effect.

City-scale checklist

• Navigation: a city does not fit the finite default (WorldExtent = 100 m). Use the manager's Infinite World mode (Hierarchical HPA*); the flow crowd keeps its own nav chunks resident via crowd-driven streaming (r.LcmNav.Mass.CrowdStreaming, default on) - agents don't lose nav when the player (the only invoker) leaves.
• Rendering: LCM Nav3D Representation culls agents visually past its LOD distances (defaults: Off at 200-250 m - deliberately conservative). For city vistas, raise LODParams.BaseLODDistance/VisibleLODDistance on the trait. This is visual LOD only - entities keep simulating; it is NOT the vanishing-crowd trap above.
• Ambient population ring (constant-density crowds around the player with bounded cost, the City Sample pattern) is a roadmap feature - until then, crowds are persistent: they exist wherever you spawned them.

Useful CVars