10 Terrible Movie Sequences That Should Have Been Awesome
10. Taking Fingerprints from a Shattered Bullet - The Dark Knight
Even great films have bad moments. And in the near-perfect film that is The Dark Knight, there exists a sequence that is both confusing and stupefying: the moment when Bruce Wayne takes fingerprints off of a shattered bullet. After finding two dead bodies in an apartment left to him by the Joker, Batman cuts out a section of brick containing stray bullets left at the scene. Jim Gordon asks if he's taking ballistics from a shattered bullet, to which Bats replies: "No. Fingerprints." The Scene: Next, we see Bruce back at the Bat bunker, setting up an experiment using an automated Gatling gun and four blocks of masonry. The gun fires a bullet into each, Bruce finds the block that closest resembles the block from the crime scene, and scans it with some fancy laser. He takes it to Lucius Fox, who digitally reconstructs the shattered bullet, using Bruce's new sample as a guide. This gives them the thumbprint left by the shooter as he loaded the bullets into his clip. Why It's Terrible: It took me a while to type up that last paragraph, because the scene plays quickly, explains nothing, and then carries on. A few questions are raised by that sequence: Did Bruce have this thing just lying around in case he needed to do something like this? How does he accomplish all of this in one night? And what the hell just happened!? In an effort to show Batman's incredible detective skills, Christopher Nolan added a scene that just feels ridiculous. Couldn't they have found a simpler, more comprehensible way of showing Batman finding fingerprints? If you want to leave the scene in there, fine. But just add one thing: Alfred needs to ask Bruce what he's doing. That way, Bruce can explain it not only to his butler, but to the audience as well. A little exposition goes a long way, and could give us a glimpse into the brilliant mind of the Batman. The scene is cool, it's just hard to follow. Note: Badass Digest has a great article breaking down the science of this scene, which I highly recommend checking out here.
9. Inside Davy Jones' Locker - The Pirates of the Caribbean: At World's End
The second film in the Pirates of the Caribbean franchise, Dead Man's Chest, ends with a surprising and exciting turn of events: Elizabeth Swan handcuffs Jack Sparrow to the mast of a Black Pearl which is minutes away from getting swallowed by the ferocious Kraken. Jack breaks free of his chains but is unable to escape the sea monster devouring both him and his ship. The Scene: At World's End, the next film in the series, picks up pretty much where Dead Man's Chest left off. The crew is trying to find a way to rescue Jack, who has been cursed to rest in Davy Jones' Locker. We don't see Jack again until about 45 minutes into the film, where he is slowly losing his mind aboard the Black Pearl, which is stranded in the middle of a barren desert wasteland. Why It's Terrible: The portrayal of the Locker itself is pretty cool, manifesting itself as a soul's worst fear. Therefore, its appearance changes depending on who is imprisoned there. Jack's driving wish in life was to sail the sea forever, so a barren wasteland devoid of any ocean would be his worst nightmare. With that said, the sequence is handled exceptionally poorly, relying on slapstick humor at the expense of any sort of character development or intriguing story beats. Even for a Disney movie, the scene of Jack chasing a peanut around the deck of the Pearl is incredibly childish and goes on for far too long, taking away any gravity the sequence could (and should) have had. The film never really tells us what's going on inside the Locker, and how it pertains to Jack personally. Killing Jack in the second movie was a bold move, and audiences had to wait a year after the events of the second film to see what happened next. Then, after a 45-minute buildup, this is what we get? The look of the Black Pearl stranded in a wasteland remains one of the most iconic and brilliant pieces in Gore Verbinski's trilogy. It just would have been nice for the film to take its events seriously, rather than using the scene for slapstick humor, which derails the film until the crew comes to rescue him.
8. Hal Jordan Makes His First Save - Green Lantern
Warner Bros.'s failed 2011 film Green Lantern was a mess on several levels, but one scene in particular stands out as especially terrible: the scene where Hal Jordan makes his first public save. All superhero films have a similar scene, showcasing the hero's debut in a dramatic, memorable way. In Richard Donner's Superman the Movie, Clark saves Lois from a crashing helicopter. In Green Lantern, Hal Jordan saves a party from a helicopter using an imaginary Hotwheels track. The Scene: Yep, a Hotwheels track. The villain of the story has telekinetically sabotaged a helicopter in an attempt to murder his own father, and Hal Jordan activates his power ring in time to save the aircraft by creating a Hotwheels track and a hot rod. The car catches the helicopter, and rides along the track until it lands safely on the ground. Why It's Terrible: The ring of a Green Lantern grants the wearer the power of will. Whatever he or she imagines, they can create. In Hal Jordan's debut moment of heroism, he manages to save a crowd of people by thinking of a toy he saw earlier in the movie in his nephew's room. The scene not only shows us Hal's complete lack of imagination, but is conducted with terrible CGI work and bad editing. The scene comes off as incredibly cheesy, melodramatic, and lame product placement.
7. The Jetpack Scene - Kick Ass
Near the end of Matthew Vaughn's 2010 film Kick Ass, Hit Girl has broken into the penthouse of Frank D'Amico and killed most of his men. When she gets cornered in the kitchen and stares down the barrel of a bazooka, it appears that the young badass has finally met her match. The Scene: Kick Ass then appears outside of the apartment on a jetpack (which is equipped with twin Gatling guns) which he uses to take out the remaining thugs. Kick Ass then kills D'Amico with the bazooka the henchman was going to use, and he and Hit Girl escape the apartment building via the jetpack. Why It's Terrible: Though the film has dedicated itself to presenting a realistic setting, it's fair to assume that audiences are willing to suspend their disbelief. If a character like Hit Girl can exist in this world, why not a jetpack? A jetpack with gatling guns should be awesome, and if the sequence had ended after the initial reveal, audiences may have been able to give it a pass. Instead, our two heroes ride the jetpack to safety, flying across the city in an overly cheesy, badly computer-generated sequence with even cornier music. It completely contrasts the intense, violent set piece that came before it and has since become one of the most eye-roll inducing moments of the film.
6. The Beach Scene - X-Men First Class
X-Men First Class, Matthew Vaughn's 2011 X-Men prequel film, was an overall enjoyable flick that helped revamp a failing franchise. Though the film isn't without its missteps, it is definitely one of the better films in the franchise, and for all intents and purposes, should have been a complete reboot. Instead, it created a ton of problems within the already convoluted X-Men film continuity (I encourage you to read fellow WhatCulture writer Alex Antliff's article on the matter here). This is thanks in no small part to the incredibly rushed, awkward beach scene that takes place after the film's Cuban Missile Crisis climax. The Scene: After Erik Lehnsherr (Magneto) kills the man who ruined his life, Sebastian Shaw, he dons his iconic helmet and walks onto the beach to confront Charles Xavier and his team of young mutants. It's the moment when we finally see what drove these two friends apart, and what ultimately paralyzes Xavier. Why It's Terrible: The scene feels incredibly forced, and comes off more as a studio note than a decision of Vaughn's. When Erik delivers his speech (in a funny accent, for some reason), the scene comes off as contrived and what he's saying doesn't really match the motivations he'd shown throughout the film. Then, when Erik deflects a bullet that then paralyzes Charles, things really start to derail. What should have been a poignant, character defining moment is instead thrown into a quick three second sequence. Erik apologizes, but goes about his business anyway and takes Mystique (and a couple other mutants we don't care about) with him. The confrontation between Erik and Charles is undoubtedly one of the most important moments in the entire franchise, and unfortunately it just doesn't play organically, leaving audiences asking, "Wait, that's it?"
5. Neo Meets The Architect - The Matrix Reloaded
Speaking of moments that didn't live up to their potential, let's discuss the moment Matrix fans had been hoping for: an explanation about what the hell was going on. The Scene: Towards the end of the second film in the trilogy, The Matrix Reloaded, Neo comes across a man who calls himself The Architect, the creator of the Matrix. The two have a long discussion about past versions of the program, the choice that Neo must make if he wants to save humanity, and... uh... Why It's Terrible: Wait, what did he say?! The scene itself is one tremendous exposition dump, and both Neo and the Architect speak in dry, emotionless tones, which just makes the sequence incredibly boring. The Architect speaks quickly and intelligently, but is giving the audience so much information that it's hard to keep up with what he's saying. The television screens in the background are incredibly distracting, and the camera continually zooms in on one, then phases back to Neo. It's a bit disorienting, and though it created quite the debate, the scene was ultimately just a head-scratcher. The Matrix trilogy is known for being incredibly cryptic and open for interpretation. But a scene as important as this one maybe should have been accomplished a little differently. As I mentioned earlier in this article, a bit of exposition goes a long way, but a mess of exposition creates problems of its own. There is a lot of great information here, if you can decipher what The Architect is saying. In a trilogy rot with dense, enigmatic ideas, it would have been refreshing for a character to finally just speak clearly for once.
4. The Jungle Chase Scene - Indiana Jones And The Kingdom of the Crystal Skull
Indiana Jones and the Kingdom of the Crystal Skull was Steven Spielberg's long-anticipated follow up to his brilliant trilogy of films featuring the fedora-clad adventurer. It received mixed to negative reviews and to this day is largely seen as an unwelcome entry in the series. This is due to a number of reasons, one of which is the casting of Shia Lebeouf as Mud, Indy's son, and the use of over-the-top, unnecessary CGI. The Scene: Near the end of the film, Indy and co. are being chased by Soviets through a jungle. The scene contains many action beats, including a sword fight between two people on the hoods of two Jeeps, hundreds of fire ants, many dead Soviets, and Mud swinging through the trees with monkeys. Why It's Terrible: Yep. You read that right. Mud gets separated from the group, and reunites with them by swinging through the trees like a rockabilly Tarzan. He's accompanied by a ridiculous number of CGI monkeys, and when he gets back to the Jeeps, the film just moves on as if nothing bizarre just happened. It's not the only problem with the incredibly overbloated chase sequence, but it's definitely the aspect that has been given the biggest amount of ridicule amongst audiences. The other films in the franchise contain some great chase sequences, and there's even a chase at the beginning of this film (where Indy is chased by Soviets through the famed warehouse seen at the end of the first film) that is filmed with the greatness we expect from Spielberg. This sequence, however, just goes on for way too long and contains too many baffling parts to keep straight.
3. Obi Wan Vs. General Grievous - Star Wars Episode III: Revenge of the Sith
The Star Wars prequels are filled with problems and missed opportunities, especially when it comes to the use of antagonists. Darth Maul was one of the franchise's most memorable characters, and yet was killed off in Episode I. Count Dooku was an okay bad guy, but Lucas failed to do anything interesting with his character. Then came General Grievous, a four-armed cyborg general trained by Dooku in lightsaber combat. He's the Supreme Commander of the Droid Armies, and known for taking the lightsabers of fallen Jedi as trophies (which he later uses against his foes). He's cool, badass, and ultimately, kind of a waste. The Scene: Obi Wan tracks Grievous to the planet Utapau, and challenges the General in combat. Grievous laughs, shrugs off his cloak, and reveals that his two arms actually separate into four. He then lights four lightsabers and begins to spin them in front of himself like a deadly propeller. Why It's Terrible: Within seconds, Obi Wan cuts off Grievous' hands, effectively disarming him and turning what could have been a unique, epic fight sequence and turning it into a drawn-out, overly computer generated chase through Utapau. Take a second and look at the picture of Grievous shown above and tell me that the fight that could have ensued between him and Obi Wan wouldn't have been awesome. Lucas was obviously holding off on big lightsaber battles until the end of the film, but it's a shame that they would introduce such an iconic, unique villain and then not use the coolest thing about him. Note: I highly recommend viewing the original, hand-drawn Clone Wars TV series. Grievous hunts a few Jedi Knights stranded within a broken down starship, in a brilliantly executed, horror-esque sequence.
2. When Harry Met Spidey - Spider-Man 3
Spider-Man 3 is the often ridiculed end to Sam Raimi's trilogy featuring everyone's favorite Web Slinger. After two incredibly successful movies, anticipation was through the roof for the third film. Unfortunately, it was a complete misfire, rife with too many villains, a messy plot, and strange directorial choices (the dancing scene shall forever go down in history as one of the worst ever). One aspect of the film that unfortunately suffered was the moment when Harry confronts Peter about killing his father, something he does by attacking Peter using his father's old Green Goblin toys. The Scene: An unsuspecting Peter is attacked by Harry while walking home one night, and the two do battle in the air, flying between (and through) buildings and alleyways. Peter struggles to not only explain to Harry what really happened, but hold on to a ring Aunt May gave him so that he can propose to Mary Jane. Harry is equipped with a slew of pumpkin bombs and one of his father's gliders, whereas (in a cool visual choice) Peter is merely in his civilian clothes. Why It's Terrible: The scene is terrible for a number of reasons. First of all, Harry looks completely ridiculous in his wet suit/ski mask costume. Secondly, the scene is completely overblown with CGI, and it really shows. The alley scenes look particularly bad. And thirdly, the scene ends as quickly as it began, with Harry hitting his head and getting amnesia. It's not exactly the confrontation that fans were hoping for, and after a 2 film build-up (and a great revelation at the end of Spidey 2 where Harry unmasks Peter), fans deserved better.
1. The Rise Of Lord Vader - Star Wars Episode III: Revenge of the Sith
After sitting through three mediocre prequel films, the moment arrived that fans had been waiting for: the appearance of Darth Vader. Sure, Anakin was technically Darth Vader about 30 minutes ago after killing Mace Windu and surrendering to the Dark Side, but his transformation wouldn't be complete without putting on the suit and adopting the oh-so-badass voice of James Earl Jones. The Scene: It's a beautifully filmed, haunting sequence, when Palpatine watches over a brutally beaten and burnt Anakin writhing in pain on a metal table, medic droids hurriedly attaching metal limbs to his body. The iconic helmet is lowered down onto his face, and with a hiss, sealed shut. Lucas has brilliantly filled the scene with smoke so that when Vader breaths for the first time, we see it happen. Then, in a chilling Frankenstein homage, his table is raised and the Dark Lord of the Sith is born. Why It's Terrible: Moments later, Vader asks if Padme is safe. When he is told by Palpatine that he caused her death, he loses it. His force abilities crush the very robots that helped save his life. The room shakes, his arms break free, and he tilts his head back to lets out a wail: "NOOOOOOOOO!" The moment is absurdly awkward, and unintentionally hilarious. It will forever go down in history as the final nail in the coffin for the prequel trilogy. It's the one moment Lucas needs to get right, the one scene that will make it all worth it. We finally, finally get to see how Anakin becomes the powerful, intimidating figure we know and love. The sequence was undoubtedly one of the most important in the entire Star Wars saga, and was ruined within a matter of seconds. Obviously, this is not an all-inclusive list of terrible sequences that could have been awesome. There are hundreds of them, in films we love and loathe. Are there any you wish had made this list? And how would you have made these terrible scenes awesome? Let us know in the comments!