FreeSpace Wiki - User contributions [en]

GTM TAG-C

2010-11-13T02:36:28Z

BlueKobold: /* Tech Room Data */

'''GTI TAG-C Missile'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Tagc.gif]]|caption=The GTI TAG-C Missile}}

==Tech Room Data==
The TAG-C is the third and final generation of TAG missiles developed by the GTI labs. This model provides greater reliability and compatibility with existing GTA turret hardware. Although these missiles are extremely scarce, tagging a target with one results in a devastating barrage from local friendly artillery. TAG-Cs have thus far been restricted to elite squadron use only.

==Performance==
===Statistics===
{{Secondary|2 665|8.0|205|1|Full|1|Full|1|Full|1|10 / 30|Aspect Seeking|N / A|2.5 s|1.75 s}}

==Notes==
*[[Weapons.tbl#$TAG:|TAGs]] the target (level-3). Effect lasts for 10 s

===Veteran Comments===
{{Comment|''Never actually used in the game, and incompatible with all GTVA fightercraft unless table alterations are made, the TAG-C looks to be a leftover vestige of something else. When the table alterations are made, it functions a lot like the [[GTM TAG-B]] missile.''

''It is unofficially confirmed that the TAG-C is part of the infamous "Subspace Missile Strike" or SSM, serving as the trigger and target point for the missiles to converge upon. The TAG-C was supposed to paint a single enemy, much like the TAG-A and TAG-B, but would summon an unavoidable barrage of heavy missile fire from subspace. This feature, although never used in the final iteration of retail FS2, is nonetheless still present in retail tables, albeit disabled. Bobboau was the first person on HLP to "unlock" the use of this weapon back in 2002. Subspace missiles recently made appearances in Flaming Sword's 'Shivans' mod and in Blue Planet: War in Heaven, and they will play a major role in the upcoming Inferno Alliance Standalone.''}}

[[Category:Weapon]]

GTM TAG-C

2010-11-09T15:16:29Z

BlueKobold: /* Notes */

'''GTI TAG-C Missile'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Tagc.gif]]|caption=The GTI TAG-C Missile}}

==Tech Room Data==
The TAG-C is the third and final generation of TAG missiles developed by the GTI labs. This model provides greater reliability and compatibility with existing GTA turret hardware. Although these missiles are extremely scarce, tagging a target with one results in a devastating barrage from local friendly artillery. TAG-Cs have thus far been restricted to elite squadron use only.

==Performance==
===Statistics===
{{Secondary|2 665|8.0|205|1|Full|1|Full|1|Full|1|10 / 30|Aspect Seeking|N / A|2.5 s|1.75 s}}

==Notes==
*[[Weapons.tbl#$TAG:|TAGs]] the target (level-3). Effect lasts for 10 s
*[[Blue_Planet#$Weaponry:|War in Heaven]] uses TAG-C missiles as the SSM trigger to great effect.

===Veteran Comments===
{{Comment|''Never actually used in the game, and incompatible with all GTVA fightercraft unless table alterations are made, the TAG-C looks to be a leftover vestige of something else. When the table alterations are made, it functions a lot like the [[GTM TAG-B]] missile.''

''It is unofficially confirmed that the TAG-C is part of the infamous "Subspace Missile Strike" or SSM, serving as the trigger and target point for the missiles to converge upon. The TAG-C was supposed to paint a single enemy, much like the TAG-A and TAG-B, but would summon an unavoidable barrage of heavy missile fire from subspace. This feature, although never used in the final iteration of retail FS2, is nonetheless still present in retail tables, albeit disabled. Bobboau was the first person on HLP to "unlock" the use of this weapon back in 2002. However, the concept of SSMs is still relatively unheard of, and only recently has begun seeing a negligible increase in the number of people interested in figuring out how it works.''}}

[[Category:Weapon]]

GTM TAG-C

2010-11-09T15:08:57Z

BlueKobold: /* Tech Room Data */

'''GTI TAG-C Missile'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Tagc.gif]]|caption=The GTI TAG-C Missile}}

==Tech Room Data==
The TAG-C is the third and final generation of TAG missiles developed by the GTI labs. This model provides greater reliability and compatibility with existing GTA turret hardware. Although these missiles are extremely scarce, tagging a target with one results in a devastating barrage from local friendly artillery. TAG-Cs have thus far been restricted to elite squadron use only.

==Performance==
===Statistics===
{{Secondary|2 665|8.0|205|1|Full|1|Full|1|Full|1|10 / 30|Aspect Seeking|N / A|2.5 s|1.75 s}}

==Notes==
*[[Weapons.tbl#$TAG:|TAGs]] the target (level-3). Effect lasts for 10 s

===Veteran Comments===
{{Comment|''Never actually used in the game, and incompatible with all GTVA fightercraft unless table alterations are made, the TAG-C looks to be a leftover vestige of something else. When the table alterations are made, it functions a lot like the [[GTM TAG-B]] missile.''

''It is unofficially confirmed that the TAG-C is part of the infamous "Subspace Missile Strike" or SSM, serving as the trigger and target point for the missiles to converge upon. The TAG-C was supposed to paint a single enemy, much like the TAG-A and TAG-B, but would summon an unavoidable barrage of heavy missile fire from subspace. This feature, although never used in the final iteration of retail FS2, is nonetheless still present in retail tables, albeit disabled. Bobboau was the first person on HLP to "unlock" the use of this weapon back in 2002. However, the concept of SSMs is still relatively unheard of, and only recently has begun seeing a negligible increase in the number of people interested in figuring out how it works.''}}

[[Category:Weapon]]

High Noon

2010-09-13T22:50:49Z

BlueKobold: /* Technical information */

{{Mission|next=Return to Babel|previous=Bearbaiting|campaign=FreeSpace 2 Campaign Walkthrough}}

'''ACT 3, MISSION 2'''

'''Fighter squadron:''' [[203rd Scorpions]]

'''Description:''' The 203rd assists the GTVA Colossus in destroying the SJ Sathanas

----
==Background==
Following an attempt at disarming at least two of the Sathanas' forward beam cannons by Alpha wing of the 203rd Scorpions, the Shivan juggernaut entered Capella to be confronted by the [[GTVA Colossus]]. If the Sathanas still has at least one main turret operational after [[Bearbaiting]], the Sathanas also decimated an Allied fleet near the Capella node. Alpha is deployed, once again, to provide bomber support for the Colossus.

==Walkthrough==
[[Image:Screen005.jpg|thumb|The Death of the Sathanas]]

You are not allowed to choose your loadout for this mission. You will be flying the [[GVB Bakha]], armed with the [[GTW Mekhu HL-7]], [[GTW Akheton SDG]], a bank of [[GTM Trebuchet]]s and a bank of [[GTM Helios|Helios torpedoes]].

This can be the easiest mission in the whole game if you performed well in the previous mission. If not, you still have work to do because the Sathanas can take out the Colossus even with one of its forward beam turrets operational. Fortunately, due to differences in timing, frames per second, maneuvering, etc., the Colossus is usually safe once you're down to one turret. If the flak guns are still operational, you may want to destroy them yourself, or order your wingmen to take them out for you.

The Basilisks can be really annoying, but you can usually take several out with Trebuchets at long range before you engage the Sathanas. Fortunately, there are only eight of them, as opposed to the many wings and waves of Shivan fighters in Bearbaiting, so when the second wave arrives, just order your wingmen to cover you. If you have gotten all four turrets, feel free to take them out yourself to get credit for the extra kills.

You can ensure you get the kill for the Sathanas by making sure you inflict more damage on it than any of your wingmen. You can do this by destroying AAA and flak turrets with your missiles and shooting down subsystems with your primaries. If your wingmen are busy with the Basilisks or if you've ordered them to depart, this should be pretty easy. After a 10-minute exchange of beam fire, the Sathanas throws in the sponge.

==Notes==
* Most of the GTVA Colossus' beam cannons are changed to the [[LRBGreen]] in this mission. This was a quick fix to a problem caused by the Colossus being given a simple [[ai-chase]] order to attack the Sathanas, which results in the Colossus circling the Sathanas from outside the targeting range of a normal [[BGreen]], [[TerSlash]] or [[BFGreen]].
* This mission gives you 10 000 points if you manage to get the Sathanas on your list of kills. This can be achieved by you inflicting more damage on it than any of your wingmen, or by inflicting at least 30% of non-beam damage.
* In the retail version of FreeSpace 2, the Colossus will not open fire on the Sathanas if you order your wingmen to ignore the Shivan juggernaut.
* If the fighterbay of the Sathanas gets disabled, you may not be able to complete the Destroy Cancer objective.

==Notable ships present==
* [[GTVA Colossus]]
* [[FreeSpace_2_Shivan_Ship_Database#SJ_Sathanas_01|SJ Sathanas 01]]

==Technical information==
{{MissionInfo|sm3-02.fs2|41.0 KB<sup>1</sup>|James Agay|10 (+1 waypoint)|2|38|20|2: Exodus|Brief3}}
===Notes===
:<sup>1</sup>This is the second smallest mission in terms of file size in the main campaign. The smallest is Training 6.
[[Category:Main FreeSpace 2 Campaign]]

Fiction Viewer

2010-08-28T14:52:44Z

BlueKobold: /* Using the Fiction Viewer (3.6.12. RC1 and newer) */

[[Image:2_fictionviewer.png|thumb|right|250px|The Fiction Viewer, FS2 style (click to enlarge)]][[Image:FictionViewer.jpg|thumb|right|250px|The Fiction Viewer (Wing Commander Saga style) with the first few paragraphs of [http://web.archive.org/web/20010308090656/vbb.volition-inc.com/ubb/Forum1/HTML/001723.html Tell A Story] (click to enlarge)]]

'''Fiction Viewer''' is a feature of [[Source Code Project|FreeSpace Open]] 3.6.10 implemented by [[User:Goober5000|Goober5000]]. It is sort of an advanced Command Briefing that mission designers could use to deepen the story that they want to tell without using the actual Command Briefing.

The Fiction Viewer is the first window that will come up in a mission, followed by the Command Briefing—if the mission has both.

==Using the Fiction Viewer (3.6.12. RC1 and newer)==
*Create a text file (.txt) that you want to show off with the Fiction Viewer, then put it into FreeSpace 2/data/fiction or FreeSpace 2/<your mod's directory name>/data/fiction.
*Open the mission in FRED. Select Editors --> Fiction Viewer and type in the file's name that you want to display, with its extension (for example: intro.txt).
*It is necessary to include self-made bits of interface art in your mod, since there is no official Volition art package for this screen. A sample one can be found here: http://blueplanet.fsmods.net/E/FictionViewer.7z The files in that archive must be extracted into the mods' data/interface folder. Without these, the game will not be able to display the fiction texts.
*There are two modes for the fiction viewer. The default one is the "FS2" style, which retains the standard layout used by the FS2 interface art. The other is the "Wing Commander Saga" style, which moves the "Accept" button to the lower left side of the screen, and is optimized for the interface art style of WCS. If you have interface art for the "WCS" style, you need to use "fictionviewerb" as the filename for the main interface background, and a fitting interface mask file named "fictionviewer-mb.pcx". For the 1024x768 resolution art, the filenames must be prefixed with "2_" (2_fictionviewerb, for example).

==Using the Fiction Viewer (pre-3.6.12. RC1)==
To use the Fiction Viewer, take the following steps:
*Go to [http://www.hard-light.net/forums/index.php/topic,50565.0.html this] thread and download the interface art. Extract the VP file from the ZIP file and put it into FreeSpace 2/data or FreeSpace 2/<the name of your mod's directory>
*Download the most stable official 3.6.10 [http://www.hard-light.net/forums/index.php/topic,64520.0.html here] or get an experimental build from [http://www.hard-light.net/forums/index.php/board,173.0.html this] board.
*Create a text file (.txt) that you want to show off with the Fiction Viewer, then put it into FreeSpace 2/data/fiction or FreeSpace 2/<your mod's directory name>/fiction.
*Create a mission which you want to use the Fiction Viewer, then [[Editing a mission in a text editor|open it in a text editor]], adding the following line before "#Command Briefing":

#Fiction Viewer

$File: YourFileName.txt

===Pre-3.6.12.-specific notes===
*Perhaps most importantly: Every time you save the mission in FRED, this piece of code will disappear! Add the Fiction Viewer code last before publishing the mission.
*The Fiction Viewer code must precede the Command Briefing code, otherwise the mission file will be broken.
*There is a colon (:) after "File", but there isn't anything after "Fiction Viewer".
*The only art style available on these builds is the "WCS" style.

==General notes==
*You must provide the file's extension (.txt), otherwise the game engine will assume the file has no extension, and look for that.
*Since the text file is not in the mission file, semicolons (;) and double quotation marks (" ") will not break the mission code.
*Color tags such as $r and $h will work.
*Characters that are not in the English alphabet (such as á, é) will not be displayed.
*The interface art can be modified by extracting the files from the VP.
*In 3.6.12 RC2 and later, the filename for the main interface screen has changed from "fvw" to "fictionviewer", to better follow the precedent set by the rest of the interface. Old interfaces must be adjusted for this, else it will cause a "No interface graphics found for the fiction viewer" error.

==External links==
*[http://www.hard-light.net/forums/index.php/topic,50565.0.html Fiction Viewer release thread]
*[http://www.hard-light.net/forums/index.php/topic,64520.0.html Official FreeSpace Open 3.6.10 release thread] (There are newer builds, but this one the most stable one)
*[http://www.hard-light.net/forums/index.php?topic=68190.0 FreeSpace Open 3.6.12. Release Candidate 1] (The first build to allow Fiction Viewer management in FRED)

[[Category:FRED]]
[[Category:Source Code Project]]