Monday 28 December 2015

Book vs. Movie - The Hunt For Red October

The Hunt for Red October is awesome, both the movie and the book. Penned by the legendary Tom Clancy in 1984, THFRO is a great techno-espionage thriller. In 1990, director John McTiernan turned it into an award-winning action-thriller classic that's still talked about today. One hotly debated topic is whether the film is better than the book. So today we're going to find out which piece of media is superior in its story-telling and mood-setting. To do this we'll mostly be looking at the differences between the two in order to get a feel for which Hunt for Red October is the more effective experience in fiction. So climb aboard, let's cast off!
But first, just a quick recap of the plot. The Red October is the newest Typhoon-class missile submarine that runs on an experimental new propulsion system that makes it nearly invisible to sonar. Its disillusioned captain Marko Ramius and his handpicked officers decide to steal the boat and defect to the US after killing the ship's political officer. After learning of Ramius' intentions, the entire Soviet Northern Fleet takes to the Atlantic to find him under the pretext of a search and rescue operation, which doesn't sound too convincing to NATO, whose forces are placed on alert. Jack Ryan, a CIA analyst who has been following the mysterious circumstances surrounding the Red October's construction, learns of these developments and correctly deduces that the sub's officers are wanting to defect. He is then tasked with guiding the boat (and its critical tech) into the US and away from the pursuing Red Fleet. After some close calls and some intensive searching a US attack sub, the USS Dallas, manages to locate the Red October, whose officers fake a reactor meltdown in order to get the crew to leave. Ryan, Commander Bart Mancuso (the Dallas's captain), and a few more American officers board the Red October, rendezvous with the defecting officers, disarm a bomb planted by a GRU mole, and begin their plans to transport it into the States, when the group is suddenly attacked by the Konovalov, an Alfa-class submarine (commanded by Viktor Tupolev, a former student of Ramius') that trailed behind them. Due to Cold War rules of engagement, none of the subs are able to fire on the Konovalov, but eventually they outsmart Tupolev and destroy it. The Red October and its remaining officers are then escorted safely to Norfolk, Virginia.
Of course one major difference between movies and books is that books have a lot more room to get everything across and are thus typically longer than film adaptations. Since movies are only around two hours long, the screenwriters have to judge which elements are important enough to make it to the script. And so there are a few components of THFRO that were cut out for brevity's sake. For example, the movie completely leaves out the scenes where a NATO helicopter crashes and a Soviet submarine suffers a reactor meltdown during the search. Similarly, Skip Tyler's role is drastically reduced and no mention is ever made of CARDINAL, the CIA mole inside the Kremlin. Unfortunately there are also some elements left out that would have made the movie better. For instance, the book explains in more detail why Ramius is so disappointed with the Soviet system and why he wants to defect. More importantly, the book also explains how the CIA hopes to cover up its theft of the Red October once the US Navy links up with it. In the book their plan was to detonate a different sub in its place in order to fool the Soviets into thinking that the Red October has been destroyed. In the movie, there is no such plan; the Americans basically luck out and manage to destroy the Konovalov (whose location is unknown to the Red Fleet) in the exact spot the Red October's crew thinks their sub was scuttled. What're the odds?
Another aspect that was altered for the film was its audience; American movies typically cater almost exclusively to American audiences. As a result, the film changes this operation into one involving only US servicemen, whereas the Royal Navy played a significant role in the novel's events. In fact, the only Brit in the whole movie is a flight attendant! Another change that often happens to movie adaptations is that the book's “boring” parts are jettisoned in favour of giving the film a more dynamic and exciting feel to it. For this reason the movie got rid of a lot of the Kremlin/White House scenes and instead added air-dropped torpedoes, lots of countermeasures, and even a few explosions. Also, while the novel had two climaxes, the movie saw fit to combine them into one (possibly due to run time constraints). This has the overall effect of making the film slightly less realistic and more intense in its action. I'll leave it to you to judge whether that's a bad thing or not.
There are a few major differences between the film and the book that sort of change how the plot and atmosphere unfold, such as the aforementioned lack of the Americans' cover-up plan. Another big difference is that in the book the Soviets never ask the US Navy to help them sink the Red October. Instead they continuously maintain that they're conducting a search and rescue operation. Probably the biggest change is the climax. In the book, the Konovalov remains behind after the Soviet fleet is informed of the Red October's apparent sinking and follows the October's convoy for a while – believing it to be an Ohio-class US sub – before realizing its true identity. The October is damaged by a torpedo, but eventually defeats the Konovalov by ramming into it, splitting that sub in half. In the movie, Tupolev correctly guesses his former mentor's course and attacks with torpedoes immediately after the October links up with the Americans and expels its crew. Through some expert manoeuvring and a lot of countermeasures, the October and the Dallas manage to hit the Konovalov with its own torpedo, destroying it in full view of the Red October's crew, who believe they are witnesses to Ramius' last stand. Honestly both these scenes are really good, but it's pretty obvious which one is more realistic.
Other than that, the remaining differences are not all that important. I won't go into detail; here's a brief list of changes the movie made:
  • Ramius doesn't let his crew in on some aspects of his defection plan
  • Jack Ryan boards the USS Dallas, which he didn't in the book
  • the GRU agent shoots and kills Borodin instead of Loginov (in the film Loginov is the GRU agent)
  • there's approximately 4 Americans board the Red October instead of around 12
  • the film ends with the October being escorted to Maine, not Virginia
And that's all for the differences. In spite of them all I've got to say, the movie follows the book pretty well. The characters are spot on and the plots are more-or-less the same. But which THFRO is better? Well, they're both really exciting and intriguing. But if you pointed a Trident missile at my head and forced me to choose, I'd probably go with the book both because it has the ability to go into more detail and into the characters' heads and because its plot feels more realistic with more professionalism from all persons/organizations portrayed. But if you're looking for an adult-oriented spy/action movie that won't make you feel like you're watching a comic book, then go watch the movie. Or go and see both. They're worth it.

Stay tuned: next time I'll be evaluating the adaptation of the Patriot Games.

Saturday 19 December 2015

Movie Review – Star Wars: The Force Awakens

Here it is! A Star Wars movie from a different director, following a different set of heroes, set in a different time period of that galaxy far, far away. The whole world's been actively anticipating the release of Star Wars: The Force Awakens, setting records for ticket pre-sales (apparently the thing has already earned back its budget after just one day!) But is it the grand adventure that we've all hoped for?
YES! YES! What we have here is a post-1983 Star Wars movie that's done (mostly) right. Taking place around 30 years after Return of the Jedi, The Force Awakens sees the New Galactic Republic at (never-ending) war with itself as the Empire's remnants – the First Order – still control many star systems, many of which are fighting back under the banner of the Resistance, led by Leia Organa. Both sides are also desperately trying to find Luke Skywalker, the last Jedi. This is a story that is very similar Episode IV: A New Hope in that it takes you to various different locations and includes a variety of characters with different backgrounds and motives. It's a very fun and energetic ride which some might consider too derivative – I mean how many movies can one make about a band of rebel fighters defeating a giant planet-destroying battle station by exploiting its one glaring, self-destructive design flaw? – yet it still holds a lot of potential for new stories.
As was the case with A New Hope, our cast of main characters is made up of a bunch of lesser-known actors, but they each do extremely well: especially John Boyega as Finn and Daisy Ridley as Rey. These two characters in particular are truly interesting and complex and I look forward to seeing more of them in the sequels. Of course the old cast of our childhood heroes is back, including Harrison Ford, Mark Hamill, Peter Mayhew, and Anthony Daniels. There's also Carrie Fisher back as Leia, who I guess took up smoking since Return of the Jedi, since her voice sounds so weird. Maybe it's the stress of leading so many insurrections and the fact that Luke was lying when he said he'd show her how to use the Force.
The one character I didn't like (and the film's biggest problem) was the main villain, Kylo Ren. He's supposed to be this tortured soul who's at odds with himself, but he kind of comes off as a whiny, angsty teenager who throws temper tantrums. Also, could they have possibly picked an actor with a less intimidating face to play him? Cool voice, though.
Director JJ Abrams really knows his stuff. In addition to getting the best out of his actors, he treats us to some well-timed comedy and some exciting cinematography. However one thing that was really disappointing was that The Force Awakens doesn't make as much use of practical effects as you might have been led to believe. It's still very CG-heavy, but at least the CG is a bit better than it was in Revenge of the Sith from 2005. A lot of the classic sound effects have been changed, but I guess that's not really a big deal. What is a big deal is that John Williams is back with another great score, which draws less on the classic themes that we're all familiar with and tries more to establish its own.
In addition to having a similar plot, TFA also has a lot of references to ANH. Some of them are delightful, others are kind of dumb. The lightsaber duels this time around are great. Unlike the ones from the prequel trilogy, they go for a less choreographed/rehearsed spectacle look and more for a natural/spontaneous feel like those of the original trilogy.
One last concern I have is that since there's once again a great evil in the galaxy that needs to be confronted, does that mean that the mythos of the previous six Star Wars films is nullified? What happened to the whole “ Chosen One (Anakin) will bring balance to the force” thing?
Oh well, I only nitpick because I care. Overall, Star Wars: The Force Awakens is a spectacular adventure for moviegoers of all ages. If you're a Star Wars fan... who am I kidding? You've already seen it. If you're not a Star Wars fan but you're slightly interested, then go watch it. The Force is strong with this one!

Rating: four out of five.

Tuesday 15 December 2015

Star Wars Highs and Lows

There's a new Star Wars coming out! Isn't that rad? And it looks like it's going to be so cool. I'm pumped; I've got my opening night tickets ready to go, so expect my review of it to be up very shortly. Until then I've been going back and watching and admiring a lot of the previous films (mostly the original trilogy). When I was a teenager, I was a pretty big fan of the Star Wars series, especially since the prequel trilogy really brought the franchise to life just as I was coming of age. So to celebrate, I've compiled a list of the highs and lows of the Star Wars series just as I did for the James Bond series last month. Just note that obviously since I haven't seen Episode VII yet, nothing from that film will be included on this list. So here we go:

Best Movie: A New Hope (1977)
Worst Movie: Attack of the Clones (2002)
Most Action-Packed Movie: Revenge of the Sith (2005)
Best Actor: Ian McDiarmid as Palpatine (episodes I, II, III, VI, and later V)
Worst Actor: Jake Lloyd as Anakin Skywalker (The Phantom Menace, 1999)
Most Puzzling Choice of Actor: Samuel L. Jackson as Mace Windu? (episodes I, II, III)
Best Jedi: Obi-Wan Kenobi (all episodes)
Best Villain: Darth Vader (episodes III, IV, V, VI)
Best Villain Besides Darth Vader: Palpatine (episodes I, II, III, VI, and later V)
Best Villain Besides Darth Vader or Palpatine: Darth Maul (from TPM)
Least-Cool Villain: General Grievous (from ROTS)
Best Non-human Character: Chewbacca (episodes III, IV, V, VI)
Best Droid Character: C-3PO (all episodes)
Best Soundtrack: A New Hope
Best Opening Scene: Revenge of the Sith
Lamest Opening Scene: Attack of the Clones
Dumbest Moment: The awkward, cringe-worthy romance in Attack of the Clones
Funniest Moment: Yoda trying to steal Luke's stuff (from The Empire Strikes Back, 1980)
Most Pointless Moment: As a child, Anakin built C-3PO (TPM)
Worst Special Edition Alteration: Tie: Removing the Ewok victory song or CG-ing Jabba's singers (both from Return of the Jedi, 1983)
Most Hilarious Non-English Speaker: Nien Nunb (ROTJ)
Most Brutal Death: General Grevious (from ROTS)
Most Intense Lightsaber Duel: Qui-Gon Jinn and Obi-Wan Kenobi vs. Darth Maul (from TPM)
Best Battle Scene: Hoth (TESB)
Best Special Effects: Return of the Jedi
Worst Special Effects: Attack of the Clones
Coolest Ground Vehicle: AT-AT walker
Coolest Space Vehicle: Vader's TIE fighter
Most Interesting Planet: Tattooine
Dumbest Line: “I don't like sand...” (Anakin, AOTC)
Who Shot First? Han. No argument on this point.

Saturday 12 December 2015

Top 10 Biggest Military Losers of Modern History

You may not have known this, but I'm a pretty big fan of modern history. From growing up with history books and studying it in university, I love learning about past cultures and ideas, and I am especially intrigued by the history of armed conflict. Scarcely a week goes by where I don't read a book or watch a movie about some past struggle. What I find curious, though, is that you'll often see the great debate about “which civilization has won the most wars throughout history”, when hardly anyone ever asks about who has lost the most. So that's what I'm here to discuss today.
Now before we begin, I'd just like to make clear that when it comes to war there are no winners, only losers; it's just that some states lose more than others. So for this reason, my list here takes human and material losses into account as well as the level of tactical/strategic victory achieved versus the sheer number of conflicts outright lost. This list will focus only on wars (not including internal coups or rebellions) fought after 1800, for two reasons: first is that most of today's countries didn't exist back then and, second, because this is the era of history I'm most familiar with. And as always, this is just a matter of opinion, so feel free to disagree.
Dishonourable mentions: Bulgaria, Finland, Germany, Iraq, Italy, Syria

10 – Hungary
In 1848, Hungarian nationalists started a revolution to gain independence from the Austrian Empire. After nearly succeeding, they were crushed once the Russians decided to lend Austria their aid. Later, Hungary became a semi-autonomous kingdom within the Austro-Hungarian Empire. It was in this state that Hungary sided with the Central Powers of the First World War. After losing in November 1918, the empire was broken up. The newly independent state of Hungary was defeated the following year in a brief war against Czechoslovakia, Romania, and Serbia. Hungary sided with the Axis forces during the Second World War and participated in the invasion of the USSR. It didn't go well; the Soviet Army turned the tide, Hungary suffered heavy casualties, Hungary's government tried to surrender, the Nazis then staged a coup, set up a puppet government, and occupied the country. The Soviets invaded Hungary, laid siege to Budapest, and conquered it in February 1945. In 1956 the Hungarians rebelled against continued Soviet domination, but the uprising was violently crushed. The nation remained under occupation until 1991.

9 – Austria
Between 1792 and 1809, Austria lost no less than four wars to the French who twice occupied Vienna. Austria finally beat France in 1814. But the French – with some Sardinian and Italian help – got their revenge by defeating Austria in 1859 in the Franco-Austrian War. Defeat again came at the hands of the Prussians during the Austro-Prussian War of 1866. After arguably initiating the First World War, Austria-Hungary took the side of the Central Powers. It suffered total defeat in November 1918, losing much of its territory. After being annexed by Nazi Germany in 1938, the Austrians fought as part of the Third Reich during the Second World War. The nation lost once again and was under Allied occupation until 1955. Since then Austria has remained strictly neutral in international affairs. And really, who can blame them?

8 – France
Although Napoleon's France conquered and commanded much of Western and Central Europe in the early 19th century, the First French Empire met its end at Waterloo in 1815. Under imperial ambitions, the Second French Empire, under the leadership of Napoleon III, invaded Mexico in 1861. Unable to cope with the Mexicans' guerrilla warfare tactics, the French withdrew in 1867. Not long after – in the Franco-Prussian War of 1870-1 – an alliance of German states swiftly crushed and humiliated the French army and occupied the country's northern half. Although France was on the winning side of the First World War, the victory's human, material, and economic cost was so devastating that most Frenchmen today consider it a loss. During the Second World War, the German blitzkrieg forced the Third French Republic to surrender after only a month and a half of combat. The northern half of the country was again occupied, while the southern half was ruled by a collaborationist regime, which was also later occupied. Despite the bravery of various resistance groups, France was not fully liberated until the summer of 1944 when the Western allies invaded and drove the Germans out. Following WWII, France then lost two major colonies after losing long and bloody campaigns: Indochina (1946-54) and Algeria (1954-62).

7 – Russia/USSR
Russia's military history has been very up and down over the centuries. After defeating Napoleon's armies once and for all in 1815, imperial Russia spent the next century winning a multitude of wars against Turkey, Poland, Persia, Egypt, and China, but also losing in several wars against the French, the British, and (at the time, surprisingly) the Japanese. Russia entered World War One on the side of the Entente Powers, where it proved completely ineffectual. Not only did Russia lose more than two million lives and tons of territory, but the nation was totally bankrupt and on the brink of a Bolshevik revolution. From 1917 to 1922, the nation was engulfed in Civil War; i.e. Russia was on both sides, so no matter what, Russia would lose. Around three million lives were lost, and of course, the bad Russians ended up winning, forming the Union of Soviet Socialist Republics. The new state tried expanding its union by waging war with neighbouring states in Eastern Europe and Central Asia with mixed success. The Second World War saw the USSR capture the Baltic states, and conquer half of Poland and parts of Finland. But in June 1941, the largest invasion in human history was launched against the USSR. The Eastern Front of WWII was the largest and most destructive military confrontation ever, and by the time it ended with the capture of Berlin in May 1945 around 27 million Soviet citizens had perished. During the Cold War (which the USSR ended up losing in 1991) the Soviet Union asserted its power over its sphere of influence, successfully pacifying uprisings in Hungary (1956) and Czechoslovakia (1968) and assisting in wars against Western-allied governments such as Korea (1950-3). However, its attempt at propping up the Marxist government of Afghanistan (1979-89) via invasion and occupation was a costly and unpopular mistake. Since 1991, the new Russian Federation has participated in many small regional wars, some successfully (against Moldova, Georgia, and now Ukraine), some not so much (against Chechnya and the Taliban).
Update 10Jan18: I originally mentioned here how Russia's fight against ISIS wasn't going well. But since writing this article history has proven me wrong; it looks as if ISIS is in serious trouble!

6 – Egypt
After three wars against the Ottoman Empire in the 1830's, the Egyptians had finally won their independence. But in 1882, they lost to the British who then ruled the land as a protectorate until after WWII. Egypt took a leading role in the Arab League's war against the new state of Israel in 1948 and suffered an embarrassing defeat. In 1956, Israeli, British, and French troops overpowered the Egyptian army and captured the Suez Canal in just seven days before the UN forced them to withdraw. It wasn't as bad as in 1967 when Israel again attacked and routed the Egyptians during the Six-Day War. During the Yom Kippur War of 1973, the Egyptians and Syrians made some impressive initial gains from their surprise attacks. However, the Israeli Defence Force promptly recovered and soon drove its adversaries back beyond their starting positions. Having lost no less than four wars to the same country in the span of 25 years, Egypt signed a permanent peace treaty with Israel in 1979.

5 – China
China was defeated in both Opium Wars against the British and French in 1839-42 and 1856-60 respectively. With its loss to Japan in the 1894-5 Sino-Japanese War, a severe blow was delivered against the Qing Dynasty. The anti-imperialist Boxer Rebellion of 1899-1901 was handily put down by an invasion force of Japanese, American, and various European troops. In 1931, imperialist Japanese forces overran and annexed Manchuria, and then launched a full-scale invasion of China in 1937, interrupting the civil war that began in 1927. Despite losing major territories and more than 20 million lives, the Chinese fought on. The Japanese withdrew after surrendering to the Allies in summer 1945. Less than a year later the civil war resumed, and since this was a civil war, that means that China was on both sides, thus assuring that the Chinese would lose. And wouldn't you believe, the bad side ended up winning, too: double loss.

4 – Poland
After gradually being partitioned away to other states in the 18th century, the Poles tried many times in the 19th century to regain their independence. At first, they cast their lot in with Napoleon's empire, but that didn't work. At the Congress of Vienna, Poland was split between the victorious Prussians and Russians. Subjugation to foreign emperors provoked a number of nationalist uprisings between 1830 and 1905, all of them ruthlessly suppressed. After the First World War, in which the Poles fought on both sides, Poland became an independent state for the first time in 123 years. Through a series of regional/local wars from 1918 to 1920 Poland managed to expand its arbitrarily-drawn borders. However, the Polish military collapsed under the weight of a joint Nazi-Soviet invasion in September 1939, sparking the Second World War. Although Polish armed forces continued to wreak havoc abroad, Poland itself was absolutely devastated by the German occupation. Despite the best efforts of the sizable Polish resistance movement, whole cities were razed and the region became the main stage for the Nazi's Holocaust. By the time the war ended, Poland's population had fallen by nearly 30%, the highest of any nation involved in WWII. Since then Poland has remained a bit more peaceful, focusing more on its commitments to its Warsaw Pact and (now) NATO brethren.

3 – Bolivia
Under the inspiration of the legendary Simon Bolivar from whom the country takes its name, Bolivia won its independence from the Spanish Empire in 1825. And it's pretty much all been downhill since. Three years afterwards, Bolivia was invaded and defeated by Peru. In 1835, the two countries formed the Peru-Bolivian Confederation. It didn't last; the confederacy was broken up after losing to the Chileans and Argentinians in 1839. Later during the War of the Pacific (1879-83), Chile again defeated a Bolivian-Peruvian alliance and was awarded with Bolivia's coastal provinces and other resource-rich territories. From 1932 to 1935, Bolivia fought against Paraguay in the costly Chaco War, which it lost despite having the larger and better equipped army. Having lost more than half of its original territory since independence due to conquest, Bolivia is today the poorest country in South America.

2 – Spain
After six years of guerrilla warfare, the Spaniards finally expelled Napoleon's Grande Arm̩e in 1814, but the war brought about a significant social and economic upheaval of Spanish society. This turbulence resulted in Spain's overseas colonies revolting. From Boliva in 1809 to Equador in 1822, Spain lost war after war trying to keep its grip on its American territories, even going so far as (unsuccessfully) starting new wars to reconquer them. Between 1833 and 1877, Spain underwent three civil wars known as the Carlist Wars; since Spain fought on both sides, that means that Spain lost all three. After losing the Spanish-American war of 1898, Spain lost Cuba and Puerto Rico Рits last remaining colonies in America Рas well as Guam and the Philippines to the USA. From 1936 to 1939, Spain once again descended into civil war (possibly making it the country with the most civil wars ever!), bringing about severe destruction and numerous atrocities. Since the 1990's Spain has focused more of its attention on its NATO commitments.

1 – Turkey
By the 19th century, the Ottoman Empire – in which Turkey was the centre – was undergoing an irreversible decline, earning its moniker as the “sick man of Europe”. In the 1800's it lost three wars each to both Russia (in 1812, 1829, and 1878) and Egypt (1832, 1839, and 1840). Also, the Greeks gained their independence by defeating the Ottoman Turks in 1827. After losing a war to Italy in 1912, the Turks found themselves in another war, this time losing to the combined forces of the Balkan League. This defeat cost the Empire nearly all of its remaining European territories. The Ottoman Empire entered the First World War on the side of the Central Powers. Its defeat in 1918 brought about the final dissolution of the empire and the occupation of Turkey. The Turks finally scored some victories from their War of Independence (1923) and the invasion of Cyprus (1974).

Tuesday 1 December 2015

Movie (Sort of) Review – Halo: Nightfall

OK, I know that Halo: Nightfall isn't technically a movie, it's a webseries. But the way I watched this was in a collected format on blu-ray which came out earlier this year, so close enough. I also decided to write about this movie since there doesn't seem to be that many reviews for it floating around. A couple weeks ago at a Halo tournament with a bunch of friends I was voted MVP (for some reason; I really didn't play all that well) and was awarded with this (thanks, Dylan!). Now let me just quickly tell you where I'm coming from, here: back in the day – from around 2005 to 2009 – I was a huge Halo fan. I played all the games, read all the novels, and listened to the soundtracks. But after a while, I guess I got tired of it and I fell out of the loop. I eventually did play Halo 4 – the first few levels – but it just didn't feel right and I couldn't bring myself to finish it. And I'm not planning on playing Halo 5 any time soon (but that's a story for another time). So can this Ridley Scott-produced series/movie/whatever be the jumping-on point that I needed? Let's find out!

Halo: Nightfall starts off with some ONI (office of naval intelligence) guys casually following an alien whose species was never shown in the games or novels – dangit, three minutes in and I'm already lost! Way to go, guys! Well, I looked it up and it turns out that this guy did appear in the comics. OK, fine, whatever. So our plot, which takes place between the events of Halo 4 and 5, follows ONI agent Jameson Locke trying to shut down a network of Elite terrorists. He does this by tracking down where the materials for their chemical weapons are coming from. This leads his team to a place that should be familiar to all Halo players, except this place is now occupied by a grave threat. The location for this film is a pretty cool idea, though it doesn't have all that much payoff to it. Unfortunately, the story winds up falling into standard survival movie territory that you've already seen lots of times before. It's also supposed to serve as an origin story for Locke: give away the ending much? There's only about three interesting characters, but at least the acting is all-around decent.

Nightfall isn't like traditional Halo stuff that we're used to. There's pretty much no gunfights or battle scenes. That's rather sad since not only is Ridley Scott great at doing battle scenes (Black Hawk Down) but also because shooting stuff is kind of what Halo is all about. Likewise, there's only three alien species in this game: one we haven't seen before and another which displays abilities radically different from what we've seen in any other media. (Seriously, if this species did behave this way in the games, the player would get wrecked all the time.) And as I mentioned earlier, the movie takes place in a familiar setting, but it just looks unrecognizable. Also, why the hell are there so many of those aliens at this place anyways?

The production was alright. The sets, environments, props, and costumes all look good. The CG effects, not so much. The cinematography was OK, not much to say there.

When I was given this movie, I jokingly asked, “Is it like Predator, but on Halo?” It turns out that that joke was actually fairly accurate. The only difference is Halo: Nightfall's plot is less original and it has a Halo paint-job. Mind you, it's a rather thin paint-job with familiar guns that are scarcely fired, a few aliens that behave in ways we've not yet seen, and a location that is unrecognizable. Overall, this barely feels like a Halo movie. If you want to get into Halo 5 and other subsequent media, you can probably skip this and it wouldn't make a difference. And if you take away the Halo name and judge it on its own, then all you're left with is an ordinary, by-the-numbers survival movie that's set in space. In short, Halo: Nightfall is watchable, but also forgettable. For die-hard fans only.


Rating: two-and-a-half out of five.