EDIT: I found a solution to my problem.
Even though I was recording in 30 fps, I also had my settings at the highest resolution possible on my display(which unfortunately causes an inconsistent frame rate because I do not have the most powerful computer). The inconsistent 30 fps caused lag which messed up the recordings, making them inaccurate. So I toned down the resolution to 640 x 480. After that, the recordings I made came out accurate.

So recently, I've been using that recorded animation recorder, http://hce.halomaps.org/index.cfm?fid=5939
to make a machinima. I rolled back to 1.09(it's not compatible with 1.10) and began recording my animations.
Now here's the problem. After injecting the animations into the scenario, compiling it, and running the recording, the recording is way off. Instead of walking 5m, the recording will walk 10m. Instead of running to cover, the recording will proceed to run past the cover I set up in Sapien and straight into the middle of the battlefield.

My point is that the recordings are very inaccurate and I'm not quite sure how to solve this. I recorded in 30 fps but that didn't seem to change anything as they still came out the same.
Anyway, hopefully somebody has a solution to this. Help would be much appreciated.
Edited by Stuffy Junk on Aug 7, 2017 at 01:05 AM

you need to lock the game to 30 FPS, otherwise it records your inputs at 60 and tries playing them back each actual ingame tick.

Some one re-released this but for the 1.10 halo. where are the links?

My recommendation is to have 1.10 and make all the camera and biped animations in max8.

http://www.halomods.com/ips/index.php?/topic/680-cmts-the-silent-cartographer-evolved-media-month-the-month-is-now-over/page__st__40
Edited by Halonimator on Aug 6, 2017 at 08:27 PM

I already had it locked at 30 fps, but I did find a solution however.
It turns out that, because I was recording at a high resolution, the frame rate was not a consistent 30 fps(the result of having an under powered pc). Because of this, the ingame ticks weren't accurate, hence the weird issue I was getting when I played back the recordings. So I lowered my resolution whenever I recorded and tada, they came out accurate.