EVE Fiction

Star Wars is fantasy, so any discussion trying to apply a scientific angle will find little of value there.

I vote Battlestar Galactica ;D

I'm afraid star trek loose badly since cheese (yes cheese thats how ridiculous star trek tech is) and computer virus create chaos onboard star trek ships that can lead to their destruction.

Like other biological forms, gel packs were susceptible to bacteria and viruses. As such, heating them could remove such infections. (VOY: "Learning Curve")
◾ They were infected with bacteria due to cheese created by Neelix. (VOY: "Learning Curve")
◾ A gel pack in the mess hall was infected with a macrovirus, and led to an outbreak when it ruptured. (VOY: "Macrocosm")
◾ During a voyage through a Mutara-class nebula, the gel packs began to fail due to subnucleonic radiation. (VOY: "One")

http://en.memory-alpha.org/wiki/Bio-neural_gel_pack

After arriving to Iconia, the Yamato received an Iconian software transmission and was unable to continue the investigation due to random system failures, later on discovered to have been caused by the software. An engineering team of 18 personnel were killed when the force field in a shuttlebay was shut down. The Yamato left Iconia to rendezvous with the Enterprise-D to solve the malfunctions and convince Captain Jean-Luc Picard to continue with the exploration of Iconia. The IRW Haakona under cloak detected the Yamato and copied its log transmissions to the Enterprise-D, while it was traveling to the rendezvous.

After the Yamato had arrived closer to the Federation side of the Neutral Zone, a position twelve hours and sixteen minutes away from Iconia at warp 8. The Iconian software caused an antimatter containment failure. The magnetic seals around the dilithium chamber collapsed, and the computer initiated the emergency release system to dump the Yamato's supply of antimatter. However, the program caused the release to halt with antimatter remaining within the ship, resulting in a warp core breach. While the saucer section was thrown free of the breach, the hull disintegrated, exposing all its decks to space. The Yamato was lost with all hands. (TNG: "Contagion")

http://en.memory-alpha.org/wiki/USS_Yamato

Other examples of how ''great'' star trek engineering is.

Star Trek Safety

Does Star Trek engineering follow any of the principles described above? Read the following excerpts from the script of the 37th TNG episode ("Contagion"):

Worf: Sir, there is an energy build-up in the Yamato's engineering section.
Picard: Yamato, this is the Enterprise, come in Yamato.
WORF: Magnetic seals in the antimatter chamber decaying!
(The USS Yamato blows up)
...
Laforge (pointing at schematic of Yamato engine room): Sensor recordings reveal that what we witnessed was an uncontrolled and catastrophic matter/antimatter mix. The magnetic seals between the chambers collapsed --
Picard: That's not possible.
Laforge: Yes, sir, it is, but a highly improbable series of events has to take place before such an occurrence can result.
Picard: Explain.
Laforge: In the event of a breach of seal integrity there is an emergency release system which dumps the antimatter.
Data: Apparently such a dump began, was then halted, and the containment seals were dropped. There was still sufficient antimatter present to lead to the result we observed.
...
(They discover that the Enterprise is infected with the same computer virus that destroyed Yamato)
Laforge: Sir, the Enterprise computer system is a lot like our bodies with a voluntary and involuntary system. Probably ninety percent of what happens on this ship is done automatically, completely beyond our control. We're sitting on a bomb that could go any second -- or never.

Of course, this is just one of many near-disasters. If I had a dollar for every time the Enterprise nearly blew up, I'd be a rich man. Two of the most obvious problems are described in the dialogue above: emergency measures are unreliable, and the entire system, as conceptualized by the show's writers and tech advisors, is inherently unsafe. Not only do the fictional engineers of Star Trek ignore the sensible and time-tested engineering risk management principles of redundancy, diversity, isolation, and failure actuation, but whenever possible, they actually do the exact opposite! Consider:
1.
Instead of minimizing excess reactivity, they seem to be doing everything in their power to increase it. Evidence of the high excess reactivity of a warp core can be found every time one of 'em blows up. For example, in "Generations", they knew the reactor was going to blow five minutes before it actually did, and they couldn't do anything but evacuate. In "Disaster", we saw a similar scenario; the reactor was counting down to doomsday throughout the entire second half of the episode. The only way they could stop these catastrophes was to eject the entire warp core or restore the containment field. You would think that they could simply shut off the flow of antimatter into the chamber (or at the very least, redirect it out into space), but it appears that even if they do so, the warp core contains enough unreacted fuel at any time to destroy the entire ship. It's a textbook example of extreme excess reactivity.

2.
Instead of redundancy and diversity, they seem to have just one system for any given function. In "Contagion", they described exactly one emergency antimatter storage dump, whose failure caused the total destruction of the USS Yamato. In "The Naked Now", we found that the ship only has one central computer core, whose partial disassembly left the Enterprise helpless in the path of an oncoming chunk of iron. In several combat incidents, all of the weapons on the entire ship were disabled by a single hit. In "Generations", we found that they have only one warp core ejection system, and when it failed, the ship was doomed. They may occasionally speak of redundancy but they've given no evidence of it, so it seems apparent that the Enterprise lacks either redundancy or diversity (or both) in its critical systems.

3.
Instead of isolating critical systems from one another, they actually merge them as much as possible! All of the ship's systems share everything from physical enclosures to sensors and of course, a common centralized computer. That is why a virus was able to spread into every conceivable system on the entire ship after starting from just one point in "Contagion", rapidly affecting everything from doors to turbolifts, replicators, lighting, weapons, shields, communications, and of course, the warp core. Instead of envisioning multiple independent systems, some of which are isolated and some of which exchange data with one another, the writers chose to envision a single "Big Brother" computer which runs everything. It knows when you've been sleeping ... it knows when you're awake ... it knows when you've been bad or good, so be good for goodness' sake ...

4.
Instead of employing the "dead man's switch" principle, their entire design principle is to make the ship utterly dependent, minute by minute, second by second, on the continued operation of numerous active systems. Without the much-ballyhooed structural integrity field, the ship won't even hold together. Without various force fields and containment systems, the ship will explode in a fraction of a second. Even when they take a biohazard on board, they contain it exclusively with a forcefield, which means that the lives of the entire crew are dependent on the continued operation, millisecond by millisecond, of some forcefield generator. I know that bottles and walls may seem "primitive" to the pinheads who write the show, but they work. And in engineering, you use what works. Not necessarily the latest and greatest.


http://www.stardestroyer.net/Empire/Essays/Engineering.html

Sure, personally I think Star Gate would probably own everything, Asgard and the Ancient's would one pawnage all.

Too many of the listed settings feature over the top plot devices, time travel and effectively universe changing magic because a script writer thought 'hey, lets be lazy!'. Heck, even Eve has it if you go looking. The problem of magical plot devices within the various settings you've listed leads to the answer to your question being: The results of such a hypothetical dreamland confrontation depend on who's writing the script / story.

Personally,

Coolest looking - SSV Normandy SR-2 (Mass Effect)

Most Powerful - V'ger (Star Trek - The Motion Picture) followed closely by the Tardis (Doctor Who)

Most Iconic - Either the Millennium Falcon or Star Destroyer (Star Wars)

Ugliest - Serenity (Firefly/Serenity) and Engineers’ Ship (Prometheus)

Most useless - The USS Sulaco (Aliens) and The Event Horizon (Event Horizon)

Honourable mention - Borg Cube (Star Trek) for making geometry intimidating.

Unfortunately, even with the sheer numbers of vessels a New Eden-based society can churn out, I am inclined to say that the limited offensive power (and correspondingly limited defensive systems) will render those fleets fairly insignificant.

Consider, for instance, that a Clone Wars-era cruiser was equipped with 48 primary weapons each with an effective yield of 200 gigatons/shot (let alone secondary weapons); shield dissipation rates would be expected to receive fire from similar weapons. By the end of the Clone Wars, such vessels were considered outmoded for general fleet combat and had been replaced by significantly more potent vessels. By 0 ABY, even these 2nd-generation vessels were long since retired from general service and replaced by still-more-powerful vessels. A Star Destroyers' anti-starfighter weapons can be effectively measured as having an output of roughly 30TJ per shot; medium-caliber turbolasers may have a staggering output of 6,700TJ, with heavy anti-capital ship weapons scaling even higher.

Compared to this, for reference, a Revelation's capacitor has a stock capacity of around 57TJ - I can't be bothered to calculate yield-per-shot at the moment, but it is likely to be considerably lower than turbolasers' effective yield.

I hereby nominate the Shadow Battlecrab as absolutely best looking ship ever designed! Followed by Narn Regime Bin'tak Dreadnought and ISA White Star class.
Honourable mention: SA-23E Mitchell-Hyundyne Starfury (Aurora class) as probably the most realistic space fighter.

Enter Babylon 5 universe. While in terms of sheer power most of the regular races' ships fall way below ISDs, Vorlons may have something to say about that. The tech overall should be around or slightly above that of the StarGate universe.

Of course, if James T. Kirk or Jean-Luc Picard are alive, every other universe loses automatically.