 |
I assume you entered the angle keypair manually? After a transformation (this can be a translation or a rotation or both) the rotation matrix is calculated and stored into the spawnargs. Only the "rotation" spawnarg is used to store the actual rotation, the "angle" spawnarg is overwritten (which fixed the weird rotation jumps we had at the beginning if that occurred to you). I don't know if the code is able to detect translation-only transforms, but given it could, DarkRadiant should check for an existing angle keypair and incorporate it into the resulting rotation matrix. I'll have to check that. |
 |
Just a (probably obvious) note: it's not limited to AI |
|
|
Looking at this again, it appears the problem is happening in rotation.h:230, where the "angle" key is set to "0" before writing the rotation matrix to the entity. Setting the "angle" to "0" will fire the key observers, resetting the rotation matrix to identity just before it's written to the entity's key value pairs. |
- Anonymous
