[4.12] Child actors: Scale and location broken

Development Programming & Scripting
1

Hi there,

it seems like UE 4.12 broke scaling and location offset of child actors.

Here’s how to reproduce this:

  • Create a new project
  • Create a new Actor Blueprint, assign a static mesh
  • Add a child actor component as child node of the static mesh component like this

93438-2_child_actor_unmodified.png
93438-2_child_actor_unmodified.png1205×438 131 KB

  • Scale it up to 200% (everything works as expected)

93437-1_child_actor_scaled.png
93437-1_child_actor_scaled.png1207×359 108 KB

  • Now try to change the change the scale facor to another value

93439-3_child_actor_scaled_again.png
93439-3_child_actor_scaled_again.png1199×390 119 KB

As you can see, changes are ignored, undo doesn’t work also.

  • Now try to change the relative location of the child actor

93440-4_child_actor_scaled_again.png
93440-4_child_actor_scaled_again.png1196×397 137 KB

Changing the location also doesn’t work.

In my projects, child actors are scaled all over the place. I can’t fix this even manually right now, they are simply out of control.

2

Working fine for me.
Maybe You should add more precise steps.
As well test it on blank project.

3

Er, that’s exactly what I did? First step says ‘Create a new project’. I also included screenshots…

Did you create the child actor node as child node under the static mesh?

4

Hello ,

I was not able to reproduce this issue on our end. Are there any small steps that may have been left out? Does the scale and/or translation update when you hit the compile button? Is the project you are using a code?

5

Hi Rudy

no, it’s Blueprint-only, super-simple, blank project. I’ve uploaded it for you:
https://dl.dropboxusercontent.com/u/24358204/UE4/childActorBug.7z

  • Just open Blueprints/BP_Chair and try to move or scale the Child Actor there (BP_Cube). Both doesn’t have any effect for me:

1028×619 211 KB

Recompiling doesn’t change anything. The change is only visible if you close and re-open the whole Blueprint.

PS: It’s also not possible to select the child actor in the viewport for some reason. You have to select it in the treeview menu on the left.

PPS: Why can’t I upload a normal 7z archive here…?

6

Hello ,

After taking a look at the project that was provided. It appears that this is the known issue (UE-16688) that was reported for you on another thread. I have provided a link below to your original question. I will update the report with the new project. I hope that this information helps.

Link: [4.7.6] Cannot set focus to child actor component in viewport - Programming & Scripting - Epic Developer Community Forums

Make it a great day

7

Hello Rudy,

this are different things. This particular report is about not being able to scale/rotate child actors in the viewport.

The other unfixed issues are about one year old and are about

  • Not being able to select the actor in the viewport
  • Not being able to configure them in the details panel
8

After further testing I was able to reproduce this issue in a clean project by converting a static mesh to a blueprint class. After reproducing this in a clean project I would agree that this is a different issue. I have written up a report (UE-31836) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as in becomes available. Thank you for your time and information.

Make it a great day

9

I can no longer find the report for this issue, nor the (possibly duplicate) issue UE-32676.

10

Hello dbuchoff,

I have pushed the issue UE-31836 to the public tracker. As for the other issue UE-32676, that was a feature request. If you go to the about section of the public tracker you will see that we are no longer tracking feature requests on the public issues tracker.

Message on site:

"Why are feature requests not found on this site?

In order to maintain consistency and clarity on needed fixes, issues.unrealengine.com only serves up bugs and their status. We encourage you to discuss feature requests over in the Feedback for Epic forum using the [FEATURE REQUEST] prefix so the community and development teams can get visibility on these more nuanced conversations as they arise."

I hope that this information helps.

Make it a great day

11

I’m getting this in 4.15.1