Merged geoset jumps to another unit

[Unelith]

Just like you can see on the screenshot above. I have merged a hood to the model seen on the RIGHT, attached it to Bone_Head. It shows correctly in all the model editors and Warcraft 3 Viewer, but it doesn't work in the game - it jumps to the model on the LEFT. Why does that happen?

BTW. In the portrait - it works properly.

 

[Infrisios]

I don't have WC3 to check, but I believe the geoset has no object it is attached to. Give it a bone/helper or any other node and you're good to go!

 

[Unelith]

As I said, I have attached it to Bone_Head, and I am sure it's a node.

 

[Infrisios]

No. You have entered bone_head into the geoset's helper groups:

Groups 1 1 {
	Matrices { 40 },
}

But the geoset is not part of any node, like:

Bone "gutz00" {
	ObjectId 0,
	GeosetId 2,
	GeosetAnimId 2,
}

I know it's awkward, but I'm pretty sure that's where the problem is.

 

[Unelith]

Ok, now I get it, but, what if I have:

Helper "Bone_Head" {
	ObjectId 40,
	Parent 39,
	Rotation 34 {...
        ... etc.
	}
}

How do I make the geoset a part of this?

EDIT: I created a new bone:

And it's like this:

Bone "Hood" {
	ObjectId 31,
	Parent 41,
	GeosetId 4,
	GeosetAnimId None,
}

Still doesn't work

 

[Stefan.K]

If you have mdlvis you can check quick on which bone to attach. Example: for footman bone head the bone is box2.

 

[Unelith]

I know where it should be attached. It attaches properly - to the Bone_Head. Only thing that is wrong, is that it attaches to Bone_Head of ANOTHER UNIT. But, I see now that in Oinkerwinkle's geomerger there are only few bones and the one I have used IS NOT on that list. Maybe you are right, I will check it out using this tool.

 

[Unelith]

OK, you were right! It was attached PROPERLY but to a wrong bone! Now it works. Thanks for help!