Madfox, open up shambler.qc. The first thing you should look for is a series of functions; sham_pain1 to sham_pain6. These should look something like the pain functions of your boss monster, and I'll call them the "pain animation" functions. Now if you look at the spawn function for a shambler, right at the bottom of the file, notice the line:

self.th_pain = sham_pain;

What you should notice is that this is not the same function as sham_pain1. sham_pain is an additional function, which I'll call the "pain controller" function. It decides whether or not to bother sending the monster into pain. If you change that line to read sham_pain1(the first "pain ainmation" function), then every time the shambler takes ANY damage, it will run the pain animation, which I think is your problem with the boss. You might want to try this with a shambler, just to see it go wrong.

So now we need to see what the "pain controller" function sham_pain does differently.

void(entity attacker, float damage) sham_pain =
{
sound (self, CHAN_VOICE, "shambler/shurt2.wav", 1, ATTN_NORM);

if (self.health <= 0)
return;

if (random()*400 > damage)
return;

if (self.pain_finished > time)
return;

self.pain_finished = time + 2;
sham_pain1 ();
};

The english language version of this code is:
Play the pain sound.
If I'm dead, return.
Make a random number between 0 and 400, and if the damage taken is less than that, return.
If the current time is less than my pain_finished time, return.
Otherwise, set my pain_finished time to 2 seconds into the future, and play the animation starting with sham_pain1.

I'd say the two most important things the "pain controller" function does are:
1) Create a random chance for the pain animation to play or not (although many smaller monsters don't have this in their pain controllers)
2) Keeps track of the pain_finished variable - not playing the "pain animation" if this variable is greater than time, but also updating it to some time in the future every time a pain animation IS played. This is basically setting a minimum time between pain animations, and that minimum time should be long enough for an attack to occur.

So basically what you want to do is copy this "pain controller" function, rename it, and replace the call to sham_pain1 with granito_pain1, the first of your "pain animation" functions. Then make sure that th_pain is set to the name of the "pain controller" in the monster spawn function. Once it works you can tweak the values further. Hope that helps. 

sham_pain and wiiiine

I will justify this post (and turn the thread away from qc back to modelling) by saying I'm putting together my Maya export stuff for you all right now. 

Version 0.01 of lunmodelgen.exe and .py:

[ http://lunaran.com/files/lunmodelgen.zip ]
[ http://lunaran.com/files/lunmodelgen.txt ]

The .txt should explain everything, but only if you read everything in it. I also included an unfinished example monster! 

 

i found a useful utility that will deform a mesh into the shape of your UVs. you can use relax and pelt mapping now for quake models. :)

http://slidelondon.com/iv

when you use it on a mesh, it creates a new mesh with a morpher modifier on it so you can go between the unfolded mesh and the original. now you can just export the skin from with the unfolded mesh, then use the morpher to bring everything back together, slap a skin modifier on top and start animating! (if you use the original mesh and then try to combine it with the unfolded mesh, the vertex numbers will be screwed up) 

So I can finally have the skins painted properly without all the annoying black space outside. 

OK, stupid question (well, stupid person...);

How is the skin information in Quake different to normal texture/skin information in 3d apps?

I'm curious as to whether I can use the funky new 3d painting shiznat in PS CS3 Extended to skin quake monsters (or at least, a combination of PS and maya/lun's script) 

There are two types of UV vertices in a quake model, onseam and offseam. The offseam vertices are the ones not on the perimeter of any shape on the skin. These are exactly like UV coordinates in any other app: each such vertex on the skin is paired with one on the model, and every triangle which meets that vertex will have the corresponding triangle meet it on the skin.

The difficulty arises once you get to a vertex on the edge of a piece on the skin. You don't want all of the triangles which meet at that vertex on the model to join onto it at that UV point on the skin, because you would like to unfold them as separate pieces.

The quake mdl format allows such vertices to be designated "onseam". Then two copies of this vertex will be made on the UV map (but not the model) - one on the left hand side of the skin, and another half the skinwidth to the right of it. To determine which triangles connect to which copy of the vertex, each triangle in the model has a flag "facesfront" which is set by the model compiler. If the triangle faces front it is connected to the left hand vertex, otherwise it connects to the right. As you might guess, the original quake model compiler calculates this based on whether the face is front or back facing, which is why you get the front/back pairing on the original skins.

The alternative, which I support despite always listing it's negative effects, is to make none of the vertices "onseam", but instead make actual duplicates of those vertices in the model which are on the edge of a skin segment, so that they can be moved where you like on the skin. This allows for much better packing of the skin, since you can do things like mirroring halves, devoting more space to things which face front, all the tricks basically. 

Preach, that gave me more perceptive!
Point is I gave the granito.qc three pain sessions so
the self.th.pain = granito_pain_decide
I can change it but how do I calculate the other three pain session?

a closer watch:
http://members.home.nl/gimli/granito.qc 

It looks like most of what you need is there. First thing I would try is change all those pain finished things to equal time + 5, if it's meant to be a really powerful monster.

There's a small bug which means the first pain animation won't ever be called, you should change

if (r < 0.66)

to

else if (r < 0.66)

otherwise when r < 0.33 it's also < 0.66 so the second pain sequence overrides the first one.

To make the pain animations less likely to happen, you could change to something like

if(r < 0.05)
{ first sequence...}
else if(r < 0.1)
{ second sequence...}
else if(r < 0.15)
{third sequence ...}


That way if r > 0.15 none of them happen. You could even finish that with:

else
self.pain_finished = time + 0.5;

so that if it doesn't go into pain that time, don't even bother to check for the next half a second, which would defend it against pain from nails/lightning a bit more.

You may find putting all these things in might go too far the other way, I'm just throwing them at you so you have the options. 

That goes great!

First I copied the shambler's part of the sham_pain, but then I lost the other two pain sessions in the self.th.pain statement.

But indeed it has more power now. It can't be shot so easily and that's what bothered me in the first place for an end boss.

Hey, thanks for that splendid cham_pain explanation! 

wouldn't gl engines copy the vertex anyways for rendering? 

Yeah, but that copy wouldn't count towards the limit of 1024, only the ones that are loaded from the mdl structure count for that. 

Was just browsing Polycount and someone made a script like the one necros posted for Maya:
http://boards.polycount.net/showthread.php?t=55987
Thought it might interest someone maybe. 

do I create the last death frame of a monster,
so its death scene leaves in another skin index? 

just add self.skin = # in the last frame function.

but seriously, madfox. post this stuff in the programming thread. :\ 

thanks for advice.
nice thread. 

if anyone's interested in modeling and uses milkshape i have a tutorial i wrote that might help you out.

it's here: http://z10.invisionfree.com/Quaked/index.php?showtopic=4 

model & animation: A rotating disc (like a gear, for example) comprised of 20 frames for 1 full rotation (frame 1 being 0 degrees, frame 10 being 180 degrees, etc). When the animation loop is interrupted, the gear will idle at frame 1.

scenario: the animation loop is interrupted at say, frame 12.

problem: the engine's interpolation adds frames in a straight line between each of the vert's positions, causing the disc to collapse briefly as it transitions from frame 12 to frame 1.

I need some way to constrain the mesh volume so it will appear to rotate naturally between frames. Is this possible with a skeletal format such as IQM? 

Is there a QC command (in supported engines) to suppress interpolation for one frame, or am I imagining it? 

there's this:

//DP_EF_TELEPORT_BIT
//idea: id software
//darkplaces implementation: divVerent
//effects bit:
float EF_TELEPORT_BIT = 2097152;
//description:
//when toggled, interpolation of the entity is skipped for one frame. Useful for teleporting.
//to toggle this bit in QC, you can do:
// self.effects += (EF_TELEPORT_BIT - 2 * (self.effects & EF_TELEPORT_BIT));

Which I haven't tried yet because because the disc in question is just a small part of a larger mesh and I don't want to nolerp the entire entity.

I could split the disc off as a separate entity but that's something I'm trying to avoid... 

You might need to animate it yourself using qc (like for enemies) to let you stop at any frame? 

the loop is dependent on player input which can change at any time. Unfortunately forcing a full loop before stopping the animation isn't possible here. 

Maybe not the same, but an answer to my experience in making a convoybelt. The intention was to create a production line with an energy cell with twenty frames. I have noticed that the method that uses darkplaces is different from fitzquake.

I animated one cell/1frame, going to the half part, then hide the cell under the convoybelt, and then sweeping it up after the other half part was gone.
The convoybelt went easy, as it is a straight line.
The claw made an angle , so I had to hide it in three frames before the next row.

When I finally got the animation right, the interpolation was discussed.
After a lot of sliding and fitting I finally got the series running, but then I realized that each engine applies its own way of "turning".

here are the model versions I used. 

I'm not understanding what you are doing.