Continuing my hopping around in the AHM storyline, I picked up issue #13 today. And once again, I found it a very enjoyable set of stories, based around two of my favorite G1 characters.
Ironhide - This particular story reminds us that Ironhide's been around a long time, and seen some ugly things. And at the beginning of the story it's finally gotten to be too much, thanks to his beatdown of Mirage. He and Optimus Prime sit down, have a drink or three and discuss their friendship from where it started to where it is now. That's a nice angle for the writer to take, because Optimus Prime doesn't have that many friends. He's in charge, and by necessity has to be somewhat distant from those under his command. Ironhide's one of the exceptions, and it's good to see that demonstrated, both via the conversation between the two and via flashback.
I've been a fan of Don Figeroa's art for several years now, and despite a poor first impression of his new style a few months ago when I first saw the art preview from the ongoing series, I find here that I like the new art quite a bit more than I thought I would. Don's art has always been detailed and expressive, and that trend continues here. The Transformers' eyes resemble the movie designs, but a lot of the new art is just altered facial styles and added layers of detail. It works for me.
Starscream - I've always had a disagreement with Starscream's portrayal as an incompetent coward. It doesn't match his original bio, and it doesn't make sense that he'd rise to be Megatron's lieutenant if he wasn't capable of doing the job. I think the "whiny coward" is a relic of the old cartoon, and one that needs to be disposed of. This issue does a good job of portraying Starscream as ambitious and egotistical, but not so much that it overwhelms his good sense. He knows that even with Megatron out of the way that his position isn't assured. Razorclaw is sure to challenge him, and there's always the possibility that Megatron will recover as well. When Shrapnel offers to finish him off, Starscream is unwilling to do that because he knows those loyal to Megatron will take revenge.
And then there's the Matrix, something Decepticons apparently can't use, and which Starscream sees no value in having, since it sits there and looks pretty and nothing else. But he's quick to figure out that the reputation may be enough to solidify his hold on the leadership based on Shrapnel's reaction. In the end, his body language suggests that he knows he's stepped in it, and that his lie is bound to come back and haunt him. I'd like to see some follow-up to this. I'd enjoy reading a plot where Starscream finally got what he always wanted and found that he hated it.
I didn't care for this artistic style as much. It got the job done and illustrated the story, but it's just not to my liking.
Overall, the second best issue of the "coda" issues.
Sunday, October 25, 2009
All Hail Megatron volume 2 TPB
I take it from reading the discussion that the story didn't work for some of you. I enjoyed it quite a bit, and perhaps having six issues in one volume improves the pacing and ties things together more effectively. I can't say, having not read individual issues. I enjoyed the story very much.
The volume begins with the creation of the Insecticons and the Swarm, and I was happy to see some art by EJ Su, whose art I liked quite a bit in Infiltration and Escalation. Thundercracker is not happy about the experiments used to create the Insecticons and the way the cast-offs are treated. "Our own kind!" he keeps insisting. It's little scenes are reactions like this that make him and others more than just background filler characters. And there are other similar scenes here and there.
The Autobots are on the run, and the way in which they were defeated and sent to Cybertron is explained by Jazz to Kup in a flashback. Devastator is the ace in the hole that he was back in the early G1 days, when he was the only combiner. It's odd that Megatron doesn't just have the Autobots all killed rather than sending them to Cybertron to be eaten by the Swarm though. I'm not sure I buy that, unless he thought they might be needed later. It's an odd choice. Regardless, Prime manages to close the portal, leaving the Autobots alive but trapped. So they're on the run, leaderless and pursued by crazy mutant Insecticons.
It's a rough scene when Ironhide beats up Mirage, convinced that he's the traitor and unwilling to hear him out. Sunstreaker, the actual traitor, stands there and watches, and it's clear this later plays into his decision to confess and end it all, as his consicence gets the better of him. As an aside, it's nice to see the Universe versions of Sunstreaker and Sideswipe used in the story, and also Mirage I believe. I'm not sure if there were others, though I did see Dropshot and Tankor/Octane near the end, which was a nice touch. Sunstreaker's apparent death is the end of a downward spiral for a proud Autobot who was violated badly by humans and who couldn't get past that. His agreement with Starscream sealed the deal, since the dire situation the Autobots find themselves trapped in can be laid directly at his feet. I'm not convinced that he's dead, since he survived the explosion and the fall as shown in issue #14, even if he is in bad shape, but that's neither here nor there. Death is meaningless in comics.
Starscream goes around gathering support for a coup, fully aware that Megatron knows what he's up to. I find the portrayal of Starscream very interesting here. He's ambitious as always, but he also genuinely seems disenchanted with Megatron's leadership and lack of goals, and he seems genuinely to believe in the Decepticon cause rather than simply being out for power. Megatron tells him at one point that he sees Starscream ultimately succeeding in wresting leadership from him one day, and that's enough to rally Starscream behind Megatron against the Autobots. And he refuses to use the opportunity to simply kill Megatron when he's helpless and take his place, saying that leadership must be earned. This seems to be a Starscream that isn't stupid, but recognizes that he's got to have the respect of the troops in order to lead them, and killing an already helpless Megatron isn't likely to get him that respect.
Omega Supreme is one of my favorite figures and characters, so having him show up and save the day was great. His explanation of how he survived the attack sent to finish him off ("I am Omega Supreme") says it all.
One of the themes of this series is the way in which various characters pay for deals with the other side. Sunstreaker is the obvious example, but Thundercracker strays from prevailing dogma and gets shot in the head by Skywarp. Drift is rejected by Thundercracker as a traitor. Ironhide beats Mirage badly because he believes Mirage is a traitor. Both sides are so locked into their causes and beliefs that there's no room for compromise. And considering how long they've been fighting, it's not surprising. But it makes one wonder how peace would ever be possible, assuming the war was ever decisively won by either side. The overall theme of this story seems to explore this idea to some extent, as the Decepticons stagnate without a challenging enemy to fight, and the Autobots fall apart without Prime to rally them, though they are in a terminal situation admittedly.
There's a lot more, but I won't regurgitate the entire plot. Suffice it to say, I'm sorry I missed the issues the first time around. I like the ideas behind the story, and the way in which the characters were used. I'm glad I've been drawn back into reading the comics. Looks like I've missed out on some good stuff.
The volume begins with the creation of the Insecticons and the Swarm, and I was happy to see some art by EJ Su, whose art I liked quite a bit in Infiltration and Escalation. Thundercracker is not happy about the experiments used to create the Insecticons and the way the cast-offs are treated. "Our own kind!" he keeps insisting. It's little scenes are reactions like this that make him and others more than just background filler characters. And there are other similar scenes here and there.
The Autobots are on the run, and the way in which they were defeated and sent to Cybertron is explained by Jazz to Kup in a flashback. Devastator is the ace in the hole that he was back in the early G1 days, when he was the only combiner. It's odd that Megatron doesn't just have the Autobots all killed rather than sending them to Cybertron to be eaten by the Swarm though. I'm not sure I buy that, unless he thought they might be needed later. It's an odd choice. Regardless, Prime manages to close the portal, leaving the Autobots alive but trapped. So they're on the run, leaderless and pursued by crazy mutant Insecticons.
It's a rough scene when Ironhide beats up Mirage, convinced that he's the traitor and unwilling to hear him out. Sunstreaker, the actual traitor, stands there and watches, and it's clear this later plays into his decision to confess and end it all, as his consicence gets the better of him. As an aside, it's nice to see the Universe versions of Sunstreaker and Sideswipe used in the story, and also Mirage I believe. I'm not sure if there were others, though I did see Dropshot and Tankor/Octane near the end, which was a nice touch. Sunstreaker's apparent death is the end of a downward spiral for a proud Autobot who was violated badly by humans and who couldn't get past that. His agreement with Starscream sealed the deal, since the dire situation the Autobots find themselves trapped in can be laid directly at his feet. I'm not convinced that he's dead, since he survived the explosion and the fall as shown in issue #14, even if he is in bad shape, but that's neither here nor there. Death is meaningless in comics.
Starscream goes around gathering support for a coup, fully aware that Megatron knows what he's up to. I find the portrayal of Starscream very interesting here. He's ambitious as always, but he also genuinely seems disenchanted with Megatron's leadership and lack of goals, and he seems genuinely to believe in the Decepticon cause rather than simply being out for power. Megatron tells him at one point that he sees Starscream ultimately succeeding in wresting leadership from him one day, and that's enough to rally Starscream behind Megatron against the Autobots. And he refuses to use the opportunity to simply kill Megatron when he's helpless and take his place, saying that leadership must be earned. This seems to be a Starscream that isn't stupid, but recognizes that he's got to have the respect of the troops in order to lead them, and killing an already helpless Megatron isn't likely to get him that respect.
Omega Supreme is one of my favorite figures and characters, so having him show up and save the day was great. His explanation of how he survived the attack sent to finish him off ("I am Omega Supreme") says it all.
One of the themes of this series is the way in which various characters pay for deals with the other side. Sunstreaker is the obvious example, but Thundercracker strays from prevailing dogma and gets shot in the head by Skywarp. Drift is rejected by Thundercracker as a traitor. Ironhide beats Mirage badly because he believes Mirage is a traitor. Both sides are so locked into their causes and beliefs that there's no room for compromise. And considering how long they've been fighting, it's not surprising. But it makes one wonder how peace would ever be possible, assuming the war was ever decisively won by either side. The overall theme of this story seems to explore this idea to some extent, as the Decepticons stagnate without a challenging enemy to fight, and the Autobots fall apart without Prime to rally them, though they are in a terminal situation admittedly.
There's a lot more, but I won't regurgitate the entire plot. Suffice it to say, I'm sorry I missed the issues the first time around. I like the ideas behind the story, and the way in which the characters were used. I'm glad I've been drawn back into reading the comics. Looks like I've missed out on some good stuff.
Thursday, October 22, 2009
Review - Maximum Dinobots TPB
Maximum Dinobots - Trade Paperback
I started reading the Transformer comics by IDW when they first began publishing, and for various reasons I dropped out about the time that Devastation began. So it’s been enjoyable to go back and fill in the gaps and catch up on a year and a half of missed stories. “Maximum Dinobots” fills in a lot of those gaps. The slow burn really does pay off quite well when that payoff is finally reached. “Maximum Dinobots” deals with story threads from not only the main series, but also Spotlights Shockwave, Ultra Magnus, Soundwave and Grimlock.
After a flashback to the “glory days” of the Dynobot team, the story starts out with Grimlock on his own, trying to get their spacecraft functioning again. He sends for help and then is located by Scorponok, who has been after him since the events of Spotlight: Grimlock, briefly summarized here. The story follows this conflict between Grimlock and Scorponok, mixed with Sunstreaker and Hunter’s search for Sunstreaker’s original head. Hot Rod and Shockwave are thrown into the mix, along with Soundwave, Ravage and Laserbeak. Given all the characters and loose ends, it should be apparent that the plot is very busy, and thick with characters, and yet it works and works well.
Grimlock also gets some character development, finally. He lost his speech impediment in the IDW series (though we get two “me, Grimlocks” in his internal dialogue as in-jokes) but retained his traditional belligerent attitude. Grimlock is and has been a character who acted based on his own beliefs and goals, while not always taking into account what those around him want, and it comes back to haunt him here. The Dinobots come into conflict with Grimlock, and Swoop briefly abandons the group, before they pull together against the headmaster attack. But it’s Sludge’s near-death that really seems to get through to Grimlock. At the end of the story, he takes responsibility for going awol with the rest of the Dynobot unit, and has seemingly begun to rethink the way he’s lived his life up to this point. He submits to imprisonment by Ultra Magnus without protest, which is something I can’t imagine Grimlock doing in the past.
I loved Shockwave’s part in the story. With a bomb implanted in his chest by Skywatch and with full knowledge that it will be detonated within a certain time if not shut off, he goes to free Soundwave and essentially does as much harm to Skywatch as he can. In one story, Skywatch loses all of their controlled Transformers and is left with nothing except a damaged reputation, just in time for Spike to help run the group in the ongoing series. I loved Shockwave’s exchange with the guy who sent him to stop Grimlock. “Do you know how much damage I could do in 24 hours?” Ha. He’s not too impressed with the humans.
Scorponok’s real head turns up, and is key to defeating his plans. I remember Magnus taking a shot at him in the Ultra Magnus spotlight, and it was nice to finally see that incident and its implications revealed. Sunstreaker gets his head back and goes in for repair, the whole experience having left him very scarred and damaged, leading to his actions in All Hail Megatron. Scorponok, Shockwave and Grimlock are arrested by Ultra Magnus, and Soundwave is free to rejoin Megatron, having been freed by Shockwave from his alt mode imprisonment. All very satisfactory.
About the only unsatisfactory thing about the story is how incompetent Scorponok is. From constantly underestimating the Dynobots, to sending Hot Rod out to be shot rather than doing it himself, the whole situation goes out of his control because Scorponok is way too overconfident. Or rather, the human in the headmaster unit is too overconfident. He did very well in setting up the whole situation with the Machinations and the headmasters, but blew it big time by throwing caution to the wind and openly trying to expose and destroy Skywatch.
Otherwise, I really enjoyed the story. It’s great to see so many of the storylines set up back when I was first reading regularly finally get tied up, though I doubt the original plan was to do so in only five issues. After lots of slow, steady buildup, it all comes to a head in five short issues. And for the most part, the story is successful and interesting, and the characters are used well. “Maximum Dinobots” is well worth reading.
I started reading the Transformer comics by IDW when they first began publishing, and for various reasons I dropped out about the time that Devastation began. So it’s been enjoyable to go back and fill in the gaps and catch up on a year and a half of missed stories. “Maximum Dinobots” fills in a lot of those gaps. The slow burn really does pay off quite well when that payoff is finally reached. “Maximum Dinobots” deals with story threads from not only the main series, but also Spotlights Shockwave, Ultra Magnus, Soundwave and Grimlock.
After a flashback to the “glory days” of the Dynobot team, the story starts out with Grimlock on his own, trying to get their spacecraft functioning again. He sends for help and then is located by Scorponok, who has been after him since the events of Spotlight: Grimlock, briefly summarized here. The story follows this conflict between Grimlock and Scorponok, mixed with Sunstreaker and Hunter’s search for Sunstreaker’s original head. Hot Rod and Shockwave are thrown into the mix, along with Soundwave, Ravage and Laserbeak. Given all the characters and loose ends, it should be apparent that the plot is very busy, and thick with characters, and yet it works and works well.
Grimlock also gets some character development, finally. He lost his speech impediment in the IDW series (though we get two “me, Grimlocks” in his internal dialogue as in-jokes) but retained his traditional belligerent attitude. Grimlock is and has been a character who acted based on his own beliefs and goals, while not always taking into account what those around him want, and it comes back to haunt him here. The Dinobots come into conflict with Grimlock, and Swoop briefly abandons the group, before they pull together against the headmaster attack. But it’s Sludge’s near-death that really seems to get through to Grimlock. At the end of the story, he takes responsibility for going awol with the rest of the Dynobot unit, and has seemingly begun to rethink the way he’s lived his life up to this point. He submits to imprisonment by Ultra Magnus without protest, which is something I can’t imagine Grimlock doing in the past.
I loved Shockwave’s part in the story. With a bomb implanted in his chest by Skywatch and with full knowledge that it will be detonated within a certain time if not shut off, he goes to free Soundwave and essentially does as much harm to Skywatch as he can. In one story, Skywatch loses all of their controlled Transformers and is left with nothing except a damaged reputation, just in time for Spike to help run the group in the ongoing series. I loved Shockwave’s exchange with the guy who sent him to stop Grimlock. “Do you know how much damage I could do in 24 hours?” Ha. He’s not too impressed with the humans.
Scorponok’s real head turns up, and is key to defeating his plans. I remember Magnus taking a shot at him in the Ultra Magnus spotlight, and it was nice to finally see that incident and its implications revealed. Sunstreaker gets his head back and goes in for repair, the whole experience having left him very scarred and damaged, leading to his actions in All Hail Megatron. Scorponok, Shockwave and Grimlock are arrested by Ultra Magnus, and Soundwave is free to rejoin Megatron, having been freed by Shockwave from his alt mode imprisonment. All very satisfactory.
About the only unsatisfactory thing about the story is how incompetent Scorponok is. From constantly underestimating the Dynobots, to sending Hot Rod out to be shot rather than doing it himself, the whole situation goes out of his control because Scorponok is way too overconfident. Or rather, the human in the headmaster unit is too overconfident. He did very well in setting up the whole situation with the Machinations and the headmasters, but blew it big time by throwing caution to the wind and openly trying to expose and destroy Skywatch.
Otherwise, I really enjoyed the story. It’s great to see so many of the storylines set up back when I was first reading regularly finally get tied up, though I doubt the original plan was to do so in only five issues. After lots of slow, steady buildup, it all comes to a head in five short issues. And for the most part, the story is successful and interesting, and the characters are used well. “Maximum Dinobots” is well worth reading.
Friday, February 13, 2009
Voyager season six episode reviews
I generally just post about political events, but how about some reviews of Star Trek Voyager episodes for a change of pace.
The Voyager Consipracy
An episode that makes fun of conspiracy nuts! I love it!
The narrative rides on a clever premise. Seven of Nine has altered her Borg alcove to allow her to assimilate enormous amounts of data while she’s regenerating. The trouble is, it’s too much information for her brain to handle, despite her Borg hardware, and she starts to go a little loopy trying to make sense of all the information. This isn’t apparent at first, as she is correctly able to diagnose a problem with the ship using some pretty disparate bits of information. But then Seven takes the fact that an alien the ship is assisting is using technology similar to the Caretaker’s from Voyager’s first episode, and she starts to spin some pretty wild conspiracy theories about Starfleet deliberately establishing a military presence in the Delta quadrant. They’re doing it in collaboration with the Cardassians, no less! She delivers this bit of information to Chakotay and actually has him wondering if there’s validity to the theory. Jeri Ryan approaches Seven’s impartation of information as though it’s verbal assault, following one stardate and events that took place on that date with another in rapid fire fashion. She then tries the same thing with Janeway, but tries to convince her that the whole stranding of Voyager was a Maquis plot.
The whole thing comes across as great fun, because it’s so absurd and the twisting of facts is so obvious to the viewer. But people do this all the time in the real world. Look at the ‘9/11 was an inside job’ conspiracy theorists for a prime example of taking lots of facts, combining them with assumptions, and producing a nutty theory. Of course, in the real world, there’s no malfunction of Borg technology to excuse the lunacy. The Doctor is able to work out what’s gone wrong with Seven of Nine and ultimately help her recover, after one of Voyager’s standard cliches, the “unauthorized shuttle launch” that’s always too late to be stopped, as Seven decides that she was the ultimate target of the consipracy and runs for her life.
Failing to stop the shuttle launch is a cliché that made me downgrade the episode a bit, but it’s not the only weakness. I find it hard to believe that Janeway and Chakotay would so easily believe Seven’s wild theories, but apparently they are convinced enough to investigate what she had to say, and to briefly distrust each other. That’s weak characterization of the captain and first officer.
On the positive side, in a series that’s often far too devoid of continuity, this episode is a breath of fresh air. Events from Voyager’s first episode are referenced, and indeed, we get to see clips from that episode. Characters discuss those events with Seven. Other episodes are mentioned, and Kes is name-checked as well, for the first time in a long time. This episode feels like part of a continuing series, rather than an episode that’s disconnected from the overall Voyager story arc. Voyager needed more stories like this.
At the end of the episode, Voyager makes some progress towards home in this episode via a “subspace catapault”, which gives them several hundred light years of progress in a few hours, and shaves three more years off the trip. It’s a happy ending to a fun episode. And the alien of the week is actually friendly and helpful for once, rather than simply being belligerent for the same of being belligerent.
Individual story rating: 7.5 out of 10
Voyager uniqueness rating: the idea behind the story could be adapted for other series with major changes, but by and large this is a story specifically tailored for Voyager and its characters.
Pathfinder
Pathfinder is an excellent story with one major flaw, which I’ll get to shortly. The episode updates the audience on events back on Earth, as Starfleet makes continual efforts to contact Voyager from halfway across the galaxy. And rather than populate the episode with all new characters, the story uses Reginald Barclay from TNG as the protagonist. Barclay is the engineer who was so socially inept and shy that he would retreat into the holodeck and live out a fantasy life where he was a success and a ladies’ man. As the story begins, he’s in some trouble, and is paid a visit by TNG regular, Deanna Troi, who had become friends with Barclay.
In addition to these two familiar characters, the episode also introduces Barclay’s supervisor, a decent guy who suffers Barclay’s quirks in the same way that LaForge did back in the original TNG episode. And the guest characters are rounded out by the presence of Admiral Paris, father to Tom Paris.
The plot concerns Barclay’s plan to contact Voyager via an artificially created wormhole and other technobabble that I won’t repeat here, based on where Starfleet has calculated the ship to be since they last made contact back in season four. This is where the story’s only major flaw comes into play. Voyager has gained nearly 30,000 light years since they contacted Starfleet in “Message in a Bottle” and “Hunters”, so Starfleet would be looking for them in the wrong place. The attempt to contact Voyager is ultimately successful, but it should not have been. On the other hand, to have the episode end in failure would have basically made the whole thing pointless, so it comes down to ending the story with a significant advance in Voyager’s quest to get home, or adhering to logic and continuity and rendering the episode meaningless. The writers could have avoided this by planning ahead and dropping another contact somewhere earlier in the season, but strict intro-series continuity is always fast and loose with Voyager. It’s one of my biggest gripes with an otherwise enjoyable series.
Barclay is well written, and his character’s history is put to good use as a basis for his obsession to contact Voyager. The crew of the Enterprise had become his surrogate family, and since being transferred to Earth, he’s become lonely and withdrawn. He’s drifted back towards his holo addiction and become obsessed with Voyager and her crew, which he has re-created in the holodeck as a ‘diagnostic tool’. He’s even named his cat Neelix. He gets very worked up when talking about how lonely the crew must be, stranded in the Delta quandrant, and it’s obvious he’s telling us more about himself than Voyager. In the end, he breaks protocol and disobeys orders to try out his theory for contacting Voyager. Had he failed, his career would have been over, but his success mitigates his misdeeds, and Janeway has her first two-way conversation with Starfleet in five and a half years.
In the end, the continuity flaw is annoying, but sadly par for the course. Otherwise, this is a very strong episode that uses Voyager’s unique situation to produce some good drama. We needed more episodes that did what this episode did.
Individual story rating: 9 out of 10
Voyager uniqueness rating: this story is tailored to specifically advance Voyager’s overall storyline
Fair Haven
Fair Haven is a quite a letdown after the excellence of Pathfinder. The town of Fair Haven is the latest holodeck getaway for the Voyager crew. Yes, it’s a holodeck episode. With a whole galaxy of ‘real’ things to explore, we have to endure another episode of the crew play-acting.
To be fair, the ship is stuck in place in this episode. The arbitrary spatial danger of the week is, in essence, a thunderstorm in space, which has collapsed Voyager’s warp field. They can’t outrun it, so Janeway makes the decision to batten down the hatches and ride out the storm. Since they can’t go anywhere, the captain initiates an open door policy for holodeck usage and lets the village simulation run 24 hours a day. It acts like artificial shore leave, I suppose. There’s nothing terribly offensive about the idea and story, but neither is there anything compelling about it. We’re watching the crew relax, which doesn’t have a lot of entertainment value. Or at least, not enough to carry an entire episode.
The ethical problem in the story comes about when Janeway finds herself attracted to one of the holodeck characters. In the Star Trek world, the holodeck simulates real people to the point that we’ve seen several characters fall for one. Way back in TNG season 1, Riker makes out with a lady in a jazz club and has enough feelings for her that he still remembers her and she becomes a plot point in season 4. Harry Kim falls for a hologram in season 3 of Voyager, though in his case there was an alien hacked into the computer and interacting with him. In both cases, characters treat a simulated human as though they were real. Janeway does much the same thing here, and the story uses that attraction to explore just how lonely she is after five years of being “the captain”, with no intimate contact with anyone. Everyone on the ship is her subordinate, not her equal, and therefore relationships are off limits. She’s closer to Chakotay than anyone else, but she really has no one to open up to or be vulnerable to. It’s the old ‘loneliness of command’ storyline applied to Janeway. This is a very valid character issue to explore, and the episode tries to do so in an interesting manner. This small community of 150 humans have no one but themselves for companionship, and given the capabilities of the holodeck, Janeway’s dilemma makes sense. In the context of the series, her actions are no more unbelievable than someone getting addicted to internet porn as a substitute for an actual physical relationship, for example.
So she develops romantic feelings for one of the holograms, who is the bartender in the village. She later feels regret for it and berates herself for allowing herself to have feelings for someone who isn’t even real. Oddly enough, she discusses it with the Doctor, who is himself a sentient hologram and therefore not quite the same as the more limited simulations on the holodeck. He’s not likely to be sympathetic to her point of view, and indeed he isn’t, trying instead to sell her on the benefits of a “relationship” that’s not real, since she can’t have a real relationship in her situation.
There’s a good, strong exploration of Janeway’s situation buried somewhere in this episode, but I’m just not sure the story that surrounds it really serves the character well. Janeway’s dilemma is the only meat in an otherwise very, very lean story, and I can’t help but feel that the story would have benefitted from less of the superfluous space danger and filler with the village’s inhabitants, and more development of Janeway’s “relationship”.
The bottom line: the story has something to say about the captain and her solitude, but can’t quite figure out how to get its message across in a compelling way. The end result is a lot of harmless fluff that is hardly compelling.
Individual story rating: 4 out of 10
Voyager uniqueness rating: some elements unique to Voyager’s situation, but could generally work for TNG or DS9 just as easily
Blink of an Eye, Virtuoso,
Memorial
Memorial feels like an old-school Voyager episode. It focuses on characters other than Seven of Nine for once, and it sets up a situation where our main characters have supposedly taken part in something that we, the viewers, know they would never do, namely a massacre of civilians during some type of forced resettlement by an alien military. The episode reminds me of Projections or Coda, where events are occurring that cannot have taken place as we see them onscreen, and so the point of the episode is to unravel the mystery behind the mind games. Sometimes this approach works, and sometimes it’s unsuccessful. Memorial is a definite success.
Chakotay, Paris, Neelix and Kim all return from a long-term away mission and begin to experience memories of being involved in the massacre. Voyager investigates by retracing their flight path, which causes other members of the crew to remember the same events, including Janeway. They locate the planet where the massacre took place, only to discover that the events they “remember” happened three centuries ago, and that memories have been implanted in their minds via the episode’s titular memorial, a stone monument. The memorial monument in question does more than just describe events, it forces visitors to the planet to experience them via implanted memories, ensuring that the massacre is never forgotten.
It’s a strong concept, and the acting by all the regulars really sells it. Maybe this material was something they could really get their minds around and believe in, and that contributes to solid, emotionally believable performances. The characters feel more real in this episode, rather than looking like pawns for the plot. Janeway’s final solution, to repair the memorial despite the trauma it’s caused the crew, is a decision that most of the crew don’t seem to agree with. And I tend to side with them rather than Janeway. At some point, history is just that: history, and however well-intentioned the memorial was, forcing innocent passers-by to live horrible events they had nothing to do with is cruel. But Janeway’s the captain, so she gets her way.
Individual story rating: 8 out of 10
Voyager uniqueness rating: could easily be used in any of the other Star Trek series and lose nothing
Tsunkatse
Who ever thought I’d see the Rock in a Star Trek episode?
Tsunkatse is Star Trek’s take on boxing, or pro-wrestling, or any such similar sporting event. It’s not a deep episode, but it has some entertainment value. I suppose. At least, if you like choreographed fights between Jeri Ryan and the Rock, which shows off the rather impressive physique that both sport in this episode. But then, that was probably the point.
Tsunkatse is a sport that’s enjoyed by the denizens of half a dozen planets in the region of space that Voyager’s passing through. Some of the crew take an interest in it at first, believing it to be akin to a martial arts tournament. That changes when Seven of Nine and Tuvok are kidnapped, and Seven is forced to compete in the matches, and the crew learn that not everyone in the sport fight willingly. But since the sport is so profitable, no one in the local governments are willing to do anything other than turn a blind eye to the occasional alien forced to fight for his or her life.
Voyager tracks down the source of the fights, which take place on a traveling spacecraft and are transmitted to all the local planets. It’s pay per view. Despite the fact that Voyager is outgunned and generally outclassed by the ship hosting the Tsunkatse matches, they manage to do enough damage to the ship to enable them to rescue first Tuvok, and then Seven, along with her opponent in a deathmatch. I note that this happens while Janeway’s away from the ship and Chakotay’s in command. Looks like he’s better at space combat than she is.
The ethical core of the episode boils down to this: will Seven take a life in the arena to save her own? Or Tuvok’s? It’s nothing we haven’t seen before in Star Trek, including the original series episode “Arena” where Kirk refuses to kill the helpless Gorn. Couple that with the overuse of Seven of Nine episodes where she “explores her humanity” and learns lessons about being human, and the content is not anything new or novel. But the episode does entertain on a surface level as a ‘crew members in jeopordy’ plot, and the pairing of Seven of Nine with Tuvok offers some interaction that we haven’t seen much of before. And DS9 fans get a nod with the presence of both J.G. Hertzler and Jeffrey Combs as characters in this story.
One final comment. The presence of a Hirogen in this story is another case of the writers ignoring Voyager’s progress, as they so often do. Voyager has traveled nearly 20,000 light years since we last saw the Hirogen, and yet they find a Hirogen ship for our friend to travel back home on far too easily. Like the Malon in Juggernaut, and the Ankari in Equinox II, the writers simply don’t seem to pay any attention to how far Voyager has traveled and how unlikely it is that races like the Malon and Hirogen would be spread out over that many light years. At least with the Hirogen, we know that they are a culture that travels far and wide on their hunts, so the mistake is less egregious here. But it still challenges the willing suspension of disbelief, not to mention simple logic.
Individual story rating: 6.5 out of 10
Voyager uniqueness rating: substitute Klingon for Hirogen, and it could easily be used in any of the other Star Trek series and lose nothing
The Voyager Consipracy
An episode that makes fun of conspiracy nuts! I love it!
The narrative rides on a clever premise. Seven of Nine has altered her Borg alcove to allow her to assimilate enormous amounts of data while she’s regenerating. The trouble is, it’s too much information for her brain to handle, despite her Borg hardware, and she starts to go a little loopy trying to make sense of all the information. This isn’t apparent at first, as she is correctly able to diagnose a problem with the ship using some pretty disparate bits of information. But then Seven takes the fact that an alien the ship is assisting is using technology similar to the Caretaker’s from Voyager’s first episode, and she starts to spin some pretty wild conspiracy theories about Starfleet deliberately establishing a military presence in the Delta quadrant. They’re doing it in collaboration with the Cardassians, no less! She delivers this bit of information to Chakotay and actually has him wondering if there’s validity to the theory. Jeri Ryan approaches Seven’s impartation of information as though it’s verbal assault, following one stardate and events that took place on that date with another in rapid fire fashion. She then tries the same thing with Janeway, but tries to convince her that the whole stranding of Voyager was a Maquis plot.
The whole thing comes across as great fun, because it’s so absurd and the twisting of facts is so obvious to the viewer. But people do this all the time in the real world. Look at the ‘9/11 was an inside job’ conspiracy theorists for a prime example of taking lots of facts, combining them with assumptions, and producing a nutty theory. Of course, in the real world, there’s no malfunction of Borg technology to excuse the lunacy. The Doctor is able to work out what’s gone wrong with Seven of Nine and ultimately help her recover, after one of Voyager’s standard cliches, the “unauthorized shuttle launch” that’s always too late to be stopped, as Seven decides that she was the ultimate target of the consipracy and runs for her life.
Failing to stop the shuttle launch is a cliché that made me downgrade the episode a bit, but it’s not the only weakness. I find it hard to believe that Janeway and Chakotay would so easily believe Seven’s wild theories, but apparently they are convinced enough to investigate what she had to say, and to briefly distrust each other. That’s weak characterization of the captain and first officer.
On the positive side, in a series that’s often far too devoid of continuity, this episode is a breath of fresh air. Events from Voyager’s first episode are referenced, and indeed, we get to see clips from that episode. Characters discuss those events with Seven. Other episodes are mentioned, and Kes is name-checked as well, for the first time in a long time. This episode feels like part of a continuing series, rather than an episode that’s disconnected from the overall Voyager story arc. Voyager needed more stories like this.
At the end of the episode, Voyager makes some progress towards home in this episode via a “subspace catapault”, which gives them several hundred light years of progress in a few hours, and shaves three more years off the trip. It’s a happy ending to a fun episode. And the alien of the week is actually friendly and helpful for once, rather than simply being belligerent for the same of being belligerent.
Individual story rating: 7.5 out of 10
Voyager uniqueness rating: the idea behind the story could be adapted for other series with major changes, but by and large this is a story specifically tailored for Voyager and its characters.
Pathfinder
Pathfinder is an excellent story with one major flaw, which I’ll get to shortly. The episode updates the audience on events back on Earth, as Starfleet makes continual efforts to contact Voyager from halfway across the galaxy. And rather than populate the episode with all new characters, the story uses Reginald Barclay from TNG as the protagonist. Barclay is the engineer who was so socially inept and shy that he would retreat into the holodeck and live out a fantasy life where he was a success and a ladies’ man. As the story begins, he’s in some trouble, and is paid a visit by TNG regular, Deanna Troi, who had become friends with Barclay.
In addition to these two familiar characters, the episode also introduces Barclay’s supervisor, a decent guy who suffers Barclay’s quirks in the same way that LaForge did back in the original TNG episode. And the guest characters are rounded out by the presence of Admiral Paris, father to Tom Paris.
The plot concerns Barclay’s plan to contact Voyager via an artificially created wormhole and other technobabble that I won’t repeat here, based on where Starfleet has calculated the ship to be since they last made contact back in season four. This is where the story’s only major flaw comes into play. Voyager has gained nearly 30,000 light years since they contacted Starfleet in “Message in a Bottle” and “Hunters”, so Starfleet would be looking for them in the wrong place. The attempt to contact Voyager is ultimately successful, but it should not have been. On the other hand, to have the episode end in failure would have basically made the whole thing pointless, so it comes down to ending the story with a significant advance in Voyager’s quest to get home, or adhering to logic and continuity and rendering the episode meaningless. The writers could have avoided this by planning ahead and dropping another contact somewhere earlier in the season, but strict intro-series continuity is always fast and loose with Voyager. It’s one of my biggest gripes with an otherwise enjoyable series.
Barclay is well written, and his character’s history is put to good use as a basis for his obsession to contact Voyager. The crew of the Enterprise had become his surrogate family, and since being transferred to Earth, he’s become lonely and withdrawn. He’s drifted back towards his holo addiction and become obsessed with Voyager and her crew, which he has re-created in the holodeck as a ‘diagnostic tool’. He’s even named his cat Neelix. He gets very worked up when talking about how lonely the crew must be, stranded in the Delta quandrant, and it’s obvious he’s telling us more about himself than Voyager. In the end, he breaks protocol and disobeys orders to try out his theory for contacting Voyager. Had he failed, his career would have been over, but his success mitigates his misdeeds, and Janeway has her first two-way conversation with Starfleet in five and a half years.
In the end, the continuity flaw is annoying, but sadly par for the course. Otherwise, this is a very strong episode that uses Voyager’s unique situation to produce some good drama. We needed more episodes that did what this episode did.
Individual story rating: 9 out of 10
Voyager uniqueness rating: this story is tailored to specifically advance Voyager’s overall storyline
Fair Haven
Fair Haven is a quite a letdown after the excellence of Pathfinder. The town of Fair Haven is the latest holodeck getaway for the Voyager crew. Yes, it’s a holodeck episode. With a whole galaxy of ‘real’ things to explore, we have to endure another episode of the crew play-acting.
To be fair, the ship is stuck in place in this episode. The arbitrary spatial danger of the week is, in essence, a thunderstorm in space, which has collapsed Voyager’s warp field. They can’t outrun it, so Janeway makes the decision to batten down the hatches and ride out the storm. Since they can’t go anywhere, the captain initiates an open door policy for holodeck usage and lets the village simulation run 24 hours a day. It acts like artificial shore leave, I suppose. There’s nothing terribly offensive about the idea and story, but neither is there anything compelling about it. We’re watching the crew relax, which doesn’t have a lot of entertainment value. Or at least, not enough to carry an entire episode.
The ethical problem in the story comes about when Janeway finds herself attracted to one of the holodeck characters. In the Star Trek world, the holodeck simulates real people to the point that we’ve seen several characters fall for one. Way back in TNG season 1, Riker makes out with a lady in a jazz club and has enough feelings for her that he still remembers her and she becomes a plot point in season 4. Harry Kim falls for a hologram in season 3 of Voyager, though in his case there was an alien hacked into the computer and interacting with him. In both cases, characters treat a simulated human as though they were real. Janeway does much the same thing here, and the story uses that attraction to explore just how lonely she is after five years of being “the captain”, with no intimate contact with anyone. Everyone on the ship is her subordinate, not her equal, and therefore relationships are off limits. She’s closer to Chakotay than anyone else, but she really has no one to open up to or be vulnerable to. It’s the old ‘loneliness of command’ storyline applied to Janeway. This is a very valid character issue to explore, and the episode tries to do so in an interesting manner. This small community of 150 humans have no one but themselves for companionship, and given the capabilities of the holodeck, Janeway’s dilemma makes sense. In the context of the series, her actions are no more unbelievable than someone getting addicted to internet porn as a substitute for an actual physical relationship, for example.
So she develops romantic feelings for one of the holograms, who is the bartender in the village. She later feels regret for it and berates herself for allowing herself to have feelings for someone who isn’t even real. Oddly enough, she discusses it with the Doctor, who is himself a sentient hologram and therefore not quite the same as the more limited simulations on the holodeck. He’s not likely to be sympathetic to her point of view, and indeed he isn’t, trying instead to sell her on the benefits of a “relationship” that’s not real, since she can’t have a real relationship in her situation.
There’s a good, strong exploration of Janeway’s situation buried somewhere in this episode, but I’m just not sure the story that surrounds it really serves the character well. Janeway’s dilemma is the only meat in an otherwise very, very lean story, and I can’t help but feel that the story would have benefitted from less of the superfluous space danger and filler with the village’s inhabitants, and more development of Janeway’s “relationship”.
The bottom line: the story has something to say about the captain and her solitude, but can’t quite figure out how to get its message across in a compelling way. The end result is a lot of harmless fluff that is hardly compelling.
Individual story rating: 4 out of 10
Voyager uniqueness rating: some elements unique to Voyager’s situation, but could generally work for TNG or DS9 just as easily
Blink of an Eye, Virtuoso,
Memorial
Memorial feels like an old-school Voyager episode. It focuses on characters other than Seven of Nine for once, and it sets up a situation where our main characters have supposedly taken part in something that we, the viewers, know they would never do, namely a massacre of civilians during some type of forced resettlement by an alien military. The episode reminds me of Projections or Coda, where events are occurring that cannot have taken place as we see them onscreen, and so the point of the episode is to unravel the mystery behind the mind games. Sometimes this approach works, and sometimes it’s unsuccessful. Memorial is a definite success.
Chakotay, Paris, Neelix and Kim all return from a long-term away mission and begin to experience memories of being involved in the massacre. Voyager investigates by retracing their flight path, which causes other members of the crew to remember the same events, including Janeway. They locate the planet where the massacre took place, only to discover that the events they “remember” happened three centuries ago, and that memories have been implanted in their minds via the episode’s titular memorial, a stone monument. The memorial monument in question does more than just describe events, it forces visitors to the planet to experience them via implanted memories, ensuring that the massacre is never forgotten.
It’s a strong concept, and the acting by all the regulars really sells it. Maybe this material was something they could really get their minds around and believe in, and that contributes to solid, emotionally believable performances. The characters feel more real in this episode, rather than looking like pawns for the plot. Janeway’s final solution, to repair the memorial despite the trauma it’s caused the crew, is a decision that most of the crew don’t seem to agree with. And I tend to side with them rather than Janeway. At some point, history is just that: history, and however well-intentioned the memorial was, forcing innocent passers-by to live horrible events they had nothing to do with is cruel. But Janeway’s the captain, so she gets her way.
Individual story rating: 8 out of 10
Voyager uniqueness rating: could easily be used in any of the other Star Trek series and lose nothing
Tsunkatse
Who ever thought I’d see the Rock in a Star Trek episode?
Tsunkatse is Star Trek’s take on boxing, or pro-wrestling, or any such similar sporting event. It’s not a deep episode, but it has some entertainment value. I suppose. At least, if you like choreographed fights between Jeri Ryan and the Rock, which shows off the rather impressive physique that both sport in this episode. But then, that was probably the point.
Tsunkatse is a sport that’s enjoyed by the denizens of half a dozen planets in the region of space that Voyager’s passing through. Some of the crew take an interest in it at first, believing it to be akin to a martial arts tournament. That changes when Seven of Nine and Tuvok are kidnapped, and Seven is forced to compete in the matches, and the crew learn that not everyone in the sport fight willingly. But since the sport is so profitable, no one in the local governments are willing to do anything other than turn a blind eye to the occasional alien forced to fight for his or her life.
Voyager tracks down the source of the fights, which take place on a traveling spacecraft and are transmitted to all the local planets. It’s pay per view. Despite the fact that Voyager is outgunned and generally outclassed by the ship hosting the Tsunkatse matches, they manage to do enough damage to the ship to enable them to rescue first Tuvok, and then Seven, along with her opponent in a deathmatch. I note that this happens while Janeway’s away from the ship and Chakotay’s in command. Looks like he’s better at space combat than she is.
The ethical core of the episode boils down to this: will Seven take a life in the arena to save her own? Or Tuvok’s? It’s nothing we haven’t seen before in Star Trek, including the original series episode “Arena” where Kirk refuses to kill the helpless Gorn. Couple that with the overuse of Seven of Nine episodes where she “explores her humanity” and learns lessons about being human, and the content is not anything new or novel. But the episode does entertain on a surface level as a ‘crew members in jeopordy’ plot, and the pairing of Seven of Nine with Tuvok offers some interaction that we haven’t seen much of before. And DS9 fans get a nod with the presence of both J.G. Hertzler and Jeffrey Combs as characters in this story.
One final comment. The presence of a Hirogen in this story is another case of the writers ignoring Voyager’s progress, as they so often do. Voyager has traveled nearly 20,000 light years since we last saw the Hirogen, and yet they find a Hirogen ship for our friend to travel back home on far too easily. Like the Malon in Juggernaut, and the Ankari in Equinox II, the writers simply don’t seem to pay any attention to how far Voyager has traveled and how unlikely it is that races like the Malon and Hirogen would be spread out over that many light years. At least with the Hirogen, we know that they are a culture that travels far and wide on their hunts, so the mistake is less egregious here. But it still challenges the willing suspension of disbelief, not to mention simple logic.
Individual story rating: 6.5 out of 10
Voyager uniqueness rating: substitute Klingon for Hirogen, and it could easily be used in any of the other Star Trek series and lose nothing
Tuesday, February 10, 2009
Obama's in over his head. Very much so.
I don't think Obama has a clue what he's doing. I'm sure he doesn't. 900 Billion dollars on pet projects for Democrats, and that's supposed to jumpstart the economy? If government spending made a strong economy, we'd have the best in the world.
That last $700 billion didn't do much, did it? So of course, we keep throwing money at the problem. Typical Democrat "solution" to everything.
That last $700 billion didn't do much, did it? So of course, we keep throwing money at the problem. Typical Democrat "solution" to everything.
Thursday, March 13, 2008
The Mum Media
How long did it take the networks to identify Spitzer's party affiliation? Good grief.
Wednesday, March 12, 2008
Subscribe to:
Posts (Atom)