• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.

Weird Model Problem

Status
Not open for further replies.
Level 12
Joined
Dec 20, 2005
Messages
137
This problem is hard to explain, but I'll do my best. I've made a wheel model for one of my heroes to throw. I made it the missile for carrion swarm.

When he throws it into the middle of nowhere it's fine, but if he hits somebody or even comes close to hitting somebody the model attaches itself to either him, a nearby unit, or the unit that was hit temporarily. I'm pretty sure the model is doing something because I don't have this problem with any of the other carrion swarm moves I have made.

I'm also pretty sure it's the model because if I try to put a unit on the map with that model file, it says it can't find the file.

Any help would be appreciated.
 
Level 25
Joined
Mar 31, 2004
Messages
4,468
Ok... This'll be guesswork, but I guess the wheels die when they hit the opponent? I'm not too sure what's going on with that

The Footman bug is a clearcut case of geosetanims. I can't remember them off by heart, but there's a part of the mdl that deals with the visibility of geosets in certain animations, and has the timing of where it is visible and invisible

I haven't poked them for a while so that's probably a very bad example...
 
Level 24
Joined
Mar 29, 2004
Messages
1,991
wingednosering said:
When he throws it into the middle of nowhere it's fine, but if he hits somebody or even comes close to hitting somebody the model attaches itself to either him, a nearby unit, or the unit that was hit temporarily. I'm pretty sure the model is doing something because I don't have this problem with any of the other carrion swarm moves I have made.

Unassigned vertices or misassigned matrices.

Check each geoset's "vertexgroups" section for "-1" values; they're unassigned and thus dangerous.

Also check that all the geoset matrices are all pointing at BONES. Only bones can have geometry attached to them.

If either of these problems is present, then the game will attach the geometry at random to anything nearby that provides anchorage.
 
Level 12
Joined
Dec 20, 2005
Messages
137
Alright guys, I'm the biggest noob in the world at modelling, so I need some help...I understand that I'm looking for -1 values, but where? Models have a lot of writing in them, and chances are, they also have a lot of negative numbers.

What part of the mdl should I edit?

[Edit]: Ok, I found the vertexgroup spots and they were all zero. Not a single -1. How do I check to make sure the models are 'pointing at the bones'?
 
Level 24
Joined
Mar 29, 2004
Messages
1,991
Matrices section.

Code:
	Groups 11 11 {
		Matrices { 0 },
		Matrices { 1 },
		Matrices { 2 },
		Matrices { 3 },
		Matrices { 4 },
		Matrices { 5 },
		Matrices { 6 },
		Matrices { 7 },
		Matrices { 8 },
		Matrices { 9 },
		Matrices { 10 },
	}

The number in each of the matrices is the number of an object within the model; ie, something that has an objectID and an associated pivot point. If any of the objects associated with these IDs are not bones, then change them to objectIDs that are for bones.
 
Level 12
Joined
Dec 20, 2005
Messages
137
Ok, how can I attach it to this thread? The site is still having trouble I think, so uploading won't work.

I'll take another look at the matrices again. If it doesn't work how can I get the model to you?

[Edit]: I double checked the matrices and vertex groups but I still can't find the problem.
 
Status
Not open for further replies.
Top