Using the "Keep World" scale rule can result in incorrect relative location when attaching actors

This seems to happen due to a precision error when calculating the relative transform between the socket and the component being attached. Occasionally, one of the transforms will have a scale of (0.999..., 0.999..., 0.999...) rather than (1,1,1), which results in the component's RelativeScale3D being set to a value very close to (1,1,1) in USceneComponent::AttachToComponent. Because the relative scale will be replicated with this new value along with the attachment info, bNetUpdateTransform will be true in USceneComponent::PostRepNotifies, causing it to skip zeroing the component's relative location on the client when attaching it.

1. Spawn a replicated actor with a replicated root component on the server
2. Immediately attach it to a socket on another replicated actor with the following attachment rules: Location Rule - Snap To Target, Rotation Rule - Snap To Target, Scale Rule - Keep World

Expected: the actor will be attached at the socket's location/rotation on both the client and server.

Actual: on the client, the attached actor may be at a large offset to the socket's location.

"Session Disconnected" UEFN

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

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

I'm working on a VR Project and I cannot add Nav Mesh to the stairs??

How to achieve HLSL Multiple Render Target in Material blueprints?

How can i modify the param name in EQS node

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

An error occurred while trying to generate project files !?

I can't open my map from the editor.

What controls of umg have mouse wheel events in UE4.27?