[BUG] Sockets don't scale correctly with negative values

Development Programming & Scripting
1

Hi,

I have a weapon class actor which has two SkeletalMesh components:

  • Arm

  • Weapon

The Arm is attached to the rootcomponent, and the weapon is attached to the arm.
Now, this class can be spawned as either left or right handed.
When it’s spawned as left handed, I simply multiply this weapon actor’s scale on the Y-axis by -1.0f.
The arms scale perfectly and are nice and symmetric with all animations working fine, however the weapon mesh, which is attached to the arm mesh via a socket does not scale correctly. There’s something funky going on there.

I’ve tried scaling the components as opposed to the whole actor, but get the same results.
Please see the screenshot below:

14487-ue4editor+2014-09-03+21-40-34-46.jpg
14487-ue4editor+2014-09-03+21-40-34-46.jpg800×568 48.6 KB

2

Really, no-one has encountered this before?

3

#SceneComponent-> Set Relative Scale 3D

Have you tried setting the relative scale of the attached component yourself?

see scenecomponent.h !

FVector RelativeScale3D //var
SetRelativeScale3D() //func

you most likely want this one as it will preserve its current socket scaling, but apply any changes you want!

#C++ Code For You!

basic code

if(SwordComp)
{
    //Get
    FVector SwitchedY = SwordComp->RelativeScale3D;
    
    //Modify
    SwitchedY.Y *= -1;
    
    //Set
    SwordComp->SetRelativeScale3D(SwitchedY);
}

Enjoy!

4

Hi ,

Thanks very much for the reply, but I’ve unfortunately already tried that without success.

Can’t figure out why this would be happening.
The terrible thing is, if I don’t get this approach working, I will have to physically duplicate the mesh and all animations and flip them outside of UE, import all of them and duplicate all the weapon code. That would really suck.

Cheers.

5

I’ve sent out some emails to Epic about your issue, I hope Epic gets back to you!

6

Thanks very much - you are a legend as usual.
Cheers!

7

Hee hee!

Hopefully they get back to you on Monday!

8

Bump. I would really appreciate it if someone from Epic could have a look at this one please. Thanks.

9

Bump again. Still nothing?

10

Still nothing still?

11

Bumpercars anyone?

12

I’m gonna email this around again and see what happen

13

Thanks , much appreciated again!

14

Bumpaddle?

15

Pinging my posterior - bum ping?

16

Epic has informed me they will be getting to your question soon / are reviewing it now!

#:heart:

17

Hi staticvoidlol,

Sorry for missing this post. This is an issue that we have been looking into for a while. Unfortunately we do not currently have a solution or workaround for it, and we cannot provide any estimates regarding when we will have a solution. For now, we recommend not mirroring skeletal meshes this way.

18

, thanks very much for all your input on this one, it is much appreciated. Keep fighting the good fight!

19

Hi ,

Thanks very much for getting back to me on this one, I can only imagine how busy you guys are.

This is however quite unfortunate news, as this has a significant impact on both the workflow (having to duplicate and mirror the components and animations) as well as the weapon code architecture.

I’ll start some diabolic rituals involving large amounts of chanting and/or cat blood so long and hope for the best.

Cheers,
staticvoidlol

20

Hi ,

Any update on this one?

This is a really troubling issue, as the workaround would be to physically duplicate and mirror all assets in external software.

Thanks.