So I want to have an NPC to look at the player when the player passes within a certain vector distance, but I want them to track the player with a "neck" rotation, kind of like they do in Hitman.

So far I have:


I thought the above would work, but it seems to be rotating the entire entity. What gives?

This is the part where you rotate the entire entity:

vec_to_angle(silver_surfer.pan,temp);

You can directly do this:

vec_to_angle(temp1,temp);

or like this, if needed:

vec_to_angle(temp1, vector(temp.pan + 90, temp.tilt, temp.roll));

Hmm that still doesn't seem to update the "head" of the NPC. It just doesn't want to track the player position for some reason.

I have never used bones in this way.

What about separating the task in two:

Can you rotate the head with keys?
Something like this:
temp1.pan += key_r;

Yes it's something that should be possible (I've done it in other game engines) but for the life of me I can't figure out how to do this in A7.

Here's where I'm at right now:



I'm not sure if I need to reset the bone in the "if" statement.

Also explain what you mean by splitting the task in two?

When the player walks near an NPC, the NPCs head should track the player based on a vector distance, not a key action, if that makes any sense.

I know I'm close, but the problem right now is that it seems the bone rotation is not being updated every frame, only once, and then that's it.

The splitting is meant for testing only.
I would implement a key action to test whether the bone rotation updates at all.

I don't understand why you use the variables instead of the vectors.

This part isn't necessary:

player_x = player.x;
silver_x = silver_surfer.x;
silver_pan = silver_surfer.pan;

But, if you want to use the variables, you should declare them this way:

var player_x[3];
var silver_x[3];
var silver_pan[3];

They have to be vectors, that means, they need an array of 3, if you use them with the vector instructions vec_set, vec_add etc..

hi,

Dont use ent_bonerotate!

I did it and wasted much time.

problem #1
if you try any collsion-detection after the ent_bonerotate you will see that the bounding box doesnt moves to new position.
(maybe not tragic on head, but on moving legs,arms...)

problem #2
if the model moves with ent_animate and should turn the head with ent_bonerotate to you it will fail because on each "walkcycle" the headposition get reset.


Both problems I described here in the forums a few weeks/days ago.

If you want I can search the links.

I was realy happy as I saw the "ent_bone..." commands got realize in the engine and did easiely animated a model with it. I had full control at runtime via script to each little finger - it was very cool.
But without updated collision boundings it got useless for my needs and I throw it away.
JCL stated in "Future forum" it would slow down the engine if ent_bonerotate would update boundingbox too.



greetings,
gri

gri, thanks for the insights, but I don't understand the second point.
Can't you play the walkcycle and ent_bone_rotate the head right after that?

In case that isn't possible, one could add a bone animation to the model with the head rotating and set its animation depending the position of the target at which the head shall look, right?

On point#2, that's ridiculous that we can't manipulate a bone while using ent_animate. This is a very basic animation feature in most game engines.

Can one of the developers comment on this?

Isn't this similar to workshop 23 in the online tutorial where part of the model tracks the movement of the mouse?.