So, I decided to start my career player again with the on disk teams. No. 4 Batting all-rounder who does fast bowling. First match. Came in after first two in the team went out for 10, Khawaja was in on about 30 odd. We managed a stable partnership of 50 off 58 (he was on fire, cracking 4's and even a 6, got troubled a few times, we both nicked, his didn't travel all the way to the keeper, mine flew past him on the leg side and the keeper didn't get anywhere near it, but still dived). Bowler dropped a catch over his head that Khawaja put over him with decent pace, everything was looking pretty good until I got out on 25 odd. Unfortunately it was to a slight glitched catch to a mid off. The thing is, even though he did a bit of a superman, watching the replay (and checking his stats afterwards) it did suggest a possible reason for why this happens.
Not knowing anything about how DBC'14 has been programmed (so yes, making shit up here), it seems that when a player is going for a catch, the game works out, based on the players attributes for Acceleration, Agility, Anticipation and Run Speed how much time it would take the player to reach the point from where he is standing to where the ball will be in a catching position. If the game decides the players attributes allow him to take the catch (and may run the catch chance calculation at this point as well, explaining why so many superman attempted catches never result in a drop). If the game says he can and will catch it, the game then runs any required animation to point the player at the point of the catch, runs it, then works out when the player needs to be in position to being the selected catching animation, then just makes the player travel that path at an average speed.
If the distance is short, the turning and catching animations take up a large portion of this time, thereby leaving little appearing 'travel' time, making it 'warp'.
I dunno, I may be simplifying the whole thing, but after watching the latest replay and the one I uploaded, everything seems to match the above scenario.
