[NGTM-1R]

And because I'm doubleposting like a madman, I'm not making this **** up: that's how real-world aircraft and their Radar Warning Receivers work.

[MatthTheGeek]

Oh yes, right. Realism. In my Freespace. How could I forget about that.

[NGTM-1R]

Oh yes, right. Realism. In my Freespace. How could I forget about that.

So you have a better explanation? One that explains how your fighter is able to detect the fact you are targeted and that enemies are seeking missile lock separately? One that explains how it can tell when you've evaded a missile even when it comes in on a dead aft bearing and you didn't turn at all?

Go on, we're waiting. Speak your genius. We seek enlightenment.

[MatthTheGeek]

One word. Oversight.

Cause we all know how rigorous Volition was in Freespace in general, right ?

Keep in mind that I'm not saying they're definitely not using systems similar to ours. I just say that you can't be sure they are.

[NGTM-1R]

Keep in mind that I'm not saying they're definitely not using systems similar to ours. I just say that you can't be sure they are.

Practically, there's no other way the system could work but to detect these things and their various degrees. You have to do it this way. It's not like they can rely on where his nose is pointed. There can easily be thirty-degree differences between nose pointing and missile target, but it will lock and fire. (To say nothing of the FOV of a missile mount on a warship like in the FS1 training missions, or on the Moloch and Deimos.) It's the same thing with a missile coming in from dead aft, you launch a countermeasure, it goes dead aft too, but your fighter still realizes somehow that the missile is now attacking the countermeasure rather than you.

That's why I asked you to describe another way. There isn't one that works for this context. You have to be able to read the enemy's mind, and that means reading his emissions since his physical actions are not always indicative.

[MatthTheGeek]

My point when talking about oversight, was that this little detail of gameplay isn't trustworthy enough to indicate that Volition wanted the Shivans to have such a similar technological basis to ours. Which would mean that, in case it indeed is an oversight, then we aren't supposed to detect these locks at that stage of our comprehension of Shivan tech.

EDIT: I must also add that I think it would be a shame to see modder's creativity be restrained about Shivan tech just because this is canon by such a minute detail of gameplay.

[The E]

Yeah, no. In the absence of other information, gameplay is canon. Of course modders are free to reinterpret what is seen in retail, but saying "this can't be canon cos I don't like itit's probably an oversight" is just stupid.

[MatthTheGeek]

Where did I say "this can't be canon" ?

[NGTM-1R]

The E is saying, I think, that canon is what made it to release. The little inconsistencies like that are now forever a part of the game universe. It's too late to go back on them, we have to live with and justify them instead. (Or just throw them the **** out and say it was for the good of the story, but at least admit we're throwing it out.)

That and the fact that the Shivans are (admitted by FS2) constrained by the same physical laws means that while their systems may be laid out differently, on a subject like how to determine optimal pulse repetition for accurate information on a moving target the governing factors are in the math, not the psychology.

[mjn.mixael]

Popcorn... I need moar.


Such a heated debate over something so trivial! 

[Black Wolf]

Popcorn... I need moar.


Such a heated debate over something so trivial! 

Aaand welcome to HLP.

Hell, welcome to the Internet.

[MrTealTwo]

Well, it was exciting reading, though