7 réponses à ce sujet

[andysks]

Hi all. This has happened to me on a couple of occasions, during a cutscene. The NPC was supposed to walk somewhere, and for the rest of the scene he keeps making the animation even though he stands on one spot. Sometimes, he even continues doing it after the conversation and will only get over it if I talk to him again, or if he is a companion get control of him. Any ideas why this is happening?

[4760]

That rings a bell: it reminds me of when the PC tries to go to the point you clicked, but cannot really reach it (although it seems he did), most probably because of a walkmesh issue (like a closed door in the path).

[andysks]

Well, kinda yes. One time I saw it, it really happened when an NPC tried to pass a door. But another time it was while out in the open with a clear path and all.

[kevL]

i guess it's either of these

- rubber banding (unit looks like its walking in place until it pops backwards to where it 'really' is)
- animation bug: anim simply doesn't quit until another anim is invoked (even a call to Idle ...)


hm, two more reasons to work on xoreos/NwN2

[andysks]

It has to be the second. Is this a known thing to you KevL? And if yes, is there a file that needs tweaking in order to fix it, or should I just go with the thought that the the builder cannot do much about some game mechanic bugs ? 

[kevL]

it 'rings a bell' like 47' says.

if so, very rare for me and i just click it and it stops. Game mechanic bug (likely): someone left out an if clause

[rjshae]

I've seen it happen a few times when a character gets caught up trying to go around a corner when there is a walk mesh with a lot of tightly packed mesh faces. Eventually it just stopped moving and I had to go back and steer it around the obstacle. Another case was a chest that the character couldn't quite reach, so it kept walking in the same direction. I suppose it could happen with dynamic collisions as well.

[andysks]

Sometimes I think that the efficiency of the pathfinding algorithms of NWN2 depends almost solely on the builder's work on creating a good walkmesh. And if I had done a sloppy job then I would fix it. However, I am very proud of my walkmesh in general. And my creature makes it on open space anyway . Now that I think about it though, it happened when I clicked to progress the scene before he had reached destination. If not 100%, then it is a very high chance that the problem lies there. Adding a carefully calculated delay on the node where he runs might fix the problem.