Re: Probert's REAL N.C.C.-1701-C
@ Mytran
Very concise "Naked Time" graphic that illustrates the issue. I like it. And much better than my "crayons" (actually "highlighters") as most will agree.
@ All
I thought it might be a good idea to ask Andrew Probert, why he included the aircraft carrier
USS Enterprise on the conference lounge display, and this is what he said:
"I didn’t want to clutter up the display. The atomic carrier is there simply for scale, being a somewhat known reference." (Andrew only provided side views for the sculptor)
Of course, from a real life production point of view, we shouldn't forget that the series was made for general, average and ordinary people (that's what I meant with "normal" in the closed TNG thread).
From an in-universe point of view in the 24th Century the starships on display would be the known size reference to get an idea of the carrier size, though.
Anyway, I provided an in-universe explanation, but anything that could suggest that the
Enterprise-C on the wall display is canon, authentic and genuine is obviously not what some people here want to hear.
@ sojourner
I think you better have your translator examined and fixed. Cadet Porky Pig could probably do it for you.
Sure, if Fleet Admiral Shanthi or Starfleet's queen bitch Nechayev would have learned from Guinan what happened in "Yesterday's Enterprise" and then confront Picard, he would have been the one "responsible" who "sent" Tasha Yar to the past in military lingo.
But Guinan (Ron Moore) presented the information in a fashion that even corn farmer Joe Sixpack from Iowa with no military background could understand, that this is
not what actually happened in "Yesterday's Enterprise".
Again, as the final screenplay writer for "Yesterday's Enterprise" Ron Moore could have easily made "Redemption II" compatible with events in "Yesterday's Enterprise",
but he did not! That's rather clear evidence that him and Carson deliberately relocated "Yesterday's Enterprise" into a "parallel universe" (Carson), because that elegant move also took care of a couple of other problematic issues (which I will apparently need to spell out at the earliest next convenience).
I'm looking forward to explanations why he made Guinan and Sela say something differently. Because he was an incompetent screenplay writer?

Because he was a sadist who anticipated that fans would be at each other throats debating how to interprete this "inconsistency"?

I really wonder
who is in need of explaining.
The one thing I increasingly notice in this discussion is that most participants have no problem accepting the revisionistic nature of retroactive continuity, but are utterly unable to accept the possibility that a revision could equally itself be revised - and with the consequence that an erased design (Probert's
Enterprise-C) has been restored like the supposedly revised timeline in "Yesterday's Enterprise".
That "decisive" detail only tells us that in the War timeline:
1. the Klingon outpost's distress messages were not received by the Klingons or the Federation
2. and there was no evidence that the Klingons received or confirmed that the E-C was responding to their distress call.
3. the Federation had no idea what happened to the E-C or even connected the dots to the battle at Narendra-3.
Contrast that to the TNG timeline where:
PICARD: Enterprise C? She was lost at the battle of Narendra Three, defending a Klingon outpost from the Romulans.
1. the E-C was confirmed to be defending a Klingon outpost at Narendra 3
2. the E-C was fighting Romulans
3. the E-C lost the battle
How would they know unless they saw the E-C? And if they did then they'd have eyewitness accounts of what it looked like. Plus, Starfleet and the Klingons would be examining the debris and if it belonged to a mystery ship instead of the native E-C that'd raise red flags.
Because the Klingon/s surviving the Romulan assault (the witness/es of what really happened at Narendra III) had learned of Garrett's first message
and her subsequent distress call:
TASHA: Enterprise C is sending out a distress call, sir. Audio only.
GARRETT [OC]: This is Captain Garrett of the Starship Enterprise, to any Federation ship. We have been attacked by Romulan warships and require immediate assistance. We've lost warp drive. Life support is failing.
Obviously no long-range communication had been possible, but even a Klingon communicator could have picked up this vital information, even if they had been "blinded".
If the Enterprise-C received and acknowledged the outpost's distress call, but nobody else ever heard it, this would suggest that at least some form of Klingon short-range communication had remained intact.
Of course, I'd announce my coming on the same frequency as the caller, but apparently that was only short-range.
And the Klingon survivor/s could have pieced together that
someone had come to their rescue because of the sudden interruption of the Romulan bombardment when the four warbirds diverted their fire against the
Enterprise-C to get rid of this uninvited Federation eyewitness.
The decisive element (also according to an original screenplay draft) was to have Klingon witnesses to tell what really happened.
On the contrary, with no Klingon survivors left alive
but wreckage of a Federation starship, the whole thing could have looked like an unprovoked Federation attack on a Klingon outpost where both perished in the mutual fire exchange. Even better than what the Roumulans could have hoped for.
Lumping Tasha's death on Vargus is inconsistent with your argument here. Of course it was called out as a meaningless death.
Volunteering to die on the E-C and then dying as a prisoner of war while knowing your sacrifice altered history to save the Federation. That's meaningful.
I can immediately think of another (4th) but truly "meaningful death" of Tasha Yar (which I forgot to list):
Man your post until the very last second to ensure the existence of the galaxy and every living being in it.
So out of these four deaths, two are most definitely "meaningful" (because of the meaningful outcomes) while the other two are debatable, at best.
Bob