https://wiki.hard-light.net/api.php?action=feedcontributions&user=Marcov&feedformat=atomFreeSpace Wiki - User contributions [en]2024-03-28T23:24:19ZUser contributionsMediaWiki 1.31.7https://wiki.hard-light.net/index.php?title=Shivan_Super_Laser&diff=53963Shivan Super Laser2017-12-08T15:14:07Z<p>Marcov: </p>
<hr />
<div>The '''Shivan Super Laser''' was the main weapon of the [[SD Lucifer]]. It was the only weapon during the [[Great War]] that resembled anything like the [[Beam weapon|beam weapons]] developed by the [[GTVA]] and used by more advanced [[Shivans|Shivan]] [[Ship|ships]] much later. It was used by the Lucifer to destroy the [[GTD Galatea]], as well as bombard the planet [[Vasuda Prime]] in [[Timeline|2335]]. It is sometimes called a '''Flux Cannon'''.<br />
<br />
{{FS12_Weapons}}<br />
==Description==<br />
Weapon used to represent the beam weapons of the [[SD Lucifer]] in FS1<br />
<br />
==Performance==<br />
===Statistics===<br />
{{Primary|30 000|0.1|1 000|15 000|Full|15 000|Full|15 000|Full|15 000}}<br />
<br />
==Notes==<br />
<br />
===Veteran Comments===<br />
{{Comment|Capable of taking down anything in its path in one or two hits, this is what made the [[SD Lucifer|Lucifer]] so dangerous. This is described as a "Flux Cannon" in the [[SD Lucifer|Lucifer's]] tech description.<br />
<br />
<br />
THE gun, the meanest, most destructive weapon in FreeSpace 1, period. It outdamages anything and everything.<br />
<br />
<br />
The FreeSpace Port made this into a beam weapon, but in retail FS1/2 it's actually a turret munition with an invisible head and a very long tail. In other words, it's a laser shot hacked to look like a beam.<br />
<br />
<br />
It kills anything below a cruiser in one shot, anything above cruiser in three. It also has absolutely INSANE kinetic power, because whenever you shoot a fighter or bomber with it, the destroyed ship is propelled by 200 m/s before exploding, and its debris goes even faster.}}<br />
[[Category:Weapon]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Shivan_Super_Laser&diff=53962Shivan Super Laser2017-12-08T15:12:51Z<p>Marcov: </p>
<hr />
<div>The '''Shivan Super Laser''' was the main weapon of the [[SD Lucifer]]. It was the only weapon during the [[Great War]] that resembled anything like the [[Beam weapon|beam weapons]] developed by the [[GTVA]] and used by more advanced [[Shivans|Shivan]] [[Ship|ships]] much later. It was used by the Lucifer to destroy the [[GTD Galatea]], as well as bombard the planet [[Vasuda Prime]] in [[Timeline|2335]].<br />
<br />
{{FS12_Weapons}}<br />
==Description==<br />
Weapon used to represent the beam weapons of the [[SD Lucifer]] in FS1<br />
<br />
==Performance==<br />
===Statistics===<br />
{{Primary|30 000|0.1|1 000|15 000|Full|15 000|Full|15 000|Full|15 000}}<br />
<br />
==Notes==<br />
<br />
===Veteran Comments===<br />
{{Comment|Capable of taking down anything in its path in one or two hits, this is what made the [[SD Lucifer|Lucifer]] so dangerous. This is described as a "Flux Cannon" in the [[SD Lucifer|Lucifer's]] tech description.<br />
<br />
<br />
THE gun, the meanest, most destructive weapon in FreeSpace 1, period. It outdamages anything and everything.<br />
<br />
<br />
The FreeSpace Port made this into a beam weapon, but in retail FS1/2 it's actually a turret munition with an invisible head and a very long tail. In other words, it's a laser shot hacked to look like a beam.<br />
<br />
<br />
It kills anything below a cruiser in one shot, anything above cruiser in three. It also has absolutely INSANE kinetic power, because whenever you shoot a fighter or bomber with it, the destroyed ship is propelled by 200 m/s before exploding, and its debris goes even faster.}}<br />
[[Category:Weapon]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Shivan_Super_Laser&diff=53961Shivan Super Laser2017-12-08T15:12:32Z<p>Marcov: </p>
<hr />
<div>The '''Shivan Super Laser''' was the main weapon of the [[SD Lucifer]]. It was the only weapon during the [[Great War]] that resembled anything like the [[Beam weapon|beam weapons]] developed by the [[GTVA]] and used by more advanced Shivan [[Ship|ships]] much later. It was used by the Lucifer to destroy the [[GTD Galatea]], as well as bombard the planet [[Vasuda Prime]] in [[Timeline|2335]].<br />
<br />
{{FS12_Weapons}}<br />
==Description==<br />
Weapon used to represent the beam weapons of the [[SD Lucifer]] in FS1<br />
<br />
==Performance==<br />
===Statistics===<br />
{{Primary|30 000|0.1|1 000|15 000|Full|15 000|Full|15 000|Full|15 000}}<br />
<br />
==Notes==<br />
<br />
===Veteran Comments===<br />
{{Comment|Capable of taking down anything in its path in one or two hits, this is what made the [[SD Lucifer|Lucifer]] so dangerous. This is described as a "Flux Cannon" in the [[SD Lucifer|Lucifer's]] tech description.<br />
<br />
<br />
THE gun, the meanest, most destructive weapon in FreeSpace 1, period. It outdamages anything and everything.<br />
<br />
<br />
The FreeSpace Port made this into a beam weapon, but in retail FS1/2 it's actually a turret munition with an invisible head and a very long tail. In other words, it's a laser shot hacked to look like a beam.<br />
<br />
<br />
It kills anything below a cruiser in one shot, anything above cruiser in three. It also has absolutely INSANE kinetic power, because whenever you shoot a fighter or bomber with it, the destroyed ship is propelled by 200 m/s before exploding, and its debris goes even faster.}}<br />
[[Category:Weapon]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Shivan_Super_Laser&diff=53960Shivan Super Laser2017-12-08T15:11:55Z<p>Marcov: </p>
<hr />
<div>The '''Shivan Super Laser''' was the main weapon of the [[SD Lucifer]]. It was the only weapon during the [[Great War]] that resembled anything like the [[Beam Weapon|beam weapons]] developed by the [[GTVA]] and used by more advanced Shivan [[Ship|ships]] much later. It was used by the Lucifer to destroy the [[GTD Galatea]], as well as bombard the [[planet]] [[Vasuda Prime]] in [[Timeline|2335]].<br />
<br />
{{FS12_Weapons}}<br />
==Description==<br />
Weapon used to represent the beam weapons of the [[SD Lucifer]] in FS1<br />
<br />
==Performance==<br />
===Statistics===<br />
{{Primary|30 000|0.1|1 000|15 000|Full|15 000|Full|15 000|Full|15 000}}<br />
<br />
==Notes==<br />
<br />
===Veteran Comments===<br />
{{Comment|Capable of taking down anything in its path in one or two hits, this is what made the [[SD Lucifer|Lucifer]] so dangerous. This is described as a "Flux Cannon" in the [[SD Lucifer|Lucifer's]] tech description.<br />
<br />
<br />
THE gun, the meanest, most destructive weapon in FreeSpace 1, period. It outdamages anything and everything.<br />
<br />
<br />
The FreeSpace Port made this into a beam weapon, but in retail FS1/2 it's actually a turret munition with an invisible head and a very long tail. In other words, it's a laser shot hacked to look like a beam.<br />
<br />
<br />
It kills anything below a cruiser in one shot, anything above cruiser in three. It also has absolutely INSANE kinetic power, because whenever you shoot a fighter or bomber with it, the destroyed ship is propelled by 200 m/s before exploding, and its debris goes even faster.}}<br />
[[Category:Weapon]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=GTVA_Colossus&diff=53825GTVA Colossus2017-12-07T05:48:19Z<p>Marcov: /* Veteran Comments */</p>
<hr />
<div>{{FS12_Ships}}<br />
The largest space-faring warship ever constructed by the [[Terrans]] or [[Vasudans]], the '''GTVA ''Colossus''''' was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six kilometers, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.<br />
<br />
With the offensive power that exceeded most [[GTVA]] battle groups, the ''Colossus'' was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more [[SD Lucifer|''Lucifer'']]-class super-destroyers, and it was deemed that the ''Colossus'' would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a ''Lucifer'''s primary weapon system.<br />
<br />
Although the ''Colossus'' was a joint endeavor of both the Terrans and Vasudans, it is apparent that the ship itself exhibits more Terran design traits than Vasudan. It can be assumed that some of the Vasudan elements manifest themselves in less immediately overt ways.<br />
<br />
==History==<br />
{{Gtvaship<br />
| image = [[File:Willy B-Colossus-MVP2014.png|300px]]<br />
| name = GTVA ''Colossus''<br />
| class = GTVA ''Colossus''<br />
| 1stapp = [[The Sixth Wonder]]<br />
| inservice = [[NTF Rebellion]]<br>[[Second Shivan Incursion]]<br />
| faction = [[Galactic Terran-Vasudan Alliance]]<br />
| fate = [[Their Finest Hour|Destroyed]] by [[SJ Sathanas|SJ ''Sathanas 17'']]<br />
}}<br />
The first combat deployment of the ''Colossus'' was against the [[Neo-Terran Front]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. NTF forces proved to be [[Feint! Parry! Riposte!|no match]] for the ''Colossus'' and her battle group, and the rebels made every effort to avoid direct combat with the warship. With his fleet shattered, and the remnants being actively pursued and destroyed by the ''Colossus'', [[Famous persons|Admiral Aken Bosch]] gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].<br />
<br />
With the NTF defeated, the ''Colossus'' was finally to fulfill the role her designers had envisioned for her: the defeat of a second Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather the even more massive [[SJ Sathanas|SJ ''Sathanas'']]-class juggernaut. Twenty years of constant struggle finally culminated with the ''Colossus'''s destruction of the [[SJ Sathanas|''Sathanas'']], all at the cost of moderate damage to the ''Colossus''.<br />
<br />
All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the ''Colossus'' was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the [[GTD Bastion|''Bastion'']], which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed a [[SD Ravana]], then a [[SJ Sathanas|SJ ''Sathanas'']] to engage the ''Colossus''. In her weakened state, it was obvious that the ''Colossus'' would not survive an engagement with another ''Sathanas''-class juggernaut, and Allied Command ordered the ''Colossus'' to withdraw.<br />
<br />
However, with the success of the ''Bastion'''s critical mission in doubt, the ''Colossus'' disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the ''Colossus'' was destroyed with the loss of all hands. The thirty-thousand officers and crew of the ''Colossus'' willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the [[Galactic Terran-Vasudan Alliance]].<br />
<br />
==Confirmed kills==<br />
*NTCv ''Hawkwood'' (Destroyed at Enif Station)<br />
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)<br />
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)<br />
*NTC ''Camisard'' (Reported destroyed in Command Briefing)<br />
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')<br />
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')<br />
*NTCv ''Danton'' (''Endgame'')<br />
*SJ ''Sathanas'' (First, High Noon mission)<br />
*SD ''Beast'' (Destroyed shortly before ''Sathanas 17'' destroyed the Colossus)<br />
<br />
==Quotes==<br />
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"<br />
<br />
"This is the GTVA ''Colossus''. Admiral Koth, you are ordered to power down your engines immediately and surrender. The Polaris jump node is blockaded, there is no escape."<br />
<br />
"You are sacrificing thousands of lives for nothing!"<br />
<br />
"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"<br />
<br />
"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"<br />
<br />
"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"<br />
<br />
==Colossus cutscene==<br />
'''Narrator:''' ''The following is classified level Rho. Unauthorized access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species? In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly-formed GTVA General Assembly. The emperor inaugurated an ambitious and unprecedented joint endeavor: The GTVA ''Colossus''.''<br />
<br />
'''Khonsu II:''' ''Together we built a civilization on the ruins of the [[Great War]], and now we stand on the threshold of a new era of prosperity and harmony. With Project Colossus, the Vasudan people celebrate our shared covenant of peaceful co-existence and mutual defense of our Terran allies.''<br />
<br />
'''Narrator:''' ''The ''Colossus'' is the most powerful space faring warship ever constructed. Spanning six kilometers from bow to stern, the ''Colossus'' has taken over twenty years to complete. Twelve ''Lucifer''-class destroyers can fit within its massive hull. Its state-of-the-art weaponry includes forty-five laser turrets, fifteen flak guns, twelve missile batteries, and twelve beam cannons. The ''Colossus'' wields more firepower than five ''Orion''-class destroyers combined. Sixty fighter and bomber wings are housed in its vast hangar and its crew numbers over thirty thousand. Among its major contractors are industry giants Triton Dynamics, Subach-Innes, and the Akheton Corporation. The alliance now wages war on multiple fronts: in Deneb, Alpha Centuri, Epsilon Pegasi, and the [[Nebula System|mysterious nebula]] beyond Gamma Draconis. Once deployed the ''Colossus'' will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.''<br />
<br />
==Description:==<br />
{{shipimage|image=[[File:Gtvacolossus-old.jpg]]|caption=The GTVA ''Colossus''}}<br />
===FS2 Tech Room Description===<br />
The GTVA ''Colossus'' resulted from an endeavor unprecedented in Terran or Vasudan history. This 6-kilometer-long behemoth is the result of 20 years of joint effort from dozens of contractors of both races. The ''Colossus'' is the most powerful space-faring warship ever made, bristling with over 80 weapon turrets. It also houses 60 fighter and bomber wings and requires a crew of over 30,000. The firepower of the ''Colossus'' is greater than that of most GTVA battle groups.<br />
<br />
===Developer Notes===<br />
None<br />
<br />
===Name Origin===<br />
Used in Latin to refer to large statues, the term is used in English (in lower case, being a common noun) to refer to anything of large size.<br />
<br />
The sixth of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue representing the god [[Helios]] that was constructed following a very important military victory. This is why the first mission featuring the ''Colossus'' is named "[[The Sixth Wonder]]."<br />
<br />
==Performance:==<br />
===Statistics===<br />
{{Ship_box<br />
|table_style = <br />
|name = GTVA ''Colossus''<br />
|type = ''See [[GTVA Colossus ship type debate]]''<br />
|manufacturer = All canon [[corporations]]<br />
|yaw_pitch_roll = 200.0, 200.0, 200.0<br />
|max_velocity = 25.0<br />
|hitpoints = 1 000 000<br />
|length = 6166<br />
|width = <br />
|height = <br />
|turrets = 63<br />
|fighters = 240<br />
}}<br />
<br />
===Armaments===<br />
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''<br />
{| border=1 cellpadding=4 style="border-collapse: collapse"<br />
|- align="center"<br />
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''<br />
|- align="center"<br />
| style="width:120px" |Turret Type<br />
| style="width:60px" |Amount<br />
|- align="center"<br />
| [[Terran Turret]]<br />
| 8<br />
|- align="center"<br />
| [[Terran Huge Turret]]<br />
| 10<br />
|- align="center"<br />
| [[Standard Flak]]<br />
| 12<br />
|- align="center"<br />
| [[MX-52]]<br />
| 8<br />
|- align="center"<br />
| [[GTM Piranha|Piranha]]<br />
| 2<br />
|- align="center"<br />
| [[AAAf]]<br />
| 10<br />
|- align="center"<br />
| [[TerSlash]]<br />
| 7<br />
|- align="center"<br />
| [[BGreen]]<br />
| 6<br />
|}<br />
<br />
==Modding Resources==<br />
{{shipimage|image=[[File:Gtvacolossus.jpg|600px]]|caption=The GTVA Colossus in FS2_Open with the [[mediavps]] enabled}}<br />
'''Retail''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br />
'''MediaVP 2014''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br><br />
History<br><br />
Proposed by: ??? on ???<br><br />
First WIP Post: ??? on ???<br><br />
First In-Game Model: ??? on ???<br><br />
Completed In-Game Model: ??? on ???<br><br />
Final Corrections: ??? on ???<br><br />
<br />
<br />
==Gallery==<br />
<gallery><br />
File:RScreen0025.jpg | Admiral Koth engages the GTVA ''Colossus''. <br />
File:RScreen0073.png | Demonstrating the meaning of superior firepower.<br />
File:RScreen0044.png | The GTVA ''Colossus''. <br />
File:RScreen0047.png | The ''Colossus'' meets its end at the hands of the [[Shivans]].<br />
</gallery><br />
<br />
==Veteran Comments==<br />
{{Comment|''The 6 BGreen beams of the Colossus are powerful and allow it to have no trouble taking on multiple destroyers at once while taking minimal damage in return. The Colossus is an all-round good ship &mdash; it has plenty of armor, a large number of turrets, and it's surprisingly fast for a ship of its size, matching the speed of the Sathanas and outpacing all destroyers.''<br />
<br />
<br />
''The GTVA Colossus is not that great at killing ships of equal size to it as the above. The placement of its main beam turrets are all over the ship, meaning that maximum firepower cannot be directed against heavier ships. However, this does also have its advantages. It means that no capital ship can be in a safe spot from it. It is also loaded with massive amounts of anti-fighter and bomber weaponry, making it a nightmare to attack. These anti-fighter weapons are also located around the main beams of the warship, making it more difficult to disable.''<br />
<br />
<br />
''I think that the blind spots of the Colossus are its rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two.''<br />
<br />
<br />
''The Colossus model is infamous for its low moment-of-inertia value, which causes it to swing around like a baseball bat during tight turns. This is also partly because its pivot point is located at the very back, where the huge engines are. Most other ships in contrast, including the Sathanas, have their pivot point located near the centre of the ship, so their turns look more normal even if their moment-of-inertia value is similar to the Colossus'.''<br />
<br />
<br />
''Keep in mind that the firepower demonstrated by the Colossus in [[High Noon]] was due to pushing the beams and fire control to their limit, resulting in considerable damage to the ship and weapons even if the Sathanas never fired a shot. Replacing the Colossus' default beams with more powerful beams without even mentioning overloads is not good at all.''<br />
<br />
<br />
''Strangely enough, the Colossus is never mentioned as either a destroyer, superdestroyer or a juggernaut in the game, instead being ambiguously called a warship. This sparked a debate, as every other canon ship was given a ship type excluding the Colossus. Further details on this debate may be found [[GTVA Colossus ship type debate|here]].''<br />
<br />
''The most likely reason for the Colossus' lack of a "ship type" is simply because the GTVA intended to build only one. It would be unnecessary to give it a designation since they were never planning to mass-produce such a huge and costly warship.''<br />
<br />
<br />
''Although many tend to praise the Colossus for its well-distributed anticapital firepower, this tactic, sadly, may usually prove ineffective. For example, if an attack operation against the Colossus were planned, the attacker's warships would have to be placed in one spot, so that the Colossus could only fire a fraction of its beam count. In short, the Colossus rarely is able to demonstrate its full firepower, since the enemy would not dare engage it from all sides anyway.''<br />
<br />
<br />
''I must question my own statement above, now. In the minds of the GTVA, no warship could pose any serious threat to the Colossus; any attack on it, concentrated on one spot or not, would not pose any significant harm to the behemoth anyway. The primary purpose of the Colossus is simply to end any kind of conflict anywhere, at any time; it jumps in, and wherever the enemy vessel is, it gets zapped by one of the Colossus' many well-distributed beams. Of course, the exception to this sort of usefulness would be an equally powerful warship - the Sathanas. However, as we know, the GTVA probably was not expecting such an encounter.''<br />
<br />
}}<br />
<br />
[[Category:Unique ships|Colossus, GTVA]]<br />
[[Category:Ship]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=GTVA_Colossus&diff=53824GTVA Colossus2017-12-07T05:47:48Z<p>Marcov: /* Veteran Comments */</p>
<hr />
<div>{{FS12_Ships}}<br />
The largest space-faring warship ever constructed by the [[Terrans]] or [[Vasudans]], the '''GTVA ''Colossus''''' was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six kilometers, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.<br />
<br />
With the offensive power that exceeded most [[GTVA]] battle groups, the ''Colossus'' was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more [[SD Lucifer|''Lucifer'']]-class super-destroyers, and it was deemed that the ''Colossus'' would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a ''Lucifer'''s primary weapon system.<br />
<br />
Although the ''Colossus'' was a joint endeavor of both the Terrans and Vasudans, it is apparent that the ship itself exhibits more Terran design traits than Vasudan. It can be assumed that some of the Vasudan elements manifest themselves in less immediately overt ways.<br />
<br />
==History==<br />
{{Gtvaship<br />
| image = [[File:Willy B-Colossus-MVP2014.png|300px]]<br />
| name = GTVA ''Colossus''<br />
| class = GTVA ''Colossus''<br />
| 1stapp = [[The Sixth Wonder]]<br />
| inservice = [[NTF Rebellion]]<br>[[Second Shivan Incursion]]<br />
| faction = [[Galactic Terran-Vasudan Alliance]]<br />
| fate = [[Their Finest Hour|Destroyed]] by [[SJ Sathanas|SJ ''Sathanas 17'']]<br />
}}<br />
The first combat deployment of the ''Colossus'' was against the [[Neo-Terran Front]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. NTF forces proved to be [[Feint! Parry! Riposte!|no match]] for the ''Colossus'' and her battle group, and the rebels made every effort to avoid direct combat with the warship. With his fleet shattered, and the remnants being actively pursued and destroyed by the ''Colossus'', [[Famous persons|Admiral Aken Bosch]] gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].<br />
<br />
With the NTF defeated, the ''Colossus'' was finally to fulfill the role her designers had envisioned for her: the defeat of a second Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather the even more massive [[SJ Sathanas|SJ ''Sathanas'']]-class juggernaut. Twenty years of constant struggle finally culminated with the ''Colossus'''s destruction of the [[SJ Sathanas|''Sathanas'']], all at the cost of moderate damage to the ''Colossus''.<br />
<br />
All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the ''Colossus'' was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the [[GTD Bastion|''Bastion'']], which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed a [[SD Ravana]], then a [[SJ Sathanas|SJ ''Sathanas'']] to engage the ''Colossus''. In her weakened state, it was obvious that the ''Colossus'' would not survive an engagement with another ''Sathanas''-class juggernaut, and Allied Command ordered the ''Colossus'' to withdraw.<br />
<br />
However, with the success of the ''Bastion'''s critical mission in doubt, the ''Colossus'' disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the ''Colossus'' was destroyed with the loss of all hands. The thirty-thousand officers and crew of the ''Colossus'' willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the [[Galactic Terran-Vasudan Alliance]].<br />
<br />
==Confirmed kills==<br />
*NTCv ''Hawkwood'' (Destroyed at Enif Station)<br />
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)<br />
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)<br />
*NTC ''Camisard'' (Reported destroyed in Command Briefing)<br />
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')<br />
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')<br />
*NTCv ''Danton'' (''Endgame'')<br />
*SJ ''Sathanas'' (First, High Noon mission)<br />
*SD ''Beast'' (Destroyed shortly before ''Sathanas 17'' destroyed the Colossus)<br />
<br />
==Quotes==<br />
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"<br />
<br />
"This is the GTVA ''Colossus''. Admiral Koth, you are ordered to power down your engines immediately and surrender. The Polaris jump node is blockaded, there is no escape."<br />
<br />
"You are sacrificing thousands of lives for nothing!"<br />
<br />
"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"<br />
<br />
"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"<br />
<br />
"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"<br />
<br />
==Colossus cutscene==<br />
'''Narrator:''' ''The following is classified level Rho. Unauthorized access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species? In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly-formed GTVA General Assembly. The emperor inaugurated an ambitious and unprecedented joint endeavor: The GTVA ''Colossus''.''<br />
<br />
'''Khonsu II:''' ''Together we built a civilization on the ruins of the [[Great War]], and now we stand on the threshold of a new era of prosperity and harmony. With Project Colossus, the Vasudan people celebrate our shared covenant of peaceful co-existence and mutual defense of our Terran allies.''<br />
<br />
'''Narrator:''' ''The ''Colossus'' is the most powerful space faring warship ever constructed. Spanning six kilometers from bow to stern, the ''Colossus'' has taken over twenty years to complete. Twelve ''Lucifer''-class destroyers can fit within its massive hull. Its state-of-the-art weaponry includes forty-five laser turrets, fifteen flak guns, twelve missile batteries, and twelve beam cannons. The ''Colossus'' wields more firepower than five ''Orion''-class destroyers combined. Sixty fighter and bomber wings are housed in its vast hangar and its crew numbers over thirty thousand. Among its major contractors are industry giants Triton Dynamics, Subach-Innes, and the Akheton Corporation. The alliance now wages war on multiple fronts: in Deneb, Alpha Centuri, Epsilon Pegasi, and the [[Nebula System|mysterious nebula]] beyond Gamma Draconis. Once deployed the ''Colossus'' will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.''<br />
<br />
==Description:==<br />
{{shipimage|image=[[File:Gtvacolossus-old.jpg]]|caption=The GTVA ''Colossus''}}<br />
===FS2 Tech Room Description===<br />
The GTVA ''Colossus'' resulted from an endeavor unprecedented in Terran or Vasudan history. This 6-kilometer-long behemoth is the result of 20 years of joint effort from dozens of contractors of both races. The ''Colossus'' is the most powerful space-faring warship ever made, bristling with over 80 weapon turrets. It also houses 60 fighter and bomber wings and requires a crew of over 30,000. The firepower of the ''Colossus'' is greater than that of most GTVA battle groups.<br />
<br />
===Developer Notes===<br />
None<br />
<br />
===Name Origin===<br />
Used in Latin to refer to large statues, the term is used in English (in lower case, being a common noun) to refer to anything of large size.<br />
<br />
The sixth of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue representing the god [[Helios]] that was constructed following a very important military victory. This is why the first mission featuring the ''Colossus'' is named "[[The Sixth Wonder]]."<br />
<br />
==Performance:==<br />
===Statistics===<br />
{{Ship_box<br />
|table_style = <br />
|name = GTVA ''Colossus''<br />
|type = ''See [[GTVA Colossus ship type debate]]''<br />
|manufacturer = All canon [[corporations]]<br />
|yaw_pitch_roll = 200.0, 200.0, 200.0<br />
|max_velocity = 25.0<br />
|hitpoints = 1 000 000<br />
|length = 6166<br />
|width = <br />
|height = <br />
|turrets = 63<br />
|fighters = 240<br />
}}<br />
<br />
===Armaments===<br />
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''<br />
{| border=1 cellpadding=4 style="border-collapse: collapse"<br />
|- align="center"<br />
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''<br />
|- align="center"<br />
| style="width:120px" |Turret Type<br />
| style="width:60px" |Amount<br />
|- align="center"<br />
| [[Terran Turret]]<br />
| 8<br />
|- align="center"<br />
| [[Terran Huge Turret]]<br />
| 10<br />
|- align="center"<br />
| [[Standard Flak]]<br />
| 12<br />
|- align="center"<br />
| [[MX-52]]<br />
| 8<br />
|- align="center"<br />
| [[GTM Piranha|Piranha]]<br />
| 2<br />
|- align="center"<br />
| [[AAAf]]<br />
| 10<br />
|- align="center"<br />
| [[TerSlash]]<br />
| 7<br />
|- align="center"<br />
| [[BGreen]]<br />
| 6<br />
|}<br />
<br />
==Modding Resources==<br />
{{shipimage|image=[[File:Gtvacolossus.jpg|600px]]|caption=The GTVA Colossus in FS2_Open with the [[mediavps]] enabled}}<br />
'''Retail''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br />
'''MediaVP 2014''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br><br />
History<br><br />
Proposed by: ??? on ???<br><br />
First WIP Post: ??? on ???<br><br />
First In-Game Model: ??? on ???<br><br />
Completed In-Game Model: ??? on ???<br><br />
Final Corrections: ??? on ???<br><br />
<br />
<br />
==Gallery==<br />
<gallery><br />
File:RScreen0025.jpg | Admiral Koth engages the GTVA ''Colossus''. <br />
File:RScreen0073.png | Demonstrating the meaning of superior firepower.<br />
File:RScreen0044.png | The GTVA ''Colossus''. <br />
File:RScreen0047.png | The ''Colossus'' meets its end at the hands of the [[Shivans]].<br />
</gallery><br />
<br />
==Veteran Comments==<br />
{{Comment|''The 6 BGreen beams of the Colossus are powerful and allow it to have no trouble taking on multiple destroyers at once while taking minimal damage in return. The Colossus is an all-round good ship &mdash; it has plenty of armor, a large number of turrets, and it's surprisingly fast for a ship of its size, matching the speed of the Sathanas and outpacing all destroyers.''<br />
<br />
<br />
''The GTVA Colossus is not that great at killing ships of equal size to it as the above. The placement of its main beam turrets are all over the ship, meaning that maximum firepower cannot be directed against heavier ships. However, this does also have its advantages. It means that no capital ship can be in a safe spot from it. It is also loaded with massive amounts of anti-fighter and bomber weaponry, making it a nightmare to attack. These anti-fighter weapons are also located around the main beams of the warship, making it more difficult to disable.''<br />
<br />
<br />
''I think that the blind spots of the Colossus are its rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two.''<br />
<br />
<br />
''The Colossus model is infamous for its low moment-of-inertia value, which causes it to swing around like a baseball bat during tight turns. This is also partly because its pivot point is located at the very back, where the huge engines are. Most other ships in contrast, including the Sathanas, have their pivot point located near the centre of the ship, so their turns look more normal even if their moment-of-inertia value is similar to the Colossus'.''<br />
<br />
<br />
''Keep in mind that the firepower demonstrated by the Colossus in [[High Noon]] was due to pushing the beams and fire control to their limit, resulting in considerable damage to the ship and weapons even if the Sathanas never fired a shot. Replacing the Colossus' default beams with more powerful beams without even mentioning overloads is not good at all.''<br />
<br />
<br />
''Strangely enough, the Colossus is never mentioned as either a destroyer, superdestroyer or a juggernaut in the game, instead being ambiguously called a warship. This sparked a debate, as every other canon ship was given a ship type excluding the Colossus. Further details on this debate may be found [[GTVA Colossus ship type debate|here]].''<br />
<br />
''The most likely reason for the Colossus' lack of a "ship type" is simply because the GTVA intended to build only one. It would be unnecessary to give it a designation since they were never planning to mass-produce such a huge and costly warship.''<br />
<br />
<br />
''Although many tend to praise the Colossus for its well-distributed anticapital firepower, this tactic, sadly, may usually prove ineffective. For example, if an attack operation against the Colossus were planned, the attacker's warships would have to be placed in one spot, so that the Colossus could only fire a fraction of its beam count. In short, the Colossus rarely is able to demonstrate its full firepower, since the enemy would not dare engage it from all sides anyway.''<br />
<br />
<br />
''I must question my own statement above, now. In the minds of the GTVA, no warship could pose any serious threat to the Colossus; any attack on it would not pose any significant harm to the behemoth anyway. The primary purpose of the Colossus is simply to end any kind of conflict anywhere, at any time; it jumps in, and wherever the enemy vessel is, it gets zapped by one of the Colossus' many well-distributed beams. Of course, the exception to this sort of usefulness would be an equally powerful warship - the Sathanas. However, as we know, the GTVA probably was not expecting such an encounter.''<br />
<br />
}}<br />
<br />
[[Category:Unique ships|Colossus, GTVA]]<br />
[[Category:Ship]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=GTVA_Colossus&diff=53823GTVA Colossus2017-12-07T05:47:29Z<p>Marcov: /* Veteran Comments */</p>
<hr />
<div>{{FS12_Ships}}<br />
The largest space-faring warship ever constructed by the [[Terrans]] or [[Vasudans]], the '''GTVA ''Colossus''''' was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six kilometers, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.<br />
<br />
With the offensive power that exceeded most [[GTVA]] battle groups, the ''Colossus'' was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more [[SD Lucifer|''Lucifer'']]-class super-destroyers, and it was deemed that the ''Colossus'' would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a ''Lucifer'''s primary weapon system.<br />
<br />
Although the ''Colossus'' was a joint endeavor of both the Terrans and Vasudans, it is apparent that the ship itself exhibits more Terran design traits than Vasudan. It can be assumed that some of the Vasudan elements manifest themselves in less immediately overt ways.<br />
<br />
==History==<br />
{{Gtvaship<br />
| image = [[File:Willy B-Colossus-MVP2014.png|300px]]<br />
| name = GTVA ''Colossus''<br />
| class = GTVA ''Colossus''<br />
| 1stapp = [[The Sixth Wonder]]<br />
| inservice = [[NTF Rebellion]]<br>[[Second Shivan Incursion]]<br />
| faction = [[Galactic Terran-Vasudan Alliance]]<br />
| fate = [[Their Finest Hour|Destroyed]] by [[SJ Sathanas|SJ ''Sathanas 17'']]<br />
}}<br />
The first combat deployment of the ''Colossus'' was against the [[Neo-Terran Front]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. NTF forces proved to be [[Feint! Parry! Riposte!|no match]] for the ''Colossus'' and her battle group, and the rebels made every effort to avoid direct combat with the warship. With his fleet shattered, and the remnants being actively pursued and destroyed by the ''Colossus'', [[Famous persons|Admiral Aken Bosch]] gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].<br />
<br />
With the NTF defeated, the ''Colossus'' was finally to fulfill the role her designers had envisioned for her: the defeat of a second Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather the even more massive [[SJ Sathanas|SJ ''Sathanas'']]-class juggernaut. Twenty years of constant struggle finally culminated with the ''Colossus'''s destruction of the [[SJ Sathanas|''Sathanas'']], all at the cost of moderate damage to the ''Colossus''.<br />
<br />
All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the ''Colossus'' was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the [[GTD Bastion|''Bastion'']], which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed a [[SD Ravana]], then a [[SJ Sathanas|SJ ''Sathanas'']] to engage the ''Colossus''. In her weakened state, it was obvious that the ''Colossus'' would not survive an engagement with another ''Sathanas''-class juggernaut, and Allied Command ordered the ''Colossus'' to withdraw.<br />
<br />
However, with the success of the ''Bastion'''s critical mission in doubt, the ''Colossus'' disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the ''Colossus'' was destroyed with the loss of all hands. The thirty-thousand officers and crew of the ''Colossus'' willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the [[Galactic Terran-Vasudan Alliance]].<br />
<br />
==Confirmed kills==<br />
*NTCv ''Hawkwood'' (Destroyed at Enif Station)<br />
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)<br />
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)<br />
*NTC ''Camisard'' (Reported destroyed in Command Briefing)<br />
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')<br />
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')<br />
*NTCv ''Danton'' (''Endgame'')<br />
*SJ ''Sathanas'' (First, High Noon mission)<br />
*SD ''Beast'' (Destroyed shortly before ''Sathanas 17'' destroyed the Colossus)<br />
<br />
==Quotes==<br />
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"<br />
<br />
"This is the GTVA ''Colossus''. Admiral Koth, you are ordered to power down your engines immediately and surrender. The Polaris jump node is blockaded, there is no escape."<br />
<br />
"You are sacrificing thousands of lives for nothing!"<br />
<br />
"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"<br />
<br />
"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"<br />
<br />
"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"<br />
<br />
==Colossus cutscene==<br />
'''Narrator:''' ''The following is classified level Rho. Unauthorized access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species? In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly-formed GTVA General Assembly. The emperor inaugurated an ambitious and unprecedented joint endeavor: The GTVA ''Colossus''.''<br />
<br />
'''Khonsu II:''' ''Together we built a civilization on the ruins of the [[Great War]], and now we stand on the threshold of a new era of prosperity and harmony. With Project Colossus, the Vasudan people celebrate our shared covenant of peaceful co-existence and mutual defense of our Terran allies.''<br />
<br />
'''Narrator:''' ''The ''Colossus'' is the most powerful space faring warship ever constructed. Spanning six kilometers from bow to stern, the ''Colossus'' has taken over twenty years to complete. Twelve ''Lucifer''-class destroyers can fit within its massive hull. Its state-of-the-art weaponry includes forty-five laser turrets, fifteen flak guns, twelve missile batteries, and twelve beam cannons. The ''Colossus'' wields more firepower than five ''Orion''-class destroyers combined. Sixty fighter and bomber wings are housed in its vast hangar and its crew numbers over thirty thousand. Among its major contractors are industry giants Triton Dynamics, Subach-Innes, and the Akheton Corporation. The alliance now wages war on multiple fronts: in Deneb, Alpha Centuri, Epsilon Pegasi, and the [[Nebula System|mysterious nebula]] beyond Gamma Draconis. Once deployed the ''Colossus'' will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.''<br />
<br />
==Description:==<br />
{{shipimage|image=[[File:Gtvacolossus-old.jpg]]|caption=The GTVA ''Colossus''}}<br />
===FS2 Tech Room Description===<br />
The GTVA ''Colossus'' resulted from an endeavor unprecedented in Terran or Vasudan history. This 6-kilometer-long behemoth is the result of 20 years of joint effort from dozens of contractors of both races. The ''Colossus'' is the most powerful space-faring warship ever made, bristling with over 80 weapon turrets. It also houses 60 fighter and bomber wings and requires a crew of over 30,000. The firepower of the ''Colossus'' is greater than that of most GTVA battle groups.<br />
<br />
===Developer Notes===<br />
None<br />
<br />
===Name Origin===<br />
Used in Latin to refer to large statues, the term is used in English (in lower case, being a common noun) to refer to anything of large size.<br />
<br />
The sixth of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue representing the god [[Helios]] that was constructed following a very important military victory. This is why the first mission featuring the ''Colossus'' is named "[[The Sixth Wonder]]."<br />
<br />
==Performance:==<br />
===Statistics===<br />
{{Ship_box<br />
|table_style = <br />
|name = GTVA ''Colossus''<br />
|type = ''See [[GTVA Colossus ship type debate]]''<br />
|manufacturer = All canon [[corporations]]<br />
|yaw_pitch_roll = 200.0, 200.0, 200.0<br />
|max_velocity = 25.0<br />
|hitpoints = 1 000 000<br />
|length = 6166<br />
|width = <br />
|height = <br />
|turrets = 63<br />
|fighters = 240<br />
}}<br />
<br />
===Armaments===<br />
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''<br />
{| border=1 cellpadding=4 style="border-collapse: collapse"<br />
|- align="center"<br />
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''<br />
|- align="center"<br />
| style="width:120px" |Turret Type<br />
| style="width:60px" |Amount<br />
|- align="center"<br />
| [[Terran Turret]]<br />
| 8<br />
|- align="center"<br />
| [[Terran Huge Turret]]<br />
| 10<br />
|- align="center"<br />
| [[Standard Flak]]<br />
| 12<br />
|- align="center"<br />
| [[MX-52]]<br />
| 8<br />
|- align="center"<br />
| [[GTM Piranha|Piranha]]<br />
| 2<br />
|- align="center"<br />
| [[AAAf]]<br />
| 10<br />
|- align="center"<br />
| [[TerSlash]]<br />
| 7<br />
|- align="center"<br />
| [[BGreen]]<br />
| 6<br />
|}<br />
<br />
==Modding Resources==<br />
{{shipimage|image=[[File:Gtvacolossus.jpg|600px]]|caption=The GTVA Colossus in FS2_Open with the [[mediavps]] enabled}}<br />
'''Retail''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br />
'''MediaVP 2014''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br><br />
History<br><br />
Proposed by: ??? on ???<br><br />
First WIP Post: ??? on ???<br><br />
First In-Game Model: ??? on ???<br><br />
Completed In-Game Model: ??? on ???<br><br />
Final Corrections: ??? on ???<br><br />
<br />
<br />
==Gallery==<br />
<gallery><br />
File:RScreen0025.jpg | Admiral Koth engages the GTVA ''Colossus''. <br />
File:RScreen0073.png | Demonstrating the meaning of superior firepower.<br />
File:RScreen0044.png | The GTVA ''Colossus''. <br />
File:RScreen0047.png | The ''Colossus'' meets its end at the hands of the [[Shivans]].<br />
</gallery><br />
<br />
==Veteran Comments==<br />
{{Comment|''The 6 BGreen beams of the Colossus are powerful and allow it to have no trouble taking on multiple destroyers at once while taking minimal damage in return. The Colossus is an all-round good ship &mdash; it has plenty of armor, a large number of turrets, and it's surprisingly fast for a ship of its size, matching the speed of the Sathanas and outpacing all destroyers.''<br />
<br />
<br />
''The GTVA Colossus is not that great at killing ships of equal size to it as the above. The placement of its main beam turrets are all over the ship, meaning that maximum firepower cannot be directed against heavier ships. However, this does also have its advantages. It means that no capital ship can be in a safe spot from it. It is also loaded with massive amounts of anti-fighter and bomber weaponry, making it a nightmare to attack. These anti-fighter weapons are also located around the main beams of the warship, making it more difficult to disable.''<br />
<br />
<br />
''I think that the blind spots of the Colossus are its rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two.''<br />
<br />
<br />
''The Colossus model is infamous for its low moment-of-inertia value, which causes it to swing around like a baseball bat during tight turns. This is also partly because its pivot point is located at the very back, where the huge engines are. Most other ships in contrast, including the Sathanas, have their pivot point located near the centre of the ship, so their turns look more normal even if their moment-of-inertia value is similar to the Colossus'.''<br />
<br />
<br />
''Keep in mind that the firepower demonstrated by the Colossus in [[High Noon]] was due to pushing the beams and fire control to their limit, resulting in considerable damage to the ship and weapons even if the Sathanas never fired a shot. Replacing the Colossus' default beams with more powerful beams without even mentioning overloads is not good at all.''<br />
<br />
<br />
''Strangely enough, the Colossus is never mentioned as either a destroyer, superdestroyer or a juggernaut in the game, instead being ambiguously called a warship. This sparked a debate, as every other canon ship was given a ship type excluding the Colossus. Further details on this debate may be found [[GTVA Colossus ship type debate|here]].''<br />
<br />
''The most likely reason for the Colossus' lack of a "ship type" is simply because the GTVA intended to build only one. It would be unnecessary to give it a designation since they were never planning to mass-produce such a huge and costly warship.''<br />
<br />
<br />
''Although many tend to praise the Colossus for its well-distributed anticapital firepower, this tactic, sadly, may usually prove ineffective. For example, if an attack operation against the Colossus were planned, the attacker's warships would have to be placed in one spot, so that the Colossus could only fire a fraction of its beam count. In short, the Colossus rarely is able to demonstrate its full firepower, since the enemy would not dare engage it from all sides anyway.''<br />
<br />
''I must question my own statement above, now. In the minds of the GTVA, no warship could pose any serious threat to the Colossus; any attack on it would not pose any significant harm to the behemoth anyway. The primary purpose of the Colossus is simply to end any kind of conflict anywhere, at any time; it jumps in, and wherever the enemy vessel is, it gets zapped by one of the Colossus' many well-distributed beams. Of course, the exception to this sort of usefulness would be an equally powerful warship - the Sathanas. However, as we know, the GTVA probably was not expecting such an encounter.''<br />
<br />
}}<br />
<br />
[[Category:Unique ships|Colossus, GTVA]]<br />
[[Category:Ship]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Ship&diff=53819Ship2017-12-07T05:14:27Z<p>Marcov: </p>
<hr />
<div>A '''ship''' is any space-faring vehicle. The term ''ship'', historically, referred mainly to large water-based vessels on [[Earth]]. However, with the advent of space travel, the term is used more often on the vessels that allowed for such an endeavor. This article will focus on such vehicles, which are sometimes colloquially called ''space-ships'' or ''starships''.<br />
<br />
==History==<br />
<br />
The [[Timeline|20th Century]] saw [[Terrans|humans]] develop craft that could travel far beyond the Earth's horizon and reach outer space. However, perhaps the most significant development in this area of travel would be the use of [[subspace]] for interstellar travel. Star systems once thought unreachable were now easily accessible, and Terrans, [[Vasudans]], and the [[Ancients]] managed to assimilate multiple planets and moons, vastly expanding their respective societies. Behind such a phenomenon was the development of highly advanced spacecraft which were equipped with '''subspace drives''', and were the means by which such travel could be possible.<br />
<br />
==Ship Types==<br />
<br />
Space-faring ships are classified into many different types. The largest distinction would be a ship's civilian or military purpose (though some ships may cross-over in this function, such as the [[GTSC Faustus]], a civilian research vessel which is lightly armed in times of war). A large ship whose purpose is military combat is called a '''warship''', while smaller vessels that serve the same purpose are called '''fighters''' and '''bombers'''.<br />
<br />
===Military===<br />
<br />
Warships are generally classified into three main categories; '''cruiser''', '''corvette''', and '''destroyer''', in order of increasing size and power. More uncommon classifications include '''frigate''', a term used to designate a large corvette (or small destroyer). '''Superdestroyer''' colloquially refers to destroyers which are larger and more powerful than is common, such as the [[SD Lucifer]] and [[GTD Hades]]; '''Juggernaut''' was used to classify the [[Shivans|Shivan]] [[SJ Sathanas]], whose size and power far surpassed those of any vessel the Terrans and Vasudans have ever encountered in their history. Additionally, only one warship could be considered beyond any form of classification; the [[GTVA Colossus]], a warship whose scope is vast enough to render it beyond the means of mass-production, negating its need for categorization. Later, warships were equipped with [[Beam weapon|beam weapons]], a state-of-the-art development once used by the SD Lucifer and replicated by the Terrans and Vasudans. However, beam-equipped Shivan warships remain far deadlier, with more efficient beam weapons than their Terran and Vasudan counterparts.<br />
<br />
Fighters and bombers are much smaller military spacecraft with far greater mobility than warships. While bombers are used to attack larger ships, fighters are there to defend such ships against bombers, dogfight other fighters, or weaken a warship's turrets and subsystems. It is worth noting that while the Shivans were at a huge advantage in the [[Great War]] due to having [[Shield|shielding systems]], they were soon outmatched by Terran and Vasudan fighters as soon as the latter were equipped with shields of their own, along with generally better weaponry.<br />
<br />
===Civilian===<br />
<br />
Civilian ships are vessels not generally used in wartime, though they may be equipped with light weaponry if needed during times of conflict. Prominent uses of such ships would be as '''transports''', '''freighters''', '''medical ships''', ''"AWACS ships''', '''escape pods''', and '''science ships'''.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Ship&diff=53818Ship2017-12-07T05:14:18Z<p>Marcov: </p>
<hr />
<div>A '''ship''' is any space-faring vehicle. The term '''ship''', historically, referred mainly to large water-based vessels on [[Earth]]. However, with the advent of space travel, the term is used more often on the vessels that allowed for such an endeavor. This article will focus on such vehicles, which are sometimes colloquially called ''space-ships'' or ''starships''.<br />
<br />
==History==<br />
<br />
The [[Timeline|20th Century]] saw [[Terrans|humans]] develop craft that could travel far beyond the Earth's horizon and reach outer space. However, perhaps the most significant development in this area of travel would be the use of [[subspace]] for interstellar travel. Star systems once thought unreachable were now easily accessible, and Terrans, [[Vasudans]], and the [[Ancients]] managed to assimilate multiple planets and moons, vastly expanding their respective societies. Behind such a phenomenon was the development of highly advanced spacecraft which were equipped with '''subspace drives''', and were the means by which such travel could be possible.<br />
<br />
==Ship Types==<br />
<br />
Space-faring ships are classified into many different types. The largest distinction would be a ship's civilian or military purpose (though some ships may cross-over in this function, such as the [[GTSC Faustus]], a civilian research vessel which is lightly armed in times of war). A large ship whose purpose is military combat is called a '''warship''', while smaller vessels that serve the same purpose are called '''fighters''' and '''bombers'''.<br />
<br />
===Military===<br />
<br />
Warships are generally classified into three main categories; '''cruiser''', '''corvette''', and '''destroyer''', in order of increasing size and power. More uncommon classifications include '''frigate''', a term used to designate a large corvette (or small destroyer). '''Superdestroyer''' colloquially refers to destroyers which are larger and more powerful than is common, such as the [[SD Lucifer]] and [[GTD Hades]]; '''Juggernaut''' was used to classify the [[Shivans|Shivan]] [[SJ Sathanas]], whose size and power far surpassed those of any vessel the Terrans and Vasudans have ever encountered in their history. Additionally, only one warship could be considered beyond any form of classification; the [[GTVA Colossus]], a warship whose scope is vast enough to render it beyond the means of mass-production, negating its need for categorization. Later, warships were equipped with [[Beam weapon|beam weapons]], a state-of-the-art development once used by the SD Lucifer and replicated by the Terrans and Vasudans. However, beam-equipped Shivan warships remain far deadlier, with more efficient beam weapons than their Terran and Vasudan counterparts.<br />
<br />
Fighters and bombers are much smaller military spacecraft with far greater mobility than warships. While bombers are used to attack larger ships, fighters are there to defend such ships against bombers, dogfight other fighters, or weaken a warship's turrets and subsystems. It is worth noting that while the Shivans were at a huge advantage in the [[Great War]] due to having [[Shield|shielding systems]], they were soon outmatched by Terran and Vasudan fighters as soon as the latter were equipped with shields of their own, along with generally better weaponry.<br />
<br />
===Civilian===<br />
<br />
Civilian ships are vessels not generally used in wartime, though they may be equipped with light weaponry if needed during times of conflict. Prominent uses of such ships would be as '''transports''', '''freighters''', '''medical ships''', ''"AWACS ships''', '''escape pods''', and '''science ships'''.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Ship&diff=53817Ship2017-12-07T05:14:09Z<p>Marcov: </p>
<hr />
<div>A '''ship''' is any space-faring vehicle. The term ''ship'', historically, referred mainly to large water-based vessels on [[Earth]]. However, with the advent of space travel, the term is used more often on the vessels that allowed for such an endeavor. This article will focus on such vehicles, which are sometimes colloquially called ''space-ships'' or ''starships''.<br />
<br />
==History==<br />
<br />
The [[Timeline|20th Century]] saw [[Terrans|humans]] develop craft that could travel far beyond the Earth's horizon and reach outer space. However, perhaps the most significant development in this area of travel would be the use of [[subspace]] for interstellar travel. Star systems once thought unreachable were now easily accessible, and Terrans, [[Vasudans]], and the [[Ancients]] managed to assimilate multiple planets and moons, vastly expanding their respective societies. Behind such a phenomenon was the development of highly advanced spacecraft which were equipped with '''subspace drives''', and were the means by which such travel could be possible.<br />
<br />
==Ship Types==<br />
<br />
Space-faring ships are classified into many different types. The largest distinction would be a ship's civilian or military purpose (though some ships may cross-over in this function, such as the [[GTSC Faustus]], a civilian research vessel which is lightly armed in times of war). A large ship whose purpose is military combat is called a '''warship''', while smaller vessels that serve the same purpose are called '''fighters''' and '''bombers'''.<br />
<br />
===Military===<br />
<br />
Warships are generally classified into three main categories; '''cruiser''', '''corvette''', and '''destroyer''', in order of increasing size and power. More uncommon classifications include '''frigate''', a term used to designate a large corvette (or small destroyer). '''Superdestroyer''' colloquially refers to destroyers which are larger and more powerful than is common, such as the [[SD Lucifer]] and [[GTD Hades]]; '''Juggernaut''' was used to classify the [[Shivans|Shivan]] [[SJ Sathanas]], whose size and power far surpassed those of any vessel the Terrans and Vasudans have ever encountered in their history. Additionally, only one warship could be considered beyond any form of classification; the [[GTVA Colossus]], a warship whose scope is vast enough to render it beyond the means of mass-production, negating its need for categorization. Later, warships were equipped with [[Beam weapon|beam weapons]], a state-of-the-art development once used by the SD Lucifer and replicated by the Terrans and Vasudans. However, beam-equipped Shivan warships remain far deadlier, with more efficient beam weapons than their Terran and Vasudan counterparts.<br />
<br />
Fighters and bombers are much smaller military spacecraft with far greater mobility than warships. While bombers are used to attack larger ships, fighters are there to defend such ships against bombers, dogfight other fighters, or weaken a warship's turrets and subsystems. It is worth noting that while the Shivans were at a huge advantage in the [[Great War]] due to having [[Shield|shielding systems]], they were soon outmatched by Terran and Vasudan fighters as soon as the latter were equipped with shields of their own, along with generally better weaponry.<br />
<br />
===Civilian===<br />
<br />
Civilian ships are vessels not generally used in wartime, though they may be equipped with light weaponry if needed during times of conflict. Prominent uses of such ships would be as '''transports''', '''freighters''', '''medical ships''', ''"AWACS ships''', '''escape pods''', and '''science ships'''.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Ship&diff=53816Ship2017-12-07T05:13:41Z<p>Marcov: Created page with "A '''ship''' is any space-faring vehicle. The term [i]ship[/i], historically, referred mainly to large water-based vessels on Earth. However, with the advent of space trav..."</p>
<hr />
<div>A '''ship''' is any space-faring vehicle. The term [i]ship[/i], historically, referred mainly to large water-based vessels on [[Earth]]. However, with the advent of space travel, the term is used more often on the vessels that allowed for such an endeavor. This article will focus on such vehicles, which are sometimes colloquially called ''space-ships'' or ''starships''.<br />
<br />
==History==<br />
<br />
The [[Timeline|20th Century]] saw [[Terrans|humans]] develop craft that could travel far beyond the Earth's horizon and reach outer space. However, perhaps the most significant development in this area of travel would be the use of [[subspace]] for interstellar travel. Star systems once thought unreachable were now easily accessible, and Terrans, [[Vasudans]], and the [[Ancients]] managed to assimilate multiple planets and moons, vastly expanding their respective societies. Behind such a phenomenon was the development of highly advanced spacecraft which were equipped with '''subspace drives''', and were the means by which such travel could be possible.<br />
<br />
==Ship Types==<br />
<br />
Space-faring ships are classified into many different types. The largest distinction would be a ship's civilian or military purpose (though some ships may cross-over in this function, such as the [[GTSC Faustus]], a civilian research vessel which is lightly armed in times of war). A large ship whose purpose is military combat is called a '''warship''', while smaller vessels that serve the same purpose are called '''fighters''' and '''bombers'''.<br />
<br />
===Military===<br />
<br />
Warships are generally classified into three main categories; '''cruiser''', '''corvette''', and '''destroyer''', in order of increasing size and power. More uncommon classifications include '''frigate''', a term used to designate a large corvette (or small destroyer). '''Superdestroyer''' colloquially refers to destroyers which are larger and more powerful than is common, such as the [[SD Lucifer]] and [[GTD Hades]]; '''Juggernaut''' was used to classify the [[Shivans|Shivan]] [[SJ Sathanas]], whose size and power far surpassed those of any vessel the Terrans and Vasudans have ever encountered in their history. Additionally, only one warship could be considered beyond any form of classification; the [[GTVA Colossus]], a warship whose scope is vast enough to render it beyond the means of mass-production, negating its need for categorization. Later, warships were equipped with [[Beam weapon|beam weapons]], a state-of-the-art development once used by the SD Lucifer and replicated by the Terrans and Vasudans. However, beam-equipped Shivan warships remain far deadlier, with more efficient beam weapons than their Terran and Vasudan counterparts.<br />
<br />
Fighters and bombers are much smaller military spacecraft with far greater mobility than warships. While bombers are used to attack larger ships, fighters are there to defend such ships against bombers, dogfight other fighters, or weaken a warship's turrets and subsystems. It is worth noting that while the Shivans were at a huge advantage in the [[Great War]] due to having [[Shield|shielding systems]], they were soon outmatched by Terran and Vasudan fighters as soon as the latter were equipped with shields of their own, along with generally better weaponry.<br />
<br />
===Civilian===<br />
<br />
Civilian ships are vessels not generally used in wartime, though they may be equipped with light weaponry if needed during times of conflict. Prominent uses of such ships would be as '''transports''', '''freighters''', '''medical ships''', ''"AWACS ships''', '''escape pods''', and '''science ships'''.</div>Marcovhttps://wiki.hard-light.net/index.php?title=GTVA_Colossus&diff=46256GTVA Colossus2017-11-20T04:29:33Z<p>Marcov: </p>
<hr />
<div>{{FS12_Ships}}<br />
The largest space-faring warship ever constructed by the [[Terrans]] or [[Vasudans]], the '''GTVA ''Colossus''''' was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six kilometers, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.<br />
<br />
With the offensive power that exceeded most [[GTVA]] battle groups, the ''Colossus'' was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more [[SD Lucifer|''Lucifer'']]-class super-destroyers, and it was deemed that the ''Colossus'' would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a ''Lucifer'''s primary weapon system.<br />
<br />
Although the ''Colossus'' was a joint endeavor of both the Terrans and Vasudans, it is apparent that the ship itself exhibits more Terran design traits than Vasudan. It can be assumed that some of the Vasudan elements manifest themselves in less immediately overt ways.<br />
<br />
==History==<br />
{{Gtvaship<br />
| image = [[File:Willy B-Colossus-MVP2014.png|300px]]<br />
| name = GTVA ''Colossus''<br />
| class = GTVA ''Colossus''<br />
| 1stapp = [[The Sixth Wonder]]<br />
| inservice = [[NTF Rebellion]]<br>[[Second Shivan Incursion]]<br />
| faction = [[Galactic Terran-Vasudan Alliance]]<br />
| fate = [[Their Finest Hour|Destroyed]] by [[SJ Sathanas|SJ ''Sathanas 17'']]<br />
}}<br />
The first combat deployment of the ''Colossus'' was against the [[Neo-Terran Front]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. NTF forces proved to be [[Feint! Parry! Riposte!|no match]] for the ''Colossus'' and her battle group, and the rebels made every effort to avoid direct combat with the warship. With his fleet shattered, and the remnants being actively pursued and destroyed by the ''Colossus'', [[Famous persons|Admiral Aken Bosch]] gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].<br />
<br />
With the NTF defeated, the ''Colossus'' was finally to fulfill the role her designers had envisioned for her: the defeat of a second Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather the even more massive [[SJ Sathanas|SJ ''Sathanas'']]-class juggernaut. Twenty years of constant struggle finally culminated with the ''Colossus'''s destruction of the [[SJ Sathanas|''Sathanas'']], all at the cost of moderate damage to the ''Colossus''.<br />
<br />
All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the ''Colossus'' was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the [[GTD Bastion|''Bastion'']], which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed a [[SD Ravana]], then a [[SJ Sathanas|SJ ''Sathanas'']] to engage the ''Colossus''. In her weakened state, it was obvious that the ''Colossus'' would not survive an engagement with another ''Sathanas''-class juggernaut, and Allied Command ordered the ''Colossus'' to withdraw.<br />
<br />
However, with the success of the ''Bastion'''s critical mission in doubt, the ''Colossus'' disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the ''Colossus'' was destroyed with the loss of all hands. The thirty-thousand officers and crew of the ''Colossus'' willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the [[Galactic Terran-Vasudan Alliance]].<br />
<br />
==Confirmed kills==<br />
*NTCv ''Hawkwood'' (Destroyed at Enif Station)<br />
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)<br />
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)<br />
*NTC ''Camisard'' (Reported destroyed in Command Briefing)<br />
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')<br />
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')<br />
*NTCv ''Danton'' (''Endgame'')<br />
*SJ ''Sathanas'' (First, High Noon mission)<br />
*SD ''Beast'' (Destroyed shortly before ''Sathanas 17'' destroyed the Colossus)<br />
<br />
==Quotes==<br />
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"<br />
<br />
"This is the GTVA ''Colossus''. Admiral Koth, you are ordered to power down your engines immediately and surrender. The Polaris jump node is blockaded, there is no escape."<br />
<br />
"You are sacrificing thousands of lives for nothing!"<br />
<br />
"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"<br />
<br />
"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"<br />
<br />
"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"<br />
<br />
==Colossus cutscene==<br />
'''Narrator:''' ''The following is classified level Rho. Unauthorized access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species? In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly-formed GTVA General Assembly. The emperor inaugurated an ambitious and unprecedented joint endeavor: The GTVA ''Colossus''.''<br />
<br />
'''Khonsu II:''' ''Together we built a civilization on the ruins of the [[Great War]], and now we stand on the threshold of a new era of prosperity and harmony. With Project Colossus, the Vasudan people celebrate our shared covenant of peaceful co-existence and mutual defense of our Terran allies.''<br />
<br />
'''Narrator:''' ''The ''Colossus'' is the most powerful space faring warship ever constructed. Spanning six kilometers from bow to stern, the ''Colossus'' has taken over twenty years to complete. Twelve ''Lucifer''-class destroyers can fit within its massive hull. Its state-of-the-art weaponry includes forty-five laser turrets, fifteen flak guns, twelve missile batteries, and twelve beam cannons. The ''Colossus'' wields more firepower than five ''Orion''-class destroyers combined. Sixty fighter and bomber wings are housed in its vast hangar and its crew numbers over thirty thousand. Among its major contractors are industry giants Triton Dynamics, Subach-Innes, and the Akheton Corporation. The alliance now wages war on multiple fronts: in Deneb, Alpha Centuri, Epsilon Pegasi, and the [[Nebula System|mysterious nebula]] beyond Gamma Draconis. Once deployed the ''Colossus'' will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.''<br />
<br />
==Description:==<br />
{{shipimage|image=[[File:Gtvacolossus-old.jpg]]|caption=The GTVA ''Colossus''}}<br />
===FS2 Tech Room Description===<br />
The GTVA ''Colossus'' resulted from an endeavor unprecedented in Terran or Vasudan history. This 6-kilometer-long behemoth is the result of 20 years of joint effort from dozens of contractors of both races. The ''Colossus'' is the most powerful space-faring warship ever made, bristling with over 80 weapon turrets. It also houses 60 fighter and bomber wings and requires a crew of over 30,000. The firepower of the ''Colossus'' is greater than that of most GTVA battle groups.<br />
<br />
===Developer Notes===<br />
None<br />
<br />
===Name Origin===<br />
Used in Latin to refer to large statues, the term is used in English (in lower case, being a common noun) to refer to anything of large size.<br />
<br />
The sixth of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue representing the god [[Helios]] that was constructed following a very important military victory. This is why the first mission featuring the ''Colossus'' is named "[[The Sixth Wonder]]."<br />
<br />
==Performance:==<br />
===Statistics===<br />
{{Ship_box<br />
|table_style = <br />
|name = GTVA ''Colossus''<br />
|type = ''See [[GTVA Colossus ship type debate]]''<br />
|manufacturer = All canon [[corporations]]<br />
|yaw_pitch_roll = 200.0, 200.0, 200.0<br />
|max_velocity = 25.0<br />
|hitpoints = 1 000 000<br />
|length = 6166<br />
|width = <br />
|height = <br />
|turrets = 63<br />
|fighters = 240<br />
}}<br />
<br />
===Armaments===<br />
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''<br />
{| border=1 cellpadding=4 style="border-collapse: collapse"<br />
|- align="center"<br />
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''<br />
|- align="center"<br />
| style="width:120px" |Turret Type<br />
| style="width:60px" |Amount<br />
|- align="center"<br />
| [[Terran Turret]]<br />
| 8<br />
|- align="center"<br />
| [[Terran Huge Turret]]<br />
| 10<br />
|- align="center"<br />
| [[Standard Flak]]<br />
| 12<br />
|- align="center"<br />
| [[MX-52]]<br />
| 8<br />
|- align="center"<br />
| [[GTM Piranha|Piranha]]<br />
| 2<br />
|- align="center"<br />
| [[AAAf]]<br />
| 10<br />
|- align="center"<br />
| [[TerSlash]]<br />
| 7<br />
|- align="center"<br />
| [[BGreen]]<br />
| 6<br />
|}<br />
<br />
==Modding Resources==<br />
{{shipimage|image=[[File:Gtvacolossus.jpg|600px]]|caption=The GTVA Colossus in FS2_Open with the [[mediavps]] enabled}}<br />
'''Retail''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br />
'''MediaVP 2014''':<br />
:$POF File: Colossus.pof<br />
:Textures: ???<br />
<br><br />
History<br><br />
Proposed by: ??? on ???<br><br />
First WIP Post: ??? on ???<br><br />
First In-Game Model: ??? on ???<br><br />
Completed In-Game Model: ??? on ???<br><br />
Final Corrections: ??? on ???<br><br />
<br />
<br />
==Gallery==<br />
<gallery><br />
File:RScreen0025.jpg | Admiral Koth engages the GTVA ''Colossus''. <br />
File:RScreen0073.png | Demonstrating the meaning of superior firepower.<br />
File:RScreen0044.png | The GTVA ''Colossus''. <br />
File:RScreen0047.png | The ''Colossus'' meets its end at the hands of the [[Shivans]].<br />
</gallery><br />
<br />
==Veteran Comments==<br />
{{Comment|''The 6 BGreen beams of the Colossus are powerful and allow it to have no trouble taking on multiple destroyers at once while taking minimal damage in return. The Colossus is an all-round good ship &mdash; it has plenty of armor, a large number of turrets, and it's surprisingly fast for a ship of its size, matching the speed of the Sathanas and outpacing all destroyers.''<br />
<br />
<br />
''The GTVA Colossus is not that great at killing ships of equal size to it as the above. The placement of its main beam turrets are all over the ship, meaning that maximum firepower cannot be directed against heavier ships. However, this does also have its advantages. It means that no capital ship can be in a safe spot from it. It is also loaded with massive amounts of anti-fighter and bomber weaponry, making it a nightmare to attack. These anti-fighter weapons are also located around the main beams of the warship, making it more difficult to disable.''<br />
<br />
<br />
''I think that the blind spots of the Colossus are its rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two.''<br />
<br />
<br />
''The Colossus model is infamous for its low moment-of-inertia value, which causes it to swing around like a baseball bat during tight turns. This is also partly because its pivot point is located at the very back, where the huge engines are. Most other ships in contrast, including the Sathanas, have their pivot point located near the centre of the ship, so their turns look more normal even if their moment-of-inertia value is similar to the Colossus'.''<br />
<br />
<br />
''Keep in mind that the firepower demonstrated by the Colossus in [[High Noon]] was due to pushing the beams and fire control to their limit, resulting in considerable damage to the ship and weapons even if the Sathanas never fired a shot. Replacing the Colossus' default beams with more powerful beams without even mentioning overloads is not good at all.''<br />
<br />
<br />
''Strangely enough, the Colossus is never mentioned as either a destroyer, superdestroyer or a juggernaut in the game, instead being ambiguously called a warship. This sparked a debate, as every other canon ship was given a ship type excluding the Colossus. Further details on this debate may be found [[GTVA Colossus ship type debate|here]].''<br />
<br />
''The most likely reason for the Colossus' lack of a "ship type" is simply because the GTVA intended to build only one. It would be unnecessary to give it a designation since they were never planning to mass-produce such a huge and costly warship.''<br />
<br />
<br />
''Although many tend to praise the Colossus for its well-distributed anticapital firepower, this tactic, sadly, may usually prove ineffective. For example, if an attack operation against the Colossus were planned, the attacker's warships would have to be placed in one spot, so that the Colossus could only fire a fraction of its beam count. In short, the Colossus rarely is able to demonstrate its full firepower, since the enemy would not dare engage it from all sides anyway.''<br />
<br />
}}<br />
<br />
[[Category:Unique ships|Colossus, GTVA]]<br />
[[Category:Ship]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Alpha_1&diff=41264Alpha 12013-01-05T12:06:57Z<p>Marcov: /* Career */</p>
<hr />
<div>'''Alpha 1''' is the designation of the fighter pilot who flies as the leader of Alpha wing. The player is given this designation in all canon campaigns, and is almost exclusively referred to as such in-game.<br />
<br />
As the player's character, Alpha 1 never speaks a single line in any canon FreeSpace mission.<br />
<br />
==Career==<br />
Logic dictates that Alpha 1 almost certainly cannot be the same person for each game. The Alpha 1 of ''FreeSpace 1'' ended up in [[Sol]], cut off. Alpha 1 of ''Silent Threat'' would be too old to be in active fighter command by the time of ''FreeSpace 2'', and in any case FS2's Alpha 1 is welcomed as a new recruit by Lieutenant Loukakis.<br />
<br />
Regardless, some major events that individual pilots with the designation Alpha 1 have experienced are listed here along with any relevant information.<br />
<br />
Alpha 1 is perhaps the best fighter pilot in the GTVA, seeing as he was responsible for scanning the first [[SJ Sathanas]] alone, as well as being one of the few who participated in the [[Into the Lion's Den|SOC mission beyond the nebula system.]] The fact that Alpha 1 wins virtually every mission he is tasked to perform is sometimes jokingly referred to by community members.<br />
<br />
===The Great War===<br />
:''Main article: [[Great War]]''<br />
*Captured [[Alexander McCarthy]].<br />
*Acquisition of [[Shivans|Shivan]] [[shield]] technology.<br />
*Witnessed the destruction of the [[GTD Galatea|GTD ''Galatea'']].<br />
*Participated in the [[Destruction of the SD Lucifer|attack]] on the [[SD Lucifer|SD ''Lucifer'']].<br />
<br />
===GTI Rebellion===<br />
:''Main article: [[Hades Rebellion]]''<br />
*Helped destroy the [[GTD Hades|GTD ''Hades'']]. (''[[Silent Threat]]'')<br />
<br />
There is some speculation that ''Silent Threat'''s Alpha 1 may be [[Aken Bosch]]. In the cutscene Monologue 4, Bosch states:<br />
:"As a young pilot I battled against the rebels of the Great War, the [[Galactic Terran Intelligence]] whose research of Shivan technology and biology would form the cornerstone of my project."<br />
<br />
===The Second Shivan Invasion===<br />
:''Main article: [[Second Shivan Incursion]]''<br />
*Weakened the first [[SJ Sathanas|SJ ''Sathanas'']] enabling the [[GTVA Colossus|GTVA ''Colossus'']] to defeat it.<br />
*Witnessed the Colossus's first and last battles.<br />
*Helped evacuate [[Capella]].<br />
*Took part in several extremely dangerous [[Special Operations Command]] operations.<br />
<br />
==Non-canon==<br />
In many [[Campaign List|user-made campaigns]], the player's character retains the designation of Alpha 1. Whether a campaign's pilot is the same Alpha 1 as the one that the player flies in the official games is determined by the user-made campaign's plot line. Newer versions of [[FreeSpace Open]] allow the [[FREDder]] to place the pilot into wings other than Alpha, Beta, and Gamma. This change inspired campaign makers to get rid of the "Player is Alpha 1" tradition.<br />
<br />
Some campaigns have also foregone the "speechless Alpha 1" convention, giving the player character a fully-fleshed out character. These campaigns are sometimes known as 'character-driven campaigns'. Notable character-driven campaigns include [[Blue Planet]] and [[Transcend]].<br />
<br />
==Trivia==<br />
*Alpha 1 only speaks once: in the ending cutscene of ''FreeSpace 1''.<br />
*[[Portal:FRED|FRED]] doesn't allow the player ship to send any in-mission messages. This can be circumvented by preceding the player ship's name with #, as in #Alpha 1. New SCP builds will take this into account if the player ship is given a callsign and replace the in-game sender name with the defined callsign accordingly.<br />
*Lines such as "Pilot down!" or "Squad lost a pilot!" are only spoken when Alpha 1 is killed. If an AI-controlled friendly craft is destroyed, its own pilot may send an automatic message (usually an agonized scream), but none of the remaining pilots will take note unless they are specifically scripted to do so.<br />
<br />
[[Category:Characters]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Alpha_1&diff=41263Alpha 12013-01-05T12:05:41Z<p>Marcov: /* Career */</p>
<hr />
<div>'''Alpha 1''' is the designation of the fighter pilot who flies as the leader of Alpha wing. The player is given this designation in all canon campaigns, and is almost exclusively referred to as such in-game.<br />
<br />
As the player's character, Alpha 1 never speaks a single line in any canon FreeSpace mission.<br />
<br />
==Career==<br />
Logic dictates that Alpha 1 almost certainly cannot be the same person for each game. The Alpha 1 of ''FreeSpace 1'' ended up in [[Sol]], cut off. Alpha 1 of ''Silent Threat'' would be too old to be in active fighter command by the time of ''FreeSpace 2'', and in any case FS2's Alpha 1 is welcomed as a new recruit by Lieutenant Loukakis.<br />
<br />
Regardless, some major events that individual pilots with the designation Alpha 1 have experienced are listed here along with any relevant information.<br />
<br />
Alpha 1 is perhaps the best fighter pilot in the GTVA, seeing as he was responsible for scanning the first [[SJ Sathanas]] alone, as well as being one of the few who participated in the [[Into The Lion's Den|SOC mission beyond the nebula system.]] The fact that Alpha 1 wins virtually every mission he is tasked to perform is sometimes jokingly referred to by community members.<br />
<br />
===The Great War===<br />
:''Main article: [[Great War]]''<br />
*Captured [[Alexander McCarthy]].<br />
*Acquisition of [[Shivans|Shivan]] [[shield]] technology.<br />
*Witnessed the destruction of the [[GTD Galatea|GTD ''Galatea'']].<br />
*Participated in the [[Destruction of the SD Lucifer|attack]] on the [[SD Lucifer|SD ''Lucifer'']].<br />
<br />
===GTI Rebellion===<br />
:''Main article: [[Hades Rebellion]]''<br />
*Helped destroy the [[GTD Hades|GTD ''Hades'']]. (''[[Silent Threat]]'')<br />
<br />
There is some speculation that ''Silent Threat'''s Alpha 1 may be [[Aken Bosch]]. In the cutscene Monologue 4, Bosch states:<br />
:"As a young pilot I battled against the rebels of the Great War, the [[Galactic Terran Intelligence]] whose research of Shivan technology and biology would form the cornerstone of my project."<br />
<br />
===The Second Shivan Invasion===<br />
:''Main article: [[Second Shivan Incursion]]''<br />
*Weakened the first [[SJ Sathanas|SJ ''Sathanas'']] enabling the [[GTVA Colossus|GTVA ''Colossus'']] to defeat it.<br />
*Witnessed the Colossus's first and last battles.<br />
*Helped evacuate [[Capella]].<br />
*Took part in several extremely dangerous [[Special Operations Command]] operations.<br />
<br />
==Non-canon==<br />
In many [[Campaign List|user-made campaigns]], the player's character retains the designation of Alpha 1. Whether a campaign's pilot is the same Alpha 1 as the one that the player flies in the official games is determined by the user-made campaign's plot line. Newer versions of [[FreeSpace Open]] allow the [[FREDder]] to place the pilot into wings other than Alpha, Beta, and Gamma. This change inspired campaign makers to get rid of the "Player is Alpha 1" tradition.<br />
<br />
Some campaigns have also foregone the "speechless Alpha 1" convention, giving the player character a fully-fleshed out character. These campaigns are sometimes known as 'character-driven campaigns'. Notable character-driven campaigns include [[Blue Planet]] and [[Transcend]].<br />
<br />
==Trivia==<br />
*Alpha 1 only speaks once: in the ending cutscene of ''FreeSpace 1''.<br />
*[[Portal:FRED|FRED]] doesn't allow the player ship to send any in-mission messages. This can be circumvented by preceding the player ship's name with #, as in #Alpha 1. New SCP builds will take this into account if the player ship is given a callsign and replace the in-game sender name with the defined callsign accordingly.<br />
*Lines such as "Pilot down!" or "Squad lost a pilot!" are only spoken when Alpha 1 is killed. If an AI-controlled friendly craft is destroyed, its own pilot may send an automatic message (usually an agonized scream), but none of the remaining pilots will take note unless they are specifically scripted to do so.<br />
<br />
[[Category:Characters]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Alpha_1&diff=41262Alpha 12013-01-05T12:05:05Z<p>Marcov: </p>
<hr />
<div>'''Alpha 1''' is the designation of the fighter pilot who flies as the leader of Alpha wing. The player is given this designation in all canon campaigns, and is almost exclusively referred to as such in-game.<br />
<br />
As the player's character, Alpha 1 never speaks a single line in any canon FreeSpace mission.<br />
<br />
==Career==<br />
Logic dictates that Alpha 1 almost certainly cannot be the same person for each game. The Alpha 1 of ''FreeSpace 1'' ended up in [[Sol]], cut off. Alpha 1 of ''Silent Threat'' would be too old to be in active fighter command by the time of ''FreeSpace 2'', and in any case FS2's Alpha 1 is welcomed as a new recruit by Lieutenant Loukakis.<br />
<br />
Regardless, some major events that individual pilots with the designation Alpha 1 have experienced are listed here along with any relevant information.<br />
<br />
Alpha 1 is perhaps the best fighter pilot in the GTVA, seeing as he was responsible for scanning the first [[SJ Sathanas]] alone, as well as being one of the few who participated in the [[IntoTheLionsDen SOC mission beyond the nebula system.]] The fact that Alpha 1 wins virtually every mission he is tasked to perform is sometimes jokingly referred to by community members.<br />
<br />
===The Great War===<br />
:''Main article: [[Great War]]''<br />
*Captured [[Alexander McCarthy]].<br />
*Acquisition of [[Shivans|Shivan]] [[shield]] technology.<br />
*Witnessed the destruction of the [[GTD Galatea|GTD ''Galatea'']].<br />
*Participated in the [[Destruction of the SD Lucifer|attack]] on the [[SD Lucifer|SD ''Lucifer'']].<br />
<br />
===GTI Rebellion===<br />
:''Main article: [[Hades Rebellion]]''<br />
*Helped destroy the [[GTD Hades|GTD ''Hades'']]. (''[[Silent Threat]]'')<br />
<br />
There is some speculation that ''Silent Threat'''s Alpha 1 may be [[Aken Bosch]]. In the cutscene Monologue 4, Bosch states:<br />
:"As a young pilot I battled against the rebels of the Great War, the [[Galactic Terran Intelligence]] whose research of Shivan technology and biology would form the cornerstone of my project."<br />
<br />
===The Second Shivan Invasion===<br />
:''Main article: [[Second Shivan Incursion]]''<br />
*Weakened the first [[SJ Sathanas|SJ ''Sathanas'']] enabling the [[GTVA Colossus|GTVA ''Colossus'']] to defeat it.<br />
*Witnessed the Colossus's first and last battles.<br />
*Helped evacuate [[Capella]].<br />
*Took part in several extremely dangerous [[Special Operations Command]] operations.<br />
<br />
==Non-canon==<br />
In many [[Campaign List|user-made campaigns]], the player's character retains the designation of Alpha 1. Whether a campaign's pilot is the same Alpha 1 as the one that the player flies in the official games is determined by the user-made campaign's plot line. Newer versions of [[FreeSpace Open]] allow the [[FREDder]] to place the pilot into wings other than Alpha, Beta, and Gamma. This change inspired campaign makers to get rid of the "Player is Alpha 1" tradition.<br />
<br />
Some campaigns have also foregone the "speechless Alpha 1" convention, giving the player character a fully-fleshed out character. These campaigns are sometimes known as 'character-driven campaigns'. Notable character-driven campaigns include [[Blue Planet]] and [[Transcend]].<br />
<br />
==Trivia==<br />
*Alpha 1 only speaks once: in the ending cutscene of ''FreeSpace 1''.<br />
*[[Portal:FRED|FRED]] doesn't allow the player ship to send any in-mission messages. This can be circumvented by preceding the player ship's name with #, as in #Alpha 1. New SCP builds will take this into account if the player ship is given a callsign and replace the in-game sender name with the defined callsign accordingly.<br />
*Lines such as "Pilot down!" or "Squad lost a pilot!" are only spoken when Alpha 1 is killed. If an AI-controlled friendly craft is destroyed, its own pilot may send an automatic message (usually an agonized scream), but none of the remaining pilots will take note unless they are specifically scripted to do so.<br />
<br />
[[Category:Characters]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=4126199th Skulls2013-01-05T12:00:21Z<p>Marcov: /* Actions */</p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls were an elite fighter squadron during the [[Second Shivan Incursion]]. Among the first squadrons to among the first squadrons to be armed with the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons, they appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th was probably directly commanded by [[Special Operations Command]].<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of its top pilots, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason...]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]].<br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=4126099th Skulls2013-01-05T11:59:40Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls were an elite fighter squadron during the [[Second Shivan Incursion]]. Among the first squadrons to among the first squadrons to be armed with the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons, they appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th was probably directly commanded by the [[Special Operations Command|SOC]].<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of its top pilots, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason...]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]].<br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=4125999th Skulls2013-01-05T11:58:45Z<p>Marcov: /* Actions */</p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls were an elite fighter squadron during the [[Second Shivan Incursion]]. Among the first squadrons to among the first squadrons to be armed with the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons, they appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th was probably directly commanded by the [[Special Operations Command|SOC]].<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of its top pilots, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason...]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=4125899th Skulls2013-01-05T11:57:26Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls were an elite fighter squadron during the [[Second Shivan Incursion]]. Among the first squadrons to among the first squadrons to be armed with the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons, they appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th was probably directly commanded by the [[Special Operations Command|SOC]].<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason...]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Beam_weapon&diff=38410Beam weapon2012-04-28T05:23:09Z<p>Marcov: /* Capabilities */</p>
<hr />
<div>[[File:RScreen0053.png|480px|right|thumb|A ''Ravana''-class destroyer firing two of its frontal primary beam weapons upon exiting subspace]]<br />
<br />
'''Beam weapons''', or '''Beam cannons''', are large, powerful, ray-based lasers often used to slice through large warships. Most capital ships in FreeSpace 2 are equipped with beams.<br />
<br />
There are three main types; '''direct-fire''', '''slashing''', and '''anti-fighter'''.<br />
<br />
==History==<br />
During the [[Great War]] and the [[GTI Rebellion]], the [[Terrans]] and [[Vasudans]] encountered the [[Shivans]], a previously-unknown alien race. Both species took note of the technological capability of the Shivans, particularly the main guns of the [[SD Lucifer|Shivan command ship]], which they termed "Flux Cannons". The two races opted to replicate this technology after the end of the GTI Rebellion in late 2335. The result of this pursuit was the invention of the deadliest and most advanced weapons of war ever created by either race, called '''beam weapons'''. The first class of ship which was fully designed with beam weapons in mind may have been the [[GVCv Sobek|GVCv ''Sobek'']], which is said to have entered service shortly after the destruction of Vasuda Prime. Further advancements enabled engineers from both races to mount these weapons on older vessels never meant to accommodate them, as well as less powerful, more energy-efficient versions on smaller ships.<br />
<br />
Despite these advances, neither species was ultimately capable of matching up to the Shivans during the [[Second Shivan Incursion]] of 2367. Shivan beams were far more destructive than any Terran or Vasudan beam weapon ever made in terms of raw power and were capable of much faster refire rates at no visible cost to ship integrity. These advantages that Shivan beam weapons have over their Terran and Vasudan counterparts were demonstrated when the most powerful ship ever constructed by both races, the GTVA ''Colossus'', was obliterated almost completely by beam fire from a ''Sathanas'' juggernaut.<br />
<br />
==Capabilities==<br />
Sufficient [[reactor]] power is required in order to fire beam weapons. Therefore, they are never mounted on fighters or bombers, which have reactors too small and too weak to support the power drain. For a time, the Vasudans' [[GVD Typhon|''Typhon''-class destroyers]] encountered similar issues, with most of them suffering from reactor overloads and system failures due to their power grid being unable to cope with the power needed to fire the beams equipped on them. The deployment of the [[GVD Hatshepsut|''Hatshepsut'']] line of destroyers would rectify this problem.<br />
<br />
In general, beam weapons are designed to be fired against ships larger than bomber-class, which are large enough to be targeted with. These are generally called "anti-capship beams" by players. However, smaller, lighter beam weapons exist that deliver less damage than anti-capship beams but are capable of targeting even fighters and bombers. These are recognised as "anti-fighter beams" in FreeSpace canon (dubbed "AAA beams" on occasion by players due to their names in the FreeSpace 2 table files). The advancement of the beam weapon in the Terran and Vasudan fleets is sufficient enough to enable the most powerful anti-capship beam from either race to easily cleave through most cruisers and corvettes in minutes and deal significant damage to destroyers, if not destroying them outright.<br />
<br />
Most Terran and Vasudan beam weapons are meant to be fired at a specified power output, dealing a consistent rate of damage assuming that the beam in question strikes its target for the entire duration of its lifetime. However, if the situation warrants, it is also possible to reduce power output to limit damage done, or increase power output beyond specified limits to increase damage rates; the latter comes with the risk of emitter and heat sink deterioration. Examples of ships that have taken either course of action are the GTC ''Rampart'' during a feint attack on two cruisers, and the GTVA ''Colossus'', during its engagement with SJ ''Sathanas 01''.<br />
<br />
==Beam types==<br />
There are four beam types included in retail FreeSpace 2, but only the first three were used throughout the course of the game.<br />
# ''Direct-fire beams'', which are essentially standard-issue point-and-shoot weapons. These beams can be directed to target specific sections of the target ship if necessary.<br />
# ''Slashing beams'', which strike their targets across a wide arc. Slashing beams have a marginally higher damage output and faster refire rate than direct-fire beams, but are much more inaccurate and may completely miss the target on occasion.<br />
# ''Anti-fighter beams'', which can target vessels smaller than cruiser-class. These beams are capable of firing more than once per pulse, but do very little damage as compared to direct-fire or slashing beams. Under the most dire circumstances, they may be used against larger vessels as well.<br />
# ''Targeting beams'', which are never used in the game and whose purpose remains unknown. One beam of this type (the [[Targeting Laser]]) is included in the FreeSpace 2 tables, but it appears to serve no purpose due to supplementary content being cut.<br />
<br />
Both the Terrans and Vasudans manufacture and make use of the first three beam types. The Shivans, however, utilise only the first and third types.<br />
<br />
==Notes for mission designers==<br />
:''See also: [[SEXP Reference]]''<br />
Newly-created missions in FRED2 do not enable beams by default. The easiest way to enable beam fire is to use the [[beam-free-all]] SEXP on every individual ship that needs to fire its beams. Greater control over each beam can be achieved through the use of the [[fire-beam]] SEXP, allowing beams to target specific ships, subsystems and turrets.<br />
<br />
fred2_open adds an option to enable all beams by default in the Mission Statistics box.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Beam_weapon&diff=38409Beam weapon2012-04-28T05:21:31Z<p>Marcov: </p>
<hr />
<div>[[File:RScreen0053.png|480px|right|thumb|A ''Ravana''-class destroyer firing two of its frontal primary beam weapons upon exiting subspace]]<br />
<br />
'''Beam weapons''', or '''Beam cannons''', are large, powerful, ray-based lasers often used to slice through large warships. Most capital ships in FreeSpace 2 are equipped with beams.<br />
<br />
There are three main types; '''direct-fire''', '''slashing''', and '''anti-fighter'''.<br />
<br />
==History==<br />
During the [[Great War]] and the [[GTI Rebellion]], the [[Terrans]] and [[Vasudans]] encountered the [[Shivans]], a previously-unknown alien race. Both species took note of the technological capability of the Shivans, particularly the main guns of the [[SD Lucifer|Shivan command ship]], which they termed "Flux Cannons". The two races opted to replicate this technology after the end of the GTI Rebellion in late 2335. The result of this pursuit was the invention of the deadliest and most advanced weapons of war ever created by either race, called '''beam weapons'''. The first class of ship which was fully designed with beam weapons in mind may have been the [[GVCv Sobek|GVCv ''Sobek'']], which is said to have entered service shortly after the destruction of Vasuda Prime. Further advancements enabled engineers from both races to mount these weapons on older vessels never meant to accommodate them, as well as less powerful, more energy-efficient versions on smaller ships.<br />
<br />
Despite these advances, neither species was ultimately capable of matching up to the Shivans during the [[Second Shivan Incursion]] of 2367. Shivan beams were far more destructive than any Terran or Vasudan beam weapon ever made in terms of raw power and were capable of much faster refire rates at no visible cost to ship integrity. These advantages that Shivan beam weapons have over their Terran and Vasudan counterparts were demonstrated when the most powerful ship ever constructed by both races, the GTVA ''Colossus'', was obliterated almost completely by beam fire from a ''Sathanas'' juggernaut.<br />
<br />
==Capabilities==<br />
Sufficient [[reactor]] power is required in order to fire beam weapons. Therefore, they are never mounted on [[http://www.hard-light.net/wiki/index.php/Ship_Classes#Fighter_Units_and_Roles fighters or bombers]], which have reactors too small and too weak to support the power drain. For a time, the Vasudans' [[GVD Typhon|''Typhon''-class destroyers]] encountered similar issues, with most of them suffering from reactor overloads and system failures due to their power grid being unable to cope with the power needed to fire the beams equipped on them. The deployment of the [[GVD Hatshepsut|''Hatshepsut'']] line of destroyers would rectify this problem.<br />
<br />
In general, beam weapons are designed to be fired against ships larger than bomber-class, which are large enough to be targeted with. These are generally called "anti-capship beams" by players. However, smaller, lighter beam weapons exist that deliver less damage than anti-capship beams but are capable of targeting even fighters and bombers. These are recognised as "anti-fighter beams" in FreeSpace canon (dubbed "AAA beams" on occasion by players due to their names in the FreeSpace 2 table files). The advancement of the beam weapon in the Terran and Vasudan fleets is sufficient enough to enable the most powerful anti-capship beam from either race to easily cleave through most cruisers and corvettes in minutes and deal significant damage to destroyers, if not destroying them outright.<br />
<br />
Most Terran and Vasudan beam weapons are meant to be fired at a specified power output, dealing a consistent rate of damage assuming that the beam in question strikes its target for the entire duration of its lifetime. However, if the situation warrants, it is also possible to reduce power output to limit damage done, or increase power output beyond specified limits to increase damage rates; the latter comes with the risk of emitter and heat sink deterioration. Examples of ships that have taken either course of action are the GTC ''Rampart'' during a feint attack on two cruisers, and the GTVA ''Colossus'', during its engagement with SJ ''Sathanas 01''.<br />
<br />
==Beam types==<br />
There are four beam types included in retail FreeSpace 2, but only the first three were used throughout the course of the game.<br />
# ''Direct-fire beams'', which are essentially standard-issue point-and-shoot weapons. These beams can be directed to target specific sections of the target ship if necessary.<br />
# ''Slashing beams'', which strike their targets across a wide arc. Slashing beams have a marginally higher damage output and faster refire rate than direct-fire beams, but are much more inaccurate and may completely miss the target on occasion.<br />
# ''Anti-fighter beams'', which can target vessels smaller than cruiser-class. These beams are capable of firing more than once per pulse, but do very little damage as compared to direct-fire or slashing beams. Under the most dire circumstances, they may be used against larger vessels as well.<br />
# ''Targeting beams'', which are never used in the game and whose purpose remains unknown. One beam of this type (the [[Targeting Laser]]) is included in the FreeSpace 2 tables, but it appears to serve no purpose due to supplementary content being cut.<br />
<br />
Both the Terrans and Vasudans manufacture and make use of the first three beam types. The Shivans, however, utilise only the first and third types.<br />
<br />
==Notes for mission designers==<br />
:''See also: [[SEXP Reference]]''<br />
Newly-created missions in FRED2 do not enable beams by default. The easiest way to enable beam fire is to use the [[beam-free-all]] SEXP on every individual ship that needs to fire its beams. Greater control over each beam can be achieved through the use of the [[fire-beam]] SEXP, allowing beams to target specific ships, subsystems and turrets.<br />
<br />
fred2_open adds an option to enable all beams by default in the Mission Statistics box.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Beam_weapon&diff=38408Beam weapon2012-04-28T05:05:34Z<p>Marcov: </p>
<hr />
<div>[[File:RScreen0053.png|480px|right|thumb|A ''Ravana''-class destroyer firing two of its frontal primary beam weapons upon exiting subspace]]<br />
<br />
'''Beam weapons''', or '''Beam cannons''', are large, powerful, ray-based lasers often used to slice through large warships. Most capital ships in FreeSpace 2 are equipped with beams.<br />
<br />
There are three main types; '''direct-fire''', '''slashing''', and '''anti-fighter'''.<br />
<br />
==History==<br />
During the [[Great War]] and the [[GTI Rebellion]], the [[Terrans]] and [[Vasudans]] encountered the [[Shivans]], a previously-unknown alien race. Both species took note of the technological capability of the Shivans, particularly the main guns of the [[SD Lucifer|Shivan command ship]], which they termed "Flux Cannons". The two races opted to replicate this technology after the end of the GTI Rebellion in late 2335. The result of this pursuit was the invention of the deadliest and most advanced weapons of war ever created by either race, called '''beam weapons'''. The first class of ship which was fully designed with beam weapons in mind may have been the [[GVCv Sobek|GVCv ''Sobek'']], which is said to have entered service shortly after the destruction of Vasuda Prime. Further advancements enabled engineers from both races to mount these weapons on older vessels never meant to accommodate them, as well as less powerful, more energy-efficient versions on smaller ships.<br />
<br />
Despite these advances, neither species was ultimately capable of matching up to the Shivans during the [[Second Shivan Incursion]] of 2367. Shivan beams were far more destructive than any Terran or Vasudan beam weapon ever made in terms of raw power and were capable of much faster refire rates at no visible cost to ship integrity. These advantages that Shivan beam weapons have over their Terran and Vasudan counterparts were demonstrated when the most powerful ship ever constructed by both races, the GTVA ''Colossus'', was obliterated almost completely by beam fire from a ''Sathanas'' juggernaut.<br />
<br />
==Capabilities==<br />
Sufficient reactor power is required in order to fire beam weapons. Therefore, they are never mounted on fighters or bombers, which have reactors too small and too weak to support the power drain. For a time, the Vasudans' [[GVD Typhon|''Typhon''-class destroyers]] encountered similar issues, with most of them suffering from reactor overloads and system failures due to their power grid being unable to cope with the power needed to fire the beams equipped on them. The deployment of the [[GVD Hatshepsut|''Hatshepsut'']] line of destroyers would rectify this problem.<br />
<br />
In general, beam weapons are designed to be fired against ships larger than bomber-class, which are large enough to be targeted with. These are generally called "anti-capship beams" by players. However, smaller, lighter beam weapons exist that deliver less damage than anti-capship beams but are capable of targeting even fighters and bombers. These are recognised as "anti-fighter beams" in FreeSpace canon (dubbed "AAA beams" on occasion by players due to their names in the FreeSpace 2 table files). The advancement of the beam weapon in the Terran and Vasudan fleets is sufficient enough to enable the most powerful anti-capship beam from either race to easily cleave through most cruisers and corvettes in minutes and deal significant damage to destroyers, if not destroying them outright.<br />
<br />
Most Terran and Vasudan beam weapons are meant to be fired at a specified power output, dealing a consistent rate of damage assuming that the beam in question strikes its target for the entire duration of its lifetime. However, if the situation warrants, it is also possible to reduce power output to limit damage done, or increase power output beyond specified limits to increase damage rates; the latter comes with the risk of emitter and heat sink deterioration. Examples of ships that have taken either course of action are the GTC ''Rampart'' during a feint attack on two cruisers, and the GTVA ''Colossus'', during its engagement with SJ ''Sathanas 01''.<br />
<br />
==Beam types==<br />
There are four beam types included in retail FreeSpace 2, but only the first three were used throughout the course of the game.<br />
# ''Direct-fire beams'', which are essentially standard-issue point-and-shoot weapons. These beams can be directed to target specific sections of the target ship if necessary.<br />
# ''Slashing beams'', which strike their targets across a wide arc. Slashing beams have a marginally higher damage output and faster refire rate than direct-fire beams, but are much more inaccurate and may completely miss the target on occasion.<br />
# ''Anti-fighter beams'', which can target vessels smaller than cruiser-class. These beams are capable of firing more than once per pulse, but do very little damage as compared to direct-fire or slashing beams. Under the most dire circumstances, they may be used against larger vessels as well.<br />
# ''Targeting beams'', which are never used in the game and whose purpose remains unknown. One beam of this type (the [[Targeting Laser]]) is included in the FreeSpace 2 tables, but it appears to serve no purpose due to supplementary content being cut.<br />
<br />
Both the Terrans and Vasudans manufacture and make use of the first three beam types. The Shivans, however, utilise only the first and third types.<br />
<br />
==Notes for mission designers==<br />
:''See also: [[SEXP Reference]]''<br />
Newly-created missions in FRED2 do not enable beams by default. The easiest way to enable beam fire is to use the [[beam-free-all]] SEXP on every individual ship that needs to fire its beams. Greater control over each beam can be achieved through the use of the [[fire-beam]] SEXP, allowing beams to target specific ships, subsystems and turrets.<br />
<br />
fred2_open adds an option to enable all beams by default in the Mission Statistics box.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Beam_weapon&diff=38407Beam weapon2012-04-28T05:05:09Z<p>Marcov: </p>
<hr />
<div>[[File:RScreen0053.png|480px|right|thumb|A ''Ravana''-class destroyer firing two of its frontal primary beam weapons upon exiting subspace]]<br />
<br />
'''Beam weapons''', or '''Beam cannons''', are large, powerful ray-based lasers often used to slice through large warships. Most capital ships in FreeSpace 2 are equipped with beams.<br />
<br />
There are three main types; '''direct-fire''', '''slashing''', and '''anti-fighter'''.<br />
<br />
==History==<br />
During the [[Great War]] and the [[GTI Rebellion]], the [[Terrans]] and [[Vasudans]] encountered the [[Shivans]], a previously-unknown alien race. Both species took note of the technological capability of the Shivans, particularly the main guns of the [[SD Lucifer|Shivan command ship]], which they termed "Flux Cannons". The two races opted to replicate this technology after the end of the GTI Rebellion in late 2335. The result of this pursuit was the invention of the deadliest and most advanced weapons of war ever created by either race, called '''beam weapons'''. The first class of ship which was fully designed with beam weapons in mind may have been the [[GVCv Sobek|GVCv ''Sobek'']], which is said to have entered service shortly after the destruction of Vasuda Prime. Further advancements enabled engineers from both races to mount these weapons on older vessels never meant to accommodate them, as well as less powerful, more energy-efficient versions on smaller ships.<br />
<br />
Despite these advances, neither species was ultimately capable of matching up to the Shivans during the [[Second Shivan Incursion]] of 2367. Shivan beams were far more destructive than any Terran or Vasudan beam weapon ever made in terms of raw power and were capable of much faster refire rates at no visible cost to ship integrity. These advantages that Shivan beam weapons have over their Terran and Vasudan counterparts were demonstrated when the most powerful ship ever constructed by both races, the GTVA ''Colossus'', was obliterated almost completely by beam fire from a ''Sathanas'' juggernaut.<br />
<br />
==Capabilities==<br />
Sufficient reactor power is required in order to fire beam weapons. Therefore, they are never mounted on fighters or bombers, which have reactors too small and too weak to support the power drain. For a time, the Vasudans' [[GVD Typhon|''Typhon''-class destroyers]] encountered similar issues, with most of them suffering from reactor overloads and system failures due to their power grid being unable to cope with the power needed to fire the beams equipped on them. The deployment of the [[GVD Hatshepsut|''Hatshepsut'']] line of destroyers would rectify this problem.<br />
<br />
In general, beam weapons are designed to be fired against ships larger than bomber-class, which are large enough to be targeted with. These are generally called "anti-capship beams" by players. However, smaller, lighter beam weapons exist that deliver less damage than anti-capship beams but are capable of targeting even fighters and bombers. These are recognised as "anti-fighter beams" in FreeSpace canon (dubbed "AAA beams" on occasion by players due to their names in the FreeSpace 2 table files). The advancement of the beam weapon in the Terran and Vasudan fleets is sufficient enough to enable the most powerful anti-capship beam from either race to easily cleave through most cruisers and corvettes in minutes and deal significant damage to destroyers, if not destroying them outright.<br />
<br />
Most Terran and Vasudan beam weapons are meant to be fired at a specified power output, dealing a consistent rate of damage assuming that the beam in question strikes its target for the entire duration of its lifetime. However, if the situation warrants, it is also possible to reduce power output to limit damage done, or increase power output beyond specified limits to increase damage rates; the latter comes with the risk of emitter and heat sink deterioration. Examples of ships that have taken either course of action are the GTC ''Rampart'' during a feint attack on two cruisers, and the GTVA ''Colossus'', during its engagement with SJ ''Sathanas 01''.<br />
<br />
==Beam types==<br />
There are four beam types included in retail FreeSpace 2, but only the first three were used throughout the course of the game.<br />
# ''Direct-fire beams'', which are essentially standard-issue point-and-shoot weapons. These beams can be directed to target specific sections of the target ship if necessary.<br />
# ''Slashing beams'', which strike their targets across a wide arc. Slashing beams have a marginally higher damage output and faster refire rate than direct-fire beams, but are much more inaccurate and may completely miss the target on occasion.<br />
# ''Anti-fighter beams'', which can target vessels smaller than cruiser-class. These beams are capable of firing more than once per pulse, but do very little damage as compared to direct-fire or slashing beams. Under the most dire circumstances, they may be used against larger vessels as well.<br />
# ''Targeting beams'', which are never used in the game and whose purpose remains unknown. One beam of this type (the [[Targeting Laser]]) is included in the FreeSpace 2 tables, but it appears to serve no purpose due to supplementary content being cut.<br />
<br />
Both the Terrans and Vasudans manufacture and make use of the first three beam types. The Shivans, however, utilise only the first and third types.<br />
<br />
==Notes for mission designers==<br />
:''See also: [[SEXP Reference]]''<br />
Newly-created missions in FRED2 do not enable beams by default. The easiest way to enable beam fire is to use the [[beam-free-all]] SEXP on every individual ship that needs to fire its beams. Greater control over each beam can be achieved through the use of the [[fire-beam]] SEXP, allowing beams to target specific ships, subsystems and turrets.<br />
<br />
fred2_open adds an option to enable all beams by default in the Mission Statistics box.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Beam_weapon&diff=38406Beam weapon2012-04-28T05:04:56Z<p>Marcov: </p>
<hr />
<div>[[File:RScreen0053.png|480px|right|thumb|A ''Ravana''-class destroyer firing two of its frontal primary beam weapons upon exiting subspace]]<br />
<br />
'''Beam weapons''', or '''Beam Cannons''', are large, powerful ray-based lasers often used to slice through large warships. Most capital ships in FreeSpace 2 are equipped with beams.<br />
<br />
There are three main types; '''direct-fire''', '''slashing''', and '''anti-fighter'''.<br />
<br />
==History==<br />
During the [[Great War]] and the [[GTI Rebellion]], the [[Terrans]] and [[Vasudans]] encountered the [[Shivans]], a previously-unknown alien race. Both species took note of the technological capability of the Shivans, particularly the main guns of the [[SD Lucifer|Shivan command ship]], which they termed "Flux Cannons". The two races opted to replicate this technology after the end of the GTI Rebellion in late 2335. The result of this pursuit was the invention of the deadliest and most advanced weapons of war ever created by either race, called '''beam weapons'''. The first class of ship which was fully designed with beam weapons in mind may have been the [[GVCv Sobek|GVCv ''Sobek'']], which is said to have entered service shortly after the destruction of Vasuda Prime. Further advancements enabled engineers from both races to mount these weapons on older vessels never meant to accommodate them, as well as less powerful, more energy-efficient versions on smaller ships.<br />
<br />
Despite these advances, neither species was ultimately capable of matching up to the Shivans during the [[Second Shivan Incursion]] of 2367. Shivan beams were far more destructive than any Terran or Vasudan beam weapon ever made in terms of raw power and were capable of much faster refire rates at no visible cost to ship integrity. These advantages that Shivan beam weapons have over their Terran and Vasudan counterparts were demonstrated when the most powerful ship ever constructed by both races, the GTVA ''Colossus'', was obliterated almost completely by beam fire from a ''Sathanas'' juggernaut.<br />
<br />
==Capabilities==<br />
Sufficient reactor power is required in order to fire beam weapons. Therefore, they are never mounted on fighters or bombers, which have reactors too small and too weak to support the power drain. For a time, the Vasudans' [[GVD Typhon|''Typhon''-class destroyers]] encountered similar issues, with most of them suffering from reactor overloads and system failures due to their power grid being unable to cope with the power needed to fire the beams equipped on them. The deployment of the [[GVD Hatshepsut|''Hatshepsut'']] line of destroyers would rectify this problem.<br />
<br />
In general, beam weapons are designed to be fired against ships larger than bomber-class, which are large enough to be targeted with. These are generally called "anti-capship beams" by players. However, smaller, lighter beam weapons exist that deliver less damage than anti-capship beams but are capable of targeting even fighters and bombers. These are recognised as "anti-fighter beams" in FreeSpace canon (dubbed "AAA beams" on occasion by players due to their names in the FreeSpace 2 table files). The advancement of the beam weapon in the Terran and Vasudan fleets is sufficient enough to enable the most powerful anti-capship beam from either race to easily cleave through most cruisers and corvettes in minutes and deal significant damage to destroyers, if not destroying them outright.<br />
<br />
Most Terran and Vasudan beam weapons are meant to be fired at a specified power output, dealing a consistent rate of damage assuming that the beam in question strikes its target for the entire duration of its lifetime. However, if the situation warrants, it is also possible to reduce power output to limit damage done, or increase power output beyond specified limits to increase damage rates; the latter comes with the risk of emitter and heat sink deterioration. Examples of ships that have taken either course of action are the GTC ''Rampart'' during a feint attack on two cruisers, and the GTVA ''Colossus'', during its engagement with SJ ''Sathanas 01''.<br />
<br />
==Beam types==<br />
There are four beam types included in retail FreeSpace 2, but only the first three were used throughout the course of the game.<br />
# ''Direct-fire beams'', which are essentially standard-issue point-and-shoot weapons. These beams can be directed to target specific sections of the target ship if necessary.<br />
# ''Slashing beams'', which strike their targets across a wide arc. Slashing beams have a marginally higher damage output and faster refire rate than direct-fire beams, but are much more inaccurate and may completely miss the target on occasion.<br />
# ''Anti-fighter beams'', which can target vessels smaller than cruiser-class. These beams are capable of firing more than once per pulse, but do very little damage as compared to direct-fire or slashing beams. Under the most dire circumstances, they may be used against larger vessels as well.<br />
# ''Targeting beams'', which are never used in the game and whose purpose remains unknown. One beam of this type (the [[Targeting Laser]]) is included in the FreeSpace 2 tables, but it appears to serve no purpose due to supplementary content being cut.<br />
<br />
Both the Terrans and Vasudans manufacture and make use of the first three beam types. The Shivans, however, utilise only the first and third types.<br />
<br />
==Notes for mission designers==<br />
:''See also: [[SEXP Reference]]''<br />
Newly-created missions in FRED2 do not enable beams by default. The easiest way to enable beam fire is to use the [[beam-free-all]] SEXP on every individual ship that needs to fire its beams. Greater control over each beam can be achieved through the use of the [[fire-beam]] SEXP, allowing beams to target specific ships, subsystems and turrets.<br />
<br />
fred2_open adds an option to enable all beams by default in the Mission Statistics box.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714599th Skulls2011-10-15T05:48:45Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason...]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714499th Skulls2011-10-15T05:48:05Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason|...Love the Treason]], [[...But Hate the Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714399th Skulls2011-10-15T05:47:26Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason|...Love the Treason]], [[...But Hate The Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714299th Skulls2011-10-15T05:46:35Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons#Lieutenant Commander Christopher Snipes|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[Love the Treason|...Love the Treason]], [[But Hate the Traitor|...But Hate The Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714199th Skulls2011-10-15T05:43:59Z<p>Marcov: Just an improvement - the Mission Specs clearly state that Alpha 1 flies with the Skulls during "As Lightning Fall" and "Into the Lion's Den".</p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the 99th is home to some of the top pilots in the GTVA, including [[Famous Persons|Christopher Snipes]], Xinny, Zero, and [[Alpha 1]]. The Skulls participated in many high-risk SOC Missions, such as in [[...Love the Treason]], [[...But Hate The Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. Alpha 1 led a strike wing of SOC pilots in the [[As Lightning Fall| rescue of Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls in ''Into the Lion's Den'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=99th_Skulls&diff=3714099th Skulls2011-10-15T05:36:50Z<p>Marcov: </p>
<hr />
<div>{{squadron}}<br />
<br />
[[Image:SquadPIRATE3.PNG|right]]<br />
<br />
==General info==<br />
<b>Squadron type:</b> Elite Space Superiority <br><br />
<b>Craft used the most:</b> [[GTF Erinyes|GTF ''Erinyes'']] <br><br />
<b>Stationed on-board:</b> Unknown <br><br />
<b>Squadron leader:</b> Lt. Commander Snipes (?) <br><br />
<br />
==Actions==<br />
The 99th Skulls appeared solely in two missions during the ''FreeSpace 2'' campaign. From what there can be gathered, the 99th Skulls were an elite squadron, probably used by the [[Special Operations Command|SOC]]. They were among the first squadrons to use the [[GTF Erinyes|GTF ''Erinyes'']] and the [[GTW UD-8 Kayser|UD-8 Kayser]] primary weapons.<br />
<br />
Quite certainly one of the best squadrons in the GTVA, the Skulls participated in many high-risk SOC Missions, such as in [[...Love the Treason]], [[...But Hate The Traitor]], [[As Lightning Fall]], and [[Into the Lion's Den]]. [[Alpha 1]] led a strike wing of SOC pilots in the [[AsLightningFall operation rescuing Snipes in the NTT Grall]]. <br />
<br />
It is uncertain whether or not Snipes is the 99th Skulls' squadron commander, although the fact that he led the wing of 99th Skulls i''As Lightning Fall'' suggests evidence for this.<br />
<br />
==Misc notes==<br />
The craft of this squadron were designated as Skull Alpha and Skull Beta in one of the ''FreeSpace 2'' missions.<br />
<br />
[[Category:Squadrons]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Command&diff=34741Command2011-05-20T12:09:59Z<p>Marcov: "Have gained notoriety within the community"? Elaborated it.</p>
<hr />
<div>[[Image:Head-CM1.gif|thumb|160px|Terran Command from [[FreeSpace 1]].]]<br />
[[Image:Head-CM2.gif|thumb|160px|Allied Command from [[FreeSpace 2]].]]<br />
In [[FreeSpace 2]], '''Allied Command''' (most frequently referred to simply as '''Command''') oversees operations conducted by the [[Galactic Terran-Vasudan Alliance]] and gives orders to pilots and other combat craft that participate in them. '''Terran Command''' (also referred to simply as Command) fulfilled the same role in [[FreeSpace 1]].<br />
<br />
In both FreeSpace games, Command seems to be an organization of command personnel. This implies that the individual who personally instructs allied pilots is merely a communications officer, and not Command itself. However, the identity of this officer in not made clear in either game. In FreeSpace 1, he is a human of Caucasian ethnicity. His head animation is Head CM-1, which is the only [[head animation]] used for larger ships in the first game. In FreeSpace 2, the officer has head animation Head-CM2, who is a dark-skinned human, presumably of African ethnicity.<br />
<br />
Over the course of the two games, the player character gets reassigned to numerous new flagships, but these reassignments don't affect how the Allied Command officer is portrayed. Even when the player is assigned to the [[GVD Psamtik|GVD ''Psamtik'']], Command remains a Terran.<br />
<br />
Command's characteristic phrases (especially "Incoming jump signature! Hostile configuration!") as well as his perceived ineptness in directing missions have made many community members repute him as a somewhat impersonal authority figure.<br />
<br />
==See Also==<br />
*[[Vasudan Tactical Command]]<br />
<br />
[[Category:FreeSpace Universe]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Fly_as_a_capital_ship&diff=34740Fly as a capital ship2011-05-20T12:04:00Z<p>Marcov: </p>
<hr />
<div>There is a trick that FREDders can do while FREDding a mission that can allow them to pilot ships that they normally can't. This includes freighters, cruisers, capital ships, and even the ''[[GTVA Colossus|Colossus]]''.<br />
<br />
For starters, suppose that you have 2 ships in a mission. [[Alpha 1]] is in a [[GTF Loki|Loki]], while Beta 1 happens to be an [[GTD Orion|Orion]]. Save the game, start FreeSpace 2, go to the mission simulator, and select the mission. When you're there, go to ship selection and there will be 2 icons, Alpha 1 (you) is a Loki, and Beta 1 is an Orion. Switch those 2 ships and start the mission. Congratulations, you're flying an Orion now. <br />
<br />
The other way is to table hack to make them drivable; put the "player ship" flag in the flags section of the warship you want to make available.<br />
<br />
Although you are tricking the game to fly as a capital ship while you should be flying as a fighter, the game will treat you as a capital ship in all respects. This means that you will be targetted by anti-capital ship [[Beam weapon|beams]], bombers will launch [[GTM Cyclops|Cyclops torpedoes]] at you, and wings protecting you will make normal cruiser guarding patrol patterns. <br />
<br />
<br />
== What are the problems with such missions? ==<br />
*While it may seem cool to control a massive ship, keep in mind that you will be going slow, turning is horrible, and you have no primary gun mounts. Although you have dozens of turrets to do the work for you, having AI-controlled turrets doing all the shooting for you can really get you bored very fast. <br />
<br />
*If you're using FSO and send beam cannons unlocked by default in the Mission SPEC, all beam cannons will fire normally, except for yours. To make your beam cannons fire normally, you have to set a [[beam-free-all]] SEXP on yourself.<br />
<br />
*Warping out while flying a capital ship is quite different from NPC capital ships warping out. Instead of shooting out forward at incredible speeds, you will be going at a slow pace, and the subspace vortex will take a minute to show up, as will take another minute for you to enter it. Mission designers should keep this in mind when requiring the player to flee a supernova in a capital ship. The bigger the ship, the longer it takes to warp out.<br />
<br />
*As your subsystems are damaged, the damage list will grow until it obscures most of the screen. <br />
<br />
*Every time you get hit, even with the most insignificant primary fire, your screen will irritatingly flash red. In 3.6.13 builds, the ships.tbl flag "no pain flash" has been added to work around this.<br />
<br />
*You can quite easily commit friendly fire. Your flak and beam guns will frequently hit all fighters that are tied up in dogfights, and your AI allies will start disciplining you for attacking them. These turrets cannot be disabled. Eventually, you be labeled as a backstabber and fail the mission.<br />
<br />
*Switching the gauges between shields, engines, and weapons can cause some unusual effects to occur. The shield gauge will work as normal and the weapons gauge won't do anything (since none of the capitals have primary weapons; however, note that weapon energy is FREDded to control turret rate of fire in missions like [[The Blade Itself]]), but messing around with the engine gauge can actually cause some ships to slow down dramatically. For example: a maxed-out engine gauge will cause a Deimos to rank out to 60m/s, but a Hecate will reduce from a normal 15m/s to only 8m/s. This behaviour depends on the ships' listed Max Overclock speed value in [[ships.tbl]].<br />
<br />
== Are there solutions to these problems? ==<br />
*The list of damaged subsystems can be prevented by ship-subsys-guardian-threshold-ing subsystems not intended to be damaged. <br />
<br />
*A new ship flag can remove the "pain flash" that occurs every time your ship is hit. <br />
<br />
*Turret control scripts exist, allowing the player to designate targets, rather than leaving it to the AI, or even take control of turrets individually and aim. <br />
<br />
*Traitor detection can be disabled easily in the mission-specs if necessary. <br />
<br />
*Additional elements can be added to provide the player with more things do to, such as managing AI fighter wings, and utilizing FRED-created abilities for the capital ship.<br />
<br />
== Conclusion ==<br />
If done well, a capital-ship flying mission can be as, if not more, entertaining than a well-made fighter-based mission. Witness the side-story single-mission campaign [[The Blade Itself]] from [[Blue Planet: War in Heaven]]. However, this should probably not be attempted by novices, as the process of building these missions is rather involved, requiring table-side edits, a solid understanding of FRED, and basic knowledge of scripting to effectively create a stimulating mission out of.<br />
<br />
[[Category:FRED]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Fly_as_a_capital_ship&diff=34739Fly as a capital ship2011-05-20T12:02:42Z<p>Marcov: </p>
<hr />
<div>There is a trick that FREDders can do while FREDding a mission that can allow them to pilot ships that they normally can't. This includes freighters, cruisers, capital ships, and even the ''[[GTVA Colossus|Colossus]]''.<br />
<br />
For starters, suppose that you have 2 ships in a mission. [[Alpha 1]] is in a [[GTF Loki|Loki]], while Beta 1 happens to be an [[GTD Orion|Orion]]. Save the game, start FreeSpace 2, go to the mission simulator, and select the mission. When you're there, go to ship selection and there will be 2 icons, Alpha 1 (you) is a Loki, and Beta 1 is an Orion. Switch those 2 ships and start the mission. Congratulations, you're flying an Orion now. <br />
<br />
The other way is to table hack to make them drivable; put the "player ship" flag in the flags section of the warship you want to make available.<br />
<br />
Although you are tricking the game to fly as a capital ship while you should be flying as a fighter, the game will treat you as a capital ship in all respects. This means that you will be targetted by anti-capital ship [[Beam Weapon|beams]], bombers will launch [[GTM Cyclops|Cyclops torpedoes]] at you, and wings protecting you will make normal cruiser guarding patrol patterns. <br />
<br />
<br />
== What are the problems with such missions? ==<br />
*While it may seem cool to control a massive ship, keep in mind that you will be going slow, turning is horrible, and you have no primary gun mounts. Although you have dozens of turrets to do the work for you, having AI-controlled turrets doing all the shooting for you can really get you bored very fast. <br />
<br />
*If you're using FSO and send beam cannons unlocked by default in the Mission SPEC, all beam cannons will fire normally, except for yours. To make your beam cannons fire normally, you have to set a [[beam-free-all]] SEXP on yourself.<br />
<br />
*Warping out while flying a capital ship is quite different from NPC capital ships warping out. Instead of shooting out forward at incredible speeds, you will be going at a slow pace, and the subspace vortex will take a minute to show up, as will take another minute for you to enter it. Mission designers should keep this in mind when requiring the player to flee a supernova in a capital ship. The bigger the ship, the longer it takes to warp out.<br />
<br />
*As your subsystems are damaged, the damage list will grow until it obscures most of the screen. <br />
<br />
*Every time you get hit, even with the most insignificant primary fire, your screen will irritatingly flash red. In 3.6.13 builds, the ships.tbl flag "no pain flash" has been added to work around this.<br />
<br />
*You can quite easily commit friendly fire. Your flak and beam guns will frequently hit all fighters that are tied up in dogfights, and your AI allies will start disciplining you for attacking them. These turrets cannot be disabled. Eventually, you be labeled as a backstabber and fail the mission.<br />
<br />
*Switching the gauges between shields, engines, and weapons can cause some unusual effects to occur. The shield gauge will work as normal and the weapons gauge won't do anything (since none of the capitals have primary weapons; however, note that weapon energy is FREDded to control turret rate of fire in missions like [[The Blade Itself]]), but messing around with the engine gauge can actually cause some ships to slow down dramatically. For example: a maxed-out engine gauge will cause a Deimos to rank out to 60m/s, but a Hecate will reduce from a normal 15m/s to only 8m/s. This behaviour depends on the ships' listed Max Overclock speed value in [[ships.tbl]].<br />
<br />
== Are there solutions to these problems? ==<br />
*The list of damaged subsystems can be prevented by ship-subsys-guardian-threshold-ing subsystems not intended to be damaged. <br />
<br />
*A new ship flag can remove the "pain flash" that occurs every time your ship is hit. <br />
<br />
*Turret control scripts exist, allowing the player to designate targets, rather than leaving it to the AI, or even take control of turrets individually and aim. <br />
<br />
*Traitor detection can be disabled easily in the mission-specs if necessary. <br />
<br />
*Additional elements can be added to provide the player with more things do to, such as managing AI fighter wings, and utilizing FRED-created abilities for the capital ship.<br />
<br />
== Conclusion ==<br />
If done well, a capital-ship flying mission can be as, if not more, entertaining than a well-made fighter-based mission. Witness the side-story single-mission campaign [[The Blade Itself]] from [[Blue Planet: War in Heaven]]. However, this should probably not be attempted by novices, as the process of building these missions is rather involved, requiring table-side edits, a solid understanding of FRED, and basic knowledge of scripting to effectively create a stimulating mission out of.<br />
<br />
[[Category:FRED]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Fly_as_a_capital_ship&diff=34738Fly as a capital ship2011-05-20T12:02:04Z<p>Marcov: </p>
<hr />
<div>There is a trick that FREDders can do while FREDding a mission that can allow them to pilot ships that they normally can't. This includes freighters, cruisers, capital ships, and even the ''[[GTVA Colossus|Colossus]]''.<br />
<br />
For starters, suppose that you have 2 ships in a mission. [[Alpha 1]] is in a [[GTF Loki|Loki]], while Beta 1 happens to be an [[GTD Orion|Orion]]. Save the game, start FreeSpace 2, go to the mission simulator, and select the mission. When you're there, go to ship selection and there will be 2 icons, Alpha 1 (you) is a Loki, and Beta 1 is an Orion. Switch those 2 ships and start the mission. Congratulations, you're flying an Orion now. <br />
<br />
The other way is to table hack to make them drivable; put the [[http://www.hard-light.net/wiki/index.php/Ships.tbl#.22player_ship.22|"player ship" flag]] in the flags section of the warship you want to make available.<br />
<br />
Although you are tricking the game to fly as a capital ship while you should be flying as a fighter, the game will treat you as a capital ship in all respects. This means that you will be targetted by anti-capital ship [[Beam Weapon|beams]], bombers will launch [[GTM Cyclops|Cyclops torpedoes]] at you, and wings protecting you will make normal cruiser guarding patrol patterns. <br />
<br />
<br />
== What are the problems with such missions? ==<br />
*While it may seem cool to control a massive ship, keep in mind that you will be going slow, turning is horrible, and you have no primary gun mounts. Although you have dozens of turrets to do the work for you, having AI-controlled turrets doing all the shooting for you can really get you bored very fast. <br />
<br />
*If you're using FSO and send beam cannons unlocked by default in the Mission SPEC, all beam cannons will fire normally, except for yours. To make your beam cannons fire normally, you have to set a [[beam-free-all]] SEXP on yourself.<br />
<br />
*Warping out while flying a capital ship is quite different from NPC capital ships warping out. Instead of shooting out forward at incredible speeds, you will be going at a slow pace, and the subspace vortex will take a minute to show up, as will take another minute for you to enter it. Mission designers should keep this in mind when requiring the player to flee a supernova in a capital ship. The bigger the ship, the longer it takes to warp out.<br />
<br />
*As your subsystems are damaged, the damage list will grow until it obscures most of the screen. <br />
<br />
*Every time you get hit, even with the most insignificant primary fire, your screen will irritatingly flash red. In 3.6.13 builds, the ships.tbl flag "no pain flash" has been added to work around this.<br />
<br />
*You can quite easily commit friendly fire. Your flak and beam guns will frequently hit all fighters that are tied up in dogfights, and your AI allies will start disciplining you for attacking them. These turrets cannot be disabled. Eventually, you be labeled as a backstabber and fail the mission.<br />
<br />
*Switching the gauges between shields, engines, and weapons can cause some unusual effects to occur. The shield gauge will work as normal and the weapons gauge won't do anything (since none of the capitals have primary weapons; however, note that weapon energy is FREDded to control turret rate of fire in missions like [[The Blade Itself]]), but messing around with the engine gauge can actually cause some ships to slow down dramatically. For example: a maxed-out engine gauge will cause a Deimos to rank out to 60m/s, but a Hecate will reduce from a normal 15m/s to only 8m/s. This behaviour depends on the ships' listed Max Overclock speed value in [[ships.tbl]].<br />
<br />
== Are there solutions to these problems? ==<br />
*The list of damaged subsystems can be prevented by ship-subsys-guardian-threshold-ing subsystems not intended to be damaged. <br />
<br />
*A new ship flag can remove the "pain flash" that occurs every time your ship is hit. <br />
<br />
*Turret control scripts exist, allowing the player to designate targets, rather than leaving it to the AI, or even take control of turrets individually and aim. <br />
<br />
*Traitor detection can be disabled easily in the mission-specs if necessary. <br />
<br />
*Additional elements can be added to provide the player with more things do to, such as managing AI fighter wings, and utilizing FRED-created abilities for the capital ship.<br />
<br />
== Conclusion ==<br />
If done well, a capital-ship flying mission can be as, if not more, entertaining than a well-made fighter-based mission. Witness the side-story single-mission campaign [[The Blade Itself]] from [[Blue Planet: War in Heaven]]. However, this should probably not be attempted by novices, as the process of building these missions is rather involved, requiring table-side edits, a solid understanding of FRED, and basic knowledge of scripting to effectively create a stimulating mission out of.<br />
<br />
[[Category:FRED]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Fly_as_a_capital_ship&diff=34737Fly as a capital ship2011-05-20T12:01:01Z<p>Marcov: Fixed spelling error (missiion --> mission), placed some links, made some things more grammatically correct.</p>
<hr />
<div>There is a trick that FREDders can do while FREDding a mission that can allow them to pilot ships that they normally can't. This includes freighters, cruisers, capital ships, and even the ''[[GTVA Colossus|Colossus]]''.<br />
<br />
For starters, suppose that you have 2 ships in a mission. [[Alpha 1]] is in a [[GTF Loki|Loki]], while Beta 1 happens to be an [[GTD Orion|Orion]]. Save the game, start FreeSpace 2, go to the mission simulator, and select the mission. When you're there, go to ship selection and there will be 2 icons, Alpha 1 (you) is a Loki, and Beta 1 is an Orion. Switch those 2 ships and start the mission. Congratulations, you're flying an Orion now. <br />
<br />
The other way is to table hack to make them drivable; put the [[http://www.hard-light.net/wiki/index.php/Ships.tbl#.22player_ship.22|"player_ship" flag]] in the flags section of the warship you want to make available.<br />
<br />
Although you are tricking the game to fly as a capital ship while you should be flying as a fighter, the game will treat you as a capital ship in all respects. This means that you will be targetted by anti-capital ship [[Beam Weapon|beams]], bombers will launch [[GTM Cyclops|Cyclops torpedoes]] at you, and wings protecting you will make normal cruiser guarding patrol patterns. <br />
<br />
<br />
== What are the problems with such missions? ==<br />
*While it may seem cool to control a massive ship, keep in mind that you will be going slow, turning is horrible, and you have no primary gun mounts. Although you have dozens of turrets to do the work for you, having AI-controlled turrets doing all the shooting for you can really get you bored very fast. <br />
<br />
*If you're using FSO and send beam cannons unlocked by default in the Mission SPEC, all beam cannons will fire normally, except for yours. To make your beam cannons fire normally, you have to set a [[beam-free-all]] SEXP on yourself.<br />
<br />
*Warping out while flying a capital ship is quite different from NPC capital ships warping out. Instead of shooting out forward at incredible speeds, you will be going at a slow pace, and the subspace vortex will take a minute to show up, as will take another minute for you to enter it. Mission designers should keep this in mind when requiring the player to flee a supernova in a capital ship. The bigger the ship, the longer it takes to warp out.<br />
<br />
*As your subsystems are damaged, the damage list will grow until it obscures most of the screen. <br />
<br />
*Every time you get hit, even with the most insignificant primary fire, your screen will irritatingly flash red. In 3.6.13 builds, the ships.tbl flag "no pain flash" has been added to work around this.<br />
<br />
*You can quite easily commit friendly fire. Your flak and beam guns will frequently hit all fighters that are tied up in dogfights, and your AI allies will start disciplining you for attacking them. These turrets cannot be disabled. Eventually, you be labeled as a backstabber and fail the mission.<br />
<br />
*Switching the gauges between shields, engines, and weapons can cause some unusual effects to occur. The shield gauge will work as normal and the weapons gauge won't do anything (since none of the capitals have primary weapons; however, note that weapon energy is FREDded to control turret rate of fire in missions like [[The Blade Itself]]), but messing around with the engine gauge can actually cause some ships to slow down dramatically. For example: a maxed-out engine gauge will cause a Deimos to rank out to 60m/s, but a Hecate will reduce from a normal 15m/s to only 8m/s. This behaviour depends on the ships' listed Max Overclock speed value in [[ships.tbl]].<br />
<br />
== Are there solutions to these problems? ==<br />
*The list of damaged subsystems can be prevented by ship-subsys-guardian-threshold-ing subsystems not intended to be damaged. <br />
<br />
*A new ship flag can remove the "pain flash" that occurs every time your ship is hit. <br />
<br />
*Turret control scripts exist, allowing the player to designate targets, rather than leaving it to the AI, or even take control of turrets individually and aim. <br />
<br />
*Traitor detection can be disabled easily in the mission-specs if necessary. <br />
<br />
*Additional elements can be added to provide the player with more things do to, such as managing AI fighter wings, and utilizing FRED-created abilities for the capital ship.<br />
<br />
== Conclusion ==<br />
If done well, a capital-ship flying mission can be as, if not more, entertaining than a well-made fighter-based mission. Witness the side-story single-mission campaign [[The Blade Itself]] from [[Blue Planet: War in Heaven]]. However, this should probably not be attempted by novices, as the process of building these missions is rather involved, requiring table-side edits, a solid understanding of FRED, and basic knowledge of scripting to effectively create a stimulating mission out of.<br />
<br />
[[Category:FRED]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Command&diff=34684Command2011-05-15T09:51:04Z<p>Marcov: Command's a "they", folks. You're wrong</p>
<hr />
<div>'''Allied Command''' (most frequently referred to only as '''Command''') oversees operations conducted by the [[Galactic Terran-Vasudan Alliance]] and gives orders to pilots and miscellaneous combat craft that participate in them.<br />
<br />
In both FreeSpace games, Allied Command seems to be an organization of command personnel, as it is frequently referred to as a "they", instead of a "he". This implies that the "Command" who personally instructs Allied pilots is merely a Communications officer, and not Command itself. However, the identity of this officer in neither FreeSpace games is known. In ''[[FreeSpace 1|Conflict: FreeSpace &ndash; The Great War]]'', he is a human of Caucasian etnicity. His head animation is Head CM-1, which is the only [[head animation]] used for larger ships in the first game. In ''[[FreeSpace 2]]'', the officer has head animation #2, who is a dark-skinned human, presumably of African ethnicity.<br />
<br />
Over the course of the two games, the player character gets reassigned to numerous new flagships, but these reassignments don't affect how the Allied Command officer is portrayed. Even when the player is assigned to the [[GVD Psamtik|GVD ''Psamtik'']], Command remains a Terran.<br />
<br />
[[Category:FreeSpace Universe]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Command&diff=34683Command2011-05-15T09:48:55Z<p>Marcov: </p>
<hr />
<div>'''Allied Command''' (most frequently referred to only as '''Command''') oversees operations conducted by the [[Galactic Terran-Vasudan Alliance]] and gives orders to pilots and miscellaneous combat craft that participate in them.<br />
<br />
In both FreeSpace games, Allied Command seems to be an organization of command personnel, as it is frequently referred to as a "they", instead of a "he". This implies that the "Command" who personally instructs Allied pilots is merely a Communications officer, and not Command itself. However, the identity of this officer in neither FreeSpace games is known. In ''[[FreeSpace 1|Conflict: FreeSpace &ndash; The Great War]]'', he is a human of Caucasian etnicity. His head animation is Head CM-1, which is the only [[head animation]] used for larger ships in the first game. In ''[[FreeSpace 2]]'', the officer has head animation #2, who is a dark-skinned human.<br />
<br />
Over the course of the two games, the player character gets reassigned to numerous new flagships, but these reassignments don't affect how the Allied Command officer is portrayed. Even when the player is assigned to the [[GVD Psamtik|GVD ''Psamtik'']], Command remains a Terran.<br />
<br />
[[Category:FreeSpace Universe]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Star_system&diff=34649Star system2011-05-13T12:37:54Z<p>Marcov: </p>
<hr />
<div>'''Star Systems''', or shortly termed "'''systems'''", are vast regions of space, supported by very large celestial objects known as '''stars'''. Occasionally, star systems hold one or more planets, supported by the intense gravitational pull of the system's star.<br />
<br />
Prior to the development of [[Subspace]] travel, space-faring species such as the [[Terran]]s and [[Vasudan]]s were only bound to within their respective star systems; the Terrans were bound to [[Sol]], and the Vasudans, to [[Vasuda]]. The birthplace of the [[Shivan]]s is unknown; whether they even originated from a star system is open to wide debate. A mysterious, ancient race, termed only as the "[[Ancients]]", allegedly originated in a star system "close to Vasuda".<br />
<br />
With the deployment of Subspace travel, various races were able to journey to other systems, places which have never been reached before. Without subspace, it would be nearly impossible to travel to other systems, as such distances are measured in several lightyears. The Terrans, Vasudans, and Ancients exploited multiple star systems, colonizing and governing them. Some systems had planets, which contained valuable resources, such as food and minerals, as well as shelter by constructing cities and villages; systems may also be used as a base of military operations where a military installation could be constructed. This made most star systems extremely valuable; some, however, have less use, such as [[Gamma Draconis]], with no usable planets or moons.<br />
<br />
A star system usually has at least one point wherein intersystem subspace travel is possible, known as [[jump node]]s. Jump nodes are highlighted in green in a ship's HUD. It is unknown as to how the Terrans or Vasudans discovered jump nodes.<br />
<br />
Star systems also allow intrasystem subspace travel, wherein any ship equipped with subspace drives can jump to one point of the system to another in the presence of the nearby star's gravitational pull.<br />
<br />
At one point during the Second Shivan Incursion, a notable star system, [[Capella]], was utterly destroyed when its star went supernova resulting from mysterious Subspace tearing weaponry on the [[SJ Sathanas]] Juggernauts; exactly why the Shivans did this is unknown, but the capability to destroy entire stars has shocked both Terrans and Vasudans.<br />
<br />
Though the [[Nebula System]] does not have any stars, it is still termed as a "system".</div>Marcovhttps://wiki.hard-light.net/index.php?title=Star_system&diff=34648Star system2011-05-13T12:29:31Z<p>Marcov: </p>
<hr />
<div>'''Star Systems''', or shortly termed "'''systems'''", are vast regions of space, supported by very large celestial objects known as '''stars'''. Occasionally, star systems hold one or more planets, supported by the intense gravitational pull of the system's star.<br />
<br />
Prior to the development of [[Subspace]] travel, space-faring species such as the [[Terran]]s and [[Vasudan]]s were only bound to within their respective star systems; the Terrans were bound to [[Sol]], and the Vasudans, to [[Vasuda]]. The birthplace of the [[Shivan]]s is unknown; whether they even originated from a star system is open to wide debate. A mysterious, ancient race, termed only as the "[[Ancients]]", allegedly originated in a star system "close to Vasuda".<br />
<br />
With the deployment of Subspace travel, various races were able to journey to other systems, places which have never been reached before. Without subspace, it would be nearly impossible to travel to other systems, as such distances are measured in several lightyears. The Terrans, Vasudans, and Ancients exploited multiple star systems, colonizing and governing them. Some systems had planets, which contained valuable resources, such as food and minerals, as well as shelter by constructing cities and villages; they may also be used as a base of military operations, where a military installation would be constructed. This made star systems extremely valuable.<br />
<br />
A star system usually has at least one point wherein intersystem subspace travel is possible, known as [[jump node]]s. Jump nodes are highlighted in green in a ship's HUD. It is unknown as to how the Terrans or Vasudans discovered jump nodes.<br />
<br />
Star systems also allow intrasystem subspace travel, wherein any ship equipped with subspace drives can jump to one point of the system to another in the presence of the nearby star's gravitational pull.<br />
<br />
At one point during the Second Shivan Incursion, a notable star system, [[Capella]], was utterly destroyed when its star went supernova resulting from mysterious Subspace tearing weaponry on the [[SJ Sathanas]] Juggernauts; exactly why the Shivans did this is unknown, but the capability to destroy entire stars has shocked both Terrans and Vasudans.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Star_system&diff=34647Star system2011-05-13T12:28:53Z<p>Marcov: </p>
<hr />
<div>'''Star Systems''', or shortly termed "'''systems'''", are vast regions of space, supported by very large celestial objects known as '''stars'''. Occasionally, star systems hold one or more planets, supported by the intense gravitational pull of the system's star.<br />
<br />
Prior to the development of [[Subspace]] travel, space-faring species such as the [[Terran]]s and [[Vasudan]]s were only bound to within their respective star systems; the Terrans were bound to [[Sol]], and the Vasudans, to [[Vasuda]]. The birthplace of the [[Shivan]]s is unknown; whether they even originated from a star system is open to wide debate. A mysterious, ancient race, termed only as the "[[Ancients]]", allegedly originated in a star system "close to Vasuda".<br />
<br />
With the deployment of Subspace travel, various races were able to journey to other systems, places which have never been reached before. Without subspace, it would be nearly impossible to travel to other systems, as such distances are measured in several lightyears. The Terrans, Vasudans, and Ancients exploited multiple star systems, colonizing and governing them. Some systems had planets, which contained valuable resources, such as food and minerals, as well as shelter by constructing cities and villages; they may also be used as a base of military operations, where a military installation would be constructed. This made star systems extremely valuable.<br />
<br />
A star system usually has at least one point wherein intersystem subspace travel is possible, known as [[jump nodes]]s. Jump nodes are highlighted in green in a ship's HUD. It is unknown as to how the Terrans or Vasudans discovered jump nodes.<br />
<br />
Star systems also allow intrasystem subspace travel, wherein any ship equipped with subspace drives can jump to one point of the system to another in the presence of the nearby star's gravitational pull.<br />
<br />
At one point during the Second Shivan Incursion, a notable star system, [[Capella]], was utterly destroyed when its star went supernova resulting from mysterious Subspace tearing weaponry on the [[SJ Sathanas]] Juggernauts; exactly why the Shivans did this is unknown, but the capability to destroy entire stars has shocked both Terrans and Vasudans.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Star_system&diff=34646Star system2011-05-13T12:28:31Z<p>Marcov: Created page with "'''Star Systems''', or shortly termed "'''systems'''", are vast regions of space, supported by very large celestial objects known as '''stars'''. Occasionally, star systems hold …"</p>
<hr />
<div>'''Star Systems''', or shortly termed "'''systems'''", are vast regions of space, supported by very large celestial objects known as '''stars'''. Occasionally, star systems hold one or more planets, supported by the intense gravitational pull of the system's star.<br />
<br />
Prior to the development of [[Subspace]] travel, space-faring species such as the [[Terran]]s and [[Vasudan]]s were only bound to within their respective star systems; the Terrans were bound to [[Sol]], and the Vasudans, to [[Vasuda]]. The birthplace of the [[Shivan]]s is unknown; whether they even originated from a star system is open to wide debate. A mysterious, ancient race, termed only as the "[[Ancients]]", allegedly originated in a star system "close to Vasuda".<br />
<br />
With the deployment of Subspace travel, various races were able to journey to other systems, places which have never been reached before. Without subspace, it would be nearly impossible to travel to other systems, as such distances are measured in several lightyears. The Terrans, Vasudans, and Ancients exploited multiple star systems, colonizing and governing them. Some systems had planets, which contained valuable resources, such as food and minerals, as well as shelter by constructing cities and villages; they may also be used as a base of military operations, where a military installation would be constructed. This made star systems extremely valuable.<br />
<br />
A star system usually has at least one point wherein intersystem subspace travel is possible, known as [[jump nodes]]. Jump nodes are highlighted in green in a ship's HUD. It is unknown as to how the Terrans or Vasudans discovered jump nodes.<br />
<br />
Star systems also allow intrasystem subspace travel, wherein any ship equipped with subspace drives can jump to one point of the system to another in the presence of the nearby star's gravitational pull.<br />
<br />
At one point during the Second Shivan Incursion, a notable star system, [[Capella]], was utterly destroyed when its star went supernova resulting from mysterious Subspace tearing weaponry on the [[SJ Sathanas]] Juggernauts; exactly why the Shivans did this is unknown, but the capability to destroy entire stars has shocked both Terrans and Vasudans.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34644Asteroid2011-05-13T11:35:26Z<p>Marcov: </p>
<hr />
<div>[[File:AsteroidCollision.jpg|480px|right|thumb|Several asteroids on a collision course towards the NTF ''Iceni'']]<br />
'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF Iceni]].<br />
<br />
Although generally larger than fighters, asteroids are very easy to destroy as only several hits from even the most basic weapons would be required to take them down. When asteroids explode, smaller fragments are formed; if the fragments are large enough, they may still continue the collision course to the victim ship, and therefore must be taken out as well.<br />
<br />
Like any solid object, asteroids are not repelled by [[shield]]s; conclusively, caution must be observed whenever near the vicinity of any asteroid, as an impact with one can cause massive hull damage to fighters and bombers, with or without shields.<br />
<br />
==Notes for mission designers==<br />
Asteroids are usually generated with the "Asteroid Field" function. However, there is also a ship called "Asteroid" in the Ships list. This asteroid is very large, but it does not move and cannot collide with objects. Furthermore, the texture of this asteroid seems to be less detailed than the ones generated with the "Asteroid Field" function; so unless you're determined, it is recommended that you use the "Asteroid Field" function instead; if you want only one, immobile asteroid, make the number of asteroids "1" and check the "Passive" box in the Asteroid Field editor.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Shield&diff=34643Shield2011-05-13T11:32:04Z<p>Marcov: </p>
<hr />
<div>[[Image:LabShield.JPG|thumb|right|400px|A [[Terran]]-[[Vasudan]] experiment on reverse-engineered shield systems, during the early stages of the [[Great War]].]]<br />
<br />
A '''shield''' is an energy-based defensive barrier which completely surrounds the vessel on which it is equipped, and serves to absorb the damage dealt to that vessel from hostile fire. Shields also deflect the force of explosions and shockwaves, making them an invaluable tool for bomber pilots. FreeSpace 2-era fighter and bomber shields are incapable of repelling energy from [[Beam weapons|beam cannons]], and are easily pierced by these weapons. Shields cannot be used whilst in [[Subspace|subspace]].<br />
<br />
Shield integrity drops when it absorbs damage, and increases again over time as it draws power from the ship's reactor to recharge itself. The speed of this regeneration can be increased if energy is diverted to shields, away from engines and weapons, with the [[Energy Transfer System]] (ETS). Each shield is split into four quadrants (left, right, forward and rear) and specific quadrants can be recharged by diverting power from other quadrants. <br />
<br />
Although shields effectively repel energy blasts and shockwaves, they do not protect their host ships from suffering damage via collision with solid objects.<br />
<br />
All [[Galactic Terran-Vasudan Alliance|GTVA]] fighters and bombers are equipped with shield generators. The strength of the shield depends on the quality of the shield generator and on the type of the fighter. Interceptors, for example, typically lack strong shields, but compensate through high speed and maneuverability. Bombers, by contrast, are primarily designed to be tough and resilient, making shield strength a higher priority in their design.<br />
<br />
==Acquiring the Shield Technology==<br />
In 2335, the [[Shivans]] appeared for the first time, using advanced technology, including the fighter shield system, which gave them a huge advantage over the [[Galactic Terran Alliance]] and [[Parliamentary Vasudan Navy]] at the time.<br />
<br />
To the [[14-Year War]]-era weapons that were in use at the time, Shivan shields were almost completely impenetrable. This advantage allowed the Shivans to win many critical, early battles, such as the destruction of the GTD ''Amadeus''.<br />
<br />
It was immediately apparent that the only way to defeat the Shivans would be to develop weapons which could penetrate their shields. A series of daring raids by Terran pilots eventually succeeded in acquiring both scan data and actual Shivan cargo containers containing shield systems. This allowed for a joint Terran-Vasudan venture to reverse-engineer the shielding system and begin mass production, eventually in [[Ribos]]. The technology was soon fitted to every Terran and Vasudan fighter in service, and the ready availability of shielded fighters to test them on allowed Terran and [[Vasudans|Vasudan]] scientists to develop weapons capable of penetrating them.<br />
<br />
==The Lucifer's Shields==<br />
The [[SD Lucifer|SD ''Lucifer'']] is the only vessel above bomber size ever encountered by Terrans or Vasudans to be equipped with an energy shield. The shielding system it used was known as 'sheath shielding', and was utterly impenetrable to any weapons at the time. The only weakness of the technology was one shared with typical fighter shields: They were inoperable in subspace, and this left the ''Lucifer'' vulnerable to attack by GTA and PVN pilots while en route to [[Earth]]. So far, the [[Galactic Terran-Vasudan Alliance]] has not been able to replicate this technology.<br />
<br />
There is no canonical information about whether FreeSpace 2-era beam weapons could penetrate the ''Lucifer'''s shields as they do fighter-mounted shields.<br />
<br />
==Gameplay==<br />
By default, basic shield management keys are "Q" to equalize shields (evenly distribute all remaining shield energy between all four quadrants), the directional keys to divert shield energy to each respective quadrant, and the "Home" and "End" keys to transfer energy to or from the shield system. In addition, energy from the ship's primary weapons can immediately be transferred to shields, recharging them instantaneously without having to wait for the ship's reactor to slowly regenerate shield integrity. By default, this function is mapped to the "Scroll Lock" key.<br />
<br />
==Notes for Modders==<br />
If you want your fighter/bomber to have shields, you must make a ''triangulated'' sphere and name it as 'shield'. Also, you must apply a single color on it.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Shield&diff=34642Shield2011-05-13T11:30:52Z<p>Marcov: </p>
<hr />
<div>[[Image:LabShield.JPG|thumb|right|400px|A [[Terran]]-[[Vasudan]] experiment on reverse-engineered shield systems, during the early stages of the [[Great War]].]]<br />
<br />
A '''shield''' is an energy-based defensive barrier which completely surrounds the vessel on which it is equipped, and serves to absorb the damage dealt to that vessel from hostile fire. Shields also deflect the force of explosions and shockwaves, making them an invaluable tool for bomber pilots. FreeSpace 2-era fighter and bomber shields are incapable of repelling energy from [[Beam weapons|beam cannons]], and are easily pierced by these weapons. Shields cannot be used whilst in [[Subspace|subspace]].<br />
<br />
Shield integrity drops when it absorbs damage, and increases again over time as it draws power from the ship's reactor to recharge itself. The speed of this regeneration can be increased if energy is diverted to shields, away from engines and weapons, with the [[Energy Transfer System]] (ETS). Each shield is split into four quadrants (left, right, forward and rear) and specific quadrants can be recharged by diverting power from other quadrants. <br />
<br />
Although shields effectively repel energy blasts and shockwaves, they do not protect their host ships from suffering damage by colliding with solid objects.<br />
<br />
All [[Galactic Terran-Vasudan Alliance|GTVA]] fighters and bombers are equipped with shield generators. The strength of the shield depends on the quality of the shield generator and on the type of the fighter. Interceptors, for example, typically lack strong shields, but compensate through high speed and maneuverability. Bombers, by contrast, are primarily designed to be tough and resilient, making shield strength a higher priority in their design.<br />
<br />
==Acquiring the Shield Technology==<br />
In 2335, the [[Shivans]] appeared for the first time, using advanced technology, including the fighter shield system, which gave them a huge advantage over the [[Galactic Terran Alliance]] and [[Parliamentary Vasudan Navy]] at the time.<br />
<br />
To the [[14-Year War]]-era weapons that were in use at the time, Shivan shields were almost completely impenetrable. This advantage allowed the Shivans to win many critical, early battles, such as the destruction of the GTD ''Amadeus''.<br />
<br />
It was immediately apparent that the only way to defeat the Shivans would be to develop weapons which could penetrate their shields. A series of daring raids by Terran pilots eventually succeeded in acquiring both scan data and actual Shivan cargo containers containing shield systems. This allowed for a joint Terran-Vasudan venture to reverse-engineer the shielding system and begin mass production, eventually in [[Ribos]]. The technology was soon fitted to every Terran and Vasudan fighter in service, and the ready availability of shielded fighters to test them on allowed Terran and [[Vasudans|Vasudan]] scientists to develop weapons capable of penetrating them.<br />
<br />
==The Lucifer's Shields==<br />
The [[SD Lucifer|SD ''Lucifer'']] is the only vessel above bomber size ever encountered by Terrans or Vasudans to be equipped with an energy shield. The shielding system it used was known as 'sheath shielding', and was utterly impenetrable to any weapons at the time. The only weakness of the technology was one shared with typical fighter shields: They were inoperable in subspace, and this left the ''Lucifer'' vulnerable to attack by GTA and PVN pilots while en route to [[Earth]]. So far, the [[Galactic Terran-Vasudan Alliance]] has not been able to replicate this technology.<br />
<br />
There is no canonical information about whether FreeSpace 2-era beam weapons could penetrate the ''Lucifer'''s shields as they do fighter-mounted shields.<br />
<br />
==Gameplay==<br />
By default, basic shield management keys are "Q" to equalize shields (evenly distribute all remaining shield energy between all four quadrants), the directional keys to divert shield energy to each respective quadrant, and the "Home" and "End" keys to transfer energy to or from the shield system. In addition, energy from the ship's primary weapons can immediately be transferred to shields, recharging them instantaneously without having to wait for the ship's reactor to slowly regenerate shield integrity. By default, this function is mapped to the "Scroll Lock" key.<br />
<br />
==Notes for Modders==<br />
If you want your fighter/bomber to have shields, you must make a ''triangulated'' sphere and name it as 'shield'. Also, you must apply a single color on it.<br />
<br />
[[Category:Technologies]]</div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34641Asteroid2011-05-13T11:28:32Z<p>Marcov: </p>
<hr />
<div>[[File:AsteroidCollision.jpg|480px|right|thumb|Several asteroids on a collision course towards the NTF ''Iceni'']]<br />
'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF Iceni]].<br />
<br />
Although generally larger than fighters, asteroids are very easy to destroy as only several hits from even the most basic weapons would be required to take them down. When asteroids explode, smaller fragments are formed; if the fragments are large enough, they may still continue the collision course to the victim ship, and therefore must be taken out as well.<br />
<br />
Like any solid object, asteroids are not repelled by [[shield]]s; conclusively, caution must be observed whenever near the vicinity of any asteroid, as an impact with one can cause massive hull damage to fighters and bombers, with or without shields.<br />
<br />
==Notes for mission designers==<br />
Asteroids are usually generated with the "Asteroid Field" function. However, there is also a ship called "Asteroid" in the Ships list. This asteroid is very large, but it does not move and cannot collide with objects. Furthermore, the texture of this asteroid seems to be less detailed than the ones generated with the "Asteroid Field" function; so unless you're determined, it is recommended that you use the "Asteroid Field" function instead; if you want only one, immobile asteroid, make the number of asteroids "1" and check the "Passive" box.</div>Marcovhttps://wiki.hard-light.net/index.php?title=File:RScreen0077.jpg&diff=34640File:RScreen0077.jpg2011-05-13T11:25:36Z<p>Marcov: </p>
<hr />
<div></div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34639Asteroid2011-05-13T11:25:09Z<p>Marcov: </p>
<hr />
<div>[[File:AsteroidCollision.jpg|480px|right|thumb|Several asteroids on a collision course towards the NTF ''Iceni'']]<br />
'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF Iceni]].<br />
<br />
Although generally larger than fighters, asteroids are very easy to destroy as only several hits from even the most basic weapons would be required to take them down. When asteroids explode, smaller fragments are formed; if the fragments are large enough, they may still continue the collision course to the victim ship, and therefore must be taken out as well.<br />
<br />
==Notes for mission designers==<br />
Asteroids are usually generated with the "Asteroid Field" function. However, there is also a ship called "Asteroid" in the Ships list. This asteroid is very large, but it does not move and cannot collide with objects. Furthermore, the texture of this asteroid seems to be less detailed than the ones generated with the "Asteroid Field" function; so unless you're determined, it is recommended that you use the "Asteroid Field" function instead; if you want only one, immobile asteroid, make the number of asteroids "1" and check the "Passive" box.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34638Asteroid2011-05-13T11:23:26Z<p>Marcov: </p>
<hr />
<div>[[File:AsteroidCollision|480px|right|thumb|Several asteroids on a collision course towards the NTF ''Iceni'']]<br />
'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF Iceni]].<br />
<br />
Although generally larger than fighters, asteroids are very easy to destroy as only several hits from even the most basic weapons would be required to take them down. When asteroids explode, smaller fragments are formed; if the fragments are large enough, they may still continue the collision course to the victim ship, and therefore must be taken out as well.<br />
<br />
==Notes for mission designers==<br />
Asteroids are usually generated with the "Asteroid Field" function. However, there is also a ship called "Asteroid" in the Ships list. This asteroid is very large, but it does not move and cannot collide with objects. Furthermore, the texture of this asteroid seems to be less detailed than the ones generated with the "Asteroid Field" function; so unless you're determined, it is recommended that you use the "Asteroid Field" function instead; if you want only one, immobile asteroid, make the number of asteroids "1" and check the "Passive" box.</div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34637Asteroid2011-05-13T11:01:54Z<p>Marcov: </p>
<hr />
<div>'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF Iceni]].</div>Marcovhttps://wiki.hard-light.net/index.php?title=Asteroid&diff=34636Asteroid2011-05-13T11:01:16Z<p>Marcov: Created page with "'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.…"</p>
<hr />
<div>'''Asteroids''' are large, celestial rocks found in Hyperspace. In the FreeSpace universe, asteroids are generally mobile, and found in large groups termed '''asteroid fields'''.<br />
<br />
Mobile asteroids are usually harmful to any vessel that comes near, as they could collide with the ship, and the resulting impact would deal damage to the ship's hull integrity. As such, asteroids are a secondary target of warship turrets and fighters, to protect important vessels crossing hazardous fields.<br />
<br />
Asteroids on a collision course towards any vessel are highlighted with white brackets in a ship's HUD. These must be destroyed before they impact the victim ship. At worst, multiple collisions from several asteroids could cause even large capital ships to experience hull failure and, ultimately, destruction. A notable mission which involves defending an important ship from asteroid collisions is [[Rebels and Renegades]], where the player's squadron must shoot down asteroids on a collision course towards the [[NTF ''Iceni'']].</div>Marcov