openmw.org

It affects through physics I am guessing, so the character does move in the actor orientation.

EDIT: I am going to look at your branch

So the way the actor is facing does not really affect anything yet? Strafing and moving forwards at the same time does make things more difficult. The forward/backward animation seems to play in these instances.

For this discussion let's ignore swimming and levitation.

I am a little off on all the details of your implementation. For mDirection is (0,-1,0) walking backwards; (0,1,0) forwards? What is strafing left and strafing right?
Are there any more directions implemented yet (jumping)?

True, and I think there is a way to handle those situations. But the way I described I think is going to work a lot better than using a normalized vector for mDirection. Using a quaternion to represent the forward direction allows the animation to do whatever the hell it wants really (forward, backw...

Something needs to be redesigned about mDirection then. If you think about when you are playing morrowind, when you want to move backwards your rotation does not change. You keep your mouse in the same place and press the 's' key instead of 'w'.

movement = ActorOrientation * movement should work.

Backwards shouldn't break, the calculation should work. Your quaternion is pointed in a good forward direction, but movement will be somewhat negative. Then they are multiplied together.

Hmm...

I meant that you could change mDirection from a normalized vector into a rotation.

Then do:
movement = mDirection * movement;

Not sure if this would help anything now though.

EDIT: So you are not taking the length anymore.

Can you do movement * QUATERNION (for mDirection)? I think that may work and allow unique zigzaging.

It also makes it so an animation can only move in one direction; for example, when walking forward any side-to-side movement is purely cosmetic and won't cause collisions. I'm thinking about this, the normalized vector method you are using may be right in this respect. If you think about it one fra...

In the new character controller, will the bip01 current rotation rotate the collision shape around all 3 axes (yaw, pitch, roll (do we need roll?))? In our newtrace for pmove, we never actually factored in rotations in the trace (so in reality the box didn't actually turn, its direction just changed...