FreeSpace Wiki - User contributions [en]

EASD Nemesis

2008-05-22T17:21:32Z

Bruce89: minor pedantry

{{Inferno_Ships}}

Famous for its nanojumps, the '''EASD ''Nemesis''''' is the flaghship of the [[Earth Alliance]]. It is a massive superdestroyer armed to the teeth with powerful beam cannons and railguns (only in INF:A SA and INF SCP).

==Description:==

===Inferno R1 Description===
The Nemesis is the flagship of the Earth Alliance. An awesome superdestroyer, she dwarfs most capital ships in both the GTVA and EA. Extremely well armed and armored, she also carries her own elite fighter squadrons. She is frequently seen around the Sol Gate, guarding the installation with her multitude of super-heavy beam cannons. The EA maintains the Nemesis as its command ship.

===Inferno: Alliance Standalone Description===

N/A

===Inferno SCP Description===

N/A

===Developer Notes===
None

===Name origin===

N/A

==Performance:==
===Statistics===
{{Ship Stats|Superdestroyer|Earth Alliance|N/A|15.0|N/A|N/A|750000|N/A|N/A}}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Inferno R1'''
| colspan=2 style="background:#300505;"| '''INFA SA'''
| colspan=2 style="background:#300505;"| '''INF SCP'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[EA Turret]]
| 5
|- align="center"
| [[Heavy Flak]]
| 4
|- align="center"
| [[Hell Fire]]
| 6
|- align="center"
| [[EA RFT]]
| 8
|- align="center"
| [[Stinger]]
| 8
|- align="center"
| [[SSilver]]
| 1
|- align="center"
| [[BSilv]]
| 9
|- align="center"
| [[BFSilv]]
| 7
|}

==Veteran Comments==
{{Comment|Against fighters, the Nemesis is probably the most dangerous EA ship. You would best be advised to steer clear of the stinger turrets, or you will most likely be eaten alive, but this is easier said than done as these turrets are deployed relatively evenly across the ship's hull. The best tactic is to disable the aft-facing turrets from long range, then move in for the kill. However, getting to the right position to do so without wasting valuable time is very hard, and if you're playing the second-to-last mission of INFR1, disabling the multitude of Stingers on the sides of the ship may be necessary. Once the Stinger turrets have been disabled, there's little else you need to worry about except for the flak turrets, which can easily be avoided. The Nemesis is also basically invincible against capital ships, with no less than 16 incredibly dangerous beam cannons placed at very convenient locations throughout the hull.

The Nemesis is in the class of ships that are difficult to fight against due to sheer size and damage-absorbative potential. It is also, dare I say it, one of the coolest-looking Terran craft to ever grace a Freespace mod. There are a couple spots near the tower where the Stingers can't get you, I found one pretty rapidly in INF R1, because they can't make the turn. However there's not all that much you can knock out from those safe areas, so duck in and out of them using them to recharge your shields when necessary.

This ship is famous for its nanojumpings, more than able to turn the tide of a battle. In order to get the effect you need to give appropriate names: FreeSpace doesn't display letters like è, ù and à(while FRED does) so the only way to make the trick work is using those letters. Apparently, there will be no differences between "Nemesis" and "Nemesisè" and the player will most likely have the illusion of fighting the same ship. Use variables to store the status of a nanojumping Nemesis (so that it can be transferred to the upcoming Nemesis)will improve the effect.}}

[[Category:Inferno Ships]]

Multimedia Files

2008-05-22T17:17:54Z

Bruce89: rm silly windows convention of namimg filetypes after their extensions, and cleanup

The FreeSpace 2 Open engine is able to use several different '''multimedia file formats''' for audio, animation and video playback. Retail FreeSpace 2 used the [[Wikipedia:Wav|WAV]] and '''ANI''' file formats, but the currently the FreeSpace 2 Open supports several [[Wikipedia:Ogg|Ogg]] container files as well. Support for the [[Wikipedia:Mp3|MP3]] file format was removed in favor of Ogg. The game engine also supports special '''.EFF''' animations.

==Ogg==
'''Ogg''' is a file format for compressed multimedia files. Unlike MP3, Ogg is an open-source, open-standard container format with a permissive license, both of which allow it to be incorporated into the FS2_Open source code. Also unlike MP3, Ogg is a [[Wikipedia:Container_format|container format]], meaning that it can contain video data (via the [[Wikipedia:Theora|Theora codec ]]) in addition to audio data (via the [[Wikipedia:Vorbis|Vorbis codec]]).

Since Ogg delivers significantly smaller file sizes than [[Wikipedia:Wav|WAV]], while retaining substantially the same level of audio quality, it is becoming more and more frequently used in FSO-targeted mods. Ogg Vorbis is not, however, a lossless format -- i.e., it is not possible to exactly reconstruct the original data from an Ogg Vorbis file because some is "lost" in the conversion process. This is not usually a problem, however, because a high-quality Ogg Vorbis file is usually indistinguishable from the source. The lossless counterpart to Ogg Vorbis is [[Wikipedia:Free_Lossless_Audio_Codec|FLAC]], which can be contained in Ogg also.

Vorbis uses a quality parameter between -1 and 10 as a measure of quality. 5 is the default, giving around 160kbps. The higher the number, the higher the quality, but anything over 5 is probably pointless.

Audacity and Goldwave are two popular programs that allow WAV files to be converted to Ogg Vorbis audio. Audacity is Free Software, while Goldwave is shareware that ceases to function after a period of time.

Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

==WAV==
The most common sound file format. WAVs are uncompressed and take up a larger amount of space than almost any other sound file type, so consider converting them to the [[*.OGG|Ogg]] Vorbis format (supported only by SCP) before including them in your campaign. Audacity and Goldwave are two examples of programs that can make this conversion. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

==ANI==
FreeSpace uses the ANI format for animation effects. It can be used either for an effect (explosions, etc.), an interface animation, or as a ship texture.

===Creating an ANI file===

Using [http://www.swooh.com/lorenzo/files/aniview11.exe AniBuilder], one can create new ANI files from AVI movies.

To create your own ANI:

#Set up a scene in a 3D animation program or in FreeSpace. Volition used [[Wikipedia:3ds_Max|3ds Max]] (an expensive modeling program) for their animations.
#Using a free recording software such as for example [http://www.planetgamecam.com GameCam] to record the scene.
#Use for example [http://www.radgametools.com/bnkdown.htm Bink] to convert the AVI into a series of 16-bit (or less) PCX files, as AniBuilder will not accept non-PCX images, or images of more than 16 bit color depth.
#Use AniBuilder to convert the PCX files to an ANI.

==EFF==
FreeSpace 2 uses the EFF ASCII format text files to store information about animated effects. These animated effects can be used for various effects such as in game animations and animated textures. Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

===Creation of EFF animation===
*For EFF animation all the individual frames of the animation have to be present in one of the [[Graphic Files|graphic file formats]] supported by the game engine.
*All files related to the EFF animation have to named so that the name of actual .EFF animation forms the basic structure of the filename.
**'''Graphic files''' add the 4 digit number - that identifies the frame where the file is used - after the animation name, starting from 0 (example_0000.dds, example_0001.dds etc.)
**'''ASCII file''' contains the information of the animation (example.eff)

===Contents of a EFF file===

====$Type:====
*Defines the file format of the graphics file used for the EFF animation
*Syntax: '''''String''''', for example ''DDS''

====$Frames:====
*Defines the length of the number of the frames in the animation
*Syntax; '''''Integer'''''

====$FPS:====
*Used ''optionally'' to define the '''frames per second''' value for the animation
*Syntax: '''''Integer'''''

====Example====

Let's say you have three dds (TGA and pcx are also acceptable) files (named 1_000, 1_0001, and 1_0002) you want to make into an animation, but you don't want to use anibuild and therefore compromise quality.

Your EFF file would be like this:

Filename (the filename, not information to be entered. This must match up with characters before _xxxx in frames): 1.eff

$Type: DDS
$Frames: 3
$FPS: 5

This EFF effect file would display one frame after another at 5 frames a second, skipping back to the beginning at the end. Please note that EFF cannot be used for streaming files (head animations, icons, mainhall, cbanis, ect.) and is meant ONLY for weapon/explosion effects and animated textures.

[[Category:File Types]]

GTW ML-16 Laser

2007-12-21T16:00:03Z

Bruce89: pathetic

The '''ML-16''' is a [[primary weapon]] which was in heavy use before the appearance of the [[Shivans]] and their shielding technology. The ML-16 works adequately against hull and devours only a negligible amount of energy, allowing the pilot to divert more power on engines.

Since the ML-16 was designed in a "shieldless" era of both Terran and Vasudan history, it largely became inadequate against shielded targets like most Shivan fighters and bombers.

As soon as the GTW Avenger cannon became available, and produced in enough quantities, the ML-16 was replaced.

{{FS12_Weapons}}
{{shipimage|image=[[Image:ML16_320x240.jpg]]|caption=The ML-16}}

==Tech Room Data==
Argon laser weapon - uses transparent ceramic technology in order to create an optical system that is extremely durable and stable under battle conditions - provides adequate destructive damage to the hull of enemy ships by vaporizing molecular bonds at the target area and destabilizing molecular bonds across the grain of the hull material.

The GTA issues ML-16 Lasers to every fighter and bomber in service.

==Performance==
===Statistics===
{{Primary|900|5|450|5|Full|5|Minimal|0.5|Poor|1.5}}
==Notes==

===User-made Campaigns===

You will see more of this weapon in the [http://tvwp.hard-light.net/ Terran-Vasudan War Project]

===Veteran Comments===
{{Comment|The ML-16 is an acceptable weapon at the beginning of the main campaign. Unfortunately, after shielding on fighters become common, the weapon loses its efficiency. Prefer the Avenger to this weapon.

The ML-16 is not a bad gun against unshielded targets. In fact, try using it against a Shivan cruiser hull and you will be pleasantly surprised. However, without any ability to damage shields, it really isn't a viable choice later in the campaign.

The ML-16 does less than 1/3 of the armor damage of the [[GTW Avenger]], and between 1/3 and 1/2 of its Freespace 2 equivalent, the [[GTW Subach HL-7]] - for the same energy. I guess the [[GTW Flail]] and the [[GTW Training Laser]] are worse on armor, but if this isn't a bad gun on unshielded targets, I don't know what is.

Since fighters with no shields obviously take less damage to destroy, the ML-16 is perfectly serviceable against them. It's not going to do much to an Orion, but surely they would have bombs even before the Tsunami.

ML-16 isn't the best weapon. Twin 16s are worse than Twin Avengers. They worked well beacause the Vasudans had crap laser, and their fighter were just crap. But when it comes to killing off shivans (The boarding mission cuscene) they do come in handy in some sort...}}

[[Category:Weapon]]

GTW ML-16 Laser

2007-12-20T17:47:37Z

Bruce89: pathetic

GTW ML-16 Laser

2007-12-19T23:25:33Z

Bruce89: rv

User talk:Selectah

2007-12-18T16:38:27Z

Bruce89: Spelling

This text is inserted only because I don't like those red text bits. --[[User:Selectah|Selectah]] 04:37, 16 December 2006 (CST)

*No need. There will always be someone willing to post on your talk page. Thanks for adding all the Silent Threat walkthroughs, Selectah. FS1 rocks! [[User:Mustang19|Mustang19]]
Cheers, Mustang19. I'ven't added ''all'' the walkthroughs. Yet. I will. At some point. ;) [[User:Selectah|Selectah]] 04:08, 20 July 2007 (CDT)

==Alpha screens==
Wow, where did you find that SF-xx shot? [[User:Mustang19|Mustang19]] 11:20, 4 December 2007 (CST)
*I've got a ton of Alpha screenies, if you're interested. The stuff I'm interested in, however, is to somehow get the Alpha missions. You know that there were unique missions in the Alpha version, no? Three of 'em, voiced and all. I guess one needs to bombard either games magazines or Volition to get a hold of a copy. Oh ya, the POF models were a bit different, as well. ~[[User:Selectah|Selectah]]

An "Alpha"? Just something shipped to reviewers to look at before the game is complete, you mean? If you haven't done so already you should look at those screenshots and see if you could find some good trivia, plus host them on HC. Interesting. [[User:Mustang19|Mustang19]] 10:01, 5 December 2007 (CST)
* Ya, you're right; the Alphas -- especially ''Alpha II'', dated 12/04/97, almost 11 years ago -- were shipped to various testers and magazine editors, so that they could get a preview of what's coming. Plus it allowed them to hype the game no end. Thing is, there was a truckload of interesting things in the Alpha(s) -- of which there was a total of two, I don't have a release date for ''Alpha I'' (ironic name, no?) -- stuff that didn't survive at all or was changed to the point of unrecognizability. Things such as unique ships (the shivan cruiser Caldera, and -- yes -- the Juggernath, which was ''not'' the GTC Orff as is usually believed, but a unique ship from the second Alpha mission, etc), a completely different HUD in the first Alpha (with shield integrity as exact percentage instead of GFX, etc), unique weaponry (some of which are still present in the screenies on Volition's site -- look for the Angelfire missile, for instance, check for stats below), a completely different pilot stat screen (with your current fleet affiliation on display and totally different pilot appearance graphics), different POF models and backgrounds (YES!! PLANETS!!), et cetera.

===Screenshots from FreeSpace Alpha===
[[Image:Alpha_hud.jpg]]

'''Early version of the HUD, from FreeSpace Alpha.'''

[[Image:Alpha_hud_2.jpg]]

'''Planet backgrounds from FreeSpace Alpha.'''

===FreeSpace Alpha-Only Weaponry===

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=4 style="background:#351515;"| '''Alpha-Only Weapons'''
|- align="center"
| style="width:100px" |'''Name'''
| style="width:80px" |'''Damage'''
| style="width:80px" |'''Velocity'''
| style="width:80px" | '''Fire Wait'''
|- align="center"
| '''Mass Driver'''
| 40
| 240
| .15
|- align="center"
| '''Neutron Flux'''
| 30
| 300
| 30
|- align="center"
| '''Mag Pulse Missile'''
| 10
| 200
| 1.00
|- align="center"
| '''Shrike Missile'''
| 45
| 130
| 1.0
|- align="center"
| '''Angelfire Missile'''
| 60
| 100
| 1.0
|}

===Alpha Missions===
{{shipimage|image=[[Image:Juggernath_mission.jpg]]|caption=Screenshot from the near-mythical Juggernath mission.}}
The Holy Grail™ for me, though, would be the unique missions of the Alphas. There were three missions in the Alpha versions, two of which are the ones' we know from the FreeSpace 1 Demo. The third Alpha-only mission -- the second in the Alpha "campaign" -- is the most interesting of the bunch. This is the fabled mission where you are ordered to escort the lone ''Juggernath'', a Fenris class cruiser. The mission contains a lot of unique dialogue, dialogue which explains the sentiments regarding the newly founded Vasudan/Terran alliance and deepens the storyline, highlighting the still present animosity towards the Vasudans. A line from Alpha 3 in the mission might serve as example; "''I just hope I don't accidentally fire on one of them in the heat of battle. Old habits die hard''". Some other lines were later dropped in favour of the present ones, such as "''Enemy at three o'clock high!''", "''Sir watch your tail''" and "''Enemy fighters just appeared on radar''".

All of this is record, and well documented in a plethora of screenshots. Should I post the ones I have, you think? These mythical missions were finished, playable, completely voiced and are -- for better or for worse -- canon. Whatevenmore, they ''do'' exist. Somewhere. Probably in a drawer at Volition. Or at the OGR office. Or in a PC Gamer cupboard. Forgotten. Me wants them. By the way, what do you mean with "hosting them on HC"? What on Earth™ is HC? [[User:Selectah|Selectah]] 03:15, 7 December 2007 (CST)

Post more shots... I'm interested. HC is Hades Combine, BTW. (http://hades-combine.com/web/index.php?ind=downloads) [[User:Snail|Snail]] 08:28, 7 December 2007 (CST)

Put your talk page up on the [[FreeSpace Alpha]] page before I forgot. I'll clean it up later. If you have any additional material, post it there. I really liked the way you presented it. [[User:Mustang19|Mustang19]] 21:18, 7 December 2007 (CST)

== Spelling ==

Correcting spelling isn't bad, so don't be so hard on yourself. [[User:Bruce89|Bruce89]] 10:38, 18 December 2007 (CST)

Boomerang

2007-12-07T18:29:17Z

Bruce89: learn wiki syntax people

==Overview==
;Original Author: Peter Drake
;Contents of Mod:
* 4 Mission files
* 56 WAV files (voiceacting)
;Number of mission: 4

==Description==
''From Hades-Combine by Spicous''
Protect civilian traffic from Shivan raids, and discover a devastating new technology.

Fully voice acted.

==Notes==
This campaign is currently re-mastered for the sake of compatibilty with the latest FS Open. See Campaign Restoration for more information.

==Campaign Restoration==
Leading Member: ''(Not known, guess is Karajorma)'' 
Other Members: ''(Not known)''

==Player Comments==
None...yet...

==Related Links==
[http://hades-combine.com/web/index.php?ind=downloads&op=entry_view&iden=143| Download Link through Hades-Combine]
{{stub}}

Fighter squadrons

2007-12-06T22:43:12Z

Bruce89: bloody hell

==Introduction==
Fighter squadrons first appeared in FreeSpace 2, but some squadrons are said to have taken part in the [[The Great War|Great War]], too. We have only a very few canon fighter squadrons, but remarkably more non-canon ones, used in [[User-made Campaigns]].

An exact number of pilots to form a squadron is unknown, it is estimated to be 12, or any of its multiplicants. One flagship houses more than one squadrons, the [[GTD Aquitaine]] was housing five squadrons, according to the FreeSpace 2 main campaign.

==Great War-era fighter squadrons==
===GTA===
*1st Avenging Angels
*3rd
*13th Reapers
*23rd Flying Panthers
*33rd Jokers
*47th Cutthroats
*[[53rd Hammerheads]]
*66th Black Knights
*79th Predators
*81st Screaming Weasels
*103rd Flaming Skulls
*[[107th Ravens]]
*[[242nd Suicide Kings]]

===PVN===
*[[203rd Scorpions]]

==FreeSpace 2-era fighter squadrons==
===GTVA - Terran===
*[[53rd Hammerheads]]
*[[64th Raptors]]
*[[70th Blue Lions]]
*[[99th Skulls]]
*[[107th Ravens]]
*[[134th Barracudas]]
*[[242nd Suicide Kings]]

===GTVA - Vasudan===
*[[203rd Scorpions]]

===NTF===
*185th

==Non-canon fighter squadrons==
===Terran-Vasudan War-era squadrons===
===Great War-era===
===FreeSpace 2-era===
===Post-Capella-era===
*[[212th Silver Scythes]] ([[Derelict]])
*[[122nd Gemini]] ([[Renegade Ressurgence]])
*[[76th Predators]] ([[Renegade Ressurgence]])
*[[88th Nova-Squadron]] ([[StormFront]])
*[[96th Reptile]] ([[Renegade Ressurgence]])
*[[33rd Heavy Fighter Squadron]] ([[Cleaning Crew]])
----

==Notes to Wiki expanders==
'''If you insert a non-canon squadron, please append the name of the campaign in brackets, if possible which gives a link to an internal or external source.'''

''For example:''
*212th Scythes ([http://freespace.volitionwatch.com/derelict/ Derelict])

[[Category:FreeSpace Universe]]

Rebels & Renegades

2007-12-04T13:27:32Z

Bruce89: fix english, wikify

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Feint! Parry! Riposte!|Previous Mission]]
| [[Campaign Walkthrough]]
| [[Love the Treason...|Next Mission]]
|-
|}

'''SOC LOOP 1, MISSION 1'''

;Fighter squadron: 185th
;Description: The Iceni has to reach Regulus and you are one of the many pilots in the NTF protecting it. You are really an undercover GTVA operative sticking around to help the alliance unravel ETAK.

----
==Background==
You have been chosen to fly undercover with the Iceni, and gather information about the new ETAK project.

==Walkthrough==
Scan both friendly capital craft right at the start for some brownie points with SOC. Aside from that this a standard asteriod-field escort mission, you can just fly along next to the Iceni and blast any bombs or rocks that come its way. Defending the Hinton as well will be more of a problem, as Faustus science cruisers are less then sturdy; fortunately the Hinton's survival is not necessary for a successful mission. Ordering your wing to defend the Iceni and making the defense of the Hinton your sole responsiblity generally works...but see below. Concentrate on killing bombers and bombs, followed by anything that you find particularly offensive.

During this mission two capital craft will attempt to attack the Iceni, a Sobek and a Mentu. You would be well advised to keep the Iceni between you and the Mentu, since the Iceni will eat the cruiser alive no matter what you do, and the cruiser has AAA beams and flak guns that can hurt you. If those VSlash beams on the Sobek make you nervous for your charges feel free to take them out, but try not to get murdered by the corvette's antifighter defenses. As long as you've been doing a reasonably good job keeping the Iceni safe, its paired BGreens will take care of the enemy capital craft without your intervention.

The Hinton, thanks to its fragile nature, has a tendancy to get blasted. You can witness an amusing Volition flub if it is destroyed by a collision with an asteroid (or the Iceni, see below), as Snipes will say the Vasudans have destroyed it regardless of who layed the final blow and/or whether any Vasudans are actually present.

Unfortunately both the Iceni and the Hinton try to jump out at the same waypoint. And have the same speed. This results in a long series of collisions at the node before they jump out. Stay away from them while this is going on, because they will probably jump out at odd angles and you don't want to get run over. Roughly 50% of the time the Iceni batters the Hinton to death at the node regardless of your efforts. Take that as yet more evidence that the NTF must be destroyed for the good of the Terran race.

This is the only campaign mission where you can actually get Vasudan kills on your list, so do as much damage as possible if for some reason you want those.

It is imperative that you get the Iceni to the node, even though you are an allied operative. If you fail, you will be executed.

==Notable ships present==
[[NTF Iceni]]

[[Category:Main Freespace 2 Campaign]]

GTVA Colossus

2007-12-04T13:22:52Z

Bruce89: minor pedantry

{{spoiler}}
*Freespace 2

{{shipimage|image=[[Image:colossus320x240.jpg]]|caption=The GTVA Colossus}}

The largest space-faring warship ever constructed by [[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.

With the offensive power that exceeded most [[GTVA]] battlegroups, 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.

==History==
The first combat use of the ''Colossus'' was against the [[Neo-Terran Front]]. NTF forces proved to be no match for the ''Colossus'' and her battlegroup, and the rebels made every effort to avoid direct combat with the [[juggernaut]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. 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]].

With the NTF defeated, the ''Colossus'' was finally to fulfil the role her designers had envisioned for her: the defeat of a Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather a [[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''.

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.

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]].

==Victims of the ''Colossus''==
*NTCv ''Hawkwood'' (Destroyed at Enif Station)
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)
*NTC ''Camisard'' (Reported destroyed in Command Briefing)
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')
*NTCv ''Danton'' (''Endgame'')
*SJ ''Sathanas'' (First, High Noon mission)
*SD ''Beast'' (Destroyed shortly before the second Shivan juggernaut destroyed the Colossus)

==Quotes==
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"

"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."

"You are sacrificing thousands of lives for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"

"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"

==Colossus, the cutscene==
'''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''.''

'''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.''

'''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.''

----

{{FS12_Ships}}

==Description:==

===FS2 Tech Room Description===
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.

===Developer Notes===
None

===Name origin===
In Latin, ''colossus'' meant "large statue". Nowadays in English, a ''colossus'' (lower case, as this is a common name) may refer to anything of giant sizes. ''Colossal'' is a related word.

One of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue that was constructed over the entrance of the harbour to the city of Rhodes.

==Performance:==
===Statistics===
{{Ship Stats|Juggernaught|[[Colossus Manufacturers]]|N/A|25.0|N/A|N/A|1 000 000|N/A|6166}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|240 fightercraft (?) (60 wings)
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 8
|- align="center"
| [[Terran Huge Turret]]
| 10
|- align="center"
| [[Standard Flak]]
| 12
|- align="center"
| [[MX-52]]
| 8
|- align="center"
| [[GTM Piranha|Piranha]]
| 2
|- align="center"
| [[AAAf|Anti-Fighter Beam]]
| 10
|- align="center"
| [[TerSlash|Terran Slashing Beam]]
| 7
|- align="center"
| [[BGreen|Big Green Beam]]
| 6
|}

==Veteran Comments==
{{Comment|
''The GTVA Colossus was an excellent warship, equipped perfectly for the job it was designed for. While engaging the NTF hordes, we always knew the battle was over when the Colossus entered the fray. The Colossus' demise was one of the bravest sacrifices ever made by a ship in the GTVA. It remained in front of a Sathanas juggernaut, even though it had no chance of surviving, so that the Bastion might reach the Epsilon Pegasi node.''

''The Colossus is really out of its league against the Sathanas, but it was never designed for killing juggernauts. The Colossus' proper role is hunting and killing destroyers, a task at which it excels. It would take a very large number of smaller ships to threaten the Colossus; witness its single-handed destruction of the NTF.''

''The GTVA Colossus is not that great at killing ships of equal size to it as the above veterans have said. 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.''

''The GTVA Colossus...just saying that makes you get shivers down your spine. When you are fighting out on the "field" and you see the 6-kilometre behemoth, you can't help but to stop and stare at it. The Colossus in my terms means blond and majestic.''

''The Colossus is a superb ship in my opinion. Its weapon placement ensures no capship or fighter can attack it and stay safe. While not designed to confront ships like the Sathanas, if properly positioned it can take them on and emerge victorious. Its real strength lies in its anti-fighter weaponry and is a killer machine when confronting smaller warships.''

''It seems odd that it is the largest endeavour in Terran-Vasudan history with so many contractors, and with construction beginning well before the NTF Rebellion, and apparently the NTF and/or the average GTVA pilots didn't recognize or know about it. I don't buy it.''

''According to FRED-made simulations, it takes approximately 25 Nephilims to kill this thing, multiply that by two or three if you involve fighters escorting both the bombers and the Colossus. The Colossus better hope that it can make use of its 200+ plus fighters, because if not, this thing can get owned by bomber attack; most destroyers carry at least 40 fighters and bombers. Only an idiot would attack the Colossus with another capital ship, however; in general, it takes at least 6 destroyers to defeat one Colly.''

''The Colossus is to destroyers what a corvette is to a cruiser, bigger and armed well enough to make mince meat out of them, though well positioned destroyers can inflict notable damage to it they will die in the end. For example, if you do nothing to the NTF cruisers in [[Feint! Parry! Riposte!]], they will maneuver into the Collosus' upper-rear blindspot and will beam the Colossus to death over the course of an hour while she is unable to return fire, as all of her beams are mounted on the front or sides.''

''I think that the weak spots of the Colossus are it's rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two. In a custom-made mission, I made the Colossus travel 10 clicks, while being attacked on all sides by destroyers of different variations. I placed a [[GTD Hecate|Hecate]] on the left side, and it was the first to be destroyed. The last warship that got destroyed was the Demon, which I placed in front of and somewhat above it. The only two surviving warships (which took down the Colossus) were the [[GTD Hades|Hades]] and [[GVD Hatshepsut|Hatshepsut]], both of which I had placed at the rear-left and rear-right of the juggernaut respectively.}}

[[Category:Unique ships|Colossus]]
[[Category:Ship]]

SJ Sathanas

2007-12-04T13:19:44Z

Bruce89: some fixes

The '''SJ ''Sathanas''''' is the most powerful space-faring warship ever encountered by the [[Galactic Terran-Vasudan Alliance|GTVA]]. With four ultra-heavy beam cannons, a Sathanas outstrips even a [[GTVA Colossus|''Colossus''-class vessel]] in terms of raw firepower.

{{spoiler}}
*Freespace 2
{{shipimage|image=[[Image:sathanas320x240.jpg]]|caption=The SJ Sathanas}}

==Overview==
The prowess of this class was tragically demonstrated when a Sathanas juggernaut destroyed the [[GTVA Colossus|GTVA ''Colossus'']] in the [[Capella]] system. The only apparent weakness of the Shivan juggernaut is that the massive beam cannons are concentrated at the bow. Aside from a comparatively diminuative anti-warship beam cannon at the stern, the other flanks of the massive warship are covered only by point-defense weapons. However, a Sathanas is still more than able to defend itself and project offensive power via the many hundreds of fighters and bombers it carries in its cavernous hangar. Thus, stopping a juggernaut is almost impossible. Even the "expedient" of disabling the massive warship is hardly worth considering, due to the numerous redundant engines found on the hull. In essence, any attack on a ''Sathanas''-class juggernaut can be considered almost suicidal. Only the ''Colossus'' demonstrated enough firepower to take on a Sathanas.

Its prefix designation, SJ, stands for "Shivan Juggernaut."

==History==
The first combat appearance of a Shivan Juggernaut was in the nebula theater, beyond the first [[Knossos]] portal in [[Gamma Draconis]], when the warship destroyed a Vasudan task force assaulting a Shivan gasmining operation. The GTVA immediately began to withdraw from the nebula, though not before sending a pilot in the new [[GVF Ptah|''Ptah'']]-class stealth fighter to scan the vessel. Based on this information, the Alliance launched a targetted bombing mission to eliminate several of the forward beam cannons (there is no canon consensus concerning exactly how many were destroyed, but at least two were taken out) in the Gamma Draconis system, and the [[GTVA Colossus|GTVA ''Colossus'']] engaged and destroyed the weakened juggernaut after it jumped to the Capella system.

After that victory, the GTVA were confident they could eliminate any threats the Shivans could present, and returned to the nebula with the objective of locating and capturing [[Admiral Aken Bosch]]. However, that goal failed to be achieved as GTVA forces discovered that multiple ''Sathanas''-class juggernauts were en route to GTVA space. Gamma Draconis was quickly overrun by the swift advance of the juggernaut fleet, which shortly entered Capella. In a desperate gamble, the GTVA fleet held the Shivans at bay while civilians were evacuated to [[Epsilon Pegasi]] and [[Vega]]. During the closing stages of the battle, the GTVA ''Colossus'' was destroyed in Capella by a Shivan juggernaut while providing a diversion for the [[GTD Bastion|GTD ''Bastion'']], which was tasked with collapsing the jump corridor to Epsilon Pegasi. In a final startling turn of events, the Shivan juggernauts instigated the super-nova of the Capella star as the jump corridor to Vega was destroyed.

==Conclusion==
The Shivan juggernaut fleet is the single, most serious threat to the survival of the Terran and Vasudan species. The GTVA barely managed to stop one Sathanas, and even then it was with a warship that took two decades and enormous amounts of resources to construct. An encounter with any more Shivan juggernauts will only be able to be stopped with extreme difficulty. All technical data concerning ''Sathanas''-class juggernauts has been classified Level Upsilon.

----

{{FS12_Ships}}

==Description:==

===FS2 Tech Room Description===
Very little is known about the SJ Sathanas class. This juggernaut seems comparable in strength to the GTVA Colossus. All intelligence concerning the Sathanas has been classified level Upsilon.

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Juggernaut
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 25.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 1 000 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 5978 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Turret Laser]]
| 22
|- align="center"
| [[Standard Flak]]
| 11
|- align="center"
| [[Long Range Flak]]
| 2
|- align="center"
| [[GTM Piranha|Piranha]]
| 5
|- align="center"
| [[SAAA|Anti-Fighter Beam]]
| 8
|- align="center"
| [[LRed|Large Red Beam]]
| 1
|- align="center"
| [[BFRed|Very Big Red Beam]]
| 4
|}

===Veteran Comments===
{{comment|''It would be the best to steer clear of the juggernaut, as it would be suicide to attack it without capital ship support. However, it is extremely vulnerable to attack from capital ships from the side and the rear, where there are little to no anti capital ship defences.''

''It is also vulnerable to fighters and bombers if they attack near enough to the weapons subsystems, making it impossible for the anti-fighter beams to reach.''

''This giant warship is curious, neither the [[GTVA Colossus|Colossus]] nor the Sathanas have very good anti-fighter defenses. A squadron of [[GTM Helios|Helios]] capable bombers can take out all of its main beam cannons, leaving it vulnerable to attack. If it wasn't for the "supercap" flag, the Sathanas in such a state would be vulnerable to attacks by destroyers.''

''The Sathanas, like most FS2 Shivan capital craft, has an attack-oriented design that makes use of the known Shivan superiority at subspace jumping (at least in capital craft) to deal devastating first-strike blows. If itself attacked, it has problems. It has a single other anti-capital beam, an LRed in a "stinger" posistion aft and below; this weapon is not sufficent to prevent the Sathanas from being flanked. The Sathanas' defenses against fightercraft assault are respectable, but as mentioned above poorly sited to defend against an attack on its main armament. (The Colossus is notably superior in this regard.) In a way the Sathanas is a microcosm of the Shivan war machine, which is dependant on continually being on the assault to keep its flaws from being exposed. On the defensive it can still deal out heavy blows, but ultimately it is not prepared for the role. It is worth noting that the only time ingame the Sathanas was actually attacked, by a Vasudan corvette in "A Monster in the Mist", it was unable to come to grips with its opponent. Even in "High Noon" the Sathanas was essentially on the offensive, in motion towards the statically positioned Colossus.''

''This is one bigass mother of a ship. However, its defensive capabilities against fighters and bombers are far below par, so you can easily see why I disagree with the first comment. A quick salvo of Helios missiles should take care of the four front beams. The only annoying thing one should be warned about this is the forward flak cannon constantly bombarding your ship. If you can get rid of that, the ship is easily fried into helpless cap-ship fodder. Given an endless amount of time, enough missiles, and enough patience, it's possible that a single fighter or bomber could take down this juggernaut, as the Shivans apparently weren't planning on engineering defenses into their cap-ship destroyer. Unless its forward beam turrets are intact, it's as harmless as a fly (although not easily as squashed). Just be warned not to sit in front of it as it jumps out.''

''This ship is sooo not to be trifled with. You have to make sure you take out its front beams before you do anything else or you and your fellow Terrans are screwed bigtime.''

''It is true that a Sathanas '''CAN''' be flanked by a smaller warship, but do not underestimate the strength of its rear-facing LRed. Without any fighters or bombers to disable it, even a [[GVD Hatshepsut|Hatshepsut-class]] destroyer may not be able to survive attacking it from behind. If that single turret is destroyed, however, it will change the outcome.}}

[[Category:Ship]]

EAI Andromeda

2007-11-28T23:57:16Z

Bruce89: spelling

{{Inferno_Ships}}

The '''EAI ''Andromeda''''' is the massive [[Earth Alliance]] installation in the outer orbit of Mars where the [[TSJ Icanus]] was constructed. It has no weapons to speak of.

==Description:==

===Inferno R1 Description===
The Andromeda is the drydock around Mars in which the Icanus super juggernaught was constructed. This station has no armament.

===Inferno: Alliance Standalone Description===

N/A

===Inferno SCP Description===

N/A

===Developer Notes===
None

===Name origin===

N/A

==Performance:==
===Statistics===
{{Ship Stats|Installation|Earth Alliance|N/A|0.0|N/A|N/A|995000|N/A|N/A}}

===Armaments===

==Veteran Comments==

[[Category:Ship]]

EAC Aesacus

2007-11-28T23:54:26Z

Bruce89: was the right "its" before

{{Inferno_Ships}}

The '''EAC ''Aesacus''''' is the [[Earth Alliance]]'s anti-fighter platform. It is specificately designed to handle wings of hostile spacecraft, and its anti-warship capability is poor.

==Description:==

===Inferno R1 Description===
Armed with the EA's rapid fire projectile turret, the Aesacus is an anti-fighter escort design. A single medium beam cannon and several torpedo banks provide limited firepower against capital ship opponents. The Aesacus has a fast cruiser with enough speed for convoy escort and attack missions.

===Inferno: Alliance Standalone Description===

N/A

===Inferno SCP Description===

N/A

===Developer Notes===
None

===Name origin===

N/A

==Performance:==
===Statistics===
{{Ship Stats|Cruiser|Earth Alliance|N/A|30.0|N/A|N/A|45000|N/A|N/A}}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Inferno R1'''
| colspan=2 style="background:#300505;"| '''INFA SA'''
| colspan=2 style="background:#300505;"| '''INF SCP'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[EA RFT]]
| 14
|- align="center"
| [[Heavy Flak]]
| 4
|- align="center"
| [[Cruiser Torpedo]]
| 8
|- align="center"
| [[Stinger]]
| 2
|- align="center"
| [[MSilv]]
| 1
|}

==Veteran Comments==

[[Category:Ship]]

EASD Nemesis

2007-11-28T23:53:11Z

Bruce89: wrong type of its

{{Inferno_Ships}}

The '''EASD ''Nemesis''''' is the flaghship of the [[Earth Alliance]]. It is a massive superdestroyer armed to the teeth with powerful beam cannons and railguns (only in INF:A SA and INF SCP).

==Description:==

===Inferno R1 Description===
The Nemesis is the flagship of the Earth Alliance. An awesome superdestroyer, she dwarfs most capital ships in both the GTVA and EA. Extremely well armed and armored, she also carries her own elite fighter squadrons. She is frequently seen around the Sol Gate, guarding the installation with her multitude of super-heavy beam cannons. The EA maintains the Nemesis as its command ship.

===Inferno: Alliance Standalone Description===

N/A

===Inferno SCP Description===

N/A

===Developer Notes===
None

===Name origin===

N/A

==Performance:==
===Statistics===
{{Ship Stats|Superdestroyer|Earth Alliance|N/A|15.0|N/A|N/A|750000|N/A|N/A}}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Inferno R1'''
| colspan=2 style="background:#300505;"| '''INFA SA'''
| colspan=2 style="background:#300505;"| '''INF SCP'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[EA Turret]]
| 5
|- align="center"
| [[Heavy Flak]]
| 4
|- align="center"
| [[Hell Fire]]
| 6
|- align="center"
| [[EA RFT]]
| 8
|- align="center"
| [[Stinger]]
| 8
|- align="center"
| [[SSilver]]
| 1
|- align="center"
| [[BSilv]]
| 9
|- align="center"
| [[BFSilv]]
| 7
|}

==Veteran Comments==

[[Category:Ship]]

33rd Heavy Fighter Squadron

2007-11-26T22:09:33Z

Bruce89: wikify

{{non-canon}}

==General info==
'''Squadron type:''' Heavy fighter squadron 
'''Craft used the most:''' [[GVF Tauret]] 
'''Stationed on-board:''' GTI(?) Vega Installation or planetary base 
'''Squadron leader:''' <?>

The Thirty-Third Heavy Fighter Squadron was originally formed during the Terran-Vasudan War, where it served as a training and guard unit based on Vasuda Prime. During the Great War, the Thirty-Third was sent into a trap by its commanders, who were Hammer of Light sympathizers, and wiped out by wings from the HLD Prophecy shortly before the Siege of Vasuda Prime.
The Thirty-Third was reconstituted during the opening days of the NTF Rebellion to serve much the same role in the Vega system, assigned to the Vega System Defense Force. It was the only fighter unit of the Vega SDF not commited to the Battle of Capella, and was therefore the only intact fighter unit in Vega for the SD Famine Crisis; consequently it was called on to serve in most of the major actions of that campaign and distingushed itself.

Like the majority of Vasudan units, due to the great Vasudan emphasis on the importance of langauge, the 33rd has only a number, not a name; names are reserved for units that perform great feats in the service of the Imperium and GTVA.

==See also==
*[[Cleaning Crew]]
[[Category:Non-canon squadrons]]

Post-Capella

2007-11-01T22:11:59Z

Bruce89: really fix link instead of removing it

{{non-canon}}

The '''Post-Capella''' period is the era which occurs after the [[Destruction of Capella]]

This time period is unclear, and can only be speculated on. However, several things are clear: the millions of Capellan refugees must find a new home, and the [[Knossos]] technology can be used to re-open the jump node to [[Sol]] and re-establish contact. Speculations on the state of Sol, after having been severed from the rest of the GTA in 2335, vary widely. Presumably, the timeline of [[FreeSpace 3]] would have concentrated on this area. Arguments and any probable timelines will be posted here.

===Two weeks after Capella incident===
Starting point for the Technological Superiority campaign.

===2371===
Starting point of the [[Twisted Infinities]] campaign.

===2374===
Starting point of the [[Lost Souls]] campaign

===2374===
Starting point of the [[BlackWater Operations]] campaign

===2375===
Starting point of the [[Scroll of Atankharzim]] campaign.

===23??===
Construction of the Terran Knossos device completed.

===2400===
Starting point of the [[Inferno]] campaign. Approximate starting point of the [[Machina Terra]] Project.

===4021===
Starting point of the [[Starforce]] Mod.

NB: Many of these mods do not reference each others timelines, and so conflicting storylines can, and frequently do occur.

[[The Second Shivan Incursion]]''' :PREVIOUS

[[Category: History]]

Choosing dimensions

2007-10-22T01:49:06Z

Bruce89: some fixes

When making textures for models always use dimensions that are equal to 2n (2 to the power of some number), this means these numbers:

16, 32, 64, 128, 256, 512, 1024, 2048, 4096 etc.

*16 is the smallest texture FS2 will deal with, using anything smaller is a waste.

*256 is a special value because without changing a registry setting D3DuseLargeTextures (or using the launcher "Use Large textures") this is the largest texture that can be used by the engine without it having to cut into sections. This is also the maximum texture size for voodoo 2 & 3 cards.

*1024 - This is the maximum texture size for many older cards that aren't voodoo, a TNT2 for example would have this maximum.

*4096 - This is the maximum for a Geforce 4 card, however make sure you consider your texture sizes carefully a 4096x4096 (16 bit) texture takes up about 34 Meg, that's more memory for one texture than the TNT2 has in in total.

So what happens if you don't use these magic numbers? The engine will use the next one up. So if your texture is 257x257 then the texture will be 512x512 and the image will either be stretched across this larger area or the extra space will be wasted.

Remember that texturing is one of the most time consuming things your card has to deal with, with bad texture sizes its easy to waste processor time without making the result look any better.

The same goes for most other textures (and anims) in FS2 and all other games, the exception to this is interface art. e.g. the main hall background, this texture won't look good if it is stretched in the Y direction to 480 or 768 because the smoothing code is different.

Operation Savior

2007-10-17T23:38:04Z

Bruce89: fix link

==General==
'''Staff:'''
*[[User:Ngtm1r|Ngtm1r]]: Storyline, FREDding, playtesting.
'''Mods included:'''
What the heck is a mod?

'''Number of Missions:''' 5

==Description==
Force entry into Polaris in the early hours of the NTF Rebellion, rescue loyalist elements of the 6th Fleet and Polaris System Defense Force, and escape with your life.

==Notes==
FSO required. Installation as standard, drop in a folder in your FSO directory and use -mod command line. Beware of lurking table files in your data folder.

==FREDder's Notes==
I overcompensated from my previous campaign being too easy. Turn down your difficulty a notch when playing.

==Related Links==
[http://www.geocities.com/ngtm1r/OperationSavior.zip The Campaign]

[http://www.nukelol.com/downloads/freespacefiles/campaigns/OperationSavior.zip Operation Savior Nukelol Mirror]

[[Category:User-made_Campaigns]]

Derelict

2007-10-17T23:36:59Z

Bruce89: some fixes

{{Derelict}}

{| border=0 align=right cellpadding=4 cellspacing=1 width=30% style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Mod Info'''''
|-
! style="color: white; height: 30px; 70%;"|[[Derelict Mission Walkthrough]]
|}
==General Info==
*'''Original Authors:''' John 'Agatheron' Crowdis, Chris 'Kellan' Regan, Robert 'Dark' Wild, and Rodrigo 'Styxx' Barni.
*'''Update Author:''' Blaise Russel.
*'''Missions:''' 46
*'''Mods included:'''
*[[GTA Cypher]]
*[[GTB Hydra]]
*[[Shivan Knossos]]

'''SCP Required'''

Derelict is widely considered to be one of the best user-created mods. Derelict SCP was enhanced in 2006 by a complete set of voiceovers, in addition, several of the missions have been cleaned up.

==Story==
Five years have passed since the jump node to the Capella system was collapsed, sealing off a massive wave of Shivan Juggernaughts from pushing further into GTVA space. The supernova and subsequent nebula hang like a growing scar throughout the GTVA as light from that event continues to spread across our worlds.

The loss of Capella created serious economic hardship throughout the Alliance, a new Great Depression is upon us. The complete loss of the planetary resources and economic foundation of a rich world was devastating in its own right, but that is not all. Two hundred million refugees continue to walk the stars, seeking a new home. Some have settled, while others have been forced to move from place to place, hoping that the next place may welcome them with open arms.

While the Galactic Terran-Vasudan Alliance continues to hold, the current depression has given way to political instability. Local governments rise and fall as often lunar tides, organized crime and piracy have prospered in a black market environment. It seems no one is immune. Radical voices are raising echoes not heard since the blood cries of the Neo-Terran Front. The Ghosts of the past are catching up with us.

Since collapsing the Capella Jump Node, the recovering GTVA Fleet has spent much of its time and resources in police actions. Our own resources are taxed to the limit, and yet still we have the challenge to live up to our calling. Even so, it is alarming that there are those who are starting to take matters into their own hands.

What happens in the political arena is not our concern today. As part of the GTVA forces, ours is to keep space safe for our citizens

You are to take a new tour of duty with the 212th Silver Scythes squadron in the Tau Sigma cluster, a remote group of systems beyond the Altair Jump Node. These are mining colonies, and while the GTVA presence is small, it is nontheless important.

This is not an easy assignment, pilot. You will often be working in less-than-ideal conditions, but we trust that your skill will help to bring some much needed relief to this region.

==Player Comments==
{{Comment|Definitely download worthy. One of the best user made campaign I ever played with brilliant atmosphere.

A masterpiece of user made campaigns. Hailed by many as one of the best. Great in depth storyline, atmosphere and intense action. ~ KR

Renowned by many to be the best FreeSpace 2 fan-made campaign made, Derelict is definitely worth a (several) play through(s)

I believe this campaign could easily be considered one of the best ever made. You do not believe me? Then go play it! It is a jewel, a well polished one!}}

==Related Links==
*[http://nix1999.shackspace.com/ Download Site] provided by ShackSpace
*[http://www.hard-light.net/forums/index.php?topic=38019.0.html Release Thread]
*[http://freespace.volitionwatch.com/derelict/index.shtml Derelict on Volition Watch]
*[http://www.nukelol.com/downloads/freespacefiles/campaigns/derelict_scp/derelict.zip Derelict SCP Nukelol Mirror]

[[Category:User-made_Campaigns]]

Template:Derelict

2007-10-13T22:09:56Z

Bruce89: all derelict is non-canon

<includeonly>[[Category:Derelict|{{PAGENAME}}]]</includeonly>
<noinclude>[[Category:Templates|Derelict]]</noinclude>
{{non-canon}}

{| border=0 cellpadding=4 cellspacing=0 style="margin: 0 auto 0 auto; background: #302020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
|-
| align="center"| [[Image:Derelict_logo.jpg]]
|-
|}

Surrender, Belisarius!

2007-10-10T23:32:25Z

Bruce89: some interesting things

{{Mission|next=The Place of Chariots|first=Surrender, Belisarius|campaign=Campaign Walkthrough}}

''ACT 1, MISSION 1''

;Fighter squadron:[[53rd Hammerheads]]
;Description: The 53rd Hammerheads, GTD Aquitaine, must defend a convoy of Vasudan transports escaping Cygnus Prime.

----
==Background==
The GTVA are evacuating Cygnus Prime. Vasudan refugees are leaving the system in transport. The Aquitaine launches the Hammerheads to reinforce a fleeing Vasudan convoy.

==Walkthrough==

This is an easy mission, quite good as a warm-up to the game. You have to defend a convoy of Vasudan transports, designated Kappa wing. Not many [[NTF]] forces attack them, just a few [[GTF Hercules]]-class fighters. In this mission, you can learn how to put the [[GTM MX-64]] Rockeye FnF (Fire & Forget) missile to good use. Most pilots underestimate these missiles, and prefer the [[GTM Tempest]] dumbfire rockets.

You can lose at maximum of one Vasudan transport. However, keeping them both alive is preferred, of course. This is an easy standard to attain, just fire continually and accurately, and both transports will survive. Once the transports reach their destination waypoint, a [[GVD Hatshepsut]]-class Vasudan destroyer, the [[GVD Psamtik]], jumps in.

After her arrival, an enemy warship, the [[GTCv Deimos]]-class NTCv Belisarius, also jumps in. Hit the Belisarius at least once before the Psamtik slashes her in half, and you will get the whole score for that kill (note: some older versions of FSO did not do this because of a bug). You can make your approach while the Psamtik is trying to convince the captain of the Belisarius to surrender. If your hull strength is low, do not risk this trick, as the Belisarius is well-armed with anti-fighter defenses. You may also hit her with one or two Rockeyes instead, which can be shot from outside of the corvette's defenses range, scoring a kill without risking your life.

==Notable ships present==
*[[GVD Psamtik]]
*NTCv Belisarius

==New equipment==
*[[GTF Myrmidon]]
*[[GTW Subach HL-7]]
*[[GTM MX-64]]
*[[GTM Tempest]]

[[Category:Main Freespace 2 Campaign]]

Fan sites

2007-10-05T22:40:12Z

Bruce89: fixes

==General Information==

Any information read on any of the sites indicated below are not considered canon, because all of them are 'fan sites'.

==Sites==

*[http://www.hard-light.net/ Hard Light Productions] (Best-known fan site)
::Has been in existence since 2001, this site has the largest and most popular forum to talk about items related to FreeSpace. This is also the location of several projects, usually referred as Hosted projects. The site also has a mild amount of mods uploaded in the main page, but links to almost all possible mods can be reached from the forums in different threads.

::The best-known Hosted projects are the [[FSSCP Introduction|Source Code Project]] and [[Inferno]].

*[http://scp.indiegames.us/news.php The Source Code Project] (Main site)
::Contains information about the latest [[SCP builds]] as well as troubleshooting and numerous programs used for modding FreeSpace.

*[http://fs2.kissifrot.com/ Skippy's campaign list]
::Valuable site for campaign and mission hunters, not only for those who are interested in modding FreeSpace on any level. This is the currently best-known collection of campaigns.

*[http://www.hades-combine.com Hades Combine]
::A comprehensive collection of FreeSpace mods. The mods are uploaded by requests or nomination. Visit the Hades Combine forums to make a request.

*[http://www.volitionwatch.com Volition Watch]
::Volition Watch is one of the oldest FreeSpace fan sites known, containing a large amount of downloads from the apex times of FreeSpace. The site is still updated nowadays, by the hands of an esteemed community member.

*[http://www.descent-freespace.com Descent FreeSpace]
::More downloads in case you have not yet found what you are looking for on the previous sites. The FreeSpace Source code is also available from here.

*[http://homepage.ntlworld.com/karajorma/freespace/intro.html The FreeSpace Oracle]
::Covers general advice about anything related to FreeSpace, mostly FREDding, modelling and troubleshooting. You can also find useful links on this site.
::''This website is usually mentioned as Karajorma's FreeSpace FAQ''

*[http://www.expage.com/06palaro Hippo's FreeSpace site]
::Information about how to get FreeSpace.

*[http://w3.enternet.hu/fscult/ The FSCult]
::Main site of the Centaur Project. You can also find downloadable COB files of old Volition ships from here as well as some mission backgrounds.

Friendly wing names

2007-10-02T22:56:16Z

Bruce89: grammar

Volition used letters of the Greek alphabet to designate friendly wings.

*Alpha
*Beta
*Gamma
*Delta
*Epsilon
*Zeta
*Eta
*Theta
*Iota
*Kappa
*Lambda
*Mu
*Nu
*Xi
*Omicron
*Pi
*Rho
*Sigma
*Tau
*Upsilon
*Phi
*Chi
*Psi
*Omega

Alpha 1 is nearly always the player's character. Alpha through Kappa (with the notable exception of Eta, which rarely appears) are used regularly for fighter wings. Lambda is used frequently for transports and freighters. Omega is used occasionally for transports. In FS1 missions with allied Terrans and Vasudans, Terran wings are usually from the first half of the alphabet while Vasudan wings are usually from the second half of the alphabet. The only FreeSpace 1 missions that violate this "rule" are [[The Great Hunt]] and [[Good Luck]] (with Epsilon wing of Thoths). Therefore, this cannot be taken as a canon convention, but instead a preference of certain Volition mission designers, like Shivan wing naming patterns.

A mission designer need not follow this naming system, although this system is very common among mission designers.

[[Category:FRED]]

Source Code Project index

2007-09-27T22:54:26Z

Bruce89: wikify

'''For a summary on how to get started with FreeSpace 2, click [[Getting_started_with_FreeSpace_2|here]].'''

===Getting Started with the FreeSpace Source Code Project (FSSCP)===

#[[FSSCP Introduction]]
#[[Getting FreeSpace]]
#Installing FreeSpace 2 (FS2) Open
#*[[FreeSpace Open Installer|Using the FreeSpace Open (FSO) Installer]]
#*[[Installing fs2_open|Manual Installation Guide (Steps to take if not using the FSO Installer)]]
#*[[Fs2_open_on_Linux|Linux Installation Guide]]

====Optional Post-Install Information====
*[[Installing mods for fs2_open|Installing Mods for FS2 Open]]
*[[Troubleshooting]]
*[[Bug Reporting]]

====Errata====
*[[FS2 Status Page]]
*[[FS2 data installation]]


===Getting Started with Development===
*[[Getting the FreeSpace2: SCP Source Code|Getting the Source Code]]
*[[Coding In C]]
*[[Linux CVS Howto]]


===Notes===
*[[Freespace 2 EULA Issues]]

[[Category:Source Code Project]]

Tables

2007-09-27T22:53:25Z

Bruce89: wikify

'''Tables''' are the major data files in [[Portal:Freespace 1|FreeSpace]] and [[Portal:Freespace 2|FreeSpace 2]]. Compared with many other games, they are highly intuitive and easy to edit, requiring no special tools other than notepad. For more detail on specific tables, see the links below.

'''''Full list of tables can be found in [[:Category:Tables]] page. In-depth modular tables info can be found in [[Modular Tables]] page.

Information on how FreeSpace uses tables can be found on the [[Freespace 2 Directory Structure|FreeSpace 2 Directory Structure]] page.'''''

==Table files==

{| border=0 align=right cellpadding=2 cellspacing=1 style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! colspan="2" style="color: white; height: 30px; background: #512020; 70%;"|'''''Tables files and related code files'''''
|-
| align="center"| [[Ai.tbl]]
| '''/ai/'''aicode.cpp
|-
| align="center"| [[Ai_profiles.tbl]]
| '''/ai/'''ai_profiles.cpp
|-
| align="center"| [[Armor.tbl]]
| '''/ship/'''ship.cpp
|-
| align="center"| [[Asteroid.tbl]]
| '''/asteroid/'''asteroid.cpp
|-
| align="center"| [[Autopilot.tbl]]
| '''/autopilot/'''autopilot.cpp
|-
| align="center"| [[Credits.tbl]]
| '''/menuui/'''credits.cpp
|-
| align="center"| [[Cutscenes.tbl]]
| '''/cutscene/'''cutscenes.cpp
|-
| align="center"| [[Fireball.tbl]]
| '''/fireball/'''fireballs.cpp
|-
| align="center"| [[Help.tbl]]
| '''/gamehelp/'''contexthelp.cpp
|-
| align="center"| [[Hud.tbl]]
| '''/hud/'''hudshield.cpp
|-
| align="center"| [[Hud_gauges.tbl]]
| '''/hud/'''hudparse.cpp
|-
| align="center"| [[Icons.tbl]]
| '''/missions/'''missionbriefcommon.cpp
|-
| align="center"| [[Iff_defs.tbl]]
| '''/iff_defs/'''iff_defs.cpp
|-
| align="center"| [[Lightning.tbl]]
| '''/nebula/'''neblightning.cpp
|-
| align="center"| [[Mainhall.tbl]]
| '''/menuui/'''mainhallmenu.cpp
|-
| align="center"| [[Medals.tbl]]
| '''/stats/'''medals.cpp
|-
| align="center"| [[Menu.tbl]]
| '''/menuui/'''snazzyui.cpp
|-
| align="center"| [[Messages.tbl]]
| '''/mission/'''missionmessage.cpp
|-
| align="center"| [[Mflash.tbl]]
| '''/weapon/'''muzzleflash.cpp
|-
| align="center"| [[Music.tbl]]
| '''/gamesnd/'''eventmusic.cpp
|-
| align="center"| [[Nebula.tbl]]
| '''/nebula/'''neb.cpp
|-
| align="center"| [[Objecttypes.tbl]]
| '''/ship/'''ship.cpp
|-
| align="center"| [[Pixels.tbl]]
| '''/palman/'''palman.cpp
|-
| align="center"| [[Rank.tbl]]
| '''/stats/'''scoring.cpp
|-
| align="center"| [[Scripting.tbl]]
| '''/parse/'''scripting.cpp
|-
| align="center"| [[Ships.tbl]]
| '''/ship/'''ship.cpp
|-
| align="center"| [[Sounds.tbl]]
| '''/gamesnd/'''gamesnd.cpp
|-
| align="center"| [[Species_defs.tbl]]
| '''/species_defs/'''species_defs.cpp
|-
| align="center"| [[Species.tbl]]
| '''/menuui/'''techmenu.cpp
|-
| align="center"| [[Ssm.tbl]]
| '''/hud/'''hudartillery.cpp
|-
| align="center"| [[Stars.tbl]]
| '''/starfield/'''starfield.cpp
|-
| align="center"| [[Strings.tbl]]
| '''/localization/'''localize.cpp
|-
| align="center"| [[Tips.tbl]]
| '''/menuui/'''playermenu.cpp
|-
| align="center"| [[Traitor.tbl]]
| '''/missionui/'''missiondebrief.cpp
|-
| align="center"| [[Tstrings.tbl]]
| '''/localization/'''localize.cpp
|-
| align="center"| [[Weapon_expl.tbl]]
| '''/weapon/'''weapons.cpp
|-
| align="center"| [[Weapons.tbl]]
| '''/weapon/'''weapons.cpp
|-
|}

In general tables files are simple unformatted text files

===.tbl files===

These files are the basic FreeSpace table used for defining various aspects of the game. Game reads only single .tbl choosing the one it encounters first while parsing the game directories.

===.tbm files===

These files are [[Modular Tables]] files. They can be used for adding content to the 'base' tables or to modify the data from those files.

For usage info and important notes, see [[Modular Tables]].

===Notes of certain table files===

====Hardcoded table files====

Some of the table files are not actually required as the basic version has been written directly to the code. However these can be overridden by table files present in game directories.

'''These files are not present in standard FreeSpace 2 .vp files'''

*[[Ai_profiles.tbl]]
*[[Autopilot.tbl]]
*[[iff_defs.tbl]]
*[[Objecttypes.tbl]]
*[[Species_defs.tbl]]

====Optional table files====

Certain tables are not found from the code nor do they belong to the basic table set. These tables are parsed if game detects them

'''These files are not present in standard FreeSpace 2 .vp files'''

*[[Armor.tbl]]
*[[Scripting.tbl]]

====Obsolete table files====

Some table files have since been 'retired' and they are no longer needed with FreeSpace Open

*[[Hud.tbl]]

==Important notes==

===Table entries must be ordered===

*As a general rule, '''''all the table entries must be ordered'''''.
*Keep the order shown in the following help sections for each table in both normal tables (tbl files) and [[Modular Tables]] (tbm files). If you don't do it, you can get parser errors on FS2 or FRED2 loading when they are reading them.

==Brief descriptions of table files==

*In all the table help pages, SCP added entries are usually marked with infoboxes that mark the branch there the particular feature has added to.
:*'''<nowiki>{{Table36| text}}</nowiki>''' gives 3.6.x branch box
{{Table36| text}}
:*'''<nowiki>{{Table37| text}}</nowiki>''' gives 3.7 branch box
{{Table37| text}}
*For full list of table related pages and links see [[:Category:Tables]]

[[Category:Tables|*]]

[[Category:Modding]]

[[Category:File Types]]

Technologies

2007-09-27T20:45:33Z

Bruce89: wikified

==Fighter and bomber equipment==
*[[Monodirectional laser gun]]
*[[Afterburner]]
*[[Shields]]
*[[Countermeasures]]
*[[Intersystem jump drives]]

==Large ship equipment==
*[[Turrets]]
*[[Beam weapons]]
*[[Flak guns]]
*[[Radar Dish]]

==Common equipment==
*[[Armouring]]
*[[Subspace Drives]]
*[[Reactor]]

==Special technologies==
*[[ETAK]]
*[[Advance Warning and Control System | AWACS]]

[[Category:Lists]]
[[Category:Technologies]]

GTVA Colossus

2007-09-23T22:12:05Z

Bruce89: grammar

{{spoiler}}
*Freespace 2

{{shipimage|image=[[Image:colossus320x240.jpg]]|caption=The GTVA Colossus}}

The largest space-faring warship ever constructed by [[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.

With the offensive power that exceeded most [[GTVA]] battlegroups, 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.

==History==
The first combat use of the ''Colossus'' was against the [[Neo-Terran Front]]. NTF forces proved to be no match for the ''Colossus'' and her battlegroup, and the rebels made every effort to avoid direct combat with the [[juggernaut]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. 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]].

With the NTF defeated, the ''Colossus'' was finally to fulfil the role her designers had envisioned for her: the defeat of a Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather a [[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''.

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.

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]].

==Victims of the ''Colossus''==
*NTCv ''Hawkwood'' (Destroyed at Enif Station)
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)
*NTC ''Camisard'' (Reported destroyed in Command Briefing)
*NTC '''Vanguard'' (''Reported destroyed in Endgame'')
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')
*NTCv ''Danton'' (''Endgame'')
*SJ ''Sathanas'' (First, High Noon mission)
*SD ''Beast'' (Destroyed shortly before the second Shivan juggernaut destroyed the Colossus)

==Quotes==
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"

"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."

"You are sacrificing thousands of lives for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"

"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"

==Colossus, the cutscene==
'''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''.''

'''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.''

'''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.''

----

{{FS12_Ships}}

==Description:==

===FS2 Tech Room Description===
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.

===Developer Notes===
None

==Performance:==
===Statistics===
{{Ship Stats|Juggernaught|[[Colossus Manufacturers]]|N/A|25.0|N/A|N/A|1 000 000|N/A|6166}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|240 fightercraft (?) (60 wings)
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 8
|- align="center"
| [[Terran Huge Turret]]
| 10
|- align="center"
| [[Standard Flak]]
| 12
|- align="center"
| [[MX-52]]
| 8
|- align="center"
| [[GTM Piranha|Piranha]]
| 2
|- align="center"
| [[AAAf|Anti-Fighter Beam]]
| 10
|- align="center"
| [[TerSlash|Terran Slashing Beam]]
| 7
|- align="center"
| [[BGreen|Big Green Beam]]
| 6
|}

==Veteran Comments==
{{Comment|
''The GTVA Colossus was an excellent warship, eqipped perfectly for the job it was designed for. While engaging the NTF hordes, we always knew the battle was over when the Colossus entered the fray. The Colossus' demise was one of the bravest sacrifices ever made by a ship in the GTVA. It remained in front of a Sathanas juggernaut, even though it had no chance of surviving, so that the Bastion might reach the Epsilon Pegasi node.''

''The Colossus is really out of its league against the Sathanas, but it was never designed for killing juggernauts. The Colossus' proper role is hunting and killing destroyers, a task at which it excels. It would take a very large number of smaller ships to threaten the Colossus; witness its single-handed destruction of the NTF.''

''The GTVA Colossus is not that great at killing ships of equal size to it as the above veterans have said. 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.''

''The GTVA Colossus...just saying that makes you get shivers down your spine. When you are fighting out on the "field" and you see the 6 kilometre behemoth, you can't help but to stop and stare at it. The Colossus in my terms means blond and majestic.''

''The Colossus is a superb ship in my opinion. It's weapon placement ensures no capship or fighter can attack it and stay safe. While not designed to confront ships like the Sathanas, if properly positioned it can take them on and emerge victorious. Its real strength lies in its anti-fighter weaponry and is a killer machine when confronting smaller warships.''

''It seems odd that it is the largest endeavour in Terran-Vasudan history with so many contractors, and with construction beginning well before the NTF Rebellion, and apparently the NTF and/or the average GTVA pilots didn't recognize or know about it. I don't buy it.''

''According to FRED-made simulations, it takes approximately 25 Nephilims to kill this thing, multiply that by two or three if you involve fighters escorting both the bombers and the Collossus. The Colossus better hope that it can make use of its 200+ plus fighters, because if not, this thing can get owned by bomber attack; most destroyers carry at least 40 fighters and bombers. Only an idiot would attack the Colossus with another capital ship, however.''

''The Colossus is to destroyers what a corvette is to a cruiser, bigger and armed well enough to make mince meat out of them, though well positiond destroyers can inflict notable damage to it they will die in the end. Like corvettes it needs help taking anything of comparable size.}}
[[Category:Unique ships|Colossus]]
[[Category:Ship]]

Feature Requests

2007-09-20T23:27:14Z

Bruce89: adhere to the English language

This page is primarily to serve as a database for feature requests for the Source Code Project.

== New Requests ==

=== Internal Cockpit View - HUD System Changes ===
In order to get a more immersive in-cockpit view than we currently have, there are a number of nessecary changes.
The short-term system changes would primarily involve:
* An option somewhere to turn cockpit view on or off.
* Placing a specified 'standard cockpit model' POF in the mission with it's eyepoint lined up with the players in-ship viewpoint.
* A way to move or replicate the HUD and all it's functionality to fit in with the standard cockpit model. (This would most likely involve completing the HUD_guages.tbl feature, but it would also involve a way to define an alternate 'in cockpit' HUD component layout)

In the long term this feature would involve:
* Being able to define a different internal cockpit on a per-ship basis.
* Different internal cockpit models would need to be associated with different HUD component layouts

The changes are described in detail in this thread [http://www.hard-light.net/forums/index.php/topic,48726.msg990018.html#msg990018 here.]

I'm more than willing to help out any coders who do take this on in regards to the modeling/texturing/interface art side of things. --[[User: VA|VA]]

:*'''Supported By:''' FSU, Twisted Infinities

=== Orders for bomber turrets ===
Currently, bomber turrets only attack your target, which makes them usless as defensive weapons. The idea is to be able to order your turret and make it useful. Added comm options would be:

*turret: (keypress shift-1),
**protect me
**sync to gun (acts as a gunpoint)
**attack my target
**defend all friendlies
**attack any hostile
*all turrets: (keypress shift-2)
**protect me
**sync to gun (acts as a gunpoint)
**attack my target
**defend all friendlies
*attack any hostile

(This idea is modified from one from the thread "actually useful bomber turrets")

:*'''Supported By:''' several comunity members.

=== Infinite landscapes ===
===> Author, please read talk section on this.

The ability to have a landscape (ground model) that repeats infinately. A lot like the current sytem of just making landcapes and placing a few, but toggleable in FRED.
Added option in "backround editor" would be:
landscape model

:*'''Supported By:''' Freespace: Arcade (unadvertised mod), Starforce

=== Multiple shield meshes ===
You can have an individual shield mesh for each part of the ship. It would also allow you to shield certain turrets, important parts, ect. and not shield everything else.

:*'''Supported By:''' freespace: arcade (unadvertised mod)

=== Toggleable subsystems ===
Support for subsystems that can be turned on and off (ie when 'off', act as though they never existed - are untargetable, leave behind no damage LOD, do not take damage, cannot be collided with, etc.) This would be useful for ships where someone might want to remove or swap a subsystem (ie fighter cockpits could have Terran and Vasudan versions). The ability to do this with turrets too would be great.
:* '''Supported By:''' Shadows of Lylat, Twisted Infinities, [[Fringespace]], The Sagitta Project

=== Minefields ===

Just like asteroid fields, only they're mines, and they explode violently instead of burning up.

:*'''Supported By:''' Starforce

=== Ship headlights ===

Ship headlights/floodlights that actually cast light on objects.

:*'''Supported By:''' Starforce

=== Maximum asteroid number increase ===

From 256 to 1024+ (possibly use depth culling to reduce rendering load).

:*'''Supported By:''' Starforce

=== Gatling Turrets ===
Support for Gatling gun turrets, which work same as a regular multipart turret but has an extra subobject (child of the barel) that rotates while the turret is firing.
:* '''Supported By:''' Nukemod - Children of Shiva, The Sagitta Project

=== Submodel Animation Triggers & Upgrades ===
Trigger Requests:
* Subspace - Performs animation on entrance to supspace, and undoes when a ship comes out of subspace, and acts as a initial position if the "mission takes place in subspace" flag is set.
*Weapon Fire - Performs animation when weapon is fired and undoes it before the weapon can fire again.
*Sexp - Animation triggered by sexp.
*Flight Control - Triggered by the the activation, toggle or motion of a particular flight control.
Requested Upgrades:
*Support for submodel translation within the submodel animation code. (It *can* already be done, but only with scripting)
*Support for "model-relative" movement in addition to "current submodel position-relative" movement that already exists.
*Incremental movement - moves a submodel to the position indicated, but does not undo the motion.
*Glowpoint linking - Make it possible to activate/deactivate/toggel a certain bank/slot of glowpoint(s).
*Counter-rotate option - allow an object to inherit its parent's motion while counter-rotating, usefull for translation effect.
*Increase heirarchy depth instance limit to at least 10 levels of heirarchy.
*Simple linked animation support - Support for animations liked with flight controls and other variable setting ship controls, usefull for making animated cockpit controls, control surfaces, and thrust vectoring nozzels.
:* '''Supported By:''' Nukemod - Children of Shiva, Twisted Infinities, [[Starfox:_Shadows_of_Lylat|Shadows of Lylat]], [[Fringespace]], The Sagitta Project

=== 3D Muzzle Flashes ===
Support for pof based 3d muzzel flashes. perhaps also add variables for scale factor and fade speed.
:* '''Supported By:''' Nukemod - Children of Shiva

=== Arrays and Other Collections ===
Support for FRED using arrays or other collections (or both) in a similar fashion to variables as there is currently no way to directly associate two variables with each other. Obviously some way to search the collection for a certain value would be needed.
:* '''Supported By:''' MindGames, [[The Babylon Project]], Twisted Infinities

=== Warping Without Vortex ===
Adds another checkbox to the arrival and departure cues for ships and wings, to disable rendering of the warp vortex, but will preserve all other aspescts of conventional warping, such as the arrival/departure speeds and deceleration/accelleration. Current option to disable warp rendering, will cause ship to appear and disappear without movement.
:* '''Supported By:''' [[The Babylon Project]], [[Fringespace]]

=== Convergence Firing ===
Also called "X-Firing", allows a weapon to have secondary source effects so that a weapon can appear to gain a charge boost from converging fire from other sources on the model. Could be either a beam or a standard primary. Would require additional data in the weapon table entry, for effects to be used and timing of the secondary prior to the main firing sequence, as well as data on the turret entry in the ships table, indicating co-ords for where the secondary effects will originate, and the number of secondary sources.
:* '''Supported By:''' [[The Babylon Project]], [[Fringespace]]

=== Adjustable Weapon Convergence ===

Add an ability in-game to adjust the distance from the firing points where a fighter/bomber's weapons will converge on a specific point, in distance from the ship (i.e. 100 m, 300 m, etc).

:* '''Supported By:''' [[Beyond the Red Line]], [[Star Wars Conversion]], [[Fringespace]]

=== Cinematic Controls ===

Add in a large number of commands in FRED to make in-mission cut scenes easier to do and with more exact control. The full list is as follows:
* FirePrimary (Ship) (# seconds)
* FireSecondary (Ship) (# times)
* FireCM (Ship) (# times)
* FireTurret (Ship) (Turret) (Target <co-ords or ship>) (# times)
* MoveRotation (Ship) (Degrees)
* MoveSmoothFP (Ship) (Waypoint)
* IgnoreAllButOrders (Ship)
* UseAfterburner (Ship) (# seconds)
* ForwardShields (Ship) (# Times)
* RightShields (Ship) (# Times)
* RearShields (Ship) (# Times)
* LeftShields (Ship) (# Times)
* TogglePrimaryB1 (Ship)
* TogglePrimaryB2 (Ship)
* ToggleSecondaryB1 (Ship)
* ToggleSecondaryB2 (Ship)
* ToggleSecondaryB3 (Ship)
* SetDoublePrimary (Ship)
* SetDoubleSecondary (Ship) (Bank)
* CounterDestroysMissile (Target Ship) (Firing Ship)

:* '''Supported By:''' The Sagitta Project

== In Progress ==
=== Customizable ship types ===
Add a new table (or an addendum to ships.tbl) that would allow modders to turn on and off individual aspects of ship types, as well as define new ones. Type should be settable in the $Flags: variable, just as it is now, and the :V: defaults should be integrated so that they may be overriden by mods.
:* '''Supported By:''' [[The Babylon Project]], Twisted Infinities, [[Fringespace]]

== Partially Complete ==

=== Side Multipart Turrets ===
Support for fully rotating turrets on the sides of ships.
:* '''Supported By:''' [[Beyond the Red Line]], [[The Babylon Project]], [[Wing Commander Saga]], Nukemod - Children of Shiva, [[Star Wars Conversion|Fate of the Galaxy]]

'''Implemented. See [http://www.hard-light.net/forums/index.php/topic,43524.0.html Bobboau's Turret Build]''' ''However'', changes have since been put '''on hiatus''' due to code incompatibilites, in both stable and HEAD builds.

== Implemented ==

=== Flak Screen ===
Ability to set detonation range/time for flak shots so that flak weapons could fire at approaching ships beyond their 'detonation range' thus generating a flak screen in front of the approaching ships with the flak explosions. Preferably with little variance in the exact detonation time as there is always a little variance in normal flak explosions. Beams already support this sort of firing with +range: option. 
[[User:Wanderer|Wanderer]] 10:56, 9 Dec 2005 (GMT)
:* '''Supported By:''' The Apocalypse Project

=== Submodel Animation Triggers & Upgrades ===
*Afterburners - Performs animation when afterburners are used and undoes the anumation when they go off.
*Turret Fire - Performs animation when a particular turret is fired and undoes it before the turret can fire again.

=== Muzzle Flashes and Turrets ===
Extented support for muzzle flashes so that all turreted weapons could use the muzzle flashes.
:* '''Supported By:''' [[Starfox:_Shadows_of_Lylat|Shadows of Lylat]], Twisted Infinities

=== Limited Sensor Range For Non-Primitive Sensors ===
Self-explanatory. Implemented, see [[SCP SEXPs#radar set max range|Radar set max range]]. [[User:Shade|Shade]] 23:52, 17 August 2007 (CDT)
:*'''Supported By:''' Starforce

Multimedia Files

2007-09-20T23:22:00Z

Bruce89: fix title

The FreeSpace 2 Open engine is able to use several different '''mediamedia file formats''' for audio, animation and video playbacks. Retail FreeSpace 2 used the [[Wikipedia:Wav|.WAV]] and '''.ANI''' file formats, but the currently the FreeSpace 2 Open supports several [[Wikipedia:Ogg|.OGG]] container files as well. Support for [[Wikipedia:Mp3|.MP3]] file format was removed in favor of the .OGG. Game engine also supports special '''.EFF''' animations.

==OGG==
'''.OGG''', or Ogg (see [[Wikipedia:Ogg|Ogg file format]]), is a file format for compressed multimedia files and a popular competitor to [[Wikipedia:Mp3|.MP3]]. Unlike MP3, Ogg uses an open-source, open-standard format and a permissive license, both of which allow it to be incorporated into the FS2_Open source code. Also unlike MP3, Ogg is a [[Wikipedia:Container_format|container format]], meaning that it can contain video data (via the [[Wikipedia:Theora|Theora codec ]]) in addition to audio data (via the [[Wikipedia:Vorbis|Vorbis codec]]).

Since Ogg delivers significantly smaller file sizes than [[Wikipedia:Wav|.WAV]], while retaining substantially the same level of audio quality, it is becoming more and more frequently used in FSO-targeted mods. Ogg is not, however, a lossless format -- i.e., it is not possible to exactly reconstruct the original data from an .OGG file because some is "lost" in the conversion process. This is not usually a problem, however, because a high-quality .OGG file is usually indistinguishable from the source. The lossless counterpart to Ogg Vorbis is [[Wikipedia:Free_Lossless_Audio_Codec|.FLAC]], which can be contained in Ogg also.

Vorbis uses a quality parameter between -1 and 10 as a measure of quality. 5 is the default, giving around 160kbps. The higher the number, the higher the quality, but anything over 5 is probably pointless.

Audacity and Goldwave are two popular programs that allow .WAV files to be converted to .OGG Vorbis audio. Audacity is Free Software, while Goldwave is shareware that ceases to function after a period of time. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

==WAV==
The most common sound file format. WAVs are uncompressed and take up a larger amount of space than almost any other sound file type, so consider converting them to the [[*.OGG|.OGG]] format (supported only by SCP) before including them in your campaign. Audacity and Goldwave are two examples of programs that can make this conversion. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

==ANI==
FreeSpace uses the .ANI format for animation effects. It can be used either for an effect (explosions, etc.), an interface animation, or as a ship texture.
*[http://www.swooh.com/lorenzo/files/aniview11.exe AniView, an ANI-viewing utility]
*[http://www.swooh.com/lorenzo/files/anib32b2.exe AniBuilder, a utility that can create ANI files out of a series of 16 bit images]

===Creating an ANI file===

Using AniBuilder (link provided above), one can create new .ANI files from .AVI movies.

To create your own .ANI:

#Set up a scene in a 3D animation program or in FreeSpace. Volition used [[Wikipedia:3ds_Max|3ds Max]] (an expensive modeling program) for their animations.
#Using a free recording software such as for example [http://www.planetgamecam.com GameCam] to record the scene.
#Use for example [http://www.radgametools.com/bnkdown.htm Bink] to convert the AVI into a series of 16-bit (or less) PCX files, as AniBuilder will not accept non-PCX images, or images of more than 16 bit color depth.
#Use AniBuilder to convert the PCX files to an ANI.

==EFF==
FreeSpace 2 uses the .EFF ASCII format text files to store information about animated effects. These animated effects can be used for various effects such as in game animations and animated textures. Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

===Creation of EFF animation===
*For EFF animation all the individual frames of the animation have to be present in one of the [[Graphic Files|graphic file formats]] supported by the game engine.
*All files related to the .EFF animation have to named so that the name of actual .EFF animation forms the basic structure of the filename.
**'''Graphic files''' add the 4 digit number - that identifies the frame where the file is used - after the animation name, starting from 0 (example_0000.dds, example_0001.dds etc.)
**'''ASCII file''' contains the information of the animation (example.eff)

===Contents of .EFF file===

====$Type:====
*Defines the file format of the graphics file used for the .EFF animation
*Syntax: '''''String''''', for example ''DDS''

====$Frames:====
*Defines the length of the number of the frames in the animation
*Syntax; '''''Integer'''''

====$FPS:====
*Used ''optionally'' to define the '''frames per second''' value for the animation
*Syntax: '''''Integer'''''

====Example====

Let's say you have three .dds (tga and pcx are also acceptable) files (named 1_000, 1_0001, and 1_0002) you want to make into an animation, but you don't want to use anibuild and therefore comprimise quality.

Your .eff file would be like this:

Filename (the filename, not information to be entered. This must match up with characters before _xxxx in frames): 1.eff

$Type: DDS
$Frames: 3
$FPS: 5

This .eff effect file would display one frame after another at 5 frames a second, skipping back to the beginning at the end. Please note that .eff cannot be used for streaming files (head animations, icons, mainhall, cbanis, ect.) and is meant ONLY for weapon/explosion effects and animated textures.

[[Category:File Types]]

Multimedia Files

2007-09-20T23:21:33Z

Bruce89: english language

The FreeSpace 2 Open engine is able to use several different '''mediamedia file formats''' for audio, animation and video playbacks. Retail FreeSpace 2 used the [[Wikipedia:Wav|.WAV]] and '''.ANI''' file formats, but the currently the FreeSpace 2 Open supports several [[Wikipedia:Ogg|.OGG]] container files as well. Support for [[Wikipedia:Mp3|.MP3]] file format was removed in favor of the .OGG. Game engine also supports special '''.EFF''' animations.

==OGG==
'''.OGG''', or Ogg (see [[Wikipedia:Ogg|Ogg file format]]), is a file format for compressed multimedia files and a popular competitor to [[Wikipedia:Mp3|.MP3]]. Unlike MP3, Ogg uses an open-source, open-standard format and a permissive license, both of which allow it to be incorporated into the FS2_Open source code. Also unlike MP3, Ogg is a [[Wikipedia:Container_format|container format]], meaning that it can contain video data (via the [[Wikipedia:Theora|Theora codec ]]) in addition to audio data (via the [[Wikipedia:Vorbis|Vorbis codec]]).

Since Ogg delivers significantly smaller file sizes than [[Wikipedia:Wav|.WAV]], while retaining substantially the same level of audio quality, it is becoming more and more frequently used in FSO-targeted mods. Ogg is not, however, a lossless format -- i.e., it is not possible to exactly reconstruct the original data from an .OGG file because some is "lost" in the conversion process. This is not usually a problem, however, because a high-quality .OGG file is usually indistinguishable from the source. The lossless counterpart to Ogg Vorbis is [[Wikipedia:Free_Lossless_Audio_Codec|.FLAC]], which can be contained in Ogg also.

Vorbis uses a quality parameter between -1 and 10 as a measure of quality. 5 is the default, giving around 160kbps. The higher the number, the higher the quality, but anything over 5 is probably pointless.

Audacity and Goldwave are two popular programs that allow .WAV files to be converted to .OGG Vorbis audio. Audacity is Free Software, while Goldwave is shareware that ceases to function after a period of time. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

==WAV==
The most common sound file format. WAVs are uncompressed and take up a larger amount of space than almost any other sound file type, so consider converting them to the [[*.OGG|.OGG]] format (supported only by SCP) before including them in your campaign. Audacity and Goldwave are two examples of programs that can make this conversion. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

==ANI==
FreeSpace uses the .ANI format for animation effects. It can be used either for an effect (explosions, etc.), an interface animation, or as a ship texture.
*[http://www.swooh.com/lorenzo/files/aniview11.exe AniView, an ANI-viewing utility]
*[http://www.swooh.com/lorenzo/files/anib32b2.exe AniBuilder, a utility that can create ANI files out of a series of 16 bit images]

===Creating an ANI file===

Using AniBuilder (link provided above), one can create new .ANI files from .AVI movies.

To create your own .ANI:

#Set up a scene in a 3D animation program or in FreeSpace. Volition used [[Wikipedia:3ds_Max|3ds Max]] (an expensive modeling program) for their animations.
#Using a free recording software such as for example [http://www.planetgamecam.com GameCam] to record the scene.
#Use for example [http://www.radgametools.com/bnkdown.htm Bink] to convert the AVI into a series of 16-bit (or less) PCX files, as AniBuilder will not accept non-PCX images, or images of more than 16 bit color depth.
#Use AniBuilder to convert the PCX files to an ANI.

==EFF==
FreeSpace 2 uses the .EFF ASCII format text files to store information about animated effects. These animated effects can be used for various effects such as in game animations and animated textures. Please note that this is a fso feature and is not supported by the original retail FreeSpace 2.

===Creation of EFF animation===
*For EFF animation all the individual frames of the animation have to be present in one of the [[Graphic Files|graphic file formats]] supported by the game engine.
*All files related to the .EFF animation have to named so that the name of actual .EFF animation forms the basic structure of the filename.
**'''Graphic files''' add the 4 digit number - that identifies the frame where the file is used - after the animation name, starting from 0 (example_0000.dds, example_0001.dds etc.)
**'''ASCII file''' contains the information of the animation (example.eff)

===Contents of .EFF file===

====$Type:====
*Defines the file format of the graphics file used for the .EFF animation
*Syntax: '''''String''''', for example ''DDS''

====$Frames:====
*Defines the length of the number of the frames in the animation
*Syntax; '''''Integer'''''

====$FPS:====
*Used ''optionally'' to define the '''frames per second''' value for the animation
*Syntax: '''''Integer'''''

====Example=====

Let's say you have three .dds (tga and pcx are also acceptable) files (named 1_000, 1_0001, and 1_0002) you want to make into an animation, but you don't want to use anibuild and therefore comprimise quality.

Your .eff file would be like this:

Filename (the filename, not information to be entered. This must match up with characters before _xxxx in frames): 1.eff

$Type: DDS
$Frames: 3
$FPS: 5

This .eff effect file would display one frame after another at 5 frames a second, skipping back to the beginning at the end. Please note that .eff cannot be used for streaming files (head animations, icons, mainhall, cbanis, ect.) and is meant ONLY for weapon/explosion effects and animated textures.

[[Category:File Types]]

User talk:Akenbosch

2007-09-20T23:17:10Z

Bruce89:

Does not understand the importance of the shift and period keys.
[[User:Supernova|Supernova]] 18:05, 20 September 2007 (CDT)
: Indeed, I shall fix the errors so far. [[User:Bruce89|Bruce89]] 18:17, 20 September 2007 (CDT)

User:Akenbosch

2007-09-20T23:16:38Z

Bruce89: moved

User talk:Akenbosch

2007-09-20T23:16:28Z

Bruce89: move to talk

Does not understand the importance of the shift and period keys.
[[User:Supernova|Supernova]] 18:05, 20 September 2007 (CDT)

SCv Moloch

2007-09-14T13:21:23Z

Bruce89: fixes

{{FS12_Ships}}
{{shipimage|image=[[Image:moloch320x240.jpg]]|caption=The SCv Moloch}}

==Description:==

===FS2 Demo Tech Room Description===
This big Shivan Mama is loaded with turrety goodness. Moloch is the name of another larger form of Aeshma, a many armed, many weaponed Indian goddess.

===FS2 Tech Room Description===
Only one class of Shivan ship is classified as a corvette - the SCv Moloch class. Though they're physically as large as the GTCv Deimos class, Molochs do not seem to pack the same punch. They are far more deadly than any Shivan cruisers, however.

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Corvette
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 30.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 80 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 724 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Turret Laser]]
| 5
|- align="center"
| [[Standard Flak]]
| 3
|- align="center"
| [[Heavy Flak]]
| 1
|- align="center"
| [[GTM Piranha|Piranha]]
| 1
|- align="center"
| [[Shivan Cluster]]
| 1
|- align="center"
| [[MX-52]]
| 2
|- align="center"
| [[SRed|Small Red Beam]]
| 3
|}
===Veteran Comments===
{{comment|''Moloch is a poor excuse for a Shivan vessel and an even poorer excuse for a corvette. A Lilith poses more threat to allied forces than this big target. Its only saving grace is its ability to carry fighters, but it's never enough to turn the tide of battle.''

''The Moloch is an opponent to be taken seriously, despite all the negative commentary, and the statement a [[GTCv Deimos|Deimos]] can take one on successfully is somewhat debateable. Shivans use much more effective (and faster-cycling) direct-fire beams, of which the Moloch has three [[SRed]]-types. Like most Shivan capital craft, its antifighter defenses are rather less impressive then those of a comparable Terran ship, but the Moloch's defenses are nonetheless probably the best, pound for pound, of any Shivan capital craft, and its well-posistioned flak guns can be very dangerous to the unwary.''

''Some people think of the Moloch as a joke, but the joke is on you when its fighters come out and tear you to pieces. The SCv Moloch is not a vessel to take lightly. It may not be able to hurt you as badly as the [[GTCv Deimos|Terran Deimos]], but that's what its fighter bay is for.''

''The fighterbay is never used in the [[Portal:Freespace 2|Freespace 2]] campaign. The Moloch has by far the worst firepower and anti-fighter defenses of any corvette, but that doesn't mean it doesn't have a niche. The Moloch is a cruiser hunter, easily capable of destroying one of the best cruisers in the game, the [[GTC Aeolus|Aeolus]], which the Moloch survives without suffering any real damage. However, when faced with a cruiser and a wing of heavy assult fighters, as in the demo mission '''[[Crisis in Capella]]''' the Moloch is in deep trouble, provided the fighters can destroy its main beam turrets quickly enough (they can). Under few circumstances will a Moloch prevail over a [[GTCv Deimos]], unless the Moloch launches bombers, the Deimos's many [[Standard Flak|flak guns]] and [[AAAf|AAA turrets]] add to its total firepower, and although the [[SRed]]s are definitely more accurate, the [[TerSlash]] does 2.2 times the maximum sustained damage, and the [[GTCv Deimos|Deimos]] has four, as opposed to the Moloch's three. However, if the Moloch is a good distance away, its accurate [[SRed]]s will be more effective than the [[TerSlash]] beams of the [[GTCv Deimos|Deimos]]. Still, in a poll, it was found few people actually consider the Moloch superior to the [[GTCv Deimos|Deimos]].''

''The Moloch is not the best of all the corvettes, but it is fairly deadly, and it can do serious damage to a Hecate class Destroyer if you don't pay attention to it.''

''I don't wanna insult anyone, but everybody who says this ship isn't dangerous has never fought it! :) The plating of its turrets is more than poor in comparison to the over corvettes, yes. But:
Firstly: Its anti-fighter missiles can hit yout ''everywhere''. At a Sobek, I can hide beneath the rear side and it won't hit me if I just take out one single flak gun.
Secondly: The convoluted design of the Moloch makes it much more difficult to disarm than a Sobek for example. At the Sobek I can park two klicks above and eliminate almost all of its turrets, including the main beam cannons. At the Moloch the antifighter and beam cannons are evenly spread all over the ship.
My conclusion: Maybe not as good as the Deimos, but definitely better than the Sobek - which is already deadly!
Do not underestimate the Moloch, just because of the distorted image the main campaign gives of it. They also misused the Aeolus!''}}
[[Category:Ship]]

SF Astaroth

2007-09-14T13:19:32Z

Bruce89: missed one

{{FS12_Ships}}
{{shipimage|image=[[Image:astaroth320x240.jpg]]|caption=The SF Astaroth}}

The '''SF ''Astaroth''''' was a Shivan fighter spotted right after the Shivans' resurface in 2367. The ''Astaroth'' was regarded as a poor fighter despite its speed and maneuverability.

==Description==
===FS2 Demo Tech Room Description===
We believe that the Astaroth is a Shivan Harpoon. It has a very high top speed, and its maneuverability is quite good. However, its shield system isn't strong enough to withstand constant fighting for long, which leads us to believe the Astaroth's primary purpose is to destroy enemy bombers.
The Astaroth ranks as a Class B threat.

===FS2 Tech Room Description===
First encountered in Gamma Draconis, the SF Astaroth is a fast, agile fighter that appears to have achieved its maneuverability at the expense of its armor and weaponry. Once the shields of an Astaroth are down, the fighter can be dispatched quickly.

===Developer Notes===
None

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 80.0 - 110.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 155.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 100
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 450
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 24 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Mega Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[GTM Harpoon|Harpoon]]
|- align="center"
| 2nd
| 40
| [[GTM MX-64|MX-64]]
|}

===Veteran Comments===
{{comment|''The Astaroth is similar to the Dragon in most respects, only more annoying. It has a ridiculously small target profile, the smallest of any ship in any Freespace game, and is fast and highly manuverable, making it annoyingly difficult to deal with via primaries. It also has a decent, though not impressive, amount of missiles to back up its lasers, unlike the Dragon. Destroy this ship at range via missiles if at all possible.''

''Very hard to dogfight against. However, a few Harpoons bring it down quickly and painlessly at medium range.''

''A couple of hits from eight banks of [[GTW Prometheus S|Prometheus]] from an [[GTF Erinyes|Erinyes]] will bring this thing down''

''While the SF ''Astaroth'' is very fast and maneuverable, its shielding and armor cannot stand much punishment and it simply lacks adequate weaponry. The ''Astaroth'' kind of reminds me of the Imperial TIE series of fighters in ''Star Wars'', only with shields and missiles.

''The Astaroth has less manoueverability than a Dragon, meaning that it won't run circles around you. And despite the small target profile, it is easier to hit, especially if you approach from the rear where you can tear them up. Also quite weak against harpoons, if the Astaroth's shields are softened up sufficiently, a single Harpoon will punch through this ship like a hot knife through butter, even if it had 100% hull.''
}}
[[Category:Ship]]

SF Astaroth

2007-09-14T13:19:16Z

Bruce89: made a wiki

{{FS12_Ships}}
{{shipimage|image=[[Image:astaroth320x240.jpg]]|caption=The SF Astaroth}}

The '''SF ''Astaroth''''' was a Shivan fighter spotted right after the Shivans' resurface in 2367. The ''Astaroth'' was regarded as a poor fighter despite its speed and maneuverability.

==Description==
===FS2 Demo Tech Room Description===
We believe that the Astaroth is a Shivan Harpoon. It has a very high top speed, and its maneuverability is quite good. However, its shield system isn't strong enough to withstand constant fighting for long, which leads us to believe the Astaroth's primary purpose is to destroy enemy bombers.
The Astaroth ranks as a Class B threat.

===FS2 Tech Room Description===
First encountered in Gamma Draconis, the SF Astaroth is a fast, agile fighter that appears to have achieved its maneuverability at the expense of its armor and weaponry. Once the shields of an Astaroth are down, the fighter can be dispatched quickly.

===Developer Notes===
None

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 80.0 - 110.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 155.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 100
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 450
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 24 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Mega Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[GTM Harpoon|Harpoon]]
|- align="center"
| 2nd
| 40
| [[GTM MX-64|MX-64]]
|}

===Veteran Comments===
{{comment|''The Astaroth is similar to the Dragon in most respects, only more annoying. It has a ridiculously small target profile, the smallest of any ship in any Freespace game, and is fast and highly manuverable, making it annoyingly difficult to deal with via primaries. It also has a decent, though not impressive, amount of missiles to back up its lasers, unlike the Dragon. Destroy this ship at range via missiles if at all possible.''

''Very hard to dogfight against. However, a few Harpoons bring it down quickly and painlessly at medium range.'' 
''A couple of hits from eight banks of [[GTW Prometheus S|Prometheus]] from an [[GTF Erinyes|Erinyes]] will bring this thing down''

''While the SF ''Astaroth'' is very fast and maneuverable, its shielding and armor cannot stand much punishment and it simply lacks adequate weaponry. The ''Astaroth'' kind of reminds me of the Imperial TIE series of fighters in ''Star Wars'', only with shields and missiles.

''The Astaroth has less manoueverability than a Dragon, meaning that it won't run circles around you. And despite the small target profile, it is easier to hit, especially if you approach from the rear where you can tear them up. Also quite weak against harpoons, if the Astaroth's shields are softened up sufficiently, a single Harpoon will punch through this ship like a hot knife through butter, even if it had 100% hull.''
}}
[[Category:Ship]]

SF Mara

2007-09-14T13:18:13Z

Bruce89: correct the correction

{{FS12_Ships}}
{{shipimage|image=[[Image:mara320x240.jpg]]|caption=The SF Mara}}

The extensively used '''SF ''Mara''''' was one of the [[Shivans|Shivan]] fighters used during their [[Second Shivan Incursion|second invasion]]. The Mara was fast, maneuverable, tough, and relatively small. The craft also had a superior secondary weapon capability that could even compete with that of a bomber-type. Like all Shivan fighters, the Mara was extremely well-shielded and its armoring was somehow superior to that of a typical Shivan fighter. Although it was still weaker than a Terran fighter's, its heavy shielding and swiftness made the Mara a formidable opponent in a dogfight. However, despite its specifications as a fighter-type, Maras were still impractical against larger vessels, thus they were often tasked with bomber escort.

It is the Mara class that was first designated of all Second Incursion-era Shivan fighters after a group of Mara fighters were detected emerging from the [[Knossos]] subspace portal in [[Gamma Draconis]]. The fighters, with the help of a [[SC Rakshasa|''Rakshasa''-class cruiser]], easily took down the patrolling GTVA force.

A special [[Special Operations Command|SOC]] managed to capture a quad of these fighters, and engineers retrofitted them for [[Terran]] use. Later, they were used in another SOC operation that discovered the actual size of the Shivan fleet, as well as a third Knossos device.

==Description:==
===FS2 Demo Tech Room Description===
''Seems to be inaccurate''
The Mara seems to be a Shivan heavy attack fighter. It is not as maneuverable as other Shivan fighters, but it packs quite a punch, and it is very resistant to our weaponry. Most often they have been used in attacking our supply convoys and transports.
Treat the Mara as a Class C threat.

===FS2 Tech Room Description===
The SF Mara class of Shivan fighters was first encountered by the GTC Vigilant while patrolling the Gamma Draconis jump node in the Capella system. All other information concerning the Mara is classified level Psi.

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 70.0 - 78.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 120.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 200
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 620
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| ~ 20 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Mega Laser]]
|- align="center"
| 2nd
| 2
| [[Shivan Heavy Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 80
| [[GTM Trebuchet|Trebuchet]]
|- align="center"
| 2nd
| 80
| [[GTM Hornet|Hornet]]
|}
===Veteran Comments===
{{comment|It would be a disservice to the Mara to say it's just a Herc II with the speed and manueverability of the Perseus. But that's the Mara in a nutshell.

My favorite fighter in the game. Sure, you could say the Erinyes has 8 gun banks to the Mara's 4, but the Mara has nearly twice the missile capacity and is significantly faster and more manueverable.

The one disadvantage of the Mara is the fairly large target profile it presents to the enemy, but its combination of maneouverability, firepower and durability easily makes up for this.

The "Terran Mara" you use in [[Into the Lion's Den]] is slightly superior to the Shivan version.}}

[[Category:Ship]]

GVC Mentu

2007-09-14T13:16:58Z

Bruce89: its was actually correct

{{FS12_Ships}}
{{shipimage|image=[[Image:mentu320x240.jpg]]|caption=The GVC Mentu}}

==Description:==

===FS2 Tech Room Description===
The GVC Mentu cruiser is the lightest of the new Vasudan warships. Following the Great War, allied scientists developed the beam cannons that now serve as the primary armaments of today's GTVA warships. Rather than modify existing ships, the Vasudans developed new designs to mount these weapons. The Mentu's 16 turrets include heavy beam cannons for duking it out with other warships, as well as AAA and flak turrets to fend off smaller craft. The GVC Somtus and the GVC Mycerinus recently demonstrated the strength of the Mentu against NTF forces in Epsilon Pegasi.
===FS2 MTS Model Description===
The GVC Mentu cruiser is the lightest of the next generation of Vasudan warships. Following the Great War, allied scientists developed the beam cannons that now serve as the primary armaments of today’s GTVA warships. Rather than modify existing ships, the Vasudans developed new designs to mount these weapons. The Mentu improves on the old PVC Aten cruiser in size and firepower. Its 16 turrets include heavy beam cannons for duking it out with other warships, as well as AAA and flak turrets to fend off fighters and bombers. The GVC Ibis and the GVC Mycerinus recently demonstrated the strength of the Mentu against rebel forces in Epsilon Pegasi.

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Cruiser
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 35.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 60 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 322 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 7
|- align="center"
| [[Terran Huge Turret]]
| 2
|- align="center"
| [[GTW Subach HL-7|Subach HL-7]]
| 1
|- align="center"
| [[Standard Flak]]
| 3
|- align="center"
| [[AAAf|Anti-Fighter Beam]]
| 3
|}

===Veteran Comments===
{{comment|''The Mentu is victim of poor weapons placement. Its main weaponry, flaks and AAA beams, is pointed upwards; attack from below, and pay the most attention to enemies below. It is also worth noting that, despite the techroom description, the Mentu mounts no anticapital beams.''

''I think the horrible [[GVC Aten]] has every right to bear no anti-warship beam cannons, but I think the Mentu should mount something, even a single [[SVas]] or [[VSlash]] would be better than nothing, because even with two of either of these weapons, an [[GTC Aeolus|Aeolus]] can kill this cruiser, without them, there is no fight.''

''With only small modifications in its weaponry the Mentu could have been one of the best (maybe THE best) cruisers in the game. If you make turrets one and two SVas and 15 and 16 standard flak, its very effective. But with its standard armament the Mentu is really a waste, and that's a great pity for the best armored cruiser after the Lilith.''}}

[[Category:Ship]]

Template:Disambiguation

2007-09-11T22:28:51Z

Bruce89: english

<includeonly>[[Category:Disambiguation pages|{{PAGENAME}}]]</includeonly>
<noinclude>[[Category:Templates|Disambiguation]]</noinclude>

<includeonly>'''''{{PAGENAME}}''''' can mean one of the following things:</includeonly>

Herc

2007-09-11T22:28:10Z

Bruce89: fix

{{disambiguation}}
*[[GTF Hercules]]- A Terran heavy fighter first seen in FS1
*[[GTF Hercules Mark II]]- A Terran heavy fighter first seen in FS2

GVD Typhon

2007-09-11T22:26:14Z

Bruce89: fixes

{{FS12_Ships}}
{{shipimage|image=[[Image:typhon320x240.jpg]]|caption=The GVD Typhon}}

When the first of the '''PVD ''Typhon'''''-class of destroyers was deployed during the [[Terran-Vasudan War]], it devastated the [[Terrans]]. At that time, the Typhon was the apex of warship design and only shortly after its first deployment could the Terrans match its power with the [[GTD Orion|GTD ''Orion'']].

When the [[Shivans]] [[Great War|first emerged]], both races deployed the best of their forces. For the Vasudans, their task force was led by the [[PVD Pinnacle|PVD ''Pinnacle'']]. One such vessel, the [[PVD Anvil|PVD ''Anvil'']] served as the flagship for the dissident group of Vasudan rebels, the [[Hammer of Light]].

After the Great War ended, many ''Typhon''-class ships were armed with beam and flak cannons and, in a limited number, saw action during the [[Second Shivan Incursion|Shivans' return]] in 2367. However, the destroyers power grid was ill suited to these new weapons and its forebear, the [[GVD Hatshepsut|GVD ''Hatshepsut'']], was superior and every possible aspect.

==Description:==

===FS1 Tech Room Description===
Where the Aten cruiser failed, the Typhon succeeded well past expectations. The Typhon is an incredible work of engineering and the model of Vasudan technology. When the first one was sighted at the Vega Engagement, it was laughed at by our technicians as a foolish display of non utilitarian design. The subsequent destruction of the GTD Eisenhower and the total decimation of the 4th fleet changed their minds very quickly. The Typhon should never be underestimated. It wields massive weaponry, and has more armor plating than any Terran Destroyer. Its only known weakness is its turret armor, which is significant, but lower than expected. In the two years since this ship first appeared, we have only managed to destroy two of them.

The Typhon is considered a Class A threat to any ships within the same system. Do not engage without backup.

===FS2 Tech Room Description===
The GVD Typhon was the height of Vasudan military technology when it appeared to face Terran forces during the early days of the Terran-Vasudan War. The first Typhon was sighted at the Vega Engagement and quickly destroyed the GTD Eisenhower and much of the 4th fleet. The more recent Hatshepsut class of destroyers is larger and wields a deadlier array of armaments, but the Typhon is still a match for almost any foe. Up to 30 wings of fighters or bombers can be housed within its docking bays, ready to engage at a moment's notice.

==Noteable Ships of this Class==

*''Parlimentary/Galatic Vasudan Navy''
*[[GVD Hedetet|GVD ''Hedetet'']]
*[[PVD Hope|PVD ''Hope'']]
*[[PVD Pinnacle|PVD ''Pinnacle'']]

''Hammer of Light''

*[[HLD Anvil|HLD ''Anvil'']]
*[[HLD Prophecy|HLD ''Prophecy'']]

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Destroyer
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 15.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 120 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 2153 m
|-
| '''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| 120 fightercraft(?) (30 wings)
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Freespace 1'''
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Huge Turret]]
| 5
| [[Terran Huge Turret]]
| 2
|- align="center"
| [[Terran Turret]]
| 4
| [[Standard Flak]]
| 5
|- align="center"
| [[FighterKiller]]
| 6
| [[FighterKiller]]
| 4
|- align="center"
|
|
| [[AAAf|Anti-Fighter Beam]]
| 2
|- align="center"
|
|
| [[BVas|Big Vasudan Beam]]
| 2
|}

===Veteran Comments===
{{comment|''The Typhon poses a threat to fightercraft much more then the Orion. In FS1 it mounts a number of rather dangerous [[FighterKiller]] missile batteries; in FS2 it has acquired [[Standard Flak|flak guns]] to supplement its now-marginally effective missile batteries. Treat it carefully at first, but if you can identify and remove the more dangerous turrets, the Typhon becomes much less of a problem.''

''With 20,000 more hit points, the Typhon is better-armored than the [[GTD Orion|GTD Orion]], but the Orion has a much stronger broadside- 66% more turrets in FS1, and 3 times as many beams in FS2. Although the Typhon's anti-bomber/fighter defenses are better than its [[Terran]] equivalent, a determined attack by heavy fighters could wipe out 90% of those defenses with minimal casualties, in [[Portal:Freespace 1|Freespace 1]] or [[Portal:Freespace 2|2]]. The Typhon's only real advantage in either game is two more fighter squadrons.''

''But perhaps the Vasudans are smart. Bombers are the real capship killers, and the Typhon's impressive 30 wings and better anti-fighter armament would give it an edge in an FS1 battle versus Orion. Particularly in a battle with FS1-style unshielded fighters, the Orion's blob turrets can be dodged, but the Typhon's [[FighterKiller|FighterKiller]] aren't as easy to shake off. Despite the advances in capital ship defenses in FS2, large ships are still sitting ducks against a real fighter/bomber attack, like in most space shooters.''

''If you read the table file for the Typhon in FS1, it says on the [[FighterKiller]] entries that it "should be [[Vasudan Flux Cannon]]" These weapons do 500 damage to an Orion, and in a battle with [[Vasudan Flux Cannon]]s, I think that the Typhon would have a significant edge over the Terran [[Orion]]. However, without [[FighterKiller]]s, it rather sucks against bombers.''}}

[[Category:Ship]]

PVD Hope

2007-09-11T22:21:33Z

Bruce89: use bloody template

{{Unique ship|[[GVD Typhon|PVD ''Typhon'']]|[[The Great War]], possibly the [[The 14-Year War|14-year war]]|''Unknown''|[[Last Hope]] ([[Exodus]] according to an FS1 multiplayer campaign)|Fought in [[The Great War]]|''Unknown''|Hope}}

The "most beloved destroyer of the Vasudan people", the '''PVD ''Hope'' ''' fought on the front line of the [[Great War]] against the Shivans. FreeSpace 1 presents two versions of the ''Hope'' 's history. The main campaign only mentions the ''Hope'' once; it jumps to [[Beta Aquilae]] after an intense battle in [[Antares]] and is attacked by two Shivan cruisers and several waves of bombers. By contrast, an FS1 multiplayer coop campaign portrays the Hope's fighters performing the same role that the single-player Terran did in [[Exodus]], [[Last Hope]], and [[A Failure to Communicate]].

[[Category:Unique ships|Hope]]

The Procyon Insurgency

2007-09-11T22:17:35Z

Bruce89: fixes to the fixes

{{spoiler|The Procyon Insurgency}}

==General Info==
'''Author:''' CP5670

'''Missions:''' 17

'''Mods included:'''

*[[GVB Amun Mark II]]
*[[AJ Arkhtori]]
*[[GVF Reshef]]
*[[PCD Saturn]]
*Vulcan cannon
*Phalanx rifle
*''Procyon Confederacy ships have their GT/GV prefixes renamed to PC''
*''Additions to and reallocations of sound files, to enhance audio effects''

==Description==

''From the campaign [http://pi.hard-light.net/about.htm website]'':

The Procyon Insurgency (PI) is a high quality 17 mission campaign for Freespace 2. It is set 18 to 20 months after the end of the main Freespace 2 campaign, near the end of the year 2368. As a new Vasudan pilot recently recruited into the ranks of the GTVA, you are assigned to the crew of the GVD Sekham in Polaris as the Alliance attempts to eradicate the rapidly propagating Procyon Confederal Autonomy. See the storyline section for details.

PI is mostly a no-frills campaign that emphasizes quality mission design, with fun and balanced gameplay and a complex and realistic plot. The missions have all been heavily playtested, on the order of 20 to 50 times each, and bugs should be at an absolute minimum. The campaign utilizes many new features added into the game from the Freespace Source Code Project and requires a fairly recent version of FS2 Open.

I (CP5670) originally started the project in June 2001 as a four mission mini-campaign, although there have been a lot of major changes since then and the final product has little in common with my original ideas. It has been the culmination of nearly 1000 hours of work spread out over the years.

==Player comments==

This is a good length high-quality campaign, arguably the best ever to be created for FreeSpace. A thick plot, challenging missions, and a good deal of originality. Warning, however: if you don't like replaying missions, stay on the lower difficulty levels.

==Links==

[http://pi.hard-light.net/walk.htm Website]

[http://pi.hard-light.net/dl.htm Download page]

[[Category:User-made_Campaigns]]

Graphic Files

2007-09-11T12:04:17Z

Bruce89: minor stuff

FreeSpace 2 Open is able to use several different '''graphic file formats'''. These include the [[Wikipedia:PCX|.PCX file format]] which was originally supported by the retail FreeSpace 2. In addition to this the game is able to make use of several other graphic file formats which are [[Wikipedia:JPEG|.JPG]], [[Wikipedia:Truevision_TGA|.TGA]] and more recently [[Wikipedia:DirectDraw_Surface|.DDS]] file formats. Of these the .DDS file format is the most often used with FreeSpace 2 Open modifications.

For animated effects and textures see [[Multimedia Files]].

==DDS==
DDS is a compressed texture format that is supported by FreeSpace SCP. Any modeler should use DDS for their textures as much as possible, as it is 1/2 the size of a PCX and 1/8 the size of a TGA image.

===Background===
The DDS File format was created by Microsoft for its DirectX graphics API, however, it has become a general format for textures and is supported by OpenGL (the graphics API the FS2 SCP uses). The official description of DDS is "The Microsoft DirectDraw Surface (DDS) file format is used to store textures and cubic environment maps, both with and without mipmap levels. This format can store uncompressed and compressed pixel formats, and is the preferred file format for storing DXTn compressed data."

===Tools===
Several tools exist for working with this format, besides any tools created by the FS2 SCP team. These tools are detailed at the [http://developer.nvidia.com/object/nv_texture_tools.html nVidia website] and should be useful.

===Usage of DDS===
The primary note to any texturer using the DDS file format is that even if DDS enables you to have twice the texture size, doesn't mean you should use all the available memory.

==JPG==

==PCX==

PCX were the first of the graphic files introduced to FreeSpace. Generally speaking, these files are among the largest graphic files used in FreeSpace. However, a lot of modders still use PCXs since it is the most compatible graphic file known inside FreeSpace. Earlier the TGA and JPG format files caused some graphical issues in game as it needed the command line option '''-jpgtga''' (see [[Command-Line_Reference]]) to work. However this command line option is no longer in use and game loads TGA and JPG format files automatically.

===Tools===
PCX is a image format that is less well supported in the standard imaging editing software such as Microsoft Paint. However, advanced image editing programs such as Photoshop or the GIMP can easily save PCX files.

==TGA==

[[Category:File Types]]

Multimedia Files

2007-09-11T11:59:34Z

Bruce89: fixes

The FreeSpace 2 Open engine is able to use several different '''mediamedia file formats''' for audio, animation and video playbacks. Retail FreeSpace 2 used the [[Wikipedia:Wav|.WAV]] and '''.ANI''' file formats, but the currently the FreeSpace 2 Open supports several [[Wikipedia:Ogg|.OGG]] container files as well. Support for [[Wikipedia:Mp3|.MP3]] file format was removed in favor of the .OGG. Game engine also supports special '''.EFF''' animations.

==OGG==
'''.OGG''', or Ogg (see [[Wikipedia:Ogg|Ogg file format]]), is a file format for compressed multimedia files and a popular competitor to [[Wikipedia:Mp3|.MP3]]. Unlike MP3, Ogg uses an open-source, open-standard format and a permissive license, both of which allow it to be incorporated into the FS2_Open source code. Also unlike MP3, Ogg is a [[Wikipedia:Container_format|container format]], meaning that it can contain video data (via the [[Wikipedia:Theora|Theora codec ]]) in addition to audio data (via the [[Wikipedia:Vorbis|Vorbis codec]]).

Since Ogg delivers significantly smaller file sizes than [[Wikipedia:Wav|.WAV]], while retaining substantially the same level of audio quality, it is becoming more and more frequently used in FSO-targeted mods. Ogg is not, however, a lossless format -- i.e., it is not possible to exactly reconstruct the original data from an .OGG file because some is "lost" in the conversion process. This is not usually a problem, however, because a high-quality .OGG file is usually indistinguishable from the source. The lossless counterpart to Ogg Vorbis is [[Wikipedia:Free_Lossless_Audio_Codec|.FLAC]], which can be contained in Ogg also.

Vorbis uses a quality parameter between -1 and 10 as a measure of quality. 5 is the default, giving around 160kbps. The higher the number, the higher the quality, but anything over 5 is probably pointless.

Audacity and Goldwave are two popular programs that allow .WAV files to be converted to .OGG Vorbis audio. Audacity is Free Software, while Goldwave is shareware that ceases to function after a period of time. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

==WAV==
The most common sound file format. WAVs are uncompressed and take up a larger amount of space than almost any other sound file type, so consider converting them to the [[*.OGG|.OGG]] format (supported only by SCP) before including them in your campaign. Audacity and Goldwave are two examples of programs that can make this conversion. [http://www.rarewares.org/ogg-oggdropxpd.php oggdropXPd] is an useful drag-and-drop encoder.

==ANI==
FreeSpace uses the .ANI format for animation effects. It can be used either for an effect (explosions, etc.), an interface animation, or as a ship texture.
*[http://www.swooh.com/lorenzo/files/aniview11.exe AniView, an ANI-viewing utility]
*[http://www.swooh.com/lorenzo/files/anib32b2.exe AniBuilder, a utility that can create ANI files out of a series of 16 bit images]

===Creating an ANI file===

Using AniBuilder (link provided above), one can create new .ANI files from .AVI movies.

To create your own .ANI:

#Set up a scene in a 3D animation program or in FreeSpace. Volition used [[Wikipedia:3ds_Max|3ds Max]] (an expensive modeling program) for their animations.
#Using a free recording software such as for example [http://www.planetgamecam.com GameCam] to record the scene.
#Use for example [http://www.radgametools.com/bnkdown.htm Bink] to convert the AVI into a series of 16-bit (or less) PCX files, as AniBuilder will not accept non-PCX images, or images of more than 16 bit color depth.
#Use AniBuilder to convert the PCX files to an ANI.

==EFF==
FreeSpace 2 uses the .EFF ASCII format text files to store information about animated effects. These animated effects can be used for various effects such as in game animations and animated textures.

===Creation of EFF animation===
*For EFF animation all the individual frames of the animation have to be present in one of the [[Graphic Files|graphic file formats]] supported by the game engine.
*All files related to the .EFF animation have to named so that the name of actual .EFF animation forms the basic structure of the filename.
**'''Graphic files''' add the 4 digit number - that identifies the frame where the file is used - after the animation name, starting from 0 (example_0000.dds, example_0001.dds etc.)
**'''ASCII file''' contains the information of the animation (example.eff)

===Contents of .EFF file===

====$Type:====
*Defines the file format of the graphics file used for the .EFF animation
*Syntax: '''''String''''', for example ''DDS''

====$Frames:====
*Defines the length of the number of the frames in the animation
*Syntax; '''''Integer'''''

====$FPS:====
*Used ''optionally'' to define the '''frames per second''' value for the animation
*Syntax: '''''Integer'''''

[[Category:File Types]]

Multimedia Files

2007-09-11T11:55:48Z

Bruce89: add note on quality

The FreeSpace 2 Open engine is able to use several different '''mediamedia file formats''' for audio, animation and video playbacks. Retail FreeSpace 2 used the [[Wikipedia:Wav|.WAV]] and '''.ANI''' file formats, but the currently the FreeSpace 2 Open supports several [[Wikipedia:Ogg|.OGG]] container files as well. Support for [[Wikipedia:Mp3|.MP3]] file format was removed in favor of the .OGG. Game engine also supports special '''.EFF''' animations.

==OGG==
'''.OGG''', or Ogg (see [[Wikipedia:Ogg|Ogg file format]]), is a file format for compressed multimedia files and a popular competitor to [[Wikipedia:Mp3|.MP3]]. Unlike MP3, Ogg uses an open-source, open-standard format and a permissive license, both of which allow it to be incorporated into the FS2_Open source code. Also unlike MP3, Ogg is a [[Wikipedia:Container_format|container format]], meaning that it can contain video data (via the [[Wikipedia:Theora|Theora codec ]]) in addition to audio data (via the [[Wikipedia:Vorbis|Vorbis codec]]).

Since Ogg delivers significantly smaller file sizes than [[Wikipedia:Wav|.WAV]], while retaining substantially the same level of audio quality, it is becoming more and more frequently used in FSO-targeted mods. Ogg is not, however, a lossless format -- i.e., it is not possible to exactly reconstruct the original data from an .OGG file because some is "lost" in the conversion process. This is not usually a problem, however, because a high-quality .OGG file is usually indistinguishable from the source. A popular lossless alternative to Ogg Vorbis is [[Wikipedia:Free_Lossless_Audio_Codec|.FLAC]].

Vorbis uses a quality parameter between -1 and 10 as a measure of quality. 5 is the default, giving around 160kbps. The higher the number, the higher the quality, but anything over 5 is probably pointless. [[User:Bruce89|Bruce89]] 06:55, 11 September 2007 (CDT)

Audacity and Goldwave are two popular programs that allow .WAV files to be converted to .OGG Vorbis audio. Audacity is freeware, while Goldwave is shareware that ceases to function after a period of time.

==WAV==
The most common sound file format. WAVs are uncompressed and take up a larger amount of space than almost any other sound file type, so consider converting them to the [[*.OGG|.OGG]] format (supported only by SCP) before including them in your campaign. Audacity and Goldwave are two examples of programs that can make this conversion.

==ANI==
FreeSpace uses the .ANI format for animation effects. It can be used either for an effect (explosions, etc.), an interface animation, or as a ship texture.
*[http://www.swooh.com/lorenzo/files/aniview11.exe AniView, an ANI-viewing utility]
*[http://www.swooh.com/lorenzo/files/anib32b2.exe AniBuilder, a utility that can create ANI files out of a series of 16 bit images]

===Creating an ANI file===

Using AniBuilder (link provided above), one can create new .ANI files from .AVI movies.

To create your own .ANI:

#Set up a scene in a 3D animation program or in FreeSpace. Volition used [[Wikipedia:3ds_Max|3ds Max]] (an expensive modeling program) for their animations.
#Using a free recording software such as for example [http://www.planetgamecam.com GameCam] to record the scene.
#Use for example [http://www.radgametools.com/bnkdown.htm Bink] to convert the AVI into a series of 16-bit (or less) PCX files, as AniBuilder will not accept non-PCX images, or images of more than 16 bit color depth.
#Use AniBuilder to convert the PCX files to an ANI.

==EFF==
FreeSpace 2 uses the .EFF ASCII format text files to store information about animated effects. These animated effects can be used for various effects such as in game animations and animated textures.

===Creation of EFF animation===
*For EFF animation all the individual frames of the animation have to be present in one of the [[Graphic Files|graphic file formats]] supported by the game engine.
*All files related to the .EFF animation have to named so that the name of actual .EFF animation forms the basic structure of the filename.
**'''Graphic files''' add the 4 digit number - that identifies the frame where the file is used - after the animation name, starting from 0 (example_0000.dds, example_0001.dds etc.)
**'''ASCII file''' contains the information of the animation (example.eff)

===Contents of .EFF file===

====$Type:====
*Defines the file format of the graphics file used for the .EFF animation
*Syntax: '''''String''''', for example ''DDS''

====$Frames:====
*Defines the length of the number of the frames in the animation
*Syntax; '''''Integer'''''

====$FPS:====
*Used ''optionally'' to define the '''frames per second''' value for the animation
*Syntax: '''''Integer'''''

[[Category:File Types]]

Talk:Multimedia Files

2007-09-11T11:53:42Z

Bruce89:

==OGG discussion==
The revert IMO seems wrong. OGG is a container, not a audio codec. I'll have a think about how to phrase this better than I did before. [[User:Bruce89|Bruce89]] 13:01, 9 September 2007 (CDT)
:The revert isn't wrong. Note that the previous version said OGG is for "compressed multimedia files", not "compressed audio files". "Multimedia" includes both audio and video. Also, I think it's sufficient for the page to say that Vorbis is for audio and Theora is for video; the additional information is worded kind of confusingly and is probably too technical anyway. [[User:Goober5000|Goober5000]] 13:52, 9 September 2007 (CDT)
:: I rewrote my edit, that is what the second edit by me was. Please do not revert it again before reading it. Please just improve it instead of rejecting it totally. [[User:Bruce89|Bruce89]] 15:18, 9 September 2007 (CDT)
::: You didn't rewrite it; you simply undid my revert... Ugh. I was trying to point you in the right direction with my comments, but I see I'll have to do it myself. New edit posted. [[User:Goober5000|Goober5000]] 02:23, 11 September 2007 (CDT)
:::: I didn't, have a look at the [http://hard-light.net/wiki/index.php?title=*.OGG&diff=12274&oldid=12205 history]. Here is a critical review of the content at the moment:
::::*MP3 is not a container format, so saying "a popular competitor to .MP3" is wrong. Vorbis is "a popular competitor to .MP3", not Ogg. You could say Ogg "is a popular competitor to .MPEG", but this seems pointless.
::::*"Also unlike MP3, Ogg is a container format, meaning that it..." seems clumsy, MP3 uses MPEG-1 as its container.
:::: [[User:Bruce89|Bruce89]] 06:53, 11 September 2007 (CDT)

Talk:Multimedia Files

2007-09-11T11:49:01Z

Bruce89: hmph

==OGG discussion==
The revert IMO seems wrong. OGG is a container, not a audio codec. I'll have a think about how to phrase this better than I did before. [[User:Bruce89|Bruce89]] 13:01, 9 September 2007 (CDT)
:The revert isn't wrong. Note that the previous version said OGG is for "compressed multimedia files", not "compressed audio files". "Multimedia" includes both audio and video. Also, I think it's sufficient for the page to say that Vorbis is for audio and Theora is for video; the additional information is worded kind of confusingly and is probably too technical anyway. [[User:Goober5000|Goober5000]] 13:52, 9 September 2007 (CDT)
:: I rewrote my edit, that is what the second edit by me was. Please do not revert it again before reading it. Please just improve it instead of rejecting it totally. [[User:Bruce89|Bruce89]] 15:18, 9 September 2007 (CDT)
::: You didn't rewrite it; you simply undid my revert... Ugh. I was trying to point you in the right direction with my comments, but I see I'll have to do it myself. New edit posted. [[User:Goober5000|Goober5000]] 02:23, 11 September 2007 (CDT)
:::: I didn't, have a look at the [http://hard-light.net/wiki/index.php?title=*.OGG&diff=12274&oldid=12205 history]. [[User:Bruce89|Bruce89]] 06:48, 11 September 2007 (CDT)

Talk:Multimedia Files

2007-09-11T11:48:17Z

Bruce89:

==OGG discussion==
The revert IMO seems wrong. OGG is a container, not a audio codec. I'll have a think about how to phrase this better than I did before. [[User:Bruce89|Bruce89]] 13:01, 9 September 2007 (CDT)
:The revert isn't wrong. Note that the previous version said OGG is for "compressed multimedia files", not "compressed audio files". "Multimedia" includes both audio and video. Also, I think it's sufficient for the page to say that Vorbis is for audio and Theora is for video; the additional information is worded kind of confusingly and is probably too technical anyway. [[User:Goober5000|Goober5000]] 13:52, 9 September 2007 (CDT)
:: I rewrote my edit, that is what the second edit by me was. Please do not revert it again before reading it. Please just improve it instead of rejecting it totally. [[User:Bruce89|Bruce89]] 15:18, 9 September 2007 (CDT)
::: You didn't rewrite it; you simply undid my revert... Ugh. I was trying to point you in the right direction with my comments, but I see I'll have to do it myself. New edit posted. [[User:Goober5000|Goober5000]] 02:23, 11 September 2007 (CDT)
:::: I didn't, have a look at the [http://hard-light.net/wiki/index.php?title=*.OGG&diff=12274&oldid=12205 history]. Incidentally, copying the content of one page and putting it into another removes all the history. Please use the '''Move''' button in the future. [[User:Bruce89|Bruce89]] 06:48, 11 September 2007 (CDT)

Template talk:FAQ Nav

2007-09-10T22:54:50Z

Bruce89:

That deletion request was just a bit a bit premature :p It's not used yet because I only made it for jr2, at his request, some 5 hours ago, and he hasn't been working on porting the FAQ since then. So rest assured, it will be used. [[User:Shade|Shade]] 12:59, 10 September 2007 (CDT)
: Sorry, it was a wee bit early I suppose. [[User:Bruce89|Bruce89]] 17:54, 10 September 2007 (CDT)