ChildActorComponent reference can't be sent to Server

Unreal Engine Pipeline & Plugins Editor Scripting
, , ,
#1

Hello,

I need to be able to pass a ChildActorComponent reference to the server (using a Custom Event RunOnServer) when clicking on any actor but when a client click on a ChildActorComponent of a different client, it sends a None value instead.

Is it a limitation or am I missing something?

My script looks like this :

65908-reference_childactor_script.jpg
65908-reference_childactor_script.jpg1541×382 85.9 KB

And this is what’s happening :

  1. Server is clicking on its own ChildActorComponent. Everything is fine. The receive Print is showing the Ref.

65906-reference_childactor_0.jpg
65906-reference_childactor_0.jpg1215×430 94.2 KB

  1. Same when Server is clicking on the Client’s ChildActorComponent.

65909-reference_childactor_1.jpg
65909-reference_childactor_1.jpg1215×430 94.7 KB

  1. Now Client click on Server’s ChildActorComponent. It still works !

65910-reference_childactor_2.jpg
65910-reference_childactor_2.jpg1215×430 94.7 KB

  1. And the bug happens when the Client is clicking on the server’s ChildActorComponent. The Receive print is showing nothing.

65911-reference_childactor_3.jpg
65911-reference_childactor_3.jpg1215×430 90.3 KB

#2

Here is a zipped test project.

Ps : Unrelated, but randomly, the client won’t spawn properly…

link text

#3

Hi Genova,

Thanks for the report! I was able to reproduce this in the test project you provided, and I’ve entered a bug report for the issue (UE-23143). It seems the Hit Actor returned for a Child Actor Component is its own Actor, rather than the returning Actor, and this reference is not being communicated to the Server as you would expect a separate Actor reference to do. I will update this post when I see any update on the report. Thanks again!

#4

Hey Ben,

Ok, thanks for the report.

Any idea of a way to work around that problem ? Without a way to communicate that reference one way or another, I’ll be quite screwed.

#5

I would use separate actors, rather than child components, for this. You can then attach them, if necessary.

If you’re committed to using Child Actor Components, you need to make sure the Server knows which of it’s own components to reference. So, for example, you can reference each child actor component with an integer, and use that as an ID. Then you can pass the server the integer and tell it to reference its own child actor component with that integer ID.

#6

Hey Ben,

Thanks for the tips. It’s what I had in mind as a last resort.
Kinda dirty but that’ll do.