Hey Epic!
I’m using a child actor component to nest blueprints inside of other blueprints, but am getting unexpected results for attaches. In this image - Cube1 is a “Child Actor Component” that spawns a blueprint which applies transforms to itself. Sphere is just a regular static mesh. When I attach the Sphere to Cube1 it seems to attach to the “Child Actor Component” rather than the actor that the child actor component spawns. This means that none of the transforms the blueprint applies to itself get inherited by Sphere.
To get the kind of behavior I expect, I have to grab the child of the “Child Actor Component” and attach to that, as exemplified in the following image:
With this setup, any transforms applied to the spawned blueprint also get applied to the Sphere. I’m wondering if this is a bug or if I’m just making a sug.
Try changing the Attach type to snap the sphere to the cube. Additionally, if you created a socket on the cube to attach to, ensure that “In Socket Name” is filled out to reflect the socket you are attempting to attach to.
Attach type doesn’t matter. Also worth noting that having Sphere be a child of Cube1 in the hierarchy has the same issue: Sphere doesn’t inherit any transforms applied to the actor spawned by Cube1. Example below:
Do you have a sample asset I can take a look at? This seems like it may still be the same error the link above shows but if I can get a copy of the asset in question I can clarify further.
We have not heard from you in several days. I am marking this thread as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.
[link text][1]
I’ve attached a file with two assets. If you open up BREAKAGE asset you’ll see it has a childActor component that spawns a “moveitself” asset (which…moves itself) with a sphere as the child of the childActor. If you drop the breakage asset in the scene and hit play you’ll see the cube run off into the distance with the sphere left behind. I wouldn’t expect this to happen.
I think this is by design. A ChildActorComponent spawns an Actor and attaches the RootComponent of that Actor to itself. It does not make the ChildActorComponent the root of the spawned Actor, that could break the functionality of the spawned Actor, it may expect a particular root.
