Ah, that’s better! I fixed the angle that the planet killer flies past the camera so that the viewer can now more clearly see the four component lances of the antiproton beam coalescing together, and I composited in the missing asteroid field and volumetric space dust layers that were missing from the previous test video.

This will not end well

This will not end well

I probably could spend another week or two endlessly tweaking this 66-frame sequence, but I think this is the best it’s going to get. It’s a shame, because there are a few things that have always bothered me about this particular sequence… more after the jump.

Mkay, so first, it was a dumbass move for Kirk to order the shields lowered while the Enterprise was in the line of fire of a leviathan that fires antiproton beams to slice up planets. My initial thought for fixing this was to somehow re-edit the sequence to excise Kirk making such a boneheaded mistake, but it basically would have meant cutting to the attack sequence immediately after Spock says “I also believe the nature of this machine precludes the possiblity of easy access to its control mechanisms” as a communicator voice-over while the camera is on the Constellation. I gave it a test try, but the transition was just too jarring and abrupt. So, our brave captain stays a dum-dum for this one.

My next objection was a little less straightforward but bothered me even more: When the Enterprise was struck by the antiproton beam the first time with shields down, everyone onboard got tossed to starboard and the ship careened out of control. Yet a few minutes later (after Decker’s disastrous strafing run on the planet killer when deflector shields are damaged and gone for good), the planet killer fired three more times on the Enterprise… and it didn’t seem like a big deal at all! All that seemed to happen was the ship shuddered, the warp drive went offline, some Enterprise crewmembers were injured or possibly killed, and some hull ruptures occured (the latter three all occurred off-camera). But no one got tossed to the deck, and the Enterprise stayed pretty much in level flight. Maybe she stayed stable because she was caught in a tractor beam, but that presents another problem: she was probably CLOSER to the planet killer for those last three shots!

To fix these glaring inconsistencies, I storyboarded an initial attack sequence where the Enterprise (which was flying like an F-18 desperately trying to evade the doomsday machine) dived behind a largish asteroid just as the planet killer fired its antiproton beam. The beam would strike the asteroid instead of the Enterprise–protecting the ship from direct damage by the beam–but the megaBOOM!! explosion of the asteroid would cause the ship to ricochet off-course and toss our gallant crewmembers out of their safety-beltless chairs. My thought here would be that this would explain why the Enterprise didn’t suffer the extreme damage she suffered later on in Act II, and it would also explain why she spun out of control (because of the shock wave from the exploding asteroid). Yeah yeah, shock waves don’t travel through the vacuum of space. Well, warp drive’s impossible too, so :p

Unfortunately, no matter how I timed it out I kept bumping up against some hard limits storytelling-wise. Because I have to cleave to the original soundtrack, I only had 66 frames for this shot and I just couldn’t figure out a way to squeeze all that visual information into less than three seconds. I suppose if I was more proficient with sound editing I might have been able to stretch out the soundtrack (perhaps by repeating some of the beats) so that I’d have more time to show everything, but I just couldn’t justify spending all that time for what was originally 2.75 seconds of film. In the end, I felt it was more important to have the camera concentrate its attention on the first glimpse of the planet killer’s main weapon being fired… the interior shot of the Enterprise crew getting tossed out of their chairs was enough of a clue to the audience that some bad juju was going down.