7 ms·
Star Trek's bridge controls can be reconfigured, but there's a standard static configuration that doesn't change while they're in use. This is also referenced
by Izkata 7y ago
Star Trek's bridge controls can be reconfigured, but there's a standard static configuration that doesn't change while they're in use. This is also referenced at a different point in Voyager when Tuvok is annoyed by how Tom Paris uses a nonstandard configuration. So that at least reduces the need for constant visual contact.
- archon 7y agoThere's another Voyager episode in which Tuvok is temporarily blinded and he tells the computer to turn on the tactile interface so he can work on a computer console. So even 25 years ago before everyone had a touchscreen in their pockets, it was obvious that touch screens wouldn't be great for all situations.
- ringshall 7y agoAnd of course there’s the comment in ‘All good things’ by Dr. Crusher when she says she can’t believe how they got by with 2D controls in the old days, and how the current holographic controls were much easier to use. So, Star Fleet made the same transition as the US Navy, from a touchscreen to 3D tactile controls.
- TomK32 7y agoIt's it true that the whole bridge section can be separated and replaced from the saucer, which of course can also be separated from that thing with the engines?
- amiga-workbench 7y agoThe bridge modules can be fairly easily swapped out in drydock, but I don't believe that can be done while underway. The Galaxy class was the first class of ship with a saucer separation system that could be re-attached while in flight. I believe the Constitution class did have the ability to separate its saucer, but that was accomplished with explosive bolts and it couldn't re-attach without being in drydock.
- animal531 7y agoRight, before they mainly used it as an escape vehicle in case of warp nacelle or containment issues.
- amiga-workbench 7y agoYeah, the warp core ejection systems always seem to conveniently fail. You would want to dump the entire engineering section and haul ass if you were sitting on an antimatter bomb.
- cannonedhamster 7y agoThere were also physical backups in case the automated ejection system didn't work. There was always a physical backup to any touch interface that was critical to system operations.
- magduf 7y agoThat galaxy-class saucer separation thing was honestly not a great idea, and it was somewhat annoying when they used it in the episodes. The problem with it is that only the "stardrive" section has warp capability, so what good is it to be able to separate except for using the saucer as a last-resort escape pod in case of warp engine failure? The saucer is simply too slow to go anywhere in a reasonable amount of time without a warp engine: at sublight speeds, it would take years just to get to the closest star system. This is probably one of the most annoying things about Star Trek: they completely ignored speed-of-light issues like this too often. Using "warp drive" as a plot device to get the characters from system to system in a week or less at FTL speeds is fine, but if you're going to do that, don't fall back on sublight "impulse drive" as something that's actually useful for anything except getting into and out of orbit.
- Izkata 7y agoOne of the reasons for that functionality I don't recall actually making it to an episode - tactical advantage in a fight. The rear section had increased maneuverability when separated, and it resulted in two targets for attackers, both of which could fire back.
- amiga-workbench 7y agoAlso in theory controls for any system can be transferred to any console on the ship, I can think of one episode where Seven transferred helm, tactical and ops down to an engineering console.
- mannykannot 7y agoThat was part of the problem on the USS McCain: there were so many different modes of control that the crew lost track of the state of the system.
- amiga-workbench 7y agoI'd be really interested to see how the UI handled signposting for those handed-off functions, because I don't think the idea is inherently unwieldy, it just needs a good clear implementation.