Merged geoset jumps to another unit

Level 5
Joined
Aug 15, 2012
Messages
136

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.
 

Attachments

  • Baltazar_Acolyte2.mdx
    104.3 KB · Views: 47
Level 6
Joined
Feb 21, 2005
Messages
110
No. You have entered bone_head into the geoset's helper groups:

Code:
Groups 1 1 {
	Matrices { 40 },
}

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

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

I know it's awkward, but I'm pretty sure that's where the problem is.
 
Level 5
Joined
Aug 15, 2012
Messages
136
Ok, now I get it, but, what if I have:
Code:
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:
Code:
Bone "Hood" {
	ObjectId 31,
	Parent 41,
	GeosetId 4,
	GeosetAnimId None,
}

Still doesn't work
 
Last edited:
Level 5
Joined
Aug 15, 2012
Messages
136
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.
 
Last edited:
Top