FreeSpace Wiki - User contributions [en]

File:RScreen0087.jpg

2011-05-31T02:44:40Z

Herra Tohtori: uploaded a new version of "File:RScreen0087.jpg": Full resolution and high quality JPG. Would have uploaded PNG, but it didn't want to accept that since file name on wiki has jpg on it.

Slammer

2010-08-14T10:46:10Z

Herra Tohtori: /* Veteran Comments */

{{BPArticle}}
==Description==
===Blue Planet Tech Room Description===
The Kiribati-Sunder GES-10 Slammer is the Federation's counterpart to the Infyrno and Piranha cluster weapons. Major differences include the addition of an aspect seeker, a remote trigger and multiple limited guidance cluster warheads that are fired at a 10 degree angle, producing a shotgun effect. The warheads themselves detonate about 3 seconds after separation. Slammers excel at offensive deployment against large groups of fighters, and they are devastating against bombers. Of all the Federation's fighter-based weapons, GTVA pilots fear Slammers the most, and unlike their Piranha and Infyrno counteparts, Slammers enjoy considerable popularity amongst pilots. Uriel gunships can carry twelve Slammers into battle for heavy fighter and bomber suppression, turning dogfights into gruesome, industrial slaughterhouses.

==Performance==
===Statistics===
{{Secondary|2500|5|250|20|1.0x|20|0.75x|15|1.0x|20|20 / 25|Aspect Seeking|N/A|3.0|3.5 s}}

===Spawned warheads===
{{Secondary|750|0|300|50|1.0x|50|1.0x|50|0.25x|12.5|40 / 80|Heat Seeking|180|N/A|1.0 s}}

==Notes==

===Veteran Comments===
{{Comment|'''Use this weapon'''. Although it takes a bit of skill to get used to at first, when used correctly the Slammer can bag you enormously satisfying multi-kills; wiping out entire bomber wings in a split second and breaking up hostile fighter formations with ease. It's fully possible to destroy an entire 6-ship fighter or bomber wing with this thing. However, be extremely cautious about using these at close range, as you are very, very likely to kill yourself within a distance of about 500 meters. Friendly fighters also have an infuriating tendency to kill you with friendly Slammer fire. Best thing to do is try not to get too close to enemy fighter formations and wait for them to break up before engaging.

Blue on blue casualties related to this weapon can be significantly reduced by telling your Slammer-carrying wingmen to ignore your target whenever you close in for primary/Hellfire kills. This somewhat reduces the risk of them deciding to fire Slammers towards your vicinity. Also, if there are pilots who are not under your direct command, keep track of what ships they are engaging, so that you don't put yourself in risk should they fire a Slammer at the target.}}
[[Category:Blue Planet weapons]]

UEFg Narayana

2010-08-13T17:29:38Z

Herra Tohtori: /* Name Origin */

{{BPArticle}}

The '''UEFg'' Narayana''''' is a frigate class of the [[United Earth Federation|UEF]] in [[Blue Planet]].

==Description:==
{{shipimage|image=[[Image:UEFgNarayana.png|600px]]|caption=The {{PAGENAME}}}}
===Blue Planet: War in Heaven Tech Description===
Heavy frigate class originally designed to engage large capital class vessels in mid and close ranges where the Karuna's firepower and armor would be insufficient. Advanced beam weaponry deployed by the GTVA, and the loss of many frigates, including several Narayanas, made it clear that the firepower of currently deployed frigate classes was not enough to counter GTVA warships. This led to a massive refit of all Narayana class heavy frigates into artillery frigates capable of engaging hostile targets with specialized artillery weaponry from extreme ranges. Since the introduction of refitted Narayana, the UEF forces have won several key engagements where Narayana's artillery weaponry played a significant role in forcing GTVA warships to withdraw from combat.

===Developer Notes===

===Credits===

===Name Origin===
Narayana or Narayan is an important Sanskrit name for Vishnu, and in many contemporary vernaculars a common Indian name. Narayana is also identified as the original man, Purusha. The Puranas present divergent views on Narayana. In the Kurma Purana he is identified with Brahman and Krishna-Vishnu, but in the Brahma Vaivarta Purana Narayana is considered different from Krishna and also considered part of Krishna.

==Performance:==
===Statistics===
{{Ship Stats|Heavy Frigate|Tethis Designs|N/A|30|N/A|N/A|90 000|N/A|}}{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Width|Width]]'''
| style="width:200px" | m
|-
| '''[[Technical_Terms_and_Definitions#Height|Height]]'''
| m
|-
| '''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| Unknown
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| Apocalypse
| 3
|- align="center"
| Mass Driver
| 2
|- align="center"
| Gauss Cannon
| 4
|- align="center"
| Burst Flak
| 4
|- align="center"
| Point Defense Turret
| 8
|}

==Veteran Comments==
{{Comment|}}

[[Category: User-made Ships]]
[[Category: Blue Planet]]

UEF Uriel

2010-08-08T18:09:58Z

Herra Tohtori: /* Name Origin */

{{BPArticle}}

:''For the original ship, see [[FTF Wraith]].''

==Description:==
{{shipimage|image=[[Image:Uefuriel.jpg]]|caption=The {{PAGENAME}}}}
===Blue Planet: War in Heaven Tech Description===
The Uriel assault fighter is the mainstay gunship class of the Federation and the most indispensable element of its fighter corps. Heavy armour and a devastating frontal array of cannons makes the Uriel the premier weapons platform against large, slow-moving targets. Uriels excel in various mission profiles ranging from airstrikes on ground targets to full-scale assaults against cruiser assets to heavy fighter or turret suppression. The fighter is also equipped with an underslung heavy long-range gauss cannon, further increasing its weapons potential. The low manoeuverability and top speed of the Uriel limits its effectiveness in dogfights, but some pilots have learned to compensate for these shortcomings. When deployed in full squadron strength, Uriels can dominate an entire battlespace with Slammer fire. The GTVA has faced down the threat of the Uriel by simply destroying as many as possible through massed Trebuchet fire, and unfortunately for the Federation, the Uriel is growing scarce to the point where it can only be deployed in vital situations.

===Developer Notes===
N/A

===Name Origin===
Saint Uriel the Archangel is one of the archangels of post-Exilic Rabbinic tradition, and also of certain Christian traditions.

==Performance:==
===Statistics===
{{Ship Stats|Heavy Assault|Stormrider|Average|65 - 90|140|Heavy|470|640|38}}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Vulcan]]
|- align="center"
| 2nd
| 6
| [[Rapier]]
|- align="center"
| 3rd
| 1
| [[Archer]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=1 align="center"| 1st
| colspan=2| [[Maul]], [[Vulcan]], [[Rapier]], [[Gattler]], [[Scalpel]]

|-
| colspan=1 align="center"| 2nd
| colspan=2| [[Maul]], [[Vulcan]], [[Rapier]], [[Gattler]], [[Scalpel]]

|-
| colspan=1 align="center"| 3rd
| colspan=2| [[Archer]]
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[Dart]]
|- align="center"
| 2nd
| 40
| [[Slammer]]
|- align="center"
| 3rd
| 40
| [[Slammer]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=1 align="center"| 1st
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]], [[Slammer]], [[Paveway]], [[Grimler]], [[Shrike]]

|-
| colspan=1 align="center"| 2nd
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]], [[Slammer]], [[Paveway]], [[Grimler]], [[Shrike]], [[Jackhammer]]

|-
| colspan=1 align="center"| 3rd
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]], [[Slammer]], [[Paveway]], [[Grimler]], [[Shrike]], [[Jackhammer]]
|}

==Veteran Comments==
{{Comment|}}

[[Category: User-made Ships]]
[[Category: Blue Planet]]

UEF Uhlan

2010-08-08T17:26:44Z

Herra Tohtori: /* Name Origin */

{{BPArticle}}

:''For the original ship, see [[FTF Lancer]].''

==Description:==
{{shipimage|image=[[Image:Uefuhlan.jpg]]|caption=The {{PAGENAME}}}}
===Blue Planet: War in Heaven Tech Description===
The UEF Uhlan is the most commonly used fightercraft in the United Earth Navy. Designed primarily for the space superiority role, the Uhlan is a cost-efficient design that is inexpensive to produce and relatively easy to pilot. The Uhlan is compatible with most Navy weapons and is generally considered a medium-performance vessel. The Uhlan is able to operate within an atmosphere due to an aerodynamic design, and its excellent Saab maneuvering thruster suite gives it sterling agility in a dogfight. Unlike many UEF fighters, however, it lacks reverse thrust.

===Developer Notes===
N/A

===Name Origin===
Uhlans were Polish light cavalry armed with lances, sabres and pistols.

==Performance:==
===Statistics===
{{Ship Stats|Space Superiority|Saab Spaceframes|Average|75 - 90|140|Average|250|390|18}}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 3
| [[Vulcan]]
|- align="center"
| 2nd
| 2
| [[Vulcan]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[Vulcan]], [[Scalpel]], [[Maul]], [[Rapier]], [[Gattler]]
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 40
| [[Javelin]]
|- align="center"
| 2nd
| 40
| [[Javelin]]
|- align="center"
| 3rd
| 40
| [[Hellfire Missile|Hellfire]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=1| 1st
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]]

|-
| colspan=1| 2nd
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]]

|-
| colspan=1| 3rd
| colspan=2| [[Dirk]], [[Dart]], [[Hellfire Missile|Hellfire]], [[Javelin]], [[Jackhammer]], [[Slammer]], [[Paveway]], [[Grimler]]
|}

==Veteran Comments==
{{Comment|}}

[[Category: User-made Ships]]
[[Category: Blue Planet]]

Modelling

2008-12-02T01:25:41Z

Herra Tohtori: /* SCP Team Recommendations */

=Modelling basics=
The community currently uses a wide range of modelling programs, from [[Blender]] to Lightwave to 3D Studio Max and others. Converters to the .POF format, as used by Freespace 2 is available via a plug in for 3D Studio Max or via the Pof Construction Suite program for .cob ([[Truespace]]) files. Any models to be made need to be converted to one of these two formats.

==Limits and Guidelines for Model Making==
===SCP Team Recommendations===
The new HT&L ('''H'''ardware '''T'''ransform and '''L'''ighting) feature of FreeSpace 2 SCP has allowed a vast increase in the number of polygons that can be displayed at any one time, however, in order to keep gameplay smooth, the SCP team recommends the following rules when making models for use in FreeSpace 2.

'''Textures :'''

:1) Use as few textures per model as is possible, optimization is the key, for fighters and bombers you should only need a single 512 x 512 map for the model. Capital ships can use more textures, but the less textures and the less memory they take up, the better.

:2) Unless it is absolutely vital, use the .DDS format for storing your images. These format files are compressed and are automatically decompressed by your video hardware, so they take up far less memory, thus improving performance. FreeSpace 2 also supports .TGA format files, but these should only be used where .DDS files are causing noticeable compression errors on your texture (this can happen most noticeably with semi-transparent textures). Although if DXT compression is giving problems it would be technically better to use uncompressed DDS files (u888 or u8888) rather than targa files, mainly because uncompressed DDS files can store mipmaps while TGA files can't.

:3) For highly detailed ships, it is better, from a memory point of view, to use one large texture than several smaller ones.

:4) ''Always'' use texture sizes that are a power of 2, i.e. 256, 512, 1024 or, at most, 4096. However, remember that older ATI cards can only use 2048² maps, thus it is recommended to use this as maximum. You can have different ratios, such as 512x256, but always use these sizes.

'''Models :'''

Remember that any Level of Detail models are going to be stored in memory, so use them sensibly. Freespace SCP now uses Mipmap technology, so you no longer need to create LODs for the textures, an old requirement of FreeSpace 2 modding. Whilst polygon count does not have as dramatic effect on performance as texture size does, it is, as always, best to optimize where possible.

===Polygon Counts===

Whilst there is no fixed limit to the number of polygons you can use on a model, and opinions vary from person to person, the writer finds the following approximate Polygon counts a good guide to work by.

:'''Fighters/Bombers''' - Less than 6000 Polygons

:'''Cruisers/Freighters''' - 6000-12000 Polygons

:'''Corvettes''' - 14000-18000 Polygons

:'''Destroyers''' - 20000-24000 Polygons

:'''Juggernauts''' - 24000 Polygons upwards

Though this list should not, by any means, be used as a rule, different modders work to different guidelines.

Note that [[Detail box]] models should not be counted directly to the overall number of polygons.

==Sub-Objects==
The first thing that needs to be understood about FreeSpace models is the hierarchy they need to be placed in to make sure that conversion is a success. Each FreeSpace model is made up of several submodels (which can also use more than one material each) or groups. How these groups are arranged will directly affect how the final model works in-game. Don't panic, it's not as scary as it sounds.

The most important parts of your ship you need to make sure are at least one individual sub-objects are :

{|
| '''Main Hull''' || The main 'Body' of the ship, will only explode when the ship is destroyed.
|-
| '''Turrets''' || Any static or rotating turrets, rotating turrets need 2 sub-models. Different sub-object for each turret, e.g. Turret01, Turret02 etc. In the case of rotating turrets, I use Turret01-base and Turret01-arm etc.
|-
| '''Subsystems''' || Destroyable sub-objects or any other eye-candy. These have the widest range of uses and feature in more advanced features. Different sub-object for each sub-system e.g. Radar01, Reactor01 etc.
|-
| '''Debris''' || The wreckage of the ship released after it is destroyed. Different sub-object for each item of Debris, e.g. Debris01, Debris02 etc.
|-
| '''LODS''' || The Level Of Detail models for the main Hull and for so-desired Turrets and/or Subsystems.
|}

Some sub-models can be further enhanced using the SCP ships.tbl expansions such as [[Animation Code]]. Always bear in mind what you want your ship to do whilst you are modelling it.

In addition the the LODs, it is possible to add further detail models to you ship using the [[Detail box]] feature.

[[Category:Modding]]

''Update ongoing by Flipside''

Modelling

2008-12-02T01:23:22Z

Herra Tohtori: /* SCP Team Recommendations */

=Modelling basics=
The community currently uses a wide range of modelling programs, from [[Blender]] to Lightwave to 3D Studio Max and others. Converters to the .POF format, as used by Freespace 2 is available via a plug in for 3D Studio Max or via the Pof Construction Suite program for .cob ([[Truespace]]) files. Any models to be made need to be converted to one of these two formats.

==Limits and Guidelines for Model Making==
===SCP Team Recommendations===
The new HT&L ('''H'''ardware '''T'''ransform and '''L'''ighting) feature of FreeSpace 2 SCP has allowed a vast increase in the number of polygons that can be displayed at any one time, however, in order to keep gameplay smooth, the SCP team recommends the following rules when making models for use in FreeSpace 2.

'''Textures :'''

:1) Use as few textures per model as is possible, optimization is the key, for fighters and bombers you should only need a single 512 x 512 map for the model. Capital ships can use more textures, but the less textures and the less memory they take up, the better.

:2) Unless it is absolutely vital, use the .DDS format for storing your images. These format files are compressed and are automatically decompressed by your video hardware, so they take up far less memory, thus improving performance. FreeSpace 2 also supports .TGA format files, but these should only be used where .DDS files are causing noticeable compression errors on your texture (this can happen most noticeably with semi-transparent textures). Even then, it is better to use the DDS file format than TGA - just without the DXT compression features, saving them as either uncompressed u888 or u8888 files, latter only if you need alpha channel in the file, which is the case with shinemaps and glass diffuse maps. Even though the filesizes of uncompressed DDS files are usually drastically larger than RLE compressed targa files, they will actually have slightly better performance since both require same amount of video memory (excluding the mip map memory requirements of DDS files), but the GPU's can use the DDS file directly while TGA file needs to be uncompressed before caching to video memory, which consumes processor cycles and system memory. In addition, uncompressed DDS files have the same mip mapping capabilities as compressed DDS files, which targa files don't have.

:3) For highly detailed ships, it is better, from a memory point of view, to use one large texture than several smaller ones.

:4) ''Always'' use texture sizes that are a power of 2, i.e. 256, 512, 1024 or, at most, 4096. However, remember that older ATI cards can only use 2048² maps, thus it is recommended to use this as maximum. You can have different ratios, such as 512x256, but always use these sizes.

'''Models :'''

Remember that any Level of Detail models are going to be stored in memory, so use them sensibly. Freespace SCP now uses Mipmap technology, so you no longer need to create LODs for the textures, an old requirement of FreeSpace 2 modding. Whilst polygon count does not have as dramatic effect on performance as texture size does, it is, as always, best to optimize where possible.

===Polygon Counts===

Whilst there is no fixed limit to the number of polygons you can use on a model, and opinions vary from person to person, the writer finds the following approximate Polygon counts a good guide to work by.

:'''Fighters/Bombers''' - Less than 6000 Polygons

:'''Cruisers/Freighters''' - 6000-12000 Polygons

:'''Corvettes''' - 14000-18000 Polygons

:'''Destroyers''' - 20000-24000 Polygons

:'''Juggernauts''' - 24000 Polygons upwards

Though this list should not, by any means, be used as a rule, different modders work to different guidelines.

Note that [[Detail box]] models should not be counted directly to the overall number of polygons.

==Sub-Objects==
The first thing that needs to be understood about FreeSpace models is the hierarchy they need to be placed in to make sure that conversion is a success. Each FreeSpace model is made up of several submodels (which can also use more than one material each) or groups. How these groups are arranged will directly affect how the final model works in-game. Don't panic, it's not as scary as it sounds.

The most important parts of your ship you need to make sure are at least one individual sub-objects are :

{|
| '''Main Hull''' || The main 'Body' of the ship, will only explode when the ship is destroyed.
|-
| '''Turrets''' || Any static or rotating turrets, rotating turrets need 2 sub-models. Different sub-object for each turret, e.g. Turret01, Turret02 etc. In the case of rotating turrets, I use Turret01-base and Turret01-arm etc.
|-
| '''Subsystems''' || Destroyable sub-objects or any other eye-candy. These have the widest range of uses and feature in more advanced features. Different sub-object for each sub-system e.g. Radar01, Reactor01 etc.
|-
| '''Debris''' || The wreckage of the ship released after it is destroyed. Different sub-object for each item of Debris, e.g. Debris01, Debris02 etc.
|-
| '''LODS''' || The Level Of Detail models for the main Hull and for so-desired Turrets and/or Subsystems.
|}

Some sub-models can be further enhanced using the SCP ships.tbl expansions such as [[Animation Code]]. Always bear in mind what you want your ship to do whilst you are modelling it.

In addition the the LODs, it is possible to add further detail models to you ship using the [[Detail box]] feature.

[[Category:Modding]]

''Update ongoing by Flipside''

Stars.tbl

2008-10-18T22:06:06Z

Herra Tohtori: /* Background graphics */

Revision information.. 
::'''3.6.x branch:''' 2.72.2.22
::'''3.7 branch:''' 2.99

Stars.tbl is used to define available background graphics, all the stars or suns that create colored light for the game and used debris animations.

==General Format==
*Stars.tbl consist of several sections
*Between different sections <nowiki>#</nowiki>'''End''' must be used
*'''Background graphics'''
**Defines the available background graphics (nebulas, planets, etc.)
*'''Stars'''
**Defines the stars
*'''Non-nebula debris'''
**Defines animation for non-nebula mode
*'''Nebula debris'''
**Defines animation for nebula mode
*<nowiki>#</nowiki>'''End'''
**Must be included to the end of the stars.tbl

===Background graphics===
*Background graphics use the names of their respective graphic files
*Background graphics can be defined in two different forms:
**'''$Bitmap:'''
***This entry type is used for objects that use additive blending (intensity = transparency), such as nebulas and suns.
***Syntax: '''String''', filename
**'''$BitmapX:'''
***This entry type is used for the retail 'green transparency' objects (ie. 0,255,0 is transparent) in case of pcx files, and for full alpha channel blending for files that can have alpha channel (TGA and DXT3/DXT5 files). Use this to make the space around solid background objects (such as planets, big asteroids and such) transparent.
**Syntax: '''String''', filename

===Stars===
*Stars are defined with several different parameters.
**'''$Sun:'''
***Defines the name of the used star
***Syntax: '''String''', filename
**'''$SunGlow:'''
***Defines the bitmap or animation used as a glow for the star
***Syntax: '''String''', filename
**'''$SunRGBI:'''
***Defines the color of the sun as well as it's intensity
***Syntax: '''Color''', four '''integers''', 0 to 255, red, green, blue and alpha respectively

{{Table36|
:*'''$SunSpecularRGB:'''
:**Defines the color of the sun specuular lighting if it is to be different from '''$SunRGBI:''' values
:**Syntax: '''Color''', three '''integers''', 0 to 255, red, green and blue respectively
:*'''$Flare:'''
:**Defines lens flare effect.
:**'''+FlareCount:'''
:***Defines number of lens flare effects attached yo the sun, if the value is omitted then 1 is used as a default number of flare effects.
:***Syntax: '''Integer'''
:**'''$FlareTexture''N'':'''
:***Defines the name of the bitmap used for the particular ( N ) lens flare texture.
:***Syntax: '''String''', filename
:**For each (defined in '''+FlareCount:''') lens flare effect
:***'''$FlareGlow''X'':'''
:****Defines the Xth lens flare effect.
:****'''+FlareTexture:'''
:*****Defines the texture used for the lens flare effect.
:*****Syntax: '''Integer''', number of the texture defines in '''$FlareTexture''N'':'''.
:****'''+FlarePos:'''
:*****Defines the position of the lens flare effect, relative value
:*****Syntax: '''Float'''
:****'''+FlareScale:'''
:*****Defines the scaling factor used for the lens flare effect.
:*****Syntax: '''Float'''
:*'''$NoGlare:'''
:**Disables blinding effect from the sun.
:**Usage: '''$NoGlare:''' without any parameters}}

===Non-nebula debris===
*There must always be four (4) of these
**'''$Debris:'''
***Defines the animations used for the debris
***Syntax: '''String'''

===Nebula debris===
*There must always be four (4) of these
**'''$DebrisNeb:'''
***Defines the animations used for the debris
***Syntax: '''String'''

==Sample==
<pre>
$Bitmap: dneb01

#end

$Sun: SunWhite
$Sunglow: Sunglow01
$SunRGBI: 1.0 1.0 1.0 1.0

#end

$Debris: debris01
$Debris: debris02
$Debris: debris03
$Debris: debris04

#end

$DebrisNeb: gas
$DebrisNeb: gas
$DebrisNeb: gas
$DebrisNeb: gas

#end

#end
</pre>

[[Category:Tables]]

Stars.tbl

2008-10-18T22:04:58Z

Herra Tohtori: /* Background graphics */

Revision information.. 
::'''3.6.x branch:''' 2.72.2.22
::'''3.7 branch:''' 2.99

Stars.tbl is used to define available background graphics, all the stars or suns that create colored light for the game and used debris animations.

==General Format==
*Stars.tbl consist of several sections
*Between different sections <nowiki>#</nowiki>'''End''' must be used
*'''Background graphics'''
**Defines the available background graphics (nebulas, planets, etc.)
*'''Stars'''
**Defines the stars
*'''Non-nebula debris'''
**Defines animation for non-nebula mode
*'''Nebula debris'''
**Defines animation for nebula mode
*<nowiki>#</nowiki>'''End'''
**Must be included to the end of the stars.tbl

===Background graphics===
*Background graphics use the names of their respective graphic files
*Background graphics can be defined in to different forms:
**'''$Bitmap:'''
***This entry type is used for objects that use additive blending (intensity = transparency), such as nebulas and suns.
***Syntax: '''String''', filename
**'''$BitmapX:'''
***This entry type is used for the retail 'green transparency' objects (ie. 0,255,0 is transparent) in case of pcx files, and for full alpha channel blending for files that can have alpha channel (TGA and DXT3/DXT5 files). Use this to make the space around solid background objects (such as planets, big asteroids and such) transparent.
**Syntax: '''String''', filename

===Stars===
*Stars are defined with several different parameters.
**'''$Sun:'''
***Defines the name of the used star
***Syntax: '''String''', filename
**'''$SunGlow:'''
***Defines the bitmap or animation used as a glow for the star
***Syntax: '''String''', filename
**'''$SunRGBI:'''
***Defines the color of the sun as well as it's intensity
***Syntax: '''Color''', four '''integers''', 0 to 255, red, green, blue and alpha respectively

{{Table36|
:*'''$SunSpecularRGB:'''
:**Defines the color of the sun specuular lighting if it is to be different from '''$SunRGBI:''' values
:**Syntax: '''Color''', three '''integers''', 0 to 255, red, green and blue respectively
:*'''$Flare:'''
:**Defines lens flare effect.
:**'''+FlareCount:'''
:***Defines number of lens flare effects attached yo the sun, if the value is omitted then 1 is used as a default number of flare effects.
:***Syntax: '''Integer'''
:**'''$FlareTexture''N'':'''
:***Defines the name of the bitmap used for the particular ( N ) lens flare texture.
:***Syntax: '''String''', filename
:**For each (defined in '''+FlareCount:''') lens flare effect
:***'''$FlareGlow''X'':'''
:****Defines the Xth lens flare effect.
:****'''+FlareTexture:'''
:*****Defines the texture used for the lens flare effect.
:*****Syntax: '''Integer''', number of the texture defines in '''$FlareTexture''N'':'''.
:****'''+FlarePos:'''
:*****Defines the position of the lens flare effect, relative value
:*****Syntax: '''Float'''
:****'''+FlareScale:'''
:*****Defines the scaling factor used for the lens flare effect.
:*****Syntax: '''Float'''
:*'''$NoGlare:'''
:**Disables blinding effect from the sun.
:**Usage: '''$NoGlare:''' without any parameters}}

===Non-nebula debris===
*There must always be four (4) of these
**'''$Debris:'''
***Defines the animations used for the debris
***Syntax: '''String'''

===Nebula debris===
*There must always be four (4) of these
**'''$DebrisNeb:'''
***Defines the animations used for the debris
***Syntax: '''String'''

==Sample==
<pre>
$Bitmap: dneb01

#end

$Sun: SunWhite
$Sunglow: Sunglow01
$SunRGBI: 1.0 1.0 1.0 1.0

#end

$Debris: debris01
$Debris: debris02
$Debris: debris03
$Debris: debris04

#end

$DebrisNeb: gas
$DebrisNeb: gas
$DebrisNeb: gas
$DebrisNeb: gas

#end

#end
</pre>

[[Category:Tables]]

Meson Bomb

2006-10-04T21:53:26Z

Herra Tohtori: Fixed plethora of factual errors considering Mesons and the speculative physics of Meson Bomb. Added another theory of bomb's mechanism.

The '''Meson Bomb''' is an experimental demolition warhead developed at the Hideki Institute in [[Vega]]. First devised as a large-scale demolition bomb to destroy meteor and asteroid fields, it was first deployed to destroy the [[Knossos]] subspace portal in Gamma Draconis to prevent the Shivans from invading Capella. Up to 17 Meson bombs have been produced so far; three were used to destroy the Knossos subspace portal in Gamma Draconis and 14 more were retrofitted in decommissioned destroyers, [[GTD Bastion|GTD ''Bastion'']] and [[GTD Nereid|GTD ''Nereid'']] to collapse the nodes to [[Vega]] and [[Epsilon Pegasi]] from [[Capella]]. Its use as a demolition warhead was first demonstrated at the destruction of the Knossos subspace portal, where thereafter Allied Command commissioned its use in the Capella contingency plan for trapping the Shivans in that system.

Its name refers to the mesons, which are a group of elementary particles called hadrons. All hadron particles consist of quarks that are kept strongly together by another particle called a gluon, but the other hadron group, baryons, consist of three quarks whereas all mesons are combinations of a quark and an anti-quark kept together by gluon. Baryons include the bulk of ordinary matter, protons and neutrons, mesons are much more rare particles. Mesons can be born in certain energy-intensive interactions. For example, cosmic radiation that impacts the Earth atmosphere creates a stream of meson particles called pions.

Mesons are in normal conditions very short-lived particles, they rapidly degenerate into gamma radiation by themselves. Physically most likely explanation for the destructive energy generated by Meson Bomb is that somehow the Meson Bomb makes it possible to contain large amounts of mesonic matter intact, preventing its disintegration by some currently unknown physical phenomenon, or perhaps by slowing time inside the Meson Bomb container by advanced subspace interaction. When the detonation-preventer is then released, the mesonic mass inside the container rapidly turns into radiation, creating same effects as described before - a hot, expanding shockwave with loads of destructive power.

A Meson Bomb's destructive energy could also be the result of some currently unknown reaction that can weaken the bonding gluon between the quark and anti-quark of a meson, releasing a cloud of quarks and anti-quarks in the mesonic matter. More than likely a great portion of quarks and anti-quarks then find each other and annihilate, creating a lot of radiation, which turns the surrounding matter into blazing hot, rapidly expanding cloud of plasma that has a lot of thermal and kinetic energy. This is the obvious
shockwave of the explosion.

However, current physics does not know of a phenomenon that could divide hadron particles into separate quarks; in fact, theoretically all attempts to separate gluon-bound quarks from each other just increase the force at which the gluon keeps the quarks together. This is called "asymptotic freedom". When the quarks have been sufficiently stretched apart, the energy density demanded to keep the quarks apart from eachg other reaches high enough level to actually transmute into matter; a new quark/anti-quark pair is born and so we now have two mesons instead of the original one. For this reason, no particle consisting of quarks is actually separable into quarks and gluons; any attempt to do so just creates more hadrons as a result of energy transmutating into matter.

The use of Meson Bomb as a tactical warhead is prohibited by its large size.

The Hideki Institute was named after Hideki Yukawa, a leading Japanese theoretical physicist that won the Nobel Prize for his thoery on meson.

Shivan Comm Node

2006-10-03T12:59:58Z

Herra Tohtori: /* Veteran Comments */

The '''Shivan Comm Node''' is a Shivan device encountered in the [[Binary system]] beyond the second knossos gate. They consist of a complex web of machinery encasing a crystalline sphere. Officially, the GTVA has no idea what the purpose of these devices are - they are labelled as "Unknown" in game, and are revealed as Comm Nodes in the tables only. <br>
<br>
Three of these devices were encountered and destroyed, each releasing a tremendous amount of energy as a shockwave. Their purpose remains officially unknown.

{{FS12_Ships}}
{{shipimage|image=[[Image:commnode320x240.jpg]]|caption=The Shivan Comm Device}}

==Description:==

===FS2 Tech Room Description===
All details concerning this object have been classified level Omega, accessible only by those immediately authorized by the GTVA Security Council.

===Developer Notes===
None

===Veteran Comments===
''Has a large blast radius when destroyed, so blow it up and run!''

''DO NOT GET HIT BY THE ROTATING BLADES!''

''On the other hand, if you have the piloting skill, you can weave in and out of the blades and watch them flatten any AI ship stupid enough to follow you. ;)''

''The fastest way to destroy these is to destroy the core crystal. More specifically, aim the conical parts of the crystal that are close to the points where it unites with the blades. Hitting these points will rapidly destroy the core, after which the whole thing blows up.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Comm Device (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[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]]
| 40 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 748 m
|}

===Armaments===
None

[[Category:Ship]]