The result of the Attach target change operation using AttackTrack's ContextMenu varies depending on the flow

At present AttackTrack's context menu has three patterns of Attach target change flow

1. Change constraintBindingID
2. Use ExsitBinding
3. Use NewBinding

However, 1 and 3 can correctly change the target, but the result of 2 is different from that.Specifically, the attachment in the selected section is not changed, and a new section is newly added to the end.

This is because the section of F3DAttachTrackEditor :: ActorSocketPicked becomes null when using ExistingBinding.Because it becomes null, a new section is added by F3DAttachTrackEditor :: AddKeyInternal via AnimatablePropertyChanged.

If we pass a Section to FActorPickerTrackEditor :: ExistingBindingPicked like FActorPickerTrackEditor :: ActorPicked , it may be resolved

See description.

Fix UE-51650

i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000

I am not able to find world outliner how to enable it?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

Error UE5 5.0.3

An error occurred while trying to generate project files !?

Installer 4.10 failed with error code R-1603

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

Why does the REMOVE method of map container remove elements have memory leaks?

Bullet replication problem. The players sees each other but does not see the bullet