'Get Closest Point on Collision" node is used to determine the distance between a primitive component (target) and another specified location (Point) as well as provide the point on the target. This works to return the point on the specified primitive component closest to the specific location Point. However, when a component higher in the component hierarchy than the target component is set to simulate physics, the point / distance returned from this node will jump between any components in the hierarchy that are children of the physics enabled component (including the physics enabled component).
No - this behavior was present in binary 4.13.2 (CL 3172292)
The debug point will move between SMC2 and SMC3 depending on which is closest to the camera as the player moves around the bluperint
The point only shows on SMC3 since that is the component being referenced by the Get Closest Point on Collision node. This would make the behavior consistent with if SMC2 was not set to Simulate Physics.
Head over to the existingAnswerHub thread and let us know what's up.