tas_log fixes

[lipsanen]

No description provided.

[SirWillian]

I feel like it's incorrect to read m_vecAbsOrigin from playerio around ProcessMovement (especially on the Post callback). Between SetupMove and FinishMove, the move data object and the player data can desync (it's only on FinishMove that it gets copied from mv into the player, and the only thing that seems to happen between Setup and Finish is ProcessMovement), so I'd expect the Post callback logs to show no change if you read from playerio. Even from a micro-optimization perspective, I don't think the calls to the inline CMoveData::GetAbsOrigin would cause issues (you gotta deref 3 different floats anyway and they all happen next to each other in code).
I see that you made the change to fix an issue on 3420, but at least following the general flow of the code it doesn't seem entirely right to do it for all games.
In what way was it broken in 3420? Based on the Source 2003 leak, my guess is that the origin member moved in CMoveData at some point.