10 Biggest Problems With Captain America: Civil War
Great? Yes. Greatest comic book flick ever? Um...
Compare Captain America: Civil War to Batman v Superman, and it feels like comparing Deuce Bigalow: Male Gigolo to Citizen Kane; they're on a completely different level, quality-wise. Without question, Marvel's latest delivered the inter-superhero melee that fans were clamouring for, and even bothered to give all the characters a good reason to fight! Who'd have thought?
Positive points aside, though (of which there were many), it almost feels like - in our collective rush to call deem the film to be a "comic book masterpiece" - we've overlooked a lot of its inherent flaws; aspects that the movie did not pull of quite as well as others, moments where the narrative betrayed itself and opted for a shortcut, or plot points that were shoe-horned into place with little subtly.
In short, problems that nobody wants to admit are even there because they'd prefer to think of this movie as one that doesn't really have any.
Unfortunately, that just isn't the case...
10. It Never Beats Its Opening Act
Civil War is made up of a lot of great and memorable scenes, but - as if often a case with a blockbuster of this kind - it never gets better than its opening in terms of action, fun factor and all-round superhero hi-jinks: the Nigeria-set, exotic counter-heist sequence, in which the Avengers attempt to stop Crossbones from stealing a dangerous virus from a secured location, is balls to the wall brilliance.
Filmmakers often want to ensure that the opening of their film is so awesome that they invest absolutely everything into making it spectacular; in this case, they pull off a total blinder, but it's hard for the rest of the flick to live up to the sheer joy of what's on display in the first 20 minutes, as we get a glimpse at the Avengers out on a mission, using their powers as a team.
For anyone who's saying: "Hey, you're forgetting the battle at the airport - isn't that the best scene by a sizeable margin?" Well, almost - except it's rendered in muted greys and browns and has a generally bittersweet, downbeat tone. It's hard to enjoy it fully - and the same way - when it's superhero vs. superhero.
Which means that the key scene set in Nigeria is very much Civil War's best moment - it's an incredible and relentless dollop of pure cinematic honey.
9. Black Panther Was A Humourless Bore
Marvel fans were eagerly awaiting the arrival of Black Panther, played in Civil War by the very capable and talented Chadwick Boseman.
Whilst it's probably safe to say that - as a new, badass superhero character - the movie more than delivered the goods on the Black Panther front, I'd argue that his real life alter-ego, T'Challa, wasn't anywhere near as convincing. In fact, he was incredibly stoic and serious to the point of being... well, a little boring.
Before the release of the film, many Marvel fans had expressed a few worries with regards to Black Panther - especially where his costume was concerned. Needn't have fret, though; the Panther costume looked awesome in all its Vibraniumness, and is arguably the coolest superhero outfit in the MCU thus far.
T'Challa, though... not so convincing. Okay, so the man is dealing with the fallout of his father's death across the span of this film, so it was never going to be all smiles and puppies. Still, was it necessary for him be so humourless and dour at every given moment? Or that every line be delivered in the same, emotionless tone?
To put it simply, T'Challa was serviceable, but - ultimately - he lacked flavour.
8. The Vision Is Oddly Out Of Place
Why is it that Thor, a hammer-wielding God from an distant planet, can co-exist alongside the likes of Iron Man and Captain America and it feel like a natural fit, but the Vision cannot?
I don't know what it is about the Vision, exactly, but he's probably the one character addition to the MCU thus far that just doesn't work. I doubt it's due to anything that Paul Bettany is doing wrong, but more to do with the explanation as to how he came out - as a sort of melting pot between J.A.R.V.I.S. and an Infinity Stone. It's all a bit weird (which is really saying something for this franchise).
There's something off about the character from a tonal point of view, too; he's wearing a suit in Civil War, presumably as a means of humanising himself, but one can't escape the feeling that this character is from a different franchise - not to mention that his incredible power levels have resulted in a stumbling block for the writers. God-like in strength, they're having to play down his abilities and make them more vague, but it almost feels like a cop-out.
It seems reasonable to suggest that the Vision will perish when it comes time for Avengers: Infinity War, because Thanos is gonna need to get his hands on that stone in order to present himself as a major threat. The Vision can't exist without said stone, of course, so it's likely that this character issue will resolve itself soon.
7. The Second Act Becomes Dangerously Close To Tedious
After a kick-!*$% opening and a succession of genuinely interesting scenes in which the Avengers are introduced to the controversial idea of their being regulated, something unexpected happens: Civil War begins to drag.
Whilst the film has been almost unanimously praised by fans and critics alike as "perfectly paced," I'd argue the very opposite: that Civil War starts with a bang, introduces a neat concept and then spends an hour so meandering before it gets to the bit that everyone is waiting to see... that being the huge showdown at the airport, in which our two superheroes factions go up against one another.
Getting to this point, however, isn't anywhere as engaging an experience as it probably should be. The reason for this, I think, stems from the fact that Civil War has a lot of characters, and we move between them at such a speed that it's hard to invest in any of their individual plights to the degree that they deserve.
When you have a film built about introducing new elements, one by one, the drama tends to suffers somewhat, and that's what happens in the middle section of this film... we get a new villain, we get Black Panther, we get Spider-Man, we get Ant-Man... instead of being a film, it starts to feel more like a trailer. Thankfully, this digressiveness comes to a halt when the fighting begins, but - from a narrative viewpoint - Civil War's middle section flirts with tediousness.
6. Why Would Tony Stark Enlist Spider-Man?
Think on this one for a second: Tony Stark is motivated to call for superhero registration after he's made to feel bad for the death of a child, so - in order to make it right - he very quickly puts another child's life in danger?
It doesn't matter that Peter Parker is a superhero - the fact that 10 minutes of Civil War is dedicated to Iron Man convincing a teenager to come and do some fighting undermines the entire point of the film. It makes Tony's point null and void. It's not that the scenes in question are bad; in fact, they're awesome. It's that the very act of Iron Man inviting him in explicitly contradicts his whole argument.
And of all the decisions made by the characters in this movie, this is probably the only one that doesn't ring true at all; we can understand Tony's position on superhero registration, even if we don't necessarily agree with it, because we know how he feels about all the deaths he has inadvertedly caused - one of the first scenes of the film is spent getting us to understand exactly that.
It's hard to sympathise with the guy, however, when - at the drop of a hat - he's willing to involve a teenager in a dangerous situation in which he could easily die.
5. Ant-Man Feels Shoe-Horned In
Ant-Man is without a doubt one of the best things about Civil War; Paul Rudd is great as always, and the character is given the opportunity to make a "big" impression (get it?). Still, the little matter of how Ant-Man winds up being involved - and his decision to help out Team Cap - isn't anywhere near as convincing.
At the film's mid-point, Sam Wilson, having fought Scott Lang during the events of the Ant-Man so flick, suggests that he might be able to help out their team. Fair enough. But then Hawkeye appears to kidnap Ant-Man; they nab the guy without telling him what's even happening, stuff him into a van, and then Captain America delivers the message that, hey, they could do with his help.
It seems like lazy writing on the part of the filmmakers, though, because it would have been more logical - and far easier - for Hawkeye to have tracked down Lang, told him about the situation, and then had him turn up on his own accord. A van?
Also: Scott Lang spent the entire length of Ant-Man trying to do right by his young daughter and to ditch his criminal lifestyle. The instant Cap tells him that he'll be branded a wanted criminal if he joins forces with him, he agrees to do it with little thought. What about his daughter? Wouldn't he have outright refused on those grounds? Doesn't his agreeing to join go against the entire point of Ant-Man?
Not buying it.
4. Black Widow's "Double Cross" Didn't Ring True
Consider for a moment that, during the events of Captain America: Civil War, Black Widow is so convinced that Tony Stark is right in his decision to regulate superhero activity that she actively goes against the two Avengers she is closet with; Captain America and Hawkeye.
If you're willing to violently fight your two best friends over an issue, then it stands to suggest that you really, really, really believe in the cause. If you're not sure which side to take or you're impartial to it, then - more than likely - you'd opt to steer clear or try to play devil's advocate. But to fight - to actually enter into a combat scenario - means that you sincerely believe that you're doing the right thing.
The fact that Black Widow joins Tony Stark's team, battles Cap and Hawkeye, and then - when she realises that they won't stop their agenda - betrays her own side, makes little to no sense. She "double crosses" Team Stark on a whim, on the basis that Captain America refuses to give up. Did she ever expect him to, though? Why did she join the other team if she was ultimately going to side with him anyway?
Whatever was going on here, it wasn't very well thought-out or explained, and Widow's character was compromised somewhat in the process.
3. The Movie Didn't Have The Guts To Kill Rhodey
There was only one moment during the events of Civil War where my heart gave a sudden, unexpected jolt of anxiousness. "Oh my God, they're going to kill him," I thought, hand over mouth. It was brilliant, but it also wasn't meant to be.
The moment in question concerns the Vision, who misses a laser shot aimed at the Falcon during the film's central superhero fight, and accidentally winds up hitting Rhodey, whose War Machine suit malfunctions and cuts out. At this point, mostly due to the way the scene was edited with sad musical notes, I genuinely believed that Rhodey was going to die. That the battle would come to a sudden, sombre halt when it turned out that one of the characters had been fatally hurt.
Nope! After initially being diagnosed as paralyzed, Rhodey survives the events of Civil War... and by the end of the film he's learning to walk again, as if nothing happened. Marvel missed an opportunity here, though; Rhodey was the perfect candidate for a character death, because he's both well-liked and dispensable.
Unfortunately, just as they did with Nick Fury's death, the studio wimped out. That was a shame, considering that Rhodey's death might have cemented Civil War as a truly great film with proper consequences, in which the superheroes learn that they are just as much a danger to themselves as the villains are.
As it stands, nobody dies and the whole ordeal feels slightly less significant.
2. Baron Zemo Is A Rather Generic Villain
You can see what Marvel were shooting for with Baron Zemo; instead of opting for a generic, super-powered villain, complete with an unconvincing motive for wanting to destroy the world, the idea this time around was to give us a human villain, with his own highly personal reasons for wanting to destroy the Avengers.
So we got Zemo, a bad guy played competently by actor Daniel Brühl, but one ultimately lacking the spark to make him memorable in our minds.
In a way, it was a smart move to make the ultimate villain of the piece into somebody who was directly affected by the events which occurred in Sokovia; Zemo lost his entire family in the conflict, and so - knowing that he wouldn't stand a chance on his own - he sets about trying to get the Avengers to destroy one another via manipulation and through exposing some forgotten truths.
On paper this idea really works, but Zemo himself is a disappointment on-screen. Perhaps they should allowed Brühl chew the scenery a bit more, or written his character as a lot more mentally unstable, thus giving movie-goers something a bit more interesting to watch.
Granted, the fact that he's just a man is kind of the point, but there's understated and there's forgettable; Zemo, sadly, falls into the latter camp.
1. It Fails To Resolve The Whole Bucky Storyline
Nothing much has changed with regards to the Bucky scenario by the end of Civil War. Instead of the film reaching some sort of conclusion on this front, Bucky is literally frozen and handed over to T'Challa for safekeeping.
C'mon, Marvel... it was time for this narrative thread to be tied up!
After all, this storyline has pretty much exhausted itself; there have been two entire movies dedicated to a character who - let's face it - isn't even that interesting. Civil War needed to end with Bucky's death, or Steve Roger's death and Bucky becoming Captain America, or with Bucky being forgiven by the Avengers and subsequently joining the team so we could all move on with our lives...
Something - anything - other than the film doing nothing to advance his place in the MCU, which is ultimately what ends up happening here.
I'd lost interest in Bucky by the time Civil War was over - the whole ordeal has moved far too slowly. Putting the character on ice - literally - has the feel of a cop-out, like the studio couldn't decide what to do with Bucky so instead they opted to just hide him away indefinitely. This really needed to be resolved.
Do you agree with any of these problems? Share your reactions below in the comments thread.