This member has provided no bio about themself...
To view this video please enable JavaScript, and consider upgrading to a web browser that supports HTML5 video
What do you mean when you write adding the parent after the child?
I am wandering if this is what is causing my issues with combined spawn objects.
Basicly, I needed another bone for the turret to pitch, so I added B_Pitch at the end of the skeleton, attached it to B_Turret and changed all BoneInfluences and similiar to refer to B_Pitch insteat of B_Turret:
<Pivot Name="ROOTTRANSFORM" Parent="-1"> <Pivot Name="B_TURRET" Parent="0"> <Pivot Name="B_MUZZLEFLASH" Parent="4"> <Pivot Name="B_DAMAGEFX02" Parent="4"> <Pivot Name="B_PITCH" Parent="1">
2 of the Bones refer to a Parent that comes after them in the hierarchy, causing that strange bug.
After I moved B_Pitch directly behind B_Turret (and updated all BoneInfluences and such), the bug vanished.
Your comment will be anonymous unless you join the community. Or sign in with your social account:
Turn out adding the parent after the child in a skeleton might cause a couple bugs.
What do you mean when you write adding the parent after the child?
I am wandering if this is what is causing my issues with combined spawn objects.
Basicly, I needed another bone for the turret to pitch, so I added B_Pitch at the end of the skeleton, attached it to B_Turret and changed all BoneInfluences and similiar to refer to B_Pitch insteat of B_Turret:
<Pivot Name="ROOTTRANSFORM" Parent="-1">
<Pivot Name="B_TURRET" Parent="0">
<Pivot Name="B_MUZZLEFLASH" Parent="4">
<Pivot Name="B_DAMAGEFX02" Parent="4">
<Pivot Name="B_PITCH" Parent="1">
2 of the Bones refer to a Parent that comes after them in the hierarchy, causing that strange bug.
After I moved B_Pitch directly behind B_Turret (and updated all BoneInfluences and such), the bug vanished.