The requested functionality was to allow for public variables created in the blueprint to be able to be edited when the blueprint is being used as a child actor. This seems to be working in 4.14 from my testing. Can you give me a scenario where it isn’t? Here’s a picture of what I’m seeing:
This is inside of the Details Panel for the Child Actor component in my ContainerBP. My other BP (MyBP) contains an Int variable called MyInt. After adding the Child Actor Component, setting the Child Actor Class to MyBP, I was able to edit this Child Actor’s variable (MyInt) through the details panel.
If there is some other functionality that you were looking for, please let me know and I can add a separate feature request.
It works but in case you are coming from an earlier engine version (4.13 in my case) you have to reassign the Child Actor Class. After this the options do appear.
This is great, but why aren’t the variable editable through script instead of just through the panel ?
I have a loop to add several Child Actor component, and I need to pass them different Variable values for their construction script. And it’s not possible at the moment.
SpawnActor has connector for exposed variables, why not Add child actor component? It would be really useful to have them. Thanks.
I can see the variables in the details panel of the parent blueprint, but I cannot access them on an instance placed in the level using the viewport details panel
I still get this, when i click on the issue tracker i just get an unknown issue, not sure if they are working on this site or not but this would really help my project.
I recently had to look into Child Actors as a lower level due to an unrelated issue, where a user was trying to rename their Child Actors. The functionality that is feasible has already been added. Anything further would require an entire rework of Child Actor component as Child Actors are rarely ever the same instance for the entire session. Child Actors are constantly being replaced due to how they are updated.
As for the feature request not being found, this is because we removed all Feature Requests from the public bug tracker. The request is still in and it was set to Fixed in 4.14.
