|
Welcome! The Trek BBS is the number one place to chat about Star Trek with like-minded fans. Please login to see our full range of forums as well as the ability to send and receive private messages, track your favourite topics and of course join in the discussions. If you are a new visitor, join us for free. If you are an existing member please login below. Note: for members who joined under our old messageboard system, please login with your display name not your login name. |
|
|||||||
| Fan Art Post your Trek fan art here, including hobby models and collectibles. |
![]() |
|
|
Thread Tools |
|
|
#1081 | ||
|
Rear Admiral
Location: Austin, Texas
|
Re: Another fan attempt at TOS deck plans
I also think that this was just a "light bulb," and that they're just replacing it. The only real place that CRA and I differ is where the ion pod deploys from... he has it leaving the ship at the B/C "teardrop" while I have it being dragged behind the ship from the "red fantail hatch." I've always found the "ion pod" to be a pretty silly concept... the major deficiency of this episode, IMHO, was having a MANNED "sensor drone," which is effectively what it is. It makes absolutely no sense to have the "pod" be physically attached to the ship (as in how that "bulb" is attached) because there is no way to justify it needing to be "ejected." My "best explanation" is that the pod is used to take specialized sensor reading that require isolation from the "background noise" of the ship. So it's basically an unpowered glass sphere with a chair and a sensor suite, and an extremely-low-powered, optically-based (ie, non-interfering) comm device. It literally is dragged behind the ship at a distance, to permit this "limited background noise" operation. Think of it like a submarine's "towed array" in that sense. Maybe the issue with it being manned is that, based upon how delicate the readings are, even the noise from a single microprocessor-type device would spoil your readings? Anyway, I envision this thing needing to be dragged, not by a "tractor beam" but by a physical cable, some distance behind the ship. In order for that to work, the ship needs to have its deflector shields down (otherwise, the shields would just slice through the tow-cable). THAT explains, to me, why this would happen as it did... the Enterprise is just fine handling an "ion storm" with its shields up, but with shields down, she's vulnerable. The ship has standing orders from "Starfleet Silly Science Command" to take uber-accurate readings of ion storms if they encounter them, using this special piece of hardware. This isn't a "starfleet-wide" standing order, just one given to a few (perhaps just one?) ship as an "additiona duty" to support the science division admiral's "pet project?" So, the ship is required to put itself at risk, but the idea is to manage that risk. Leave the shields down long enough to get a few readings in the "low-background-noise pod" but retract it in time to get the shields back up and prevent any serious damage from occurring. The part that makes NO sense, under any circumstances, is that the guy IN the pod is working without any on-ship support. When Kirk gave the command to recover the pod, it shouldn't have been Finney who was responsible for hitting that particular switch, but in the context of the episode, it was, it seems. Since Finney didn't obey the command to "self-recover" when it was given, Kirk had to hit his command chair's "raise the shields" button, which ends up making the ship "safe" but also cuts the tow-cable (and the air supply, fiber-optic communication line, etc) to the pod. In normal circumstances, they could just circle around and recover the pod, beam him back aboard, etc, but with an ion storm, they would have a hard time locking on with transporter, or even locating this "no emissions" pod at all... meaning by the time they found it, IF they found it, he'd certainly be dead. Until Kirk raised the shields, the ship was essentially like an airplane in a lightning storm... and I'd say that it just happened to catch a single "lightning strike" on that particular running light. That's MY take on it. I think it's similar to CRA's. Now, as for why that item really CAN'T be a manned device... see this: ![]() (And remember, this is on my 1067' long ship... it'll be slightly smaller if you stick with the 947' ship.) This could be a dome on the end of a "capsule-shaped coffin" but as a useable working space... not so much. And if it weren't being deployed outside of the ship... Finney would literally be INSIDE THE HULL the entire time anyway, no more or less protected than the bridge crew (with their overhead window) anyway! |
||
|
|
|
#1082 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
But yeah, I envision it being based in the secondary hull too. |
|
|
|
#1083 |
|
Vice Admiral
Location: In selfless service to fandom, on the road to becoming a Star Trek trivia god...
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1084 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
I'll also review and post the deck levels as Jefferies saw them for the primary and secondary hulls (though I'll most likely stick with the windows for the levels within the dorsal). Where ever I can I'll attempt to post the raw data (so others can make attempts at figuring out how it might apply). |
|
|
|
#1085 |
|
Vice Admiral
Location: In selfless service to fandom, on the road to becoming a Star Trek trivia god...
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1086 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
To provide unique coordinates for both the primary and secondary hulls, each hull has been given it's own zero height (0 ft). For the primary hull, 0 ft is designated the "Weather Deck" and is at the upper rim of the hull. For the secondary hull, 0 ft is designated the "Waterline" and is at the center line axis of the hull. The heights for most of the decks are... Primary Hull:The dorsal is independent of both hulls and it's deck heights I'll figure out based on studies of the 11 foot model's window placement. I've applied the information above to my drafts of the primary and secondary hulls in this diagram. This information can be applied to my earlier sketches where this had been left rather vague. |
|
|
|
#1087 | |
|
Commander
Location: Birdog
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1088 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
From the show, I'd guess the hull thickness to be between 8 to 12 inches... ![]() ...which is about what we see for the shuttlecraft too. As for deck heights... the highest ceilings shown were in the corridors and sickbay, but most other rooms were lower (with structural members often being seen). |
|
|
|
#1089 |
|
Fleet Captain
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1090 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
As for why use the compartment diagram at all? It provides a very nice partitioning of massive decks. Other wise you start with nothing and the question pops up later as to how the compartments come into play. But mainly it was a better starting point than big blank circular decks. The top view of the secondary hull in the turbo lift diagram is more helpful though, and if you look at the floor plans of the secondary hull that I've done you might see where I sort of followed that partitioning rather than the other one (which had bulkheads down the center of the hull). But again, it is not exclusively used... it is used in concert with a number of other references (Jefferies deck heights, the actual set dimensions, the physical shape of the model, etc.). I'd have reached different conclusions if I ignored any of them or weighted them differently (and other people have obviously reached different conclusions), and my conclusions might change again if I find more data. All I'm doing is distilling and refining all the data as I see it... which is why I'm also attempting to make sure people have the data so they can distill and refine it in their own way. I'm not saying (and never have said) that my interpretation is the only one or even the best one. All this really is is my best efforts. |
|
|
|
#1091 | |
|
Commander
Location: Birdog
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1092 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
Early secondary hull partitioning... And some of the graphics used in TOS (including the hull pressure compartments and turbo lift diagrams)... And a better version of the turbo lift diagram can be found here. Don't worry about it... you'd be surprised at how often I mix up some of these numbers (and waste a ton of effort before noticing). |
|
|
|
#1093 | |
|
Commander
Location: Birdog
|
Re: Another fan attempt at TOS deck plans
|
|
|
|
|
#1094 |
|
Fleet Captain
|
Re: Another fan attempt at TOS deck plans
Last edited by TIN_MAN; December 13 2009 at 03:32 AM. |
|
|
|
|
#1095 |
|
Commodore
Location: Twin Cities
|
Re: Another fan attempt at TOS deck plans
But other than that aspect, the alternating sections wouldn't make that much difference (other than the bulkhead right at the window clusters). A lot of it would just be rotating the compartments. But for deck 6 by itself... as it stands now, the compartments enclose both decks 5 & 6 (each compartment being two decks thick) which was needed not to cut a compartment totally in half by a turbo lift tube if the compartment becomes completely closed off (you can go under the tube by dropping down a deck and back up again). The fact that compartments are generally not single decks was sort of important in making them as robust as possible on their own. And it made isolated compartments less claustrophobic for me personally. I spent a lot of time imagining what it would be like when the pressure doors close and you're stuck in a compartment not knowing if the rest of the ship is even still habitable and how long you'd be there for. ![]() I'm sure there are other ways around this (using the other diagram), but I thought that was a good solution to a number of issues while working within that framework. |
|
![]() |
| Bookmarks |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
|
All times are GMT +1. The time now is 02:30 PM.
Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
FireFox 2+ or Internet Explorer 7+ highly recommended.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
FireFox 2+ or Internet Explorer 7+ highly recommended.





















