Hi Bob, looking at the callstack this spot seems odd:
SActorDetails::SetObjects(const TArray<…> &, bool) SActorDetails.cpp:237 SLevelEditor::OnActorSelectionChanged(const TArray<…> &, bool) SLevelEditor.cpp:1765SLevelEditor::OnActorSelectionChanged forwards a selection change notification to the active editor modes, but I do not see that in the callstack provided. It’s possible it was optimized out, so I’m curious if your group is using any custom U/FEditorModes that may be active that are causing the details panel to try to refresh in this way, that may be holding stale pointers. One other question is if there are local engine modifications within that SLevelEditor function, those should be removed or updated to not fire until the selection is updated for the PIE world using the PIE start/end delegates.