Spoilers Star Trek Beyond: Errors, Goofs, Inconsistencies
- Thread starter starfox
- Start date
Really, the most glaring error for me was(and I will warn any potential readers in case this is considered a spoiler, SO SPOILERS.... but the scene is in a lot of trailers) when Kirk ordered Sulu to Warp the Enterprise out of the area after the swarm took out the deflector dish. I immediately thought to myself, uh, without a navigational deflector wouldn't going to warp kinda...... suck? You know micro asteroids and stellar debris and such.
Very forgivable error... didn't ruin the movie at all for me. I mean at least the swarm didn't target the aft nacelle.....
Very forgivable error... didn't ruin the movie at all for me. I mean at least the swarm didn't target the aft nacelle.....
Totally noticed that too, but too was able to let it go and still enjoyed the scene and yes...nowhere near as bad as "aft nacelle"
I thought about that for a moment, but figured with the ship already being torn to shreds in screen sci fi logic, it's not much of a risk.
In my personal head canon I always pretend Khan says at the 'aft of the nacelle' and he simply muddles his words slightly.
In the movie, when the dish is destroyed, Sulu tells them that the shields are now totally gone. But complies with an order to warp them away.
So the dish is the main shield generator in this universe, not needed for warp flight. As the Franklin doesn't seem to need one to warp around either.
Or given even smashing into a mountain at terminal velocity doesn't hurt a ship much now, they were willing to take the risk and loose them at sublight in the nebula, struggle to Yorktown and patch up all the damage there.
So the dish is the main shield generator in this universe, not needed for warp flight. As the Franklin doesn't seem to need one to warp around either.
Or given even smashing into a mountain at terminal velocity doesn't hurt a ship much now, they were willing to take the risk and loose them at sublight in the nebula, struggle to Yorktown and patch up all the damage there.
Well, wouldn't the incoming swarm ships be trivial to deflect away, compared to an asteroid approaching a ship at warp? That's more of an inconsistency than not.
I mean, if things can puncture the hull that easily with shields up, those ships won't last too long anyway.
Or then it just shows that the puncturing ships are even better shielded.
It never did, and thankfully so. Every crash landing in Trek history, including some at warp speed, has resulted in the ship or shuttle landing more or less intact - at worst, her various segments (nacelles, say) have been severed but themselves have landed in pristine condition. The mountains they have met have fared much worse.
If starships weren't that tough, there could be no Star Trek.
My list of silly and irrelevant technical grievances:
1) The technobabble on jamming the swarm. UHF is "high frequency"? All radio is by definition pretty low frequency, and unlikely to be chosen by future folks. Especially as radio was out of fashion back in Archer's days already, so Edison would be as unlikely to utilize it as the Ancients.
2) The nonsense of having to drop the Franklin off the cliff first.
3) The way Jaylah's holograms worked, especially in the motorbike scene. They perfectly adapt to the local terrain, without a need for guidance from the real Kirk - so why is Kirk actually there himself? Why not stand off so as to better protect his crew by creating a truly invulnerable diversion?
That's not too many. The big concepts here are fine, and the performance of the gear our heroes operate is consistent enough. And the in-universe references are all cool.
Timo Saloniemi
It never did, and thankfully so. Every crash landing in Trek history, including some at warp speed, has resulted in the ship or shuttle landing more or less intact - at worst, her various segments (nacelles, say) have been severed but themselves have landed in pristine condition. The mountains they have met have fared much worse.
If starships weren't that tough, there could be no Star Trek.
My list of silly and irrelevant technical grievances:
1) The technobabble on jamming the swarm. UHF is "high frequency"? All radio is by definition pretty low frequency, and unlikely to be chosen by future folks. Especially as radio was out of fashion back in Archer's days already, so Edison would be as unlikely to utilize it as the Ancients.
2) The nonsense of having to drop the Franklin off the cliff first.
3) The way Jaylah's holograms worked, especially in the motorbike scene. They perfectly adapt to the local terrain, without a need for guidance from the real Kirk - so why is Kirk actually there himself? Why not stand off so as to better protect his crew by creating a truly invulnerable diversion?
That's not too many. The big concepts here are fine, and the performance of the gear our heroes operate is consistent enough. And the in-universe references are all cool.
Timo Saloniemi
Last edited by a moderator:
There are clearly ways of dealing with that without a dish. Miranda and Oberth class ships manage just fine. Not to mention all the non-Starfleet ships that don't use one either.
Rather than using " ultra" as a hyperbolic descriptor, I just assumed they were referencing that specific range of radio frequencies by its ITU designation. That they first describe it as Ultra High Frequency instead of just saying UHF seemed to be designed to set up the classic Star Trek problem-solving trope of having one character present a super complicated-sounding technobable solution just so some other character can restate and oversimplify it for the audience. You know, like putting too much air in a balloon!
Ambassador Spock's service record on the tablet Spock is handed. It mentions him serving as Executive Officer on the Enterprise NCC-1701-A, and I thought he took a vow never to reveal information about the future?
Fitting the Enterprise crew (430 by TOS numbers or 1100 according to the old Experience the Enterprise site) into the tiny USS Franklin.
The Franklin having no visible shuttlebays, despite the transporter being cargo-only (until Scotty gets his hands on it) and us seeing NX-01-style shuttlepods landing in the Franklin logs.
Fitting the Enterprise crew (430 by TOS numbers or 1100 according to the old Experience the Enterprise site) into the tiny USS Franklin.
The Franklin having no visible shuttlebays, despite the transporter being cargo-only (until Scotty gets his hands on it) and us seeing NX-01-style shuttlepods landing in the Franklin logs.
I think it's safe to say the crew were hidden away in another hidey hole of Jaylah's and not on the Franklin considering it's size and their lack of presence during the final confrontation. Which is absolutely fine as Krall and his merry drones had already buggered off and left the planet, so it'd be far safer being left than brought into a firefight.
As for Spock and his service record - Kirk and Spock obviously knew something of Spock #1's past. They knew they served together, and that Kirk #1 was captain. It's not a big spoiler for the other universe. I suspect all the vital information would have been erased form any personal records he had, but personal stuff would have remained. It might not be logical, but I'm sure he'd want to pass on something to his other self.
It doesn't make much sense for the Stargazer to already exist. It's another instance where they inserted a Trek reference just to have one- without using it in a context that makes sense.
I'll just pretend that there was a time travel adventure going on at Yorktown. What a wacky place.
I'll just pretend that there was a time travel adventure going on at Yorktown. What a wacky place.
Or it is an Easter egg that has no bearing on the universe.
Speaking of Easter eggs, I don't think R2D2 is in Beyond since the FX wasn't done by ILM.
It doesn't make sense for a Firefly class ship to be flying around on New Caprica, but it happened and doesn't ruin the show.
Why not? My impression was that Stargazer was an old ship even when Picard took command. It's kitbashed from refit-Enterprise parts, so is presumably from the same era.
The Aegis is 1787 and in the Bridge Simulator game, she's been out there some time, Yorktown is building the newest and best ships in the fleet because fuck it, she is. And Stargazer could well be the brand newest hull, ready to get out there.
The Enterprise A, could well have been the NCC 3071 for all we know (which would have been cool....).
Don't fret these things, you won't live as long.
The Enterprise A, could well have been the NCC 3071 for all we know (which would have been cool....).
Don't fret these things, you won't live as long.
How do we know that it wasn't a previous version of the vessel? After all there has been plenty of enterprises down the years...
We have little reason to assume any significant portion of the crew survived. Krall's methods for kidnapping them were quite destructive: 50% casualties might well be expected there already. Krall would then kill further crew for his life support needs. How many times did Scotty manage to fire up the transporter? A dozen times would already be stretching it, and it was no more than 20 crew per sortie...
Probably not what the writers intended, but that's what the movie tells us. The meager hundred or so extras being marched around is all Kirk was able to rescue. And you can stow a hundred people in two runabouts.
Would the Franklin have actually needed a surface access method? She was an experimental vessel even in her later years - possibly still a propulsion testbed, "pushing frontiers" by flying to a great distance and back, rather than by surveying anything at the destination.
OTOH, despite Scotty's protestations, she did fine in planetary landings and takeoffs on her own!
Timo Saloniemi
Similar threads
