Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: Zalardis on March 10, 2008, 05:01:15 am
-
Just the object which you destory in the Mission " Into the Lion's Den"(The loop mission that you drive a Shivan
class Fighter Mara)
I think it was the most secret martial device in the game, and there is no explanation in the TECH ROOM
PS: Mara(reconstructed by the GTVI) was the actually best type of Fighter i have used……
-
Which object? You're very descriptionless.
martialc?
-
It's the Shvian Comm Node.
Never really explained, but the Shivans have less of them now...
-
They can get sky sports, thats the only reason........
-
They are communications nodes. You can tell by going close to them (Not to close :P) they sound like the cruiser's (a few missions back) communications to the Iceni.
-
They can get sky sports, thats the only reason........
I would've thought that they were watching pr0n, when suddenly the SOC did a devastating attack, rendering the 'satellites' inoperative. Which made the Shivans angry enough to go and blow Capella up as retaliation.
Edit: Partially pointless nitpicking.
The loop mission that you drive a Shivan class Fighter Mara
Cars are driven. Space ships are flown.
Mara(reconstructed by the GTVI)
Well, they did some modifications, maybe. And probably minor changes so that it would accommodate Terrans. But reconstruction? No no.
-
They probably dropped in a 2nd Gen. Shivan-ship-to-Terran-Cockpit complete with WORKING interfaces and communications. Remember the problem with the Dragon in FS1? The scientists couldn't make it work completely, so they did the best they could. When you jump in a Mara, everything seems to work. That, and it was retrofitted to use Terran weaponry.
-
Hmm... they've figured out beams and flak cannons since then, they must have also gotten the hang of reverse-engineering, possibly on whatever Shivan fighters they had their hands on at the end of the Great War.
-
Edit: Partially pointless nitpicking.
The loop mission that you drive a Shivan class Fighter Mara
Cars are driven. Space ships are flown.
If you're going to nitpick, you pilot space fighters, not fly them.
-
Edit: Partially pointless nitpicking.
The loop mission that you drive a Shivan class Fighter Mara
Cars are driven. Space ships are flown.
If you're going to nitpick, you pilot space fighters, not fly them.
Cars are drive.
Airplanes are flown.
Space ships are piloted.
-
The gta, gti, gtva, and gtvi have had years of experience in modifying and reverse engineering shivan technology to at least have a much better understanding in modifying it's fighter when compared to the first time a shivan fighter was modified for the first time in fs1.
-
The gta, gti, gtva, and gtvi have had years of experience in modifying and reverse engineering shivan technology to at least have a much better understanding in modifying it's fighter when compared to the first time a shivan fighter was modified for the first time in fs1.
That's true, but it seems that the Terran Mara has no slide capacity. Mind you, I don't read those tablefiles...
I think the Comm Node's a plot device. In Inferno, they prevent capital ships from jumping in. Such a feature of the Comm Node isn't FS2 canon...so I think it's safe to assume that you can give the Comm Node any features you wish (like disabling shields or severely compromising your hull integrity).
-
Random tech description I wrote for a mod a while back:
"These enigmatic static emplacements are essentially extremely powerful subspace communication arrays. It is theorized that these communication terminals, or Shivan Communication Nodes, are designed for the purpose of communicating with specific points over intergalactic distances. However, the amount of energy needed to do so is immense, and hence upon its destruction considerable amounts of energy are released. The spinning blades and shell form a highly directional subspace field through which quantum pulses are exchanged. It is theorized that the objective vortex can also be used as the inceptive vortex, through which subsequential quantum pulses can be relayed. This creates a form of two-way communication between vast distances. The technological implications of such a device pose numerous significant questions. Could the same technology be used to communicate with Earth? Or more urgently, could a similar principle be applied by the Shivans to create jump nodes which are traversable by ships of significant size? Though these questions will not soon be answered, the enigma of this device yet more emphasizes what little we know about the race we call the Shivans."
-
All this so Carl can try to phone home. :pimp:
-
I personally believe that they are tied into ETAK. Whilst we are still discovering the Shivans as a race, we have only recently learnt a minimal amount of the communications systems that they use through accidently picked up transmissions. What if they were able to freely tune into NTF wavelengths by the use of said devices?
-
$Name: Shivan Comm Node
$Short name: CommSat
$Species: Shivan
+Tech Description:
XSTR("All details concerning this object have been classified level Omega, accessible only by those immediately authorized by the GTVA Security Council.", 3182)
$end_multi_text
$POF file: Comm2S-01.pof
$Detail distance: (0, 2000, 6500, 18000)
$ND: 226 2 8
$ND: 200 3 7
$ND: 178 3 5
$ND: 71 1 1
$ND: 198 1 1
$ND: 153 1 1
$ND: 87 0 0
$ND: 250 247 248
$ND: 253 191 200
$Show damage: NO
$Density: 1
$Damp: 0.2
$Rotdamp: 0.2
$Max Velocity: 0.0, 0.0, 0.0
$Rotation time: 200.0, 200.0, 200.0
$Rear Velocity: 0.0
$Forward accel: 0.0
$Forward decel: 0.0
$Slide accel: 0.0
$Slide decel: 0.0
$Expl inner rad: 100.0
$Expl outer rad: 2400.0
$Expl damage: 400.0
$Expl blast: 6500.0
$Expl Propagates: YES ;; If set to Yes, then when the ship dies, the explosion propagates through it.
$Shockwave Speed: 600.0 ;; speed shockwave expands at, 0 means no shockwave
$Shockwave Count: 2
$Default PBanks: ()
$Default SBanks: ()
$SBank Capacity: ()
$Shields: 0
$Power Output: 1.0
$Max Oclk Speed: 0.0
$Max Weapon Eng: 100.0
$Hitpoints: 40000
$Flags: ( "dont collide invisible" "knossos")
$AI Class: Captain
$Afterburner: NO
$Countermeasures: 0
$Scan time: 2000
$EngineSnd: 185 ;; Engine sound of ship
$Closeup_pos: 0.0, 0.0, -870
$Closeup_zoom: 0.40
$Score: 300
$Subsystem: piece1A, 30,20
$Subsystem: piece2A, 15,5
$Subsystem: piece3A, 30,20
$Subsystem: piece4A, 2,50
$Subsystem: piece5A, 15,5
$Subsystem: core, 2,0
If the table says that it is a Comm node, then it is a comm node. :P
-
:v: should have made the level omega stuff available when you reach the Admiral rank
-
:v: should have made the level omega stuff available when you reach the Admiral rank
Yea but you have to reach Admiral while flying SOC only missions. Can't have a regular Admiral having all the intelligence needed for battle.
-
Why wouldn't the admiralty have top level security clearance?
-
Why wouldn't the admiralty have top level security clearance?
We already know the GTVA has crappy need-to-know security protocols. Also Omega clearance specifically states that someone knowing about it must be directly authorized by the Security Council, which implies this clearance is not handed out to anyone as "a matter of course." There are things that the admiralty wouldn't be cleared for. They only need to see the results from them, not know how those results are achieved.
-
Yea it's kind of like saying a General would have access to all the CIA intelligence data.
-
if it generates a subspace field through which quantam pulses are sent... would that make it into a subspace node? :drevil:
it's my plot device!
-
if it generates a subspace field through which quantam pulses are sent... would that make it into a subspace node? :drevil:
it's my plot device!
It generates a coherent tetryonic beam that, when calibrated appropriately, causes tachyon surges, which result in artificial quantum singularities within fluidic event horizons.
There. Enough jargon for you?
-
if it generates a subspace field through which quantam pulses are sent... would that make it into a subspace node? :drevil:
it's my plot device!
$Name: Shivan Comm Node
$Short name: CommSat
$Species: Shivan
+Tech Description:
XSTR("All details concerning this object have been classified level Omega, accessible only by those immediately authorized by the GTVA Security Council.", 3182)
$end_multi_text
$POF file: Comm2S-01.pof
$Detail distance: (0, 2000, 6500, 18000)
$ND: 226 2 8
$ND: 200 3 7
$ND: 178 3 5
$ND: 71 1 1
$ND: 198 1 1
$ND: 153 1 1
$ND: 87 0 0
$ND: 250 247 248
$ND: 253 191 200
$Show damage: NO
$Density: 1
$Damp: 0.2
$Rotdamp: 0.2
$Max Velocity: 0.0, 0.0, 0.0
$Rotation time: 200.0, 200.0, 200.0
$Rear Velocity: 0.0
$Forward accel: 0.0
$Forward decel: 0.0
$Slide accel: 0.0
$Slide decel: 0.0
$Expl inner rad: 100.0
$Expl outer rad: 2400.0
$Expl damage: 400.0
$Expl blast: 6500.0
$Expl Propagates: YES ;; If set to Yes, then when the ship dies, the explosion propagates through it.
$Shockwave Speed: 600.0 ;; speed shockwave expands at, 0 means no shockwave
$Shockwave Count: 2
$Default PBanks: ()
$Default SBanks: ()
$SBank Capacity: ()
$Shields: 0
$Power Output: 1.0
$Max Oclk Speed: 0.0
$Max Weapon Eng: 100.0
$Hitpoints: 40000
$Flags: ( "dont collide invisible" "knossos")
$AI Class: Captain
$Afterburner: NO
$Countermeasures: 0
$Scan time: 2000
$EngineSnd: 185 ;; Engine sound of ship
$Closeup_pos: 0.0, 0.0, -870
$Closeup_zoom: 0.40
$Score: 300
$Subsystem: piece1A, 30,20
$Subsystem: piece2A, 15,5
$Subsystem: piece3A, 30,20
$Subsystem: piece4A, 2,50
$Subsystem: piece5A, 15,5
$Subsystem: core, 2,0
If the table says that it is a Comm node, then it is a comm node. :P
-
But what is a Comm node? For all we know Comm is short for Command not Communications. Or Committee, Commerce or a whole bunch of other words beginning with comm. :D Not that it matters in the slightest cause the only place that you can see that name is in FRED.
I tend to agree that :v: meant it to be for communications but I've got no objection to a 3rd party campaign saying it's for something else. Comm Node could easily be what the GTVA thought it was, that doesn't mean that they are correct.
-
Indeed. After all, the GTA originally thought the Scorpion was the best fighter in the Shivans' arsenal.
-
it wasn't? :shaking:
-
One big argument against it being a communication device is the fact that it has no comm subsystem.
Yeah, I'm going to leave now, before someone decides to murder me for that.
-
One big argument against it being a communication device is the fact that it has no comm subsystem.
Yeah, I'm going to leave now, before someone decides to murder me for that.
Likely our scanners cannot detect such a subsystem. It just can detect the spinning things( :P ) the core and the crystal.
-
if it generates a subspace field through which quantam pulses are sent... would that make it into a subspace node? :drevil:
it's my plot device!
$Name: Shivan Comm Node
Blah Blah
$Flags: ( "dont collide invisible" "knossos")
Blah Blah
If the table says that it is a Comm node, then it is a comm node. :P
It says its a knossos in the flags. I always thought it had something to do with the knossos.
-
it wasn't? :shaking:
Kind of easy to see, seeing as how an Apollo can easily kill it with Avenger cannons :P
-
One big argument against it being a communication device is the fact that it has no comm subsystem.
Maybe it doesn't have a comm subsytem is because the whole thing is communications.
-
it wasn't? :shaking:
The Scorpion was annoying. But not the most dangerous. Or did you forget the Dragon?
-
But what is a Comm node? For all we know Comm is short for Command not Communications. Or Committee, Commerce or a whole bunch of other words beginning with comm. :D Not that it matters in the slightest cause the only place that you can see that name is in FRED.
I tend to agree that :v: meant it to be for communications but I've got no objection to a 3rd party campaign saying it's for something else. Comm Node could easily be what the GTVA thought it was, that doesn't mean that they are correct.
Could be both command and communications.
-
it wasn't? :shaking:
The Scorpion was annoying. But not the most dangerous. Or did you forget the Dragon?
Dragons were not dangerous but they were pesky little buggers.
-
Oh, they were dangerous. In FS1 on Insane, two Dragons took out all of my wingmen. :P
-
They're not dangerous when you launch secondaries from safe distance :rolleyes:
-
Pilot: "Haha! Die, you puny Dragon, die!"
*missile launch*
Non-canon on-board computer: "Beep. You missed."
Pilot: "Dang..."
*Extreme pain and suffering*
-
/me facepalms
Mobius totally missed what I was saying.
Lobo's right though. :D
-
They're not dangerous when you launch secondaries from safe distance :rolleyes:
Really? Firing dual Harpoons never seem to work.
Either that or I'm firing them the wrong way. :nervous:
I find the Shivan Comm Node to be some kind of open-ended plot device.
-
It is also good to note that even though tackling Dragons with secondaries might seem like a good strategy, the reality is that you can only have so much missiles in FS1. Not too much, oh no. Never. They always run out. And let's face it. The only missile with even a half-decent chance of hitting a Dragon is the Interceptor.
-
Firing dual harpoons seems to be less accurate than firing one harpoon. Generally if i'm picking off one target where the missile must get to it's destination i only fire one. I usually only do dual secondaries on bigger ships.
I'm pretty sure comm node is what comm node stands for. Communications that is. Even if it stands for command node, it's still performs communications anyway. But, if the knossos had to do with the knossos in a way, then that makes it a very unique device. Sort of like how the terrans have the charybdis class vessel. The shivan comm node could probably be shivans version of a charybdis, except not shipified. If the shivans can use it to block communications and cause signal jamming, then maybe they used it to keep the ancients from locking down knossos'es like how the ancients locked down the knossos in gamma draconis. Except that in this case in the situation that the shivans efforts to keep the ancients from locking down this one was the fact that the ancients got to it first before the shivans warped into gamma draconis first to lay down some multi-purpose comm nodes.
However this seems like an unlikely situation. But, the shivan comm node being multi-purpose for communications and performing awacs functionality could be likely. It sucks that a shivan transport vessel wasn't captured so that one of the shivan comm nodes couldn't have been captured. Then again, that mission was a suicide mission and was only meant to see what was behind the knossos in the nebula. The only way gtva would have tried to capture one of those comm nodes is if they knew they were there in the first place, which they didn't. And if they did know those devices were there in the first place, they would have already flown a suicide mission into the system that lied behind the knossos in the nebula, in which the gtva would have been ****ing retarded for not pulling all of it's forces out of the nebula because the shivans would follow.
-
Which object? You're very descriptionless.
martialc?
Oh?
-
Just the object which you destory in the Mission " Into the Lion's Den"(The loop mission that you drive a Shivan
class Fighter Mara)
I think it was the most secret martial device in the game, and there is no explanation in the TECH ROOM
PS: Mara(reconstructed by the GTVI) was the actually best type of Fighter i have used……
You're first post in this thread is oddly written. It confuses readers. So i didn't know what you were asking.
-
It says its a knossos in the flags. I always thought it had something to do with the knossos.
By that logic certain things would be random crap. Like the Boadicea is a cruiser, the Ganymede is a drydock AND a capital ship, Asteroids are navbuoys, the Sathanas is an AWACS, the list goes on. Stuff in the tables doesn't count as in-universe stuff IMO.
-
the Sathanas is an AWACS,
What?
-
Check the table entry :P
-
$Subsystem: communication, 3, 0.0
$AWACS: 1.0 2500.0 ;; intensity, radius - intensity is currently ignored
Ah.
That's not random crap, that's making it inevitable the Shivans find you!
-
if it generates a subspace field through which quantam pulses are sent... would that make it into a subspace node? :drevil:
it's my plot device!
It generates a coherent tetryonic beam that, when calibrated appropriately, causes tachyon surges, which result in artificial quantum singularities within fluidic event horizons.
There. Enough jargon for you?
That makes no sense at all. For one, tahyons are hypothetical particles with imaginary mass, so they don't interact with normal matter or energy, and for them, the speed of light is a lower speed limit. For two, a singularity can't have a fluidic event horizon because fluid dynamics do not apply to an abstract gravitational boundary.
Also, none of these "functions" of any ship in the game is hard-coded. A FREDer has to SExp whatever function it is. Therefore, it can have whatever function you want. You can give an Orion cruiser the "ability" to disable shields and jump drives if you desire.
-
That makes no sense at all. For one, tahyons are hypothetical particles with imaginary mass, so they don't interact with normal matter or energy, and for them, the speed of light is a lower speed limit. For two, a singularity can't have a fluidic event horizon because fluid dynamics do not apply to an abstract gravitational boundary.
:lol: I know. I was merely putting together some funny words I've heard in various Star Trek shows. And if we want to talk about physics, how about the way ships behave in space in FS?
-
Yeah, get the ground crews to uninstall them.
Who's to say that all that technobabble isn't feasible in his fictional universe :p
-
That makes no sense at all. For one, tachyons are hypothetical particles with imaginary mass, so they don't interact with normal matter or energy, and for them, the speed of light is a lower speed limit. For two, a singularity can't have a fluidic event horizon because fluid dynamics do not apply to an abstract gravitational boundary.
:lol: I know. I was merely putting together some funny words I've heard in various Star Trek shows. And if we want to talk about physics, how about the way ships behave in space in FS?
I know, and I know. :lol: More than a few theories on Star Trek shows actually have grounds in theoretical physics, theories such as warp drive. The only problem with warp drive is that it requires matter that breaks known physics. (BTW, I'm watching Star Trek: Voyager right now. 8472 Boothby :lol:)
-
It's actually a psionic-pulse generator that excites the subatomic waves of subspace thereby stimulating the celestial realms and producing complex prions.
-
It's actually a psionic-pulse generator that excites the subatomic waves of subspace thereby stimulating the celestial realms and producing complex prions.
All this for the shivan Pr0n channel :yes:
-
(BTW, I'm watching Star Trek: Voyager right now. 8472 Boothby :lol:)
Hence the word "fluidic" in my jargon.
It's actually a psionic-pulse generator that excites the subatomic waves of subspace thereby stimulating the celestial realms and producing complex prions.
All this for the shivan Pr0n channel :yes:
:nervous: Someone has found the TruthTM! *gasp*
-
(BTW, I'm watching Star Trek: Voyager right now. 8472 Boothby :lol:)
Hence the word "fluidic" in my jargon.
Ah... BTW, I put my 8472 Shivan theory on the wiki, if any cares to take a look. I think it's more plausible that the Capella Barbecue theory. Homework time, goodbye!
-
I found the Truth© earlier on in this topic :-P
-
It's actually a psionic-pulse generator that excites the subatomic waves of subspace thereby stimulating the celestial realms and producing complex prions.
All this for the shivan Pr0n channel :yes:
:nervous: Someone has found the TruthTM! *gasp*
(http://img366.imageshack.us/img366/2056/carlsl7.jpg)
On the left we have carl dressed up, on the right we have carl going down the catwalk.
Carl's a ****ing freak! :no:
-
(BTW, I'm watching Star Trek: Voyager right now. 8472 Boothby :lol:)
Hence the word "fluidic" in my jargon.
It's actually a psionic-pulse generator that excites the subatomic waves of subspace thereby stimulating the celestial realms and producing complex prions.
All this for the shivan Pr0n channel :yes:
:nervous: Someone has found the TruthTM! *gasp*
When will people discover a real TM sign is made by pressing ALT, Shift and X together? Well, atleast on swiss keyboards...
-
When will people discover a real TM sign is made by pressing ALT, Shift and X together? Well, atleast on swiss keyboards...
Clearly not on any of my keyboards. :rolleyes:
-
Can't you change the keyboard layout™ (hah! a TM™ sign!) on your windoze machine?
-
Or you can go into Start > All Programs > Accessories > System Tools > Character Map
-
Or you could memorise the Alt code. (hidden text below)
Alt+666 gives Ü, as in, "Über"!
-
Do you mean you're monkey'd sig?
-
Do you mean you're monkey'd sig?
Nope. It's the black text between (hidden text below) and that (not so funny) signature.
-
Nope. It's the black text between (hidden text below) and that (not so funny) signature.
Sorry...I got a little carried away. On the other hand, I like the moderators' response. :blah: