I recently started rewriting my character class. Originally it extended a Kinematic object. Now I'm extending the Character one.

Oddly, the code for manipulating the matrix in the kinematic does not work the same.



This causes the player to rotate in all six degrees with the Kinematic codes but the Character code does nothing. It doesn't even flinch. This is not the only variation of rotational codes I used on the Character object, all had little effect.

What am I doing wrong or should I do in order to get my object to rotate correctly?

if you take a look at Game::Chr header:
if you want to use Game::Chr then you'd need to operate on virtual animate function, and apply modifications there, it may be difficult without having the game chr sources.

Alright, I got that sorted out, but now I'm having a different problem.

My movement code creates a temporary matrix (mat) and assigns the velocities to that before passing it to the controller.


The first part works correctly and provides the thrust. But the second, braking, part only works when the player's direction is the Zero Vector otherwise it is incorrect and can cause insane amounts of acceleration and other bad things. Clearly this is not the best way to do it but I could find no way to brake an actor mostly adding friction.

The simple way is to just divide the entire players velocity by some arbitrary number which I suppose is "friction" but this causes other problems. I want to apply the brakes only in the directions the player is not moving in. So if the player has a velocity along the X,Y and Z axis (say 10,10,10) and I move to be going directly along the Z axis I want the other two directions to be reduced to 0 (resulting in 0,0,10). This problem becomes a lot more difficult when the player starts moving at a random angle as the reverse thrust is applied to each direction.

As I said the code I am using above works, but only if the player is moving along the zero vector. How would I adapt this to work at any angle?

Velocity is defined as a direction and a magnitude--or direction and speed. You shouldn't need to transform the velocity vector. That should be your problem with the direction. (I may be wrong here, I'm just starting to use the Essenthel engine. You may find it enlightening to look into vector and matrix math to see and understand what is going on behind the scenes.)
For your reverse motion, I believe your issue is that while holding the brakes, you are constantly adding that backwards vector. Try adding in a check to make sure it's not moving at a 'negative' velocity relative to the direction of travel. In addition, you'll probably want to have your braking power multiplied by the Time.d() as well, so you don't lose your brakes during low frame rates.
Hope that helps.