Unreal 5.8.4 PCG Undo Report Warns of Lost Instance Overrides

Procedural Content Generation can save environment artists a great deal of repetitive work, but it becomes difficult to trust when a routine editor action changes a placed actor's configuration. A developer report published on November 1, 2026 describes an Unreal Engine 5.8.4 workflow in which undoing an edit to a Blueprint actor appears to reset values assigned to its PCG component.

The reporter provides a specific reproduction sequence. Create a PCG graph with a parameter whose default is empty, add that graph to a PCG component inside a Blueprint actor, and place the actor in a level. Override the parameter on the placed instance, then rename or delete the actor and press Undo. According to the report, the component returns with its graph parameter back at the empty default. The developer also observes that the previous graph instance becomes invalid. Undoing a direct parameter edit reportedly works correctly, suggesting that the problematic path involves reconstructing the actor's components.

This is a public bug report, not an official Epic confirmation or evidence that every project using PCG is affected. The system details identify Mac and Unreal Engine 5.8.4; behavior on other operating systems, project configurations, or engine builds has not been established. The reporter includes a proposed explanation involving cached component instance data, object duplication, and transaction handling, but that proposed root cause remains a developer's analysis.

The distinction matters for teams building procedurally populated levels. Per-instance overrides can carry asset references, seed choices, and local rules that are not obvious from the general graph. If those values silently revert during ordinary level editing, a scene could regenerate with the wrong content later, possibly without a clear error message.

Developers working with a similar setup can create a disposable test map, record an actor's overridden values, and reproduce the exact rename-and-undo sequence. If the behavior appears, preserve a copy of the level, note the operating system and engine build, and report precise steps to Epic. Avoid using an unverified code patch in a production branch merely because it appears in a forum discussion. Until a fix is confirmed, carefully reviewing instance parameters after undo-sensitive editing is a reasonable precaution.