Which they don't.No, it's like suggesting that some highly classified program in the NSA or CIA has a more advanced computer than CERN.
Of course not. Just that THEY'RE not the ones working on it. They outsource that work in defense contracts to people like Intel and IBM, who DO specialize in high performance computing and have billions of dollars worth of business riding on their ability to master that technology. The CIA and the NSA use that functionality, but they're not the ones developing it.You think they're taking things like quantum cryptography lightly?
Implying that something as huge and expensive as an aircraft carrier could ever be described as "run of the mill"The Vengeance isn't a run-of-the-mill aircraft carrier.
Superior COMBATANT, yes. In which case you're probably right, it's definitely not an aircraft carrier. It's more the equivalent to a small black-budget military aircraft or an attack submarine, considering it had to be built using off the shelf (and off the books) hardware without drawing attention to itself.It's a top secret project built by an organization that "doesn't exist", designed to be superior to any other type of vessel known to Starfleet.
Is to neutralize the control signals it uses to coordinate its movements, thus forcing the drones to either disperse into a huge chaotic mass of isolated (and unarmed) small targets that can be shot down at your leisure, or go on colliding with each other like the world's most hilarious air show disaster.A good way to defeat a swarm...
As a question of endurance, then its firepower is irrelevant. Vengeance is a Big Gun battleship optimized for smashing other starships.Looked at that way...if the V had the computational ability (whether man or machine) to analyze the signal to figure out what was going on, and the endurance to survive the swarm's assault long enough for them to either exploit the swarm's vulnerability or escape to a safe distance until they could do so, then maybe the V would have fared substantially better.
The computational aspect is much more important. We KNOW Vengeance doesn't have the personnel for it, and we also know this sort of information is not and has never been the kind of thing a computer will actually produce unless someone on the crew starts asking very specific questions.I don't think we know enough about the V to say for certain whether the V had that sort of endurance though.
What are you wondering for? That's EXACTLY what he did.I wonder whether if it was a choice between losing the weapon and losing the initiative by letting the ship escape, whether he would have just had the swarm blow the ship out of the sky.
Neither was cutting off the engineering section at the neck, actually. Both of those were specifically intended to deprive the ship of propulsive power in order to buy time for his boarding action to find the artifact. If Enterprise had been higher up in its orbit, the saucer wouldn't have crashed at all and Krall would have simply left the ship as a lifeless derelict and flown off with the crew.^To respond to the last point first, I admit I only saw the movie twice, but I don't think Krall ever thought the E had a serious chance of escaping. And I don't see the need to go all-caps on me there. If you're referring to snipping off the nacelles, that was very clearly not intended to destroy the ship.
This, again, assumes the Vengeance's crew would be able to formulate a defense in ANY amount of time, which far from certain.The endurance of the V becomes highly relevant if we look at the situation in terms of buying the ship enough time to a) retreat to a safe distance and/or b) formulate a defense. If we assume the ship (so to speak) could implement a defense in ten minutes, then the battle hinges on whether the V can survive against the swarm for ten minutes.
Well, it's DESIGNED to be operated by a minimal crew, which fits its mission profile as a fast attack craft used in covert operations (the more people know about it, the more things can go wrong). We can safely assume it had close to its standard crew complement at the time Admiral Marcus sent it against the Enterprise, considering that had Marcus' plan actually worked the way it was supposed to the Federation would have been at war with the Klingons only hours later.Also, while I've generally agreed with the points you've made in this discussion, you seem to be operating from the premise that the V would have minimal crew (one?) during the confrontation.
It would pretty much HAVE to be for Marcus' plan to make any sense. Of course, Marcus' plan making sense is also far from a sure thing...We don't know whether the V was fully equipped during ID
The only other picture to consider is that someone on the bridge of the Vengeance would be able to detect the swarm's signal and recognize in a handful of minutes, while under attack and with the ship being boarded, that the signal is NOT a jamming signal but is actually a cybernetic network coordinating the swarm's movements, that it is susceptible to interference at a very specific frequency, that it can be disrupted by broadcasting strongly on said frequency, and to even have in mind a specific type of signal that would be disruptive enough and random enough to affect the swarm. And do all of this with no prior experience with the swarm, no benefit of hindsight, not even a GLIMPSE of the underlying technology, without Jayla's input as to the nature of the swarm and how it moves, and without several hours (days?) of time to consider their encounter and come up with ideas on how to fight it.I'll be the first to agree with you that the V's computers all by themselves wouldn't have saved the ship, but there's more to the picture than you seem to be considering.
Given the miscellaneous hull panels, the Vengeance's hull is not particularly thick, I doubt it is much greater than that of the Enterprise's hull. It is also unknown how much the swarm ships can penetrate, except the maximum observed is punching through the airlock doors of Yorktown. I don't remember how thick those are.However, if its armor is thick enough, it could cause the swarm ships to be destroyed as they impact the ship and are unable to penetrate its armor. How much armor (or ship structure) is required to prevent the Swarm from penetrating through, and does the Vengeance carry that much?
We've never seen shields in the 23rd century at all. In another thread we kind of had an "Aha!" moment where we realized that TOS-era ships use a type of DEFLECTOR that doesn't have any visible effects; it's mainly used for pushing incoming projectiles and energy off their course from the ship, which either reduces their striking power or causes them to miss altogether. Certain things -- torpedoes, for example -- can "burrow" through those deflectors and still impact, but evidently they don't do anywhere near as much damage in doing so. An exception to this might be the V'ger glowpedo, which his the deflectors and then flattens against it as its sparkly bits try to push through (and partially succeed). But that's a "form of plasma-energy" and therefore more similar to a phaser blast or something; projectile weapons with propulsive systems will probably still push through even though they're not as powerful.Have we ever seen shields in the Kelvinverse?
I agree that 23rd century "shields" were not like the nextgen "bubble" effect. However, we have seen the TOS shields/deflectors be effective against torpedoes numerous times (Errand Of Mercy springs to mind, with the torpedoes impacting on the surface of the lower saucer)We've never seen shields in the 23rd century at all. In another thread we kind of had an "Aha!" moment where we realized that TOS-era ships use a type of DEFLECTOR that doesn't have any visible effects; it's mainly used for pushing incoming projectiles and energy off their course from the ship, which either reduces their striking power or causes them to miss altogether. Certain things -- torpedoes, for example -- can "burrow" through those deflectors and still impact, but evidently they don't do anywhere near as much damage in doing so. An exception to this might be the V'ger glowpedo, which his the deflectors and then flattens against it as its sparkly bits try to push through (and partially succeed). But that's a "form of plasma-energy" and therefore more similar to a phaser blast or something; projectile weapons with propulsive systems will probably still push through even though they're not as powerful.
The bubble shield of TNG is probably an additional layer of protection for softer ships like the E-D that don't use a lot of armor protection (all those windows, man!). 23rd century ships probably just use a thicker hull.
Considering a matter-antimatter detonation against an unshielded target would pretty much obliterate said target instantly (see "Obsession" and "Immunity Syndrome" for references and also the black hole scene in ST09 for what that kind of detonation SHOULD look like) it's a foregone conclusion that photon torpedoes do not work that way. The best example is the attack on Kronos-1, in which Gorkon's ship is hit in its engine room by not one but TWO photon torpedoes without its shields up.
There's ALOT of evidence for the theory that photon torpedoes are basically over-engineered kinetic kill weapons: their warheads deliver a lot of kinetic energy, something like a rapidly-expanding forcefield that creates a physical shockwave even in the vacuum of space (something even nuclear warheads cannot really accomplish). Their main advantage, however, seems to be their ability to punch through layers of deflector shields and damage the target underneath; photon torpedoes can and do cause physical damage even against fully shielded targets, sometimes to the point of heavily damaging said target without even taking the shields down. An excellent example of the latter is again in TUC, where Chang's photon torpedoes leave huge dents in the Enterprise's hull and blow out consoles all across the ship even while their shields are still up (and they do the same thing to the Excelsior).
We use essential cookies to make this site work, and optional cookies to enhance your experience.