Variant Manager: LevelVariantSets asset corruption after rename or duplicate

When renaming or duplicating a LevelVariantSets asset that contains a Director Blueprint, the internal DirectorClass reference becomes mismatched. Although the DirectorBlueprint pointer updates correctly to the new asset, the DirectorClass continues referencing the old generated class whose Outer remains the original LevelVariantSets asset.

Because of this stale reference, the renamed or duplicated asset still retains references to the original asset, leading to corrupted Director Blueprint references and broken function bindings.

Additionally, renaming the asset and performing “Save All” leaves behind the original asset under its previous name. This asset remains in the Content Browser and is reported as unsaveable.

This issue reproduces consistently from Unreal Engine 5.4 through 5.6.1 and is still present in Main (CL 46622846).

A temporary workaround was provided to the licensee: adding a FixupDirectorOwnership routine called in PostLoad, PostDuplicate, and PostRename. This function realigns ownership of the Director Blueprint and its generated class (UBlueprintGeneratedClass), ensuring DirectorClass correctly references the current asset. The code was shared via the EPS case thread.

1. Create a new Level Variant Sets asset
2. Add a Variant and reference an actor from the level.
3. Right-click the actor in the Variant Manager and Add Function Caller.
4. In the Properties pane, click on 'None' -> Create Quick Binding -> ActorHasTag.
5. A Director Blueprint for the asset is created.
6. Save the asset.
7. In the Content Browser: try to rename or duplicate the asset.

Expected result: Rename and duplicate operations perform as expected. The duplicate asset contains no reference to the original asset. The renamed asset contains no reference to the original asset.

Actual result: The renamed or duplicated asset keeps invalid references to the original asset. For rename operations, trying to save all assets triggers an editor error because it will try to save the original asset even though it has been renamed.