This will be an explorer, so it will be spending FAR more time in cruise configuration, and sprint configuration will be of less importance (it won't be expected to fight a war).
However we also can't really afford to trade cruising speed for sprint speed on an explorer either.
I'll admit to being more interested in top cruise than sprint. It's an exploration vessel, it's going to have more use out of that.
It's going to be out exploring. It's not going to be near any starfleet ships to respond to distress and if it responds to a call it's because it literally stumbles over something and sprint won't matter.By that same token, its first use is as an exploration vessel, which by its nature is usually something the ship can do at a more relaxed pace. Copernicus should only have to pour speed on in response to an immediate crisis, which sprint speed would help with. Explorers responding to problems tend to be called on short notice and at short ranges because they happen to be in the area, so a sprint speed is the more relevant factor.
I'm just going to say it now; it will be kind of sad if our Warp 7 explorer can't actually manage to hit Warp 7.
However we also can't really afford to trade cruising speed for sprint speed on an explorer either.
@Sayle, before the bonuses from whichever option we pick are factored in, what's our current cruise and sprint?
I see the transporter has become standard. And apt that it is located in the bowels of the ship, right between the computer core (on which it depends) and sickbay (which it shall service).
Also, NOyodyne, please. I'd prefer this ship to work.
By that same token, its first use is as an exploration vessel, which by its nature is usually something the ship can do at a more relaxed pace. Copernicus should only have to pour speed on in response to an immediate crisis, which sprint speed would help with. Explorers responding to problems tend to be called on short notice and at short ranges because they happen to be in the area, so a sprint speed is the more relevant factor.
Does the performance roll apply only to the bonus of that configuration or would it apply generally to both sets.
In which case, I think I'd like to back
Does the performance roll apply only to the bonus of that configuration or would it apply generally to both sets.
IE if we pick a quad spring configuration and roll well/badly will it effect the cruise speed?
In which case, I think I'd like to back
[ ] Dual Nacelles Sprint (+0.2 Sprint)
Which finally hits the Warp 7 target on a sprint, with a minimum of risk.
There's not been any mention of five-year missions in the design briefing, and moreover this isn't the Federation of Kirk's time - it's entirely fair to imagine we're not at that point yet, since we're (probably) more than 50 years of development away from the Constitution-class which as far as we know were the first vessels capable of such long-term deployment. If Copernicus just does short jaunts into the unknown from Federation territory it would still be an iterative step forward.The core reason you build an explorer is to go on five-year missions beyond Federation borders, and the more stuff it can visit and do in that time, the higher your return on investment.
Probably going to do more NX Enterprise style 6 months to Two Year Voyages at mostAlso the parallel configuration toys with yet again failing to achieve the speed the engine was named for, which is just fucking embarrassing if it happens.
There's not been any mention of five-year missions in the design briefing, and moreover this isn't the Federation of Kirk's time - it's entirely fair to imagine we're not at that point yet, since we're (probably) more than 50 years of development away from the Constitution-class which as far as we know were the first vessels capable of such long-term deployment. If Copernicus just does short jaunts into the unknown from Federation territory it would still be an iterative step forward.
It also boosts chonk and chonk is good.