Elheru Aran wrote:But there's some small consolation-- one of his "kids" pulls out a rather interesting model of, apparently, a starfighter of some kind? Wouldn't mind a closer look at that.
You wanted a closer look? Here it is. Aliens EVAC Fighter.
Moderator: Vympel
Elheru Aran wrote:But there's some small consolation-- one of his "kids" pulls out a rather interesting model of, apparently, a starfighter of some kind? Wouldn't mind a closer look at that.
It's a good question but they wouldn't have helped. The entire chairs and consoles were ripped out. If you were strapped in, you'd probably die anyway when a 50kg chair lands on you.Elheru Aran wrote: -- Why does not the fucking Enterprise have SEAT BELTS. Goddamnit.
In David Weber's Honorverse series, they used a shield system but it was considered 'solid' in that it would block both incoming and outgoing fire. To avoid damaging their own shields and wasting their energy, they fired through shield 'windows' that were opened and closed as needed. Given that the Enterprise can fire at almost any angle, I'd say either the shields rotate the windows as necessary, which would take a lot of work, but it would be possible. The problem is, there's a unique thing we see when the BoP fires through the Enterprise's shields: there is some shield interaction, while none has ever been seen when the ships fire. Also, we saw the Enterprise's phaser fire hit the BoP's shields and be absorbed. So, I'm going to say that they're using a type of window to fire.Tribble wrote:There was a really good point I just read on the YouTube comments. In order for a ship to fire through its own shields, it has to have the frequency of its weapons calibrated to the frequency of its shields. Otherwise, the shots would hit the inside of the shield, right?
So...
The BOP's weapons are calibrated to the E-Ds shields
This means that the BOP's shields must also be calibrated to the E-D's shields in order for the BOP's weapons to fire through them.
The E-D's weapons are naturally calibrated to its shields.
This means that the E-D's shots should be going through both its shields and the BOP's shields, since they are all on the same frequency.
Yet another reason why this fight should have ended with a single salvo.
Which is either poor design or absolutely shitty materials. The consoles are built *into* the ship's structure. They should *not* be getting ripped out, and if they do, it really doesn't matter if you're strapped in or not. Note that people are more likely to survive auto accidents while wearing seat belts; the whole "if you're flung away from the accident you're more likely to survive" notion is bullshit.Prometheus Unbound wrote:It's a good question but they wouldn't have helped. The entire chairs and consoles were ripped out. If you were strapped in, you'd probably die anyway when a 50kg chair lands on you.Elheru Aran wrote: -- Why does not the fucking Enterprise have SEAT BELTS. Goddamnit.
Elheru Aran wrote:Fisher, thanks for the picture. Aliens toy, eh? Cool beans
If the ships are using windows for weapons / scanning (the Pheonix does so in "The Wounded,") then the shields shouldn't need a frequency at all, and they should block the entire spectrum. And if that were the case, why would the weapons have a frequency setting as well? They wouldn't need to if they were fired through a window in the shields.Baffalo wrote:In David Weber's Honorverse series, they used a shield system but it was considered 'solid' in that it would block both incoming and outgoing fire. To avoid damaging their own shields and wasting their energy, they fired through shield 'windows' that were opened and closed as needed. Given that the Enterprise can fire at almost any angle, I'd say either the shields rotate the windows as necessary, which would take a lot of work, but it would be possible. The problem is, there's a unique thing we see when the BoP fires through the Enterprise's shields: there is some shield interaction, while none has ever been seen when the ships fire. Also, we saw the Enterprise's phaser fire hit the BoP's shields and be absorbed. So, I'm going to say that they're using a type of window to fire.Tribble wrote:There was a really good point I just read on the YouTube comments. In order for a ship to fire through its own shields, it has to have the frequency of its weapons calibrated to the frequency of its shields. Otherwise, the shots would hit the inside of the shield, right?
So...
The BOP's weapons are calibrated to the E-Ds shields
This means that the BOP's shields must also be calibrated to the E-D's shields in order for the BOP's weapons to fire through them.
The E-D's weapons are naturally calibrated to its shields.
This means that the E-D's shots should be going through both its shields and the BOP's shields, since they are all on the same frequency.
Yet another reason why this fight should have ended with a single salvo.
Now, this works out pretty well for the Klingons because if they are using windows, the bulk of Klingon ships have very narrow weapon arcs. If this is the case, then it would limit the amount of processing they'd need to do to fire through their own shields. Plus, imagine how hard it would be to hit the narrow 'window' in the shields? But I mean, that's just a theory of mine and most of mine are hit or miss.
You answered your own question; Lursa was targeting manually using the periscope thing. Just like how Khan didn't realise Sulu was manually locking weapons.Eternal_Freedom wrote:On that note, shouldn't the E-D have had more warning? How many times have we see Worf announce "the vessel has armed weapons" or "they are locking weapons on us." Hell, The E-Nil managed that in TWOK. A report of "they are targeting us" should be answered with "lock our own weapons on them, be ready to return fire." Riker shouldn't have needed to order Work to return fire.
The fact that the Enterprise did fire on the BoP and her phaser strike was blocked by the BoP's shields should show you that your logic is faulty.Tribble wrote:There was a really good point I just read on the YouTube comments. In order for a ship to fire through its own shields, it has to have the frequency of its weapons calibrated to the frequency of its shields. Otherwise, the shots would hit the inside of the shield, right?
So...
The BOP's weapons are calibrated to the E-Ds shields
This means that the BOP's shields must also be calibrated to the E-D's shields in order for the BOP's weapons to fire through them.
The E-D's weapons are naturally calibrated to its shields.
This means that the E-D's shots should be going through both its shields and the BOP's shields, since they are all on the same frequency.
Yet another reason why this fight should have ended with a single salvo.
To be fair, the writers were backed into a corner by Rick Berman, who told them "The Enterprise has to have a space battle that causes enough damage that the stardrive blows up and sends the saucer crashing onto the planet below. Because of our budget however, you can only have one enemy starship. Oh, and that enemy starship has to be a Klingon Bird of Prey, because we're reusing the explosion shot from Star Trek VI."Tribble wrote:What's sad is that this stupidity could have been avoided so easily. All they had to do was have the E-D get attacked by multiple ships and while they manage to destroy them all they suffer the irreparable damage to the warp core.
Or instead of it being a 20 year old BOP they could have used a Vor'cha, and the opening salvo knocked out the shield generators.
Sloppy, sloppy writing.
How about the "not detecting armed weapons" or "not detecting they're preparing to fire"?Prometheus Unbound wrote:You answered your own question; Lursa was targeting manually using the periscope thing. Just like how Khan didn't realise Sulu was manually locking weapons.Eternal_Freedom wrote:On that note, shouldn't the E-D have had more warning? How many times have we see Worf announce "the vessel has armed weapons" or "they are locking weapons on us." Hell, The E-Nil managed that in TWOK. A report of "they are targeting us" should be answered with "lock our own weapons on them, be ready to return fire." Riker shouldn't have needed to order Work to return fire.
They can pick up the offensive ship using its computer to scan for targets, but not someone using their eyes.
writing that makes meEternal_Freedom wrote:
How about the "not detecting armed weapons" or "not detecting they're preparing to fire"?
If you'd said that to start with we could have saved ourselves another four pages of 'waaa! Generations wasn't very good'Prometheus Unbound wrote:writing that makes meEternal_Freedom wrote:
How about the "not detecting armed weapons" or "not detecting they're preparing to fire"?
Well. Ok, sure. But then we wouldn't have a discussion.Crazedwraith wrote:If you'd said that to start with we could have saved ourselves another four pages of 'waaa! Generations wasn't very good'Prometheus Unbound wrote:writing that makes meEternal_Freedom wrote:
How about the "not detecting armed weapons" or "not detecting they're preparing to fire"?
Though how the board would have coped without that point being underlined for the umpteenth time I do not know.
The writers were also keen to crash the Enterprise. Ron Moore proposed a saucer crash as a season-ending cliffhanger during TNG.DaveJB wrote: To be fair, the writers were backed into a corner by Rick Berman, who told them "The Enterprise has to have a space battle that causes enough damage that the stardrive blows up and sends the saucer crashing onto the planet below. Because of our budget however, you can only have one enemy starship. Oh, and that enemy starship has to be a Klingon Bird of Prey, because we're reusing the explosion shot from Star Trek VI."