If you've seen enough Tom Cruise action movies you may have noticed a recurring element. The guy runs. He runs in movies a lot. You'd think Hollywood would have enough practice filming him running at this point that it'd be easy, but apparently, that's not the case. Filming a Tom Cruise running sequence can actually be difficult because it turns out the actor is super fast. Much faster than his co-stars.
Action movies tend to be looked down upon by movie critics, in large part due to the fact that there is less "acting" going on, but according to the director of Jack Reacher: Never Go Back, Edward Zwick, that's not the case. He tells Screen Crush that even when Tom Cruise is running he has to act, because he has to look like he's running at full speed, even though he apparently has to pull up a bit in order to run with Cobie Smulders.
With all the practice that Tom Cruise gets running in his movies, it's not really that surprising that he's fast. Eventually, if you do something often enough you can't help but be good at it. Although, it sounds like Cruise is even better than you might expect. Edward Zwick says that Cobie Smulders is pretty fast herself, but Cruise leaves her in the dust when he's going full tilt. That's pretty impressive.
The Tom Crusie running thing has become something of a joke, though Edward Zwick says he didn't realize how much Tom Cruise ran in films when he wrote Jack Reacher: Never Go Back Rather, he simply felt that a movie that has characters on the run, needed to include actual running.
With several more action movies on his plate, including another Mission: Impossible movie, we're sure there'll be plenty more chances for Tom Crusie to show off how fast he is. You can see Tom Cruise run now in Jack Reacher: Never Go Back which hits theaters today.
CinemaBlend’s resident theme park junkie and amateur Disney historian. Armchair Imagineer. Epcot Stan. Future Club 33 Member.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.