FreeSpace Wiki - User contributions [en]

Sounds.tbl

2012-07-07T01:09:48Z

IssMneur: /* Game Sounds */ Clairify how the indexes need to be used

{{TableVersion|4879}}

Sounds.tbl is a file for defining the various sounds played ingame.

==Format==
*Table file consists of several sections
*First section defines the sound for the actual game play. It begins at '''#Game Sounds Start''' and ends at'''#Game Sounds End'''
*Second section defines the interface sounds. It starts at '''#Interface Sounds Start''' and ends at '''#Interface Sounds End'''
*Third section defines the flyby sounds for different species. It begins at '''#Flyby Sounds Start''' and ends at '''#Flyby Sounds End'''

==Game Sounds==
*Defines the game sounds by means of an index.
{{Note|Retail indexing must remain intact, so removing entries is not recommended. However adding new ones or altering existing ones is possible. See the [[Hardcoded sounds|hardcoded sounds list]] for the retail indexing.}}
*Cockpit sounds are in general non-3D sounds that ought to be of type '0', however all the other in-flight sounds are in general 3D sounds and ought to of type '1' (or type '2')
*Each sound is defined on a single line that begins with '''$Name:'''
**'''First''' value is the index number of the sound ('''Integer''')
**'''Second''' value is the name of actual sound file ('''String''', filename). The name of the file can be replaced with 'empty' if the particular sound index is not in use
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1)
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value sets the sound type to either standard sound (type '0'), 3D stereo sound (type '1'), or Aureal A3D (type '2'). This defaults to 3D stereo if it is not available ('''Integer''', 0, 1 or 2)
**'''Sixth''' and '''seventh''' values are used to define the attenuation distances for the 3D sounds. These are not used with normal non-3D sounds (type 0)
***'''Sixth''' value defines the distance from the origin of sound where it begins to attenuate ('''Integer''')
***'''Seventh''' value sets the distance from the origin of the sound where it is inaudible ('''Integer''')

==Interface Sounds==
{{Note| These '''MUST''' be sequential, no gaps are permitted. Also note that some indices are reserved for hardcoded effects, see [[Hardcoded sounds|here]] for a full list. You can use empty entries as padding to fill out any gaps.}}
*Defines the game interface sounds. Uses sounds indexes as well. Indexing must remain intact so removing entries is not recommended. However adding new ones or altering existing ones is possible
*Interface sounds are not 3D sounds. Use type '0' sounds
*Each sound is defined on a single line that begins with '''$Name:'''
**'''First''' value is the index number of the sound ('''Integer''')
**'''Second''' value is the name of actual sound file ('''String''', filename). The name of the file can be replaced with 'empty' if the particular sound index is not in use.
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1)
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value set the sound type to either standard sound (type '0'), 3D stereo sound (type '1'), or Aureal A3D (type '2') which defaults to 3D stereo if it is not available. For interface sounds, these are all type '0'. ('''Integer''', 0, 1 or 2)

==Flyby Sounds==
*Each species has two flyby sounds. One for the fighters and one for the bombers.
*Flyby sounds are all 3D sounds of type '1'
*Each flyby sound is defined on a single line that begins with the species name ('''String''', species name, eg. '''$Terran:''')
**'''First''' ( is the ship flyby type. Type '0' for fighters, and type '1' for bombers. ('''Integer''', 0 or 1)
**'''Second''' value is the name of actual sound file ('''String'''). The name of the file can be replaced with 'empty' if the particular sound index is not in use.
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1).
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value set the sound type to either standard sound (type '0'), 3D stereo sound (type '1'), or Aureal A3D (type '2') which defaults to 3D stereo if it is not available. For flyby sounds, they should be all be type '1'. ('''Integer''', 0, 1 or 2)
**'''Sixth''' and '''seventh''' values are used to define the attenuation distances for the 3D sounds. These are not used with normal non-3D sounds (type 0)
***'''Sixth''' value defines the distance from the origin of sound where it begins to attenuate ('''Integer''')
***'''Seventh''' value sets the distance from the origin of the sound where it is inaudible ('''Integer''')

==Sample==
*Retail FreeSpace 2 table

<pre>
;
; sounds.tbl *
;
; file to specify general game sounds
;
; I M P O R T A N T
; **********************************************************
; * *
; ====> DO NOT MODIFY THE ORDER OF THE LISTED SOUNDS <====*
; * *
; **********************************************************
; I M P O R T A N T
;
; If a sound entry appears in this file, there is a hook into the game to
; play the sound. This file can only be modified to change *existing* sounds.
; Talk to a programmer if you want to add brand new sounds. Adding a line to
; this file will not make your sound appear in the game, it will more than
; likely break something.
;
; If you don't want the sound to play, put none.wav as the sound to play.
;
; The fields for a sound entry are:
; 1) unqiue sound signature
; 2) filename of the sound
; 3) flag to indicate sound should always be pre-loaded before a mission
; 4) the default volume (from 0.0 -> 1.0)
; 5) 0 - not 3d 1 - stereo 3D 2 - Aureal A3D (if available), otherwise use stereo 3D
; 6) distance at which sound starts to attenuate (for 3d sounds only)
; 7) distance at which sound is inaudible (for 3d sounds only)
;
#Game Sounds Start
; Misc sounds section ** = Aureal 3d support | * = FS = 3D support
$Name: 0 trk-loop.wav, 0, 0.40, 0 ; Missle tracking to acquire a lock (looped)
$Name: 1 lock.wav, 0, 0.40, 0 ; Missle lock (non-looping)
$Name: 2 cycle.wav, 0, 0.60, 0 ; cycle primary weapon
$Name: 3 cycle.wav, 0, 0.60, 0 ; cycle secondary weapon
$Name: 4 ship_p.wav, 0, 0.30, 0 ; engine sound (as heard in cockpit)
$Name: 5 reveal.wav, 0, 0.40, 0 ; cargo revealed
$Name: 6 breakup.wav, 0, 0.60, 1, 100, 800 ; ship death roll (3d sound)
$Name: 7 boom_3.wav, 0, 0.90, 2, 600, 1200 ; * ship explosion 1 (3d sound)
$Name: 8 beep_2.wav, 0, 0.40, 0 ; target acquried
$Name: 9 switch_1.wav, 0, 0.50, 0 ; energy level change success
$Name: 10 beep_5.wav, 0, 0.50, 0 ; energy level change fail
$Name: 11 switch_2.wav, 0, 0.50, 0 ; energy transfer success
$Name: 12 beep_5.wav, 0, 0.50, 0 ; energy transfer faile
$Name: 13 thr_full.wav, 0, 0.40, 0 ; set full throttle
$Name: 14 thr_off.wav, 0, 0.40, 0 ; set zero throttle
$Name: 15 thr_up.wav, 0, 0.40, 0 ; set 1/3 or 2/3 throttle (up)
$Name: 16 thr_dwn.wav, 0, 0.40, 0 ; set 1/3 or 2/3 throttle (down)
$Name: 17 approach.wav, 0, 0.60, 1, 10, 800 ; dock approach retros (3d sound)
$Name: 18 attach.wav, 0, 0.60, 1, 10, 800 ; dock attach (3d sound)
$Name: 19 detach.wav, 0, 0.60, 1, 10, 800 ; dock detach (3d sound)
$Name: 20 depart.wav, 0, 0.60, 1, 10, 800 ; dock depart retros (3d sound)
$Name: 21 aburn_1.wav, 0, 0.70, 0 ; afterburner engage (3d sound)
$Name: 22 aburn_2.wav, 0, 0.90, 0 ; afterburner burn sound (looped)
$Name: 23 vaporize2.wav, 0, 0.90, 0 ; Destroyed by a beam (vaporized)
$Name: 24 aburn_1f.wav, 0, 0.50, 0 ; afterburner fail (no fuel when aburn pressed)
$Name: 25 alert_2.wav, 0, 0.40, 0 ; heat-seeker launch warning
$Name: 26 m_fail.wav, 0, 0.60, 0 ; tried to fire a missle when none are left
$Name: 27 l_fail.wav, 0, 0.60, 0 ; tried to fire lasers when not enough energy left
$Name: 28 fail.wav, 0, 0.50, 0 ; target fail sound (i.e. press targeting key, but nothing happens)
$Name: 29 beep_1.wav, 0, 0.50, 0 ; squadmate message menu appears
$Name: 30 beep_1.wav, 0, 0.50, 0 ; squadmate message menu disappears
$Name: 31 debris.wav, 0, 0.40, 2, 100, 300 ; ** debris sound (persistant, looping) (3d sound)
$Name: 32 subhit.wav, 0, 0.60, 0 ; subsystem gets destroyed on player ship
$Name: 33 m_load.wav, 0, 0.60, 1, 10, 50 ; missle start load (during rearm/repair) (3d sound)
$Name: 34 m_lock.wav, 0, 0.50, 1, 10, 50 ; missle load (during rearm/repair) (3d sound)
$Name: 35 repair.wav, 0, 0.50, 0 ; ship is being repaired (during rearm/repair) (looped)
$Name: 36 l_hit.wav, 0, 0.90, 0, 30, 100 ; * player ship is hit by laser fire (3d sound)
$Name: 37 m_hit.wav, 0, 0.90, 0, 30, 100 ; * player ship is hit by missile (3d sound)
$Name: 38 cycle.wav, 0, 0.80, 0 ; countermeasure cycle
$Name: 39 s_hit_4.wav, 0, 0.60, 1, 200, 600 ; * shield hit (3d sound)
$Name: 40 s_hit_2.wav, 0, 0.80, 1, 10, 100 ; * player shield is hit (3d sound)
$Name: 41 select.wav, 0, 0.60, 0 ; mouse click
$Name: 42 alert_3.wav, 0, 0.60, 0 ; aspect launch warning
$Name: 43 beep_4.wav, 0, 0.60, 0 ; shield quadrant transfer successful
$Name: 44 wash.wav, 0, 0.80, 1, 200, 400 ; Engine wash looping sound
$Name: 45 warp_1.wav, 0, 0.60, 2, 750, 1500 ; ** warp hole opening up for arriving (3d sound)
$Name: 46 warp_1.wav, 0, 0.60, 2, 750, 1500 ; ** warp hole opening up for departing (3d sound)
$Name: 47 aburn_1f.wav, 0, 0.50, 0 ; player warp has failed
$Name: 48 static.wav, 0, 0.60, 0 ; hud gauge static
$Name: 49 boom_1.wav, 0, 0.90, 1, 600, 1200 ; * ship explosion 2 (3d sound)
$Name: 50 rev1.wav, 0, 0.70, 0 ; ship is warping out in 3rd person
$Name: 51 s_hit_0.wav, 0, 0.70, 1, 100, 200 ; * heavy ship-ship collide sound (3d sound)
$Name: 52 collide.wav, 0, 0.70, 1, 100, 200 ; * light ship-ship collide sound (3d sound)
$Name: 53 s_hit_1.wav, 0, 0.70, 1, 100, 200 ; * shield ship-ship collide overlay sound (3d sound)
$Name: 54 alert_1.wav, 0, 0.50, 0 ; missile threat indicator flashes
$Name: 55 proximity1.wav, 0, 0.70, 0 ; proximity warning (heat seeker)
$Name: 56 proximity2.wav, 0, 0.70, 0 ; proximity warning (aspect)
$Name: 57 directive.wav, 0, 0.70, 0 ; directive complete
$Name: 58 subhit2.wav, 0, 0.90, 1, 250, 800 ; * other ship subsystem destroyed (3d sound)
$Name: 59 atomic.wav, 0, 0.90, 1, 2000, 4000 ; * captial ship explosion (3d sound)
$Name: 60 subhit2.wav, 0, 0.90, 1, 250, 1500 ; * captial ship subsystem destroyed (3d sound)
$Name: 61 warp2.wav, 0, 1.00, 1, 1500, 2000 ; [obsolete] large ship warps out (looping 3d sound)
$Name: 62 ast_lghit.wav, 0, 0.80, 1, 750, 1500 ; ** large asteroid blows up (3d sound)
$Name: 63 ast_smhit.wav, 0, 0.80, 1, 500, 1000 ; ** small asteroid blows up (3d sound)
$Name: 64 cue_voice.wav, 0, 0.90, 0 ; sound to indicate voice is about to start
$Name: 65 end_voice.wav, 0, 0.90, 0 ; sound to indicate voice has ended
$Name: 66 scan.wav, 0, 0.50, 0 ; cargo scanning (looping)
$Name: 67 l_flyby.wav, 0, 0.80, 1, 50, 250 ; * weapon flyby sound
$Name: 68 asteroid.wav, 0, 0.50, 1, 200, 700 ; [obsolete] asteroid sound (persistant, looping) (3d sound)
$Name: 69 warp_open.wav, 0, 1.00, 2, 2000, 4000 ; capital warp hole opening (3d sound)
$Name: 70 warp_close.wav, 0, 1.00, 2, 2000, 4000 ; capital warp hole closing (3d sound)
$Name: 71 rumble.wav, 0, 0.70, 1, 600, 1000 ; LARGE engine ambient
$Name: 72 subspace_left.wav, 0, 0.30, 0 ; subspace ambient sound (left channel) (looping)
$Name: 73 subspace_right.wav, 0, 0.30, 0 ; subspace ambient sound (right channel) (looping)
$Name: 74 Evaded.wav, 0, 0.70, 0 ; "evaded" HUD popup
$Name: 75 rumble.wav, 0, 0.70, 1, 600, 1000 ; HUGE engine ambient
;
; Weapons section
;
$Name: 76 L_Sidearm.wav, 0, 0.50, 1, 50, 400 ; SD-4 Sidearm laser fired
$Name: 77 L_Scalpel.wav, 0, 0.50, 1, 50, 400 ; DR-2 Scalpel fired
$Name: 78 L_Flail2.wav, 0, 0.50, 1, 50, 400 ; Flail II fired
$Name: 79 L_Prom_R.wav, 0, 0.50, 1, 50, 400 ; Prometheus R laser fired
$Name: 80 L_Prom_S.wav, 0, 0.50, 1, 50, 400 ; Prometheus S laser fired
$Name: 81 L_Newton.wav, 0, 0.50, 1, 50, 400 ; GTW-66 Newton Cannon fired
$Name: 82 L_Kayser.wav, 0, 0.55, 1, 50, 400 ; UD-8 Kayser Laser fired
$Name: 83 L_Circle.wav, 0, 0.50, 1, 50, 400 ; GTW-19 Circe laser fired
$Name: 84 L_Lich.wav, 0, 0.50, 1, 50, 400 ; GTW-83 Lich laser fired
$Name: 85 hit_1.wav, 0, 0.90, 1, 200, 800 ; Laser impact
$Name: 86 L_Vasmid.wav, 0, 0.50, 1, 50, 400 ; Subach-HLV Vasudan laser
$Name: 87 m_wasp.wav, 0, 0.80, 1, 50, 400 ; rockeye missile launch
$Name: 88 boom_2.wav, 0, 0.80, 1, 500, 1000 ; missile impact 1
$Name: 89 m_mag.wav, 0, 0.80, 1, 50, 400 ; mag pulse missile launch
$Name: 90 m_fury.wav, 0, 0.80, 1, 50, 400 ; fury missile launch
$Name: 91 m_shrike.wav, 0, 0.80, 1, 50, 400 ; shrike missile launch
$Name: 92 m_angel.wav, 0, 0.80, 1, 50, 400 ; angel fire missile launch
$Name: 93 m_cluster.wav, 0, 0.80, 1, 50, 400 ; cluster bomb launch
$Name: 94 m_clusterb.wav, 0, 0.80, 1, 50, 400 ; cluster baby bomb launch
$Name: 95 m_stiletto.wav, 0, 0.80, 1, 50, 400 ; stiletto bomb launch
$Name: 96 m_tsunami.wav, 0, 0.80, 1, 50, 400 ; tsunami bomb launch
$Name: 97 m_harbinger.wav, 0, 0.80, 1, 50, 400 ; harbinger bomb launch
$Name: 98 m_mega.wav, 0, 0.80, 1, 50, 400 ; mega wokka launch
$Name: 99 counter_1.wav, 0, 0.70, 1, 50, 200 ; countermeasure 1 launch
$Name: 100 l_alien1.wav, 0, 0.60, 1, 50, 400 ; Shivan light laser (3d sound)
$Name: 101 clusterboom.wav, 0, 0.80, 1, 750, 2000 ; shockwave ignition (3d sound)
$Name: 102 m_swarm.wav, 0, 0.70, 1, 50, 400 ; swarm missile sound (3d sound)
$Name: 103 l_alien2.wav, 0, 0.60, 1, 100, 400 ; Shivan heavy laser (3d sound)
$Name: 104 capital4.wav, 0, 0.70, 1, 500, 1500 ; Vasudan SuperCap engine (3d sound)
$Name: 105 capital5.wav, 0, 0.70, 1, 500, 1500 ; Shivan SuperCap engine (3d sound)
$Name: 106 capital6.wav, 0, 0.70, 1, 500, 1500 ; Terran SuperCap engine (3d sound)
$Name: 107 l_vaslight.wav, 0, 0.60, 1, 50, 400 ; Vasudan light laser fired (3d sound)
$Name: 108 l_alien3.wav, 0, 0.60, 1, 50, 400 ; Shivan heavy laser (3d sound)
$Name: 109 shockwave.wav, 0, 1.00, 1, 50, 800 ; ** shockwave impact (3d sound)
$Name: 110 Turret_T1.wav, 0, 0.50, 2, 200, 1000 ; TERRAN TURRET 1
$Name: 111 Turret_T2.wav, 0, 0.50, 2, 200, 1000 ; TERRAN TURRET 2
$Name: 112 Turret_V1.wav, 0, 0.50, 2, 200, 1000 ; VASUDAN TURRET 1
$Name: 113 Turret_V2.wav, 0, 0.50, 2, 200, 1000 ; VASUDAN TURRET 2
$Name: 114 Turret_S1.wav, 0, 0.50, 2, 200, 1000 ; SHIVAN TURRET 1
$Name: 115 paintloop.wav, 0, 0.60, 1, 50, 200 ; targeting laser loop sound
$Name: 116 FlakLaunch.wav, 0, 0.60, 1, 250, 1000 ; Flak Gun Launch
$Name: 117 boom_4.wav, 0, 0.80, 1, 400, 800 ; Flak Gun Impact
$Name: 118 m_emp.wav, 0, 0.60, 1, 50, 400 ; EMP Missle
$Name: 119 Escape.wav, 0, 0.60, 1, 200, 600 ; Escape Pod Drone
$Name: 120 Vaporize1.wav, 0, 0.70, 0 ; Beam Hit 1
$Name: 121 beam_loop.wav, 0, 0.70, 2, 1500, 3000 ; beam loop
$Name: 122 beam_up.wav, 0, 0.70, 2, 1500, 3000 ; beam power up
$Name: 123 beam_down.wav, 0, 0.70, 2, 1500, 3000 ; beam power down
$Name: 124 beam_shot1.wav, 0, 0.70, 2, 1500, 2500 ; Beam shot 1
$Name: 125 beam_shot2.wav, 0, 0.70, 2, 1500, 2500 ; Beam shot 2
;Ship Engine Sounds section
$Name: 126 ship_a1.wav, 0, 0.60, 1, 200, 400 ; Terran fighter engine (3d sound)
$Name: 127 ship_a2.wav, 0, 0.70, 1, 300, 600 ; Terran bomber engine (3d sound)
$Name: 128 ship_a3.wav, 0, 0.80, 1, 400, 800 ; Terran cruiser engine (3d sound)
$Name: 129 ship_b1.wav, 0, 0.70, 1, 200, 400 ; Vasudan fighter engine (3d sound)
$Name: 130 ship_b2.wav, 0, 0.80, 1, 300, 600 ; Vasudan bomber engine (3d sound)
$Name: 131 ship_b3.wav, 0, 0.80, 1, 400, 800 ; Vasudan cruiser engine (3d sound)
$Name: 132 ship_c1.wav, 0, 0.60, 1, 200, 400 ; Shivan fighter engine (3d sound)
$Name: 133 ship_c2.wav, 0, 0.70, 1, 300, 600 ; Shivan bomber engine (3d sound)
$Name: 134 ship_c3.wav, 0, 0.80, 1, 400, 800 ; Shivan cruiser engine (3d sound)
$Name: 135 beacon.wav, 0, 0.60, 1, 300, 600 ; Repair ship beacon/engine sound (3d sound)
$Name: 136 capital1.wav, 0, 0.70, 1, 500, 1500 ; Terran capital engine (3d sound)
$Name: 137 capital2.wav, 0, 0.70, 1, 500, 1500 ; Vasudan capital engine (3d sound)
$Name: 138 capital3.wav, 0, 0.70, 1, 500, 1500 ; Shivan capital engine (3d sound)
; Electrical arc sound fx on the debris pieces
$Name: 139 Arc_01.wav, 0, 0.30, 2, 200, 500 ; ** 0.10 second spark sound effect (3d sound)
$Name: 140 Arc_02.wav, 0, 0.30, 2, 200, 500 ; ** 0.25 second spark sound effect (3d sound)
$Name: 141 Arc_03.wav, 0, 0.30, 2, 200, 500 ; ** 0.50 second spark sound effect (3d sound)
$Name: 142 Arc_04.wav, 0, 0.30, 2, 200, 500 ; ** 0.75 second spark sound effect (3d sound)
$Name: 143 Arc_05.wav, 0, 0.30, 2, 200, 500 ; ** 1.00 second spark sound effect (3d sound)
; Beam Sounds
$Name: 144 BT_LTerSlash.wav, 0, 0.70, 2, 1500, 3000 ; LTerSlash beam loop
$Name: 145 BT_TerSlash.wav, 0, 0.70, 2, 1500, 3000 ; TerSlash beam loop
$Name: 146 BT_SGreen.wav, 0, 0.70, 2, 1500, 3000 ; SGreen beam loop
$Name: 147 BT_BGreen.wav, 0, 0.70, 2, 1500, 3000 ; BGreen beem loop
$Name: 148 BT_BFGreen.wav, 0, 0.70, 2, 1500, 3000 ; BFGreen been loop
$Name: 149 BT_AntiFtr.wav, 0, 0.70, 2, 1500, 3000 ; Antifighter beam loop
$Name: 150 BT_up_1.wav, 0, 0.60, 2, 1500, 3000 ; 1 sec warm up
$Name: 151 BT_up_1.5.wav, 0, 0.60, 2, 1500, 3000 ; 1.5 sec warm up
$Name: 152 BT_up_2.5.wav, 0, 0.60, 2, 1500, 3000 ; 2.5 sec warm up
$Name: 153 BT_up_3.wav, 0, 0.60, 2, 1500, 3000 ; 3 sec warm up
$Name: 154 BT_up_3.5.wav, 0, 0.60, 2, 1500, 3000 ; 3.5 sec warm up
$Name: 155 BT_up_5.wav, 0, 0.60, 2, 1500, 3000 ; 5 sec warm up
$Name: 156 BT_dwn_1.wav, 0, 0.70, 2, 2000, 3000 ; LTerSlash warm down
$Name: 157 BT_dwn_2.wav, 0, 0.70, 2, 2000, 3000 ; TerSlash warm down
$Name: 158 BT_dwn_3.wav, 0, 0.70, 2, 2000, 3000 ; SGreen warm down
$Name: 159 BT_dwn_4.wav, 0, 0.70, 2, 2000, 3000 ; BGreen warm down
$Name: 160 BT_dwn_5.wav, 0, 0.70, 2, 2000, 3000 ; BFGreen warm down
$Name: 161 BT_dwn_6.wav, 0, 0.70, 2, 2000, 3000 ; T_AntiFtr warm down
$Name: 162 Empty, 0, 0.50, 0
$Name: 163 Empty, 0, 0.50, 0
$Name: 164 Empty, 0, 0.50, 0
$Name: 165 Empty, 0, 0.50, 0
$Name: 166 Empty, 0, 0.50, 0
$Name: 167 Empty, 0, 0.50, 0
$Name: 168 Empty, 0, 0.50, 0
$Name: 169 Empty, 0, 0.50, 0
$Name: 170 Empty, 0, 0.50, 0
$Name: 171 Empty, 0, 0.50, 0
$Name: 172 Empty, 0, 0.50, 0
$Name: 173 SupNova1.wav, 0, 1.00, 0 ; SuperNova (distant)
$Name: 174 SupNova2.wav, 0, 1.00, 0 ; SuperNova (shockwave)
$Name: 175 ship_c4.wav, 0, 0.80, 1, 400, 800 ; Shivan large engine (3d sound)
$Name: 176 ship_c5.wav, 0, 0.80, 1, 400, 1000 ; Shivan large engine (3d sound)
$Name: 177 BS_SRed.wav, 0, 0.70, 2, 1500, 3000 ; SRed beam loop
$Name: 178 BS_LRed.wav, 0, 0.70, 2, 1500, 3000 ; LRed beam loop
$Name: 179 BS_AntiFtr.wav, 0, 0.70, 2, 1500, 3000 ; Antifighter beam loop
$Name: 180 Thunder_01.wav, 0, 0.70, 0 ; Thunder 1 sound in neblua
$Name: 181 Thunder_02.wav, 0, 0.70, 0 ; Thunder 2 sound in neblua
$Name: 182 BS_up_1.wav, 0, 0.60, 2, 1500, 3000 ; 1 sec warm up
$Name: 183 BS_up_1.5.wav, 0, 0.60, 2, 1500, 3000 ; 1.5 sec warm up
$Name: 184 BS_up_3.wav, 0, 0.60, 2, 1500, 3000 ; 3 sec warm up
$Name: 185 Commnode.wav, 0, 0.60, 1, 200, 500 ; Shivan Commnode
$Name: 186 Pirate.wav, 0, 0.60, 1, 400, 1000 ; Volition PirateShip
$Name: 187 BS_dwn_1.wav, 0, 0.70, 2, 2000, 3000 ; SRed warm down
$Name: 188 BS_dwn_2.wav, 0, 0.70, 2, 2000, 3000 ; LRed warm down
$Name: 189 BS_dwn_3.wav, 0, 0.70, 2, 2000, 3000 ; AntiFtr warm down
$Name: 190 Inst1.wav, 0, 0.80, 1, 500, 2000 ; Instellation 1
$Name: 191 Inst2.wav, 0, 0.80, 1, 500, 2000 ; Instellation 2
;
#Game Sounds End
;
#Interface Sounds Start
$Name: 0 user_c.wav, 0, 0.70, 0 ; mouse click
$Name: 1 empty, 0, 0.70, 0 ; pick up a ship icon (not used)
$Name: 2 load01.wav, 0, 0.60, 0 ; drop a ship icon on a wing slot
$Name: 3 unload01.wav, 0, 0.60, 0 ; drop a ship icon back to the list
$Name: 4 beep_4.wav, 0, 0.70, 0 ; press briefing, ship selection or weapons bar (top-left)
$Name: 5 user_c.wav, 0, 0.70, 0 ; Switching to a new screen, but not commit
$Name: 6 beep_4.wav, 0, 0.70, 0 ; help pressed
$Name: 7 commit.wav, 0, 0.60, 0 ; commit pressed
$Name: 8 user_c.wav, 0, 0.70, 0 ; prev/next pressed
$Name: 9 user_c.wav, 0, 0.70, 0 ; scroll pressed (and scroll)
$Name: 10 fail.wav, 0, 0.70, 0 ; general failure sound for any event
$Name: 11 shipview.wav, 0, 0.50, 0 ; ship animation starts (ie text and ship first appear)
$Name: 12 main_amb.wav, 0, 0.60, 0 ; ambient sound for the Terran main hall (looping)
$Name: 13 vas_amb.wav, 0, 0.60, 0 ; ambient sound for the Vasudan main hall (looping)
$Name: 14 user_a.wav, 0, 0.70, 0 ; brief stage change
$Name: 15 user_i.wav, 0, 0.70, 0 ; brief stage change fail
$Name: 16 beep_3.wav, 0, 0.70, 0 ; selet brief icon
$Name: 17 user_o.wav, 0, 0.50, 0 ; user_over (mouse over a control)
$Name: 18 user_c.wav, 0, 0.70, 0 ; user_click (mouse selects a control)
$Name: 19 reset.wav, 0, 0.70, 0 ; reset (or similar button) pressed
$Name: 20 textdraw.wav, 0, 0.60, 0 ; briefing text wipe
$Name: 21 Lift_Mix.wav, 0, 0.50, 0 ; main hall - elevator
$Name: 22 weapview.wav, 0, 0.60, 0 ; weapon animation starts
$Name: 23 dooropen.wav, 0, 0.50, 0 ; door in main hall opens
$Name: 24 doorclose.wav, 0, 0.50, 0 ; door in main hall closes
$Name: 25 itemdraw.wav, 0, 0.50, 0 ; glow in main hall opens
$Name: 26 Crane_1.wav, 0, 0.50, 0 ; main hall - crane 1
$Name: 27 sub_amb.wav, 0, 0.60, 0 ; ambient sound for menus off the main hall (looping)
$Name: 28 user_c.wav, 0, 0.70, 0 ; popup dialog box appeared
$Name: 29 user_c.wav, 0, 0.70, 0 ; popup dialog box goes away
$Name: 30 1_yes.wav, 0, 1.00, 0 ; voice clip played when volume slider changes
$Name: 31 Crane_2.wav, 0, 0.50, 0 ; main hall - crane 2
$Name: 32 Option1.wav, 0, 0.70, 0 ; main hall options - mouse on
$Name: 33 Option2.wav, 0, 0.70, 0 ; main hall options - mouse off
$Name: 34 Techroom1.wav, 0, 0.70, 0 ; main hall tech room - mouse on
$Name: 35 Techroom2.wav, 0, 0.70, 0 ; main hall tech room - mouse off
$Name: 36 Exitopen.wav, 0, 0.60, 0 ; main hall exit open
$Name: 37 Exitclose.wav, 0, 0.60, 0 ; main hall exit close
$Name: 38 pa_1.wav, 0, 0.50, 0 ; main hall random intercom 1
$Name: 39 pa_2.wav, 0, 0.50, 0 ; main hall random intercom 2
$Name: 40 pa_3.wav, 0, 0.50, 0 ; main hall random intercom 3
$Name: 41 highlight.wav, 0, 0.40, 0 ; spinning highlight in briefing
$Name: 42 noiz.wav, 0, 0.40, 0 ; static in a briefing stage cut
$Name: 43 Camp_on.wav, 0, 0.70, 0 ; main hall campaign - mouse on
$Name: 44 Camp_off.wav, 0, 0.70, 0 ; main hall campaign - mouse off
$Name: 45 V_Hatch_Open.wav, 0, 0.70, 0 ; vasudan hall - exit open
$Name: 46 V_Hatch_Close.wav, 0, 0.70, 0 ; vasudan hall - exit close
$Name: 47 V_Roll_Open.wav, 0, 0.80, 0 ; vasudan hall - hatch open
$Name: 48 V_Roll_Close.wav, 0, 0.80, 0 ; vasudan hall - hatch close
$Name: 49 V_Lift_Up.wav, 0, 0.70, 0 ; vasudan hall - lift up
$Name: 50 V_Lift_Down.wav, 0, 0.70, 0 ; vasudan hall - lift down
$Name: 51 V_Lite_On.wav, 0, 0.70, 0 ; vasudan hall - glow on
$Name: 52 V_Lite_Off.wav, 0, 0.70, 0 ; vasudan hall - glow off
$Name: 53 Skiff.wav, 0, 0.70, 0 ; vasudan hall - skiff loop
$Name: 54 V_Map_On.wav, 0, 0.70, 0 ; vasudan hall - screen on
$Name: 55 V_Map_Off.wav, 0, 0.70, 0 ; vasudan hall - screen off
$Name: 56 V_Head_1.wav, 0, 0.70, 0 ; vasudan hall - vasudan greeting
$Name: 57 V_Head_2.wav, 0, 0.70, 0 ; vasudan hall - vasudan bye
$Name: 58 V_Pa_01.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 1
$Name: 59 V_Pa_02.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 2
$Name: 60 V_Pa_03.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 3
$Name: 61 bup.wav, 0, 0.90, 0 ; bup bup bup-bup bup bup
$Name: 62 thankyou.wav, 0, 0.90, 0 ; thankyou
$Name: 63 V_Exit_Open.wav, 0, 0.70, 0 ; vasudan hall - exit open
$Name: 64 V_Exit_Close.wav, 0, 0.70, 0 ; vasudan hall - exit close
;
#Interface Sounds End
;
; Each species can have up to 4 different flyby sounds
; NOTE : the parse code expects to see exactly 2 sounds for terran, then 2 for vasudan, then 2 for shivan
; the first sound for each species is the fighter/small flyby sound. the second is the bomber/big flyby sound
#Flyby Sounds Start

$Terran: 0 T_flyby1.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)
$Terran: 1 T_flyby2.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)

$Vasudan: 0 V_flyby1.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)
$Vasudan: 1 V_flyby2.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)

$Shivan: 0 S_flyby1.wav, 0, 0.75, 1, 200, 400 ; * SHIVAN ship1 flyby player sound (3d sound)
$Shivan: 1 S_flyby2.wav, 0, 0.75, 1, 200, 400 ; * SHIVAN ship1 flyby player sound (3d sound)

#Flyby Sounds End
</pre>

[[Category:Tables]]

Command-Line Reference

2012-02-09T05:39:00Z

IssMneur: /* Troubleshooting */ Document -disable_di_mouse

The following command-line options can be chosen from the launcher.

===Graphics===
====-spec====
'''"Enable Specular"'''

Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).

====-env====
'''"Enable Environment maps"'''

It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]

====-glow====
'''"Enable Glowmaps"'''

Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)

====-mipmap====
'''"Enable mipmapping"'''

Causes for non-mipmapped textures to have mipmaps generated within the GPU on certain kind of texture formats, (IIRC, DDS formatted textures with a power of 2 size in both width and height). 
Since the use of already mipmapped DDS textures has become common, it has become depreciated.
The quality of the generated mipmaps depends on each GPU and used driver. It is normally used with [[Command-Line_Reference#-img2dds|-img2dds]] flag.

====-nomotiondebris====
'''"Disable motion debris"'''

====-noscalevid====
"Disable scale-to-window for Movies"

Disables fullscreen scaling of video clips.

====-missile_lighting====
'''"Apply Lighting to Missiles"'''

====-normal====
'''"Enable Normal Maps"'''

Normal maps require GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)

====-post_process====
'''"Enable Post Processing"'''

enables the use (if present) of post-processing effects as defined by the post_process.tbl. Bloom usage has an additional cmdline option for setting it's value, most post processing effects are achieved in mission per the mission designer or can be enabled globally in the table.

====-soft_particles====
'''"Enable soft particles"'''

====-3dshockwave====
'''"Enable 3D Shockwaves"'''

This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-fxaa====
'''"Enable FXAA antialiasing"'''

Enables the FXAA postprocessing stage. Needs optional FXAA shaders, which can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-flightshaftsoff====
'''"Force Lightshafts off"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission.

===Game Speed===
====-img2dds====
'''"Compress non-compressed images"'''

Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
'''"Disable vertical sync"'''

====-cache_bitmaps====
'''"Cache bitmaps between missions"'''

Will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
'''"Another Pair of Scanning Lines"'''

Adds a second pair of scanning lines to the target window when scanning an object.

====-targetinfo====
'''"Enable Info next to Target"'''

Displays target info, such as name and class, beside the targeted object.

====-orbradar====
'''"Enables 3D radar"'''

An Orb style 3D radar will replace the standard 2D version.

====-rearm_timer====
'''"Enable Rearm/Repair Completion Timer"'''

Displays time remaining until rearm and repair from a support ship is complete.

====-ballistic_gauge====
'''"Enable the analog Ballistic Ammo gauge"'''

Adds an ammo gauge to the HUD when armed with a ballistic weapon.

===Gameplay===
====-ship_choice_3d====
'''"Use Models for Ship Selection"'''

Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.

====-weapon_choice_3d====
'''"Use Models for Weapon Selection"'''

Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.

====-3dwarp====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

====-warp_flash====
'''"Enable Flash upon Warp"'''

Enable a flash at warp in and warp out.

====-no_ap_interrupt====
'''"Disable Interrupting of AutoPilot"'''

Tells the game to not allow players to interrupt an autopilot already-in-progress.

===Audio===
====-snd_preload====
'''"Preload mission game sounds"'''

Useful in preventing game stuttering when sounds are played for the first time.

====-nosound====
'''"Disable Sound and Music"'''

====-nomusic====
'''"Disables Music"'''

===Multiplayer===
====-standalone====
'''"Run as Stand Alone Server"'''

Creates a standalone multi-player server.

====-startgame====
'''"Skip Mainhall and Start Hosting"'''

Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
'''"Start Hosted Server as Closed"'''

Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
'''"Host Confirms Join requests"'''

Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder—or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
'''"Disables Flight Deck option"'''

Disables return to the flight deck screen after a mission completes.

===Troubleshooting===
====-nohtl====
'''"Software Mode (very slow)"'''
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
'''"Disable Setting of Gamma"'''

Disables the gamma settings in the options screen.

====-nomovies====
'''"Disable Video Playback"'''

Disables all video playback.

====-noparseerrors====
'''"Disable Parsing Errors"'''

Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.

====-safeloading====
Loads missions the old way. Typically safer, but slower.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-query_speech====
'''"Does this build have Speech?"'''

Determines if the current build includes text-to-speech.

====-novbo====
'''"Disable OpenGL VBO"'''

====-noibx====
'''"Don't use cached index buffers (IBX)"'''

Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.

====-loadallweps====
'''"Load all weapons, even those not used"'''

====-disable_fbo====
'''"Disable OpenGL RenderTargets"'''

====-no_glsl====
'''"Disable GLSL (shader) Support"'''

Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

====-disable_glsl_model====
'''"Don't use shaders for model rendering"'''

====-ati_swap====
'''"Fix Color issues on some ATI cards"'''

====-no_3d_sound====
'''"Use only 2D/stereo for sound effects"'''

====-disable_di_mouse====
'''"Disables the DirectInput mouse code for FSO on windows."'''

'''Windows Only''' Can make mouse movement smoother on certain machines.

===Experimental===
====-ingame_join====
'''"Allows Ingame Joining"'''

Enables ingame joining in multiplayer. FIXME: Host option?

====-voicer====
'''"Voice Recognition"'''

Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

===Development Tools===
====-fps====
'''"Show frames per second on HUD"'''

Displays current frames per second.

====-pos====
'''"Show Position of Camera"'''

Displays current position coordinates of camera.

====-window====
'''"Run in Window"'''

Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.

====-fullscreen_window====
'''"Run in Fullscreen Window"'''

====-timerbar====
Displays a timing bar across the top of the screen. Timerbar format varies by build. This is a relic from the Volition development days, and is unmaintained.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-stats====
'''"Show Statistics"'''

Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
'''"Show Coordinates"'''

Shows coordinates of the mouse cursor.

====-show_mem_usage====
'''"Show Memory Usage"'''

Shows detailed RAM usage based on file, handler and process usage and display on the left-center side of the screen during mission load and while in mission.

The meaning of the info displayed in the upper right corner of the HUD is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod. 
Details for each object are output to a pofspew.txt file created in the data folder. 
Otherwise, ibx files are created in game before each mission.

====-tablecrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-table_crcs MediaVPs" will create a table_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the tables used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-missioncrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-mission_crcs MediaVPs" will create a mission_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the missions used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-dis_collisions====
'''"Disable Collisions"'''

Disables all collisions.

====-dis_weapons====
'''"Disable Weapon Rendering"'''

Disables weapons rendering.

====-output_sexps====
'''"Outputs SEXPs to sexps.html"'''

====-output_scripting====
'''"Outputs scripting to scripting.html"'''

====-nograb====
Unix only. Disables focus grabbing in a window.

====-save_render_target====
'''"Save Render Targets to file"'''

====-debug_window====
'''"Display Debug Window"'''

Lists the fs2_open.log in (nearly)real-time generation.

====-verify_vps====
'''"Spew VP crcs to vp_crcs.txt"'''

Exports the CRC values of the VP files being loaded into a vp_crcs.txt file.

====-reparse_mainhall====
'''"Reparse mainhall.tbl when loading halls"'''

Mainhall.tbl will be reparsed every time a mainhall is loaded, as opposed to just once at game startup.

====-start_mission====
'''"Skip the mainhall in jump right into the specified mission"'''

Jump into the mission specified by the filename. Only in effect on the first run. This will skip load of the mainhall and its other related things altogether.

==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

===Lighting===
These factors can dramatically alter the atmosphere of the game. [[Sample Lighting Settings|This page]] has some sample lighting settings with screenshots.

====-ambient_factor====
This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra-realistic dark looking.

====-spec_exp====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16. However, 11 is recommended. This is a relative value.

====-spec_point====
This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0. However, 0.6 is recommended. This is a relative value.

====-spec_static====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, is 0.8 recommended. This is a relative value.

====-spec_tube====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, 0.4 is recommended. This is a relative value.

====-ogl_spec====
Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focused and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

===Graphics===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-res====
Allows you to specify a resolution if the desired one cannot be set in the Launcher.
For example, -res 1920x1080 would run the game in 1920 x 1080 resolution. Since it requires an argument, it needs to be entered as a custom flag when using the Launcher. The "Run at specified resolution" option the Launcher gives is essentially this, but without being able to actually specify a resolution, it doesn't work.

====-fxaa_preset====
Requires both -post_processing and -fxaa. Can be used to adjust the FXAA quality and speed, 0 is fastest, 6 is highest quality. Default setting is 3.

===Gameplay===
====-mod====
{{Note| Please note that the ''[[mod.ini]]'' file is a feature exclusive to the Windows Launcher.}}
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behavior, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and [[mod.ini]] file.

Within the Launcher's MOD tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''.
If ''Freespace2/moddir/[[mod.ini]]'' exists it will be used to modify the -mod flag, too.

For further details, see '''[[mod.ini]]'''

'''Data precedence'''

As already said, within the different directories, the data precedence is set by the specified order in the -mod flag. The lowest priority goes to the Freespace2 installation directory.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are "similar" to zip archives. They just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order, so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter that this ''Mission.fs2'' is also inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhanced ones adding them in a higher priority place.

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

{{Warning| '''Priority and Texture Formats'''

''Obsolete behavior - Until FS2_open v3.6.9.:''

FS2_Open can use several file formats in textures: [http://en.wikipedia.org/wiki/PCX PCX], [http://en.wikipedia.org/wiki/DirectDraw_Surface DDS], [http://en.wikipedia.org/wiki/JPG JPG] and [http://en.wikipedia.org/wiki/TGA TGA]. Make sure you keep the format when you update your texture. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

The reason to do this is that, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. This behavior can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one.

''New behavior - From FS2_open v3.6.10. (including previous beta testing releases):''

The former issue has been fixed. Now texture format priority is only applied within the same location. In this ''strange'' situation it goes DDS -> TGA -> JPG -> PCX. Examples:
* ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.dds'' is loaded instead of ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.tga''.
* But your improved ''/Freespace2/data/maps/MyTexture.xxx'' will override them both despite of its format.
In this way, when you update any texture, you don't have to pay attention to its original format. Just place it in a higher priority place.

Nevertheless, global priority is kept between animated and static textures. Because of their management, animated textures (ANIs and EFFs) are looked for BEFORE static ones. In this way there's no way to update an animated texture with a static one (an obsolete ANI is always going to be loaded before the newer DDS version). The solution: use an updated EFF with just one frame.

}}

====-fov====
Specifies the Field of View for the player eyepoint.

Takes one argument decimal specifying the angle of the viewing cone in radians, from 0 to 2*pi

You can set the cone of view making things look bigger/smaller. The problem with this is that if you choose a small FOV, you will have a squashed look on the edges of your screen - stretched edges with a too high FOV. It is recommended to change the FOV as FS2 normally has some perspective distortion at the screen edges (FOV too high). Set the FOV to something like 0.39 - it will fix the distortion problem, and (as a nice side-effect) will make everything look bigger and more realistic scale-wise. On the other hand, it also stretches the backgrounds - this is usually not a big issue, but it does get annoying if using a skybox.
The default is 0.75, if you go higher, you'll get the fish-eye effect. Feel free to experiment. This must be entered into the "Custom flags" field

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a standalone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a standalone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a standalone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}
====-timeout====
{{Sectstub}}
====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low, then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

[[Category:Lists]]
[[Category:Source Code Project]]

Command-Line Reference

2012-02-09T05:30:59Z

IssMneur: /* Development Tools */ Add -start_mission

The following command-line options can be chosen from the launcher.

===Graphics===
====-spec====
'''"Enable Specular"'''

Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).

====-env====
'''"Enable Environment maps"'''

It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]

====-glow====
'''"Enable Glowmaps"'''

Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)

====-mipmap====
'''"Enable mipmapping"'''

Causes for non-mipmapped textures to have mipmaps generated within the GPU on certain kind of texture formats, (IIRC, DDS formatted textures with a power of 2 size in both width and height). 
Since the use of already mipmapped DDS textures has become common, it has become depreciated.
The quality of the generated mipmaps depends on each GPU and used driver. It is normally used with [[Command-Line_Reference#-img2dds|-img2dds]] flag.

====-nomotiondebris====
'''"Disable motion debris"'''

====-noscalevid====
"Disable scale-to-window for Movies"

Disables fullscreen scaling of video clips.

====-missile_lighting====
'''"Apply Lighting to Missiles"'''

====-normal====
'''"Enable Normal Maps"'''

Normal maps require GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)

====-post_process====
'''"Enable Post Processing"'''

enables the use (if present) of post-processing effects as defined by the post_process.tbl. Bloom usage has an additional cmdline option for setting it's value, most post processing effects are achieved in mission per the mission designer or can be enabled globally in the table.

====-soft_particles====
'''"Enable soft particles"'''

====-3dshockwave====
'''"Enable 3D Shockwaves"'''

This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-fxaa====
'''"Enable FXAA antialiasing"'''

Enables the FXAA postprocessing stage. Needs optional FXAA shaders, which can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-flightshaftsoff====
'''"Force Lightshafts off"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission.

===Game Speed===
====-img2dds====
'''"Compress non-compressed images"'''

Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
'''"Disable vertical sync"'''

====-cache_bitmaps====
'''"Cache bitmaps between missions"'''

Will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
'''"Another Pair of Scanning Lines"'''

Adds a second pair of scanning lines to the target window when scanning an object.

====-targetinfo====
'''"Enable Info next to Target"'''

Displays target info, such as name and class, beside the targeted object.

====-orbradar====
'''"Enables 3D radar"'''

An Orb style 3D radar will replace the standard 2D version.

====-rearm_timer====
'''"Enable Rearm/Repair Completion Timer"'''

Displays time remaining until rearm and repair from a support ship is complete.

====-ballistic_gauge====
'''"Enable the analog Ballistic Ammo gauge"'''

Adds an ammo gauge to the HUD when armed with a ballistic weapon.

===Gameplay===
====-ship_choice_3d====
'''"Use Models for Ship Selection"'''

Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.

====-weapon_choice_3d====
'''"Use Models for Weapon Selection"'''

Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.

====-3dwarp====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

====-warp_flash====
'''"Enable Flash upon Warp"'''

Enable a flash at warp in and warp out.

====-no_ap_interrupt====
'''"Disable Interrupting of AutoPilot"'''

Tells the game to not allow players to interrupt an autopilot already-in-progress.

===Audio===
====-snd_preload====
'''"Preload mission game sounds"'''

Useful in preventing game stuttering when sounds are played for the first time.

====-nosound====
'''"Disable Sound and Music"'''

====-nomusic====
'''"Disables Music"'''

===Multiplayer===
====-standalone====
'''"Run as Stand Alone Server"'''

Creates a standalone multi-player server.

====-startgame====
'''"Skip Mainhall and Start Hosting"'''

Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
'''"Start Hosted Server as Closed"'''

Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
'''"Host Confirms Join requests"'''

Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder—or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
'''"Disables Flight Deck option"'''

Disables return to the flight deck screen after a mission completes.

===Troubleshooting===
====-nohtl====
'''"Software Mode (very slow)"'''
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
'''"Disable Setting of Gamma"'''

Disables the gamma settings in the options screen.

====-nomovies====
'''"Disable Video Playback"'''

Disables all video playback.

====-noparseerrors====
'''"Disable Parsing Errors"'''

Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.

====-safeloading====
Loads missions the old way. Typically safer, but slower.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-query_speech====
'''"Does this build have Speech?"'''

Determines if the current build includes text-to-speech.

====-novbo====
'''"Disable OpenGL VBO"'''

====-noibx====
'''"Don't use cached index buffers (IBX)"'''

Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.

====-loadallweps====
'''"Load all weapons, even those not used"'''

====-disable_fbo====
'''"Disable OpenGL RenderTargets"'''

====-no_glsl====
'''"Disable GLSL (shader) Support"'''

Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

====-disable_glsl_model====
'''"Don't use shaders for model rendering"'''

====-ati_swap====
'''"Fix Color issues on some ATI cards"'''

====-no_3d_sound====
'''"Use only 2D/stereo for sound effects"'''

===Experimental===
====-ingame_join====
'''"Allows Ingame Joining"'''

Enables ingame joining in multiplayer. FIXME: Host option?

====-voicer====
'''"Voice Recognition"'''

Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

===Development Tools===
====-fps====
'''"Show frames per second on HUD"'''

Displays current frames per second.

====-pos====
'''"Show Position of Camera"'''

Displays current position coordinates of camera.

====-window====
'''"Run in Window"'''

Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.

====-fullscreen_window====
'''"Run in Fullscreen Window"'''

====-timerbar====
Displays a timing bar across the top of the screen. Timerbar format varies by build. This is a relic from the Volition development days, and is unmaintained.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-stats====
'''"Show Statistics"'''

Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
'''"Show Coordinates"'''

Shows coordinates of the mouse cursor.

====-show_mem_usage====
'''"Show Memory Usage"'''

Shows detailed RAM usage based on file, handler and process usage and display on the left-center side of the screen during mission load and while in mission.

The meaning of the info displayed in the upper right corner of the HUD is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod. 
Details for each object are output to a pofspew.txt file created in the data folder. 
Otherwise, ibx files are created in game before each mission.

====-tablecrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-table_crcs MediaVPs" will create a table_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the tables used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-missioncrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-mission_crcs MediaVPs" will create a mission_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the missions used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-dis_collisions====
'''"Disable Collisions"'''

Disables all collisions.

====-dis_weapons====
'''"Disable Weapon Rendering"'''

Disables weapons rendering.

====-output_sexps====
'''"Outputs SEXPs to sexps.html"'''

====-output_scripting====
'''"Outputs scripting to scripting.html"'''

====-nograb====
Unix only. Disables focus grabbing in a window.

====-save_render_target====
'''"Save Render Targets to file"'''

====-debug_window====
'''"Display Debug Window"'''

Lists the fs2_open.log in (nearly)real-time generation.

====-verify_vps====
'''"Spew VP crcs to vp_crcs.txt"'''

Exports the CRC values of the VP files being loaded into a vp_crcs.txt file.

====-reparse_mainhall====
'''"Reparse mainhall.tbl when loading halls"'''

Mainhall.tbl will be reparsed every time a mainhall is loaded, as opposed to just once at game startup.

====-start_mission====
'''"Skip the mainhall in jump right into the specified mission"'''

Jump into the mission specified by the filename. Only in effect on the first run. This will skip load of the mainhall and its other related things altogether.

==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

===Lighting===
These factors can dramatically alter the atmosphere of the game. [[Sample Lighting Settings|This page]] has some sample lighting settings with screenshots.

====-ambient_factor====
This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra-realistic dark looking.

====-spec_exp====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16. However, 11 is recommended. This is a relative value.

====-spec_point====
This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0. However, 0.6 is recommended. This is a relative value.

====-spec_static====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, is 0.8 recommended. This is a relative value.

====-spec_tube====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, 0.4 is recommended. This is a relative value.

====-ogl_spec====
Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focused and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

===Graphics===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-res====
Allows you to specify a resolution if the desired one cannot be set in the Launcher.
For example, -res 1920x1080 would run the game in 1920 x 1080 resolution. Since it requires an argument, it needs to be entered as a custom flag when using the Launcher. The "Run at specified resolution" option the Launcher gives is essentially this, but without being able to actually specify a resolution, it doesn't work.

====-fxaa_preset====
Requires both -post_processing and -fxaa. Can be used to adjust the FXAA quality and speed, 0 is fastest, 6 is highest quality. Default setting is 3.

===Gameplay===
====-mod====
{{Note| Please note that the ''[[mod.ini]]'' file is a feature exclusive to the Windows Launcher.}}
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behavior, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and [[mod.ini]] file.

Within the Launcher's MOD tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''.
If ''Freespace2/moddir/[[mod.ini]]'' exists it will be used to modify the -mod flag, too.

For further details, see '''[[mod.ini]]'''

'''Data precedence'''

As already said, within the different directories, the data precedence is set by the specified order in the -mod flag. The lowest priority goes to the Freespace2 installation directory.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are "similar" to zip archives. They just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order, so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter that this ''Mission.fs2'' is also inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhanced ones adding them in a higher priority place.

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

{{Warning| '''Priority and Texture Formats'''

''Obsolete behavior - Until FS2_open v3.6.9.:''

FS2_Open can use several file formats in textures: [http://en.wikipedia.org/wiki/PCX PCX], [http://en.wikipedia.org/wiki/DirectDraw_Surface DDS], [http://en.wikipedia.org/wiki/JPG JPG] and [http://en.wikipedia.org/wiki/TGA TGA]. Make sure you keep the format when you update your texture. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

The reason to do this is that, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. This behavior can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one.

''New behavior - From FS2_open v3.6.10. (including previous beta testing releases):''

The former issue has been fixed. Now texture format priority is only applied within the same location. In this ''strange'' situation it goes DDS -> TGA -> JPG -> PCX. Examples:
* ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.dds'' is loaded instead of ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.tga''.
* But your improved ''/Freespace2/data/maps/MyTexture.xxx'' will override them both despite of its format.
In this way, when you update any texture, you don't have to pay attention to its original format. Just place it in a higher priority place.

Nevertheless, global priority is kept between animated and static textures. Because of their management, animated textures (ANIs and EFFs) are looked for BEFORE static ones. In this way there's no way to update an animated texture with a static one (an obsolete ANI is always going to be loaded before the newer DDS version). The solution: use an updated EFF with just one frame.

}}

====-fov====
Specifies the Field of View for the player eyepoint.

Takes one argument decimal specifying the angle of the viewing cone in radians, from 0 to 2*pi

You can set the cone of view making things look bigger/smaller. The problem with this is that if you choose a small FOV, you will have a squashed look on the edges of your screen - stretched edges with a too high FOV. It is recommended to change the FOV as FS2 normally has some perspective distortion at the screen edges (FOV too high). Set the FOV to something like 0.39 - it will fix the distortion problem, and (as a nice side-effect) will make everything look bigger and more realistic scale-wise. On the other hand, it also stretches the backgrounds - this is usually not a big issue, but it does get annoying if using a skybox.
The default is 0.75, if you go higher, you'll get the fish-eye effect. Feel free to experiment. This must be entered into the "Custom flags" field

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a standalone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a standalone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a standalone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}
====-timeout====
{{Sectstub}}
====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low, then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

[[Category:Lists]]
[[Category:Source Code Project]]

Commandline

2012-02-09T05:23:15Z

IssMneur: Redirect this page so that search can find it

#REDIRECT [[Command-Line Reference]]

Engine limitations

2011-12-04T19:14:22Z

IssMneur: Add some general limits

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, developed to boost engine limits. Starting with FS2_Open 3.6.10 these builds can be used in Multiplayer, older builds are not capable of joining the servers due to several incompatibilities. In addition, Inferno and regular builds are incompatible to each other in Multiplayer; someone using an Inferno build will not be able to play with someone using a regular build and vice versa. Those builds are named after the [[Inferno]] mod, but are extensively used by many other projects, like [[The Babylon Project|TBP]].
Inferno builds will become the standard, starting at FS2_Open revision 3.7, with 3.6.12 being the last version to be distributed both in normal and Inferno variants.

==General==
The overall limits of the various subsystem managers.
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505;"| '''Limit'''
|- align="center"
| Textures
| 4750
|- align="center"
| Sound tracks
| 30
|- align="center"
| Sounds
| No Limit
|}

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| 300
|- align="center"
| Beam Sections
| colspan=2| 5
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=2| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=2|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=2| 5
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=2| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=2| 75
|- align="center"
| Debriefing
| colspan=2| 2,000 Characters per Stage
|}

Please Note - Although not hardcoded, there are limits to the numbers of [[Modular Tables|‎ .tbm files]] that the game will recognize.

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 2000
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 700
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20
|- align="center"
| Waypoint Paths
| 32
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|- align="center"
| Firing Points Per-Bank
| 25
|- align="center"
| Debris Chunks
| 64
|}

==Sub-Weapon Types==

The maximums for the sub types of weapons.

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Type'''
| style="background:#300505; width:75px"| '''Max Instances'''
|- align="center"
| Corkscrew Missiles
| 64
|- align="center"
| Swarm Missiles
| 100
|}

[[Category:Source Code Project]]
[[Category:Modding]]

Sandbox

2011-12-04T19:10:52Z

IssMneur: Test refs

==Option I==

===Entry===
*fluff
*Example:
::<pre>this here</pre>

===Entry II===
{{Table37|
*fluff
*Example:
::<pre>this here</pre>
}}

==Option II==

===Entry===
*fluff
*Example:
::<code>this here</code>

===Entry II===
{{Table37|
*fluff
*Example:
::<code>this here</code>
}}

==Option III==

===Entry===
*fluff
*Example:
::<tt>this here</tt>

===Entry II===
{{Table37|
*fluff
*Example:
::<tt>this here</tt>
}}

==Option IV==

===Entry===
*fluff
*Example:
{{Example|this here}}

===Entry II===
{{Table37|
*fluff
*Example:
{{Example|this here}}
}}

===Citations===
<ref name="LazyDog" />

<references>
<ref name="LazyDog">This is the lazy dog reference.</ref>
</references>

Nebula Data Files

2011-09-30T05:39:18Z

IssMneur: Sorry I mislead you swashmebuckle, this is used only for V1 nebula

Nebula Data Files (.neb) are models of the nebula when using the version 1 nebula. They are never used in the FS2 retail campaign. These are loaded by the [[FreeSpace_2_Mission_File_Format#.23Background_bitmaps|+Nebula:]] directive in the mission file.

There are six .neb files located in FS2's sparky.vp container, beginning with nebfull01.neb

FreeSpace 2 Mission File Format

2011-09-30T05:35:18Z

IssMneur: /* #Background bitmaps */ Add historical note of still parsed entries

.fs2 files are simple text files defining how FS2 will 'execute' a given mission.
It refers to external files for the actual assets used in the mission, including [[Model files]] and [[Tables]].

==General Format==
File section headers start with the "#" character.
Each file section should be separated by a blank line.

Statements start with either the "$" or "+" characters, and may last for multiple lines.
Comments are indicated by ";!", and continue to the end of the line.

STRING refers to a String data. The game parses these from the ":" at the end of the flag it belongs to until the next flag begins.

XSTR is a single XSTR entry, formatted like this: XSTR("Text data", -1) . The "-1" refers to the entry in tstrings.tbl that contains the translated version.

INT is a single integer.

FLOAT is a floating point number, usually used with 6 digits after the decimal point.

SEXP is a symbolic expression or chain of symbolic expressions. Example:
<pre>( when
( >
( distance "Zeta 3" "center:1" )
2000
)
( send-message
"#Command"
"High"
"msg08"
)
)</pre>

==Sections==

===#Mission Info===
Fields:

$Version: STRING
*contains the version number for this mission
$Name: XSTR
*contains the name of this mission. Uses tstrings.tbl for translation.
$Author: STRING
*The author's name
$Created: STRING
*The time and date that this mission was created on. Format is "MM/DD/YY at HH:MI:SS", where MM = Month, DD = Day, YY = Year, HH = Hours (24 hour format), MI = minutes and SS = seconds.
$Notes: STRING
*Contains any notes the mission designer wishes to add.
$End Notes: ??

$Mission Desc: XSTR
*Contains a short description of this mission. Uses tstrings.tbl for translation.
$end_multi_text

+Game Type Flags: INT

+Flags: INT

+NebAwacs: FLOAT

+Storm: STRING

+Red Alert: INT

+Scramble: INT

+Disallow Support: 0 or 1
*Whether or not support ships are available on this mission

+Hull Repair Ceiling: FLOAT

+Subsystem Repair Ceiling: FLOAT

+Player Entry Delay: FLOAT

+Viewer pos: FLOAT, FLOAT, FLOAT
*FRED camera position

+Viewer orient:
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT
*Orientation Matrix for FRED camera

+SquadReassignName: STRING

+SquadReassignLogo: STRING
*Squadron the player is reassigned to

$Skybox Model: STRING
*Which skybox model to use

$AI Profile: STRING
*Which AI profile is used
----
===#Fiction Viewer===
$File: STRING
*Name of the text file that will be displayed in the fiction viewer. The file needs to be in data/fiction, and interface art for the fiction viewer must be present.
----
===#Sexp_variables===

$Variables:
----

===#Plot Info===

$Tour: XSTR

$Pre-Briefing Cutscene: STRING

$Pre-Mission Cutscene: STRING

$Next Mission Success: STRING

$Next Mission Partial: STRING

$Next Mission Failure: STRING

----

===#Command Briefing===
*Defines the Command Briefing section of the briefing. If no command briefing is required, leave this blank. Stages are defined like this:

$Stage Text: XSTR
*The text to be displayed in this stage
$end_multi_text

$Ani Filename: STRING
*The ani that will be played while the above text is displayed

+Wave Filename: STRING
*The filename of the voiceover
----

===#Briefing===
*Defines the Mission Briefing. Leaving this blank will cause 'no briefing' to be shown instead of a mission briefing.

====Briefing init====
$start_briefing

$num_stages: INT
*Number of stages in this briefing. Stages are defined as follows:

$start_stage

$multi_text
XSTR
*Briefing text for this stage.
$end_multi_text

$voice: STRING
*Voiceover filename

$camera_pos: FLOAT, FLOAT, FLOAT
*Camera position for this stage

$camera_orient:
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT
*Camera orientation matrix

$camera_time: INT

$num_lines: INT

$num_icons: INT

$Flags: INT

$Formula: SEXP

====Icons====
*Icons are defined as follows

$start_icon

$type: INT

$team: STRING
*Friendly, Hostile, or Neutral

$class: STRING
*Must be a valid reference to a ship class from ships.tbl

$pos: FLOAT, FLOAT, FLOAT

$label: STRING

+id: INT

$hlight: INT

$mirror: INT

$multi_text

$end_multi_text

$end_icon
----
===#Debriefing_info===

$num stages: INT
*Number of debriefing stages. Debrief stages are defined as follows

$Formula: SEXP
*Conditions that must be true for the debriefing stage to be shown. Note that several debrief stages may be shown at the same time.

$Multi text

XSTR

$end_multi_text

$Voice: STRING

$Recommendation text: XSTR

$end_multi_text
----

===#Alternate Types===
$Alt: STRING
*Contains an Alternate type name. This is a list entry; All alternate types used in the mission must appear here. Must be terminated by #end.

----

===#Callsigns:===
$Callsign: STRING
*Similar to the Alternate Types list. All Callsigns used in the mission must be listed here. Must be terminated by #end.

----
===#Players===
*Defines the players for the mission. At least one player must be defined.

$Starting Shipname: STRING

$Ship Choices: ( STRING INT )
*The STRING contains the ship class, the INT holds the number of ships available. Can be left blank ( "$Ship choices: ( )" is valid).

+Weaponry Pool: ( STRING INT )
*The STRING contains the weapon name, the INT the number of weapons available. Primary weapons are listed before secondary weapons.

*NOTE: For multiplayer TVT missions, these three items need to be present a second time to define the loadout team 2 gets.

----
===#Objects===
*Defines all the objects in the mission and their initial state.
*This includes all ships (including the player ships), installations and other objects.
*Does not include asteroid (debris) fields.

$Name: STRING

$Class: STRING

$Alt: STRING
*Alternate class name. Must be defined in the #Alternate Types list above.

$Callsign: STRING
*Optional Callsign. Must be defined in the #Callsigns list above.

$Team: STRING

$Location: FLOAT, FLOAT, FLOAT

$Orientation:
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT,
FLOAT, FLOAT, FLOAT

$IFF: STRING

$AI Behavior: STRING

+AI Class: STRING

$AI Goals: ( goals ( SEXP ) )
*SEXP must be from the ai goals list

$Cargo 1: XSTR

+Initial Velocity: INT

+Initial Hull: INT

+Subsystem: STRING

$Arrival Location: STRING

$Arrival Cue: SEXP

$Departure Location: STRING

$Departure Cue: SEXP

$Determination: INT

+Flags: ( STRING )
*Flags must be enclosed by "".

+Respawn priority: INT

+Orders Accepted: INT
*This is a bitfield

+Group: INT

+Score: INT

+Persona Index: INT
----

===#Wings===
*Defines all wings in the mission, friendly and hostile

$Name: STRING

$Waves: INT

$Wave Threshold: INT

$Special Ship: INT

$Arrival Location: STRING

$Arrival Cue: SEXP

$Departure Location: STRING

$Departure Cue: SEXP

$Ships: ( STRING )

$AI Goals: ( goals ( SEXP ) )
*SEXP must be from the ai goals list

+Hotkey: INT

+Flags: ( STRING )

----
===#Events===
*The SEXPs that make up the Events List. Events are formatted as follows:

$Formula: SEXP

+Name: STRING

+Repeat Count: INT

+Interval: INT

+Chained: INT
*The INT shows the chain delay in seconds.

+Objective: XSTR

+Team: INT

----

===#Goals===
*The mission directives. Goals are formatted as follows:

$Type: STRING
*Primary or Secondary

+name: STRING

$MessageNew: XSTR

$end_multi_text

$Formula: SEXP

+No music

+Invalid
----
===#Waypoints===

$Name: STRING

$List: ( ( FLOAT, FLOAT, FLOAT ) )
*The list can contain more than one Waypoint, example: ( ( FLOAT, FLOAT, FLOAT ) ( FLOAT, FLOAT, FLOAT ) )
----
===#Messages===

$Name: STRING

$Team: INT

$MessageNew: XSTR

$end_multi_text

+Persona: STRING

+AVI Name: STRING

+Wave Name: STRING

----
===#Reinforcements===

$Name: STRING
*Name of the wing that is available as reinforcement. That wing needs to have the "reinforcement" flag.

$Type: STRING

$Num times: INT

+Arrival Delay: INT

+No Messages: ( STRING )

+Yes Messages: ( STRING )
----

===#Background bitmaps===

$Num stars: INT

$Ambient light level: INT

+Neb2: STRING

+Neb2Flags: INT

+Nebula: STRING
* (Optional) '''HISTORICAL''' Version 1 nebula, not used in FS2 retail campaign.

*+Color: STRING
** (Optional) '''HISTORICAL''' Version 1 nebula, not used in FS2 retail campaign.
*+Pitch: INT
** (Optional) '''HISTORICAL''' Version 1 nebula, not used in FS2 retail campaign.
*+Bank: INT
** (Optional) '''HISTORICAL''' Version 1 nebula, not used in FS2 retail campaign.
*+Heading: INT
** (Optional) '''HISTORICAL''' Version 1 nebula, not used in FS2 retail campaign.

$Bitmap List:
*Contains all background bitmaps and suns. Sun entries look like this:

$Sun: STRING

$Angles: FLOAT FLOAT FLOAT

*Background nebulae and other objects look like this:

$Starbitmap: STRING

+Angles: FLOAT FLOAT FLOAT

+ScaleX: FLOAT

+ScaleY: FLOAT

+DivX: INT

+DivY: INT
----

===#Asteroid Fields===

$Density: INT

+Field Type: INT

+Debris Genre: INT

+Field Debris Type: INT

$Average Speed: FLOAT

$Minimum: FLOAT, FLOAT, FLOAT

$Maximum: FLOAT, FLOAT, FLOAT

----

===#Music===

$Event Music: STRING

$Briefing Music: STRING
----

===#End===
*The end of the file.

[[Category:Modding]]
[[Category:FRED]]
[[Category:File Types]]

Lightning.tbl

2011-09-27T03:32:46Z

IssMneur: Add +flash_to_bang_percent: to the .tbl

{{TableVersion|4879|4879|7814}}
{{Fileversion|7814}}
Lightning.tbl is used to define the different storms seen in game (such as nebula conditions).

{{Table3613|
*The hardcoded limit of a maximum of 10 different bolts and storm types has been removed in favour of a dynamic system. This allows the creation of a wider range of nebula lightning and storm types within a campaign.}}

==Format==
*Lightning.tbl consists of two sections '''#Bolts begin''' that defines the various lightning bolt types used and the '''#Storms begin''' that defines the method how the different lightning bolts are used in the storms. Bolts sections ends with '''#Bolts end''' and storm section with '''#Storms end'''.

==Bolts==

===$Bolt:===
*Used to define the name of the bolt.
*Syntax: '''String'''

===+b_scale:===
*Defines the 'spread' of the child forks. Smaller values cause tighter bolts.
*Syntax: '''Float'''

===+b_shrink:===
*Defines the percentual value (from 0 to 1) that is for the lenght of the 'child' forks
*Syntax: '''Float'''

===+b_poly_pct:===
*Defines the width of the lightning compared to the lenght of the lightning in percents. Large values are not recommended, retail values are from 0.002 to 0.0075.
*Syntax: '''Float'''

===+b_rand:===
*Sets the probability (from 0 to 1) of generating 'child lightnings' for the 'nodes' of the main lightning. High values may cause the game to run out of lightning nodes.
*Syntax: '''Float'''

===+b_add:===
*Sets the drawing distance (in meters) of the lightning glow from the actual lightning towards the viewpoint, same as the z_add used with beams. Changing this value with lightnings is not recommended.
*Syntax: '''Float'''

===+b_strikes:===
*Defines the number of times the bolt strikes
*Syntax: '''Integer'''

===+b_lifetime:===
*Defines the total lifetime of the bolt in milliseconds. Lenght of invidual strikes is '''+b_lifetime:''' divided by '''+b_strikes:'''
*Syntax: '''Integer'''

===+b_noise:===
*Defines the 'noise' of a multi striking lightning (from 0 to 1). Cause the lightning to 'imitate' movement. Large values are not recommended.
*Syntax: '''Float'''

===+b_emp:===
*Sets the EMP effect caused by the lightning. First the EMP intensity followed by time the EMP affects the ships in seconds.
*Syntax: '''Float''' '''Float'''

===+b_texture:===
*Defines the texture used for the main bolt texture
*Syntax: '''String'''

===+b_glow:===
*Defines the texture used for the main bolt glow
*Syntax: '''String'''

===+b_bright:===
*Defines the brightness of the bolts. Higher values cause screen to flash brighter
*Syntax: '''Float'''

==Storms==

===$Storm:===
*Defines the name of the storm
*Syntax: '''String'''

===+bolt:===
*Each storm may have up to 10 bolts defined. One bolt type may be listed under a same storm more than once to change the odds of that lightnings appearance.
*Type of the lightning is randomly determined from the listed bolts.
*Syntax: '''String'''

===+flavor:===
*Flavor defines a vector that is added to the lightnings. So it forces the lightnings to be aligned along the vector. Smaller values have lesser effect while extremely large values (longer vector) cause linear lightning bolts.
*Syntax: '''Float''' '''Float''' '''Float'''

===+random_freq:===
*Defines the '''minimum''' and '''maximum''' for the random lightning 'firings' in milliseconds
*Syntax: '''Integer''' '''Integer'''

===+random_count:===
Defines the '''minimum''' and '''maximum''' number of lightnings fired at each timestamp
*Syntax: '''Integer''' '''Integer'''

===+flash_to_bang_percent:===
{{Table3613|
Defines the '''percentage''' of nebula flashes that get turned into bangs. Max ''100''. Min ''0'' (effectively turn off thunder).
*Syntax: '''Integer'''}}

==Sample==

*Retail FreeSpace 2 table

<pre>; Man, do I like this table :)

; individual bolt definitions. can have up to 10 different bolt types
#Bolts begin

;; individual lightning bolt types
$Bolt: b_standard
; this is a percentage of the length of a given beam. envision a circle in the plane of where the bolt
; strikes. the radius of this circle is the length of the beam * b_scale. when generating child forks on the
; bolt, a point is picked randomly within ths circle and that's where thr fork "aims". smaller values produce a
; tighter bolt
+b_scale: 0.5

; when generating the child forks, this is % of the distance from the start of the fork to the point its aiming at
; that will be its endpoint. So if you had a value of 0.25, each child fork would be 25% the distance to the strike plane
+b_shrink: 0.3

; this is the thickness of the main trunk of a bolt relative to the length of the bolt. so 0.003 means the bolt is 0.3% as
; wide as it is long
+b_poly_pct: 0.002

; this is the % chance that any given node on the main trunk will spawn a child node. BE CAREFUL WITH THIS! too high of
; a percentage will generate mega-lightning bolts which will run out of nodes. =o
+b_rand: 0.24

; this should probably never be messed with. its just a fudge factor which ensures that the glow of a beam is drawn closer
; to the eye that the bolt itself (so its always "over" the bolt). in meters.
+b_add: 2.0

; the # of times the bolt "strikes"
+b_strikes: 2

; the total lifetime of the bolt (in ms). the length of an individual strike is b_lifetime / b_strikes
+b_lifetime: 280

; the "noise" in a multi-strike bolt. each of the nodes in the bolt is perturbed a bit between strikes to make it seem
; like its moving. large values don't look too good
+b_noise: 0.015

; the EMP effect caused by proximity to this lightning bolt. max intensity is 500.0. max time is 30 seconds
+b_emp: 0.0 0.0

; main bolt texture
+b_texture: lightning

; main bolt glow
+b_glow: beam-dblue

; brightness of the bolt. 0.0 to 1.0. higher values result in brighter screen flashes
+b_bright: 0.3

$Bolt: b_red
+b_scale: 0.2
+b_shrink: 0.3
+b_poly_pct: 0.0075
+b_rand: 0.45
+b_add: 2.0
+b_strikes: 4
+b_lifetime: 200
+b_noise: 0.04
+b_emp: 0.0 0.0
+b_texture: lightning
+b_glow: beam-red
+b_bright: 0.2

$Bolt: b_green
+b_scale: 0.3
+b_shrink: 0.3
+b_poly_pct: 0.0075
+b_rand: 0.2
+b_add: 2.0
+b_strikes: 3
+b_lifetime: 240
+b_noise: 0.03
+b_emp: 0.0 0.0
+b_texture: lightning
+b_glow: beam-green3
+b_bright: 0.14

$Bolt: b_emp
+b_scale: 0.6
+b_shrink: 0.3
+b_poly_pct: 0.0075
+b_rand: 0.3
+b_add: 2.0
+b_strikes: 5
+b_lifetime: 300
+b_noise: 0.04
+b_emp: 350.0 5.0
+b_texture: lightning
+b_glow: beam-dblue
+b_bright: 0.4

#Bolts end

; storm types
#Storms begin

; this is what the mission designers will choose in fred. can have up to 10 different storm varieties
$Storm: s_standard
; can have a max of 10 different bolt types. one will be randomly chosen. if you want to make bolts happen more or
; less often, add them multiple times. So if you had 4 b_standard bolts and 1 b_red bolt, the b_red bolt would happen
; 1/5 as often as the b_standard
+bolt: b_standard
+bolt: b_standard
+bolt: b_red
+bolt: b_green

; direction vector value. flavor of the storm. if all 3 values are 0, its completely random. otherwise lightning bolts will tend to
; align themselves to the vector. the longer the flavor vector, the more tightly aligned the bolts will be
+flavor: 0.0 0.0 0.0

; how often random bolts are fired, min-max range, in ms
+random_freq: 1500 1750

; min/max. how many bolts are spewed each random timestamp
+random_count: 1 2

$Storm: s_active
; can have a max of 10 different bolt types. one will be randomly chosen. if you want to make bolts happen more or
; less often, add them multiple times. So if you had 4 b_standard bolts and 1 b_red bolt, the b_red bolt would happen
; 1/5 as often as the b_standard
+bolt: b_standard
+bolt: b_standard
+bolt: b_standard
+bolt: b_standard
+bolt: b_red

; direction vector value. flavor of the storm. if all 3 values are 0, its completely random. otherwise lightning bolts will tend to
; align themselves to the vector. the longer the flavor vector, the more tightly aligned the bolts will be
+flavor: 0.0 500.0 0.0

; how often random bolts are fired, min-max range, in ms
+random_freq: 200 400

; min/max. how many bolts are spewed each random timestamp
+random_count: 1 4

$Storm: s_emp
+bolt: b_standard
+bolt: b_standard
+bolt: b_standard
+bolt: b_red
+bolt: b_red
+bolt: b_emp
+bolt: b_red
+bolt: b_red

+flavor: 0.0 500.0 0.0

; how often random bolts are fired, min-max range, in ms
+random_freq: 300 700

; min/max. how many bolts are spewed each random timestamp
+random_count: 1 4

$Storm: s_medium
+bolt: b_standard
+bolt: b_standard
+bolt: b_red
+bolt: b_red
+bolt: b_standard
+bolt: b_standard
+bolt: b_green

+flavor: 0.1 1.0 0.2

; how often random bolts are fired, min-max range, in ms
+random_freq: 900 1850

; min/max. how many bolts are spewed each random timestamp
+random_count: 1 3

#Storms end</pre>

[[Category:Tables]]

Weapons.tbl

2011-09-20T02:53:04Z

IssMneur: Update $substitute: - rename of +frequency to +period and removal of the requirement to specify +period or +index

{{Fileversion|7766}}

==Special Case Weapons==
===Beam Cannons===
*'''REQUIRES: "beam" flag'''
*'''REQUIRES: [[weapons.tbl#$BeamInfo:|$BeamInfo:]]'''
===Flak Guns===
*'''REQUIRE: "flak" and "particle spew" flags'''
*Must have inner and outer radius defined to have any effect.
*Does not use any model or weapon effect though model must be defined, usually Hornet.pof. Instead it uses [[Weapons.tbl#$Pspew:|particle spew]]. Trails can also be added.

==Weapons Table==

==General Format==
*The weapons table consist of several sections
*All sections beginning with <nowiki>#</nowiki> need <nowiki>#</nowiki>'''End''' before the next section.
**<nowiki>#</nowiki>'''Primary Weapons'''
***Defines all '''standard primaries weapons''' as well as '''beam cannons''' and '''flak cannons'''.
**<nowiki>#</nowiki>'''Secondary Weapons'''
***Defines all '''secondary weapons'''.
**<nowiki>#</nowiki>'''Beam Weapons'''
***I haven't got any ideas for this one.
**<nowiki>#</nowiki>'''[[Weapons.tbl#Countermeasures|Countermeasures]]'''
***Defines the used countermeasure.
**'''$Player Weapon Precedence'''
***Player Weapon Precedence is used in weapon selection when a default specified by the mission designer is not available to the player. The next weapon on the list is used in its place (assuming that weapon is allowed for the player).

==Core Table==

===$Name:===
*This is the name of the weapon. If it's going to be used by the player, keep it under 12 characters so it doesn't spill over the HUD box. Two special characters can be used in the name: '''#''' and '''@'''. Their usage details are the very same than inside the [[Ships.tbl#.24Name:_2|$Name field from Ships.tbl]].
*Syntax: '''''String'''''

====+nocreate====
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===$Alt Name:===
{{Table3611|
*An alternative name that can be referenced instead of $Name:
*Syntax: '''''String'''''}}

===$Subtype:===
{{Table3610| }}

===+Title:===
*This is the title of the weapon in the Weapons loadout screen. Only needed for player allowed weapons. Title may be anything. Numerical value is a reference to translations in [[Tstrings.tbl]]
*Syntax: XSTR('''''"String"''''', -1)

===+Description:===
*This is the description you see in the weapons loadout screen. Again, these aren't based on any hard numbers, just approximations. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

'''Example'''

<pre>
XSTR(
"''Standard Issue
''Level 3 Hull Damage
''Level 2 Shield Damage''", -1)
$end_multi_text
</pre>

===+Tech Title:===
*Title of the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: XSTR('''''"String"''''', -1)

===+Tech Anim:===
*Animation used for the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: '''''String''''', animation filename
**Example: ''Tech_Subach_HL-7''

===+Tech Description:===
*Descriptive text you see in the tech room. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

'''Example'''

<pre>
XSTR(
"''The Subach-Innes HL-7...''", 3245)
$end_multi_text
</pre>

===$Tech Model:===
{{Table3610|
*Defines model used in wing loadout screen and in Tech Room for the weapon.
*Syntax: '''''String.pof''''', model filename}}

===$Selection Effect:===
{{Table3613|
*Defines which selection effect to use when the -weapon_choice_3d commandline flag is enabled or no ani can be found for the selected weapon.
*Syntax: '''''String''''', either "FS1", or "Off". This defaults to the FS2 effect.
}}

===$HUD Image:===
{{Table3610|
*Defines the picture used to represent the weapon in HUD loadout list
*Syntax: '''''String''''', filename}}

===$Model File:===
*Filename of the model file (.pof) at data/models folder. Additional fields beginning from '''''@Laser Bitmap:''''' and ending to '''''@Laser Tail Radius:''''' are not needed if a model has been defined for the weapon.
*Standard primaries and beam cannons do not use specific models so for those the name is 'none'.
*Flak weapons and secondaries use models, though the exact model is not important with the flak weapons.
*Syntax: '''''String.pof''''' or ''none'', model filename
**Example: ''none''

===$POF target LOD:===
{{Table3610|
*Defines the LOD (Level-Of-Detail) of the model used in HUD targeting view
*Syntax: '''''Integer'''''}}

===$Detail Distance:===
{{Table3613|
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers are (from left to right): 1/8, 1/4, 1, 4, 8
*Optional. If not defined the game uses the formula ((radius * 20.0 + 20.0) * LOD)
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''}}

===$External Model File:===
{{Table3610|
*Defines the models shown on the gunpoint, used with Bobb's external-visible-weapon code.
*Syntax: '''''String.pof''''', model filename}}

===$Submodel Rotation Speed:===
{{Table3610|
*Defines the rotation speed of the external weapon model
*Syntax: '''''Float'''''}}

===$Submodel Rotation Acceleration:===
{{Table3610|
*Defines the rotation acceleration of the external weapon model
*Syntax: '''''Float'''''}}

===@Laser Bitmap:===
**The graphic file to be used as the weapon effect if no model is defined.
**Syntax: '''''String''''', filename

===@Laser Glow:===
**The graphic file that determines the glow of the weapon effect if no model is defined. The color in which this gets drawn is determined by @Laser Color and @Laser Color2.
**Syntax: '''''String''''', filename

===@Laser Color:===
**The color of the glow effect when you fire the weapon.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''250, 0, 0''

===@Laser Color2:===
**The color of the glow effect at the weapon's maximum range.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''0, 0, 250''

===@Laser Length:===
**Length of the weapon effect.
**Syntax: '''''Float''''', meters

===@Laser Head Radius:===
**Width of the head of the weapon effect.
**Syntax: '''''Float''''', meters

===@Laser Tail Radius:===
**Width of the tail of the weapon effect.
**Syntax: '''''Float''''', meters

===$Mass:===
*How much of a kinetic effect this weapon has on its target. 3+ gives you the Flail effect. Set it to 10 and you can knock cruisers around.
*This is somehow multiplied by the speed. ie ''$Mass: 3'' and ''$Velocity: 200'' has much weaker kinetic effect than ''$Mass: 3'' and ''$Velocity: 1000''. Also $Mass is used to calculate intensity of "shudder" effect if flagged.
*Syntax: '''''Float''''', blast effect

===$Velocity:===
*How fast the weapon travels. Is also used to define the weapon range, '''''$Velocity x $Lifetime = range'''''.
*Beams travel instantly so this field has effect only on weapon range and AI beam targeting with certain beam types. $Velocity of beam also applies to its kinetic effect along with $Mass.
*Syntax: '''''Float''''', meters per second

===$Fire Wait:===
*Time in seconds between firings
*Note that Fire wait will be reset to 1 if it is set over 5 for non turreted primary weapons
*Syntax: '''''Float''''', seconds

===$Damage:===
*Base damage this weapon does. The actual damage is this number multiplied by the factors below.
*Base damage this beam does is continuous damage, damage is 5.5 times the damage value per second. The actual damage is this number multiplied by one of the factors below.
*Syntax: '''''Float''''', damage

===$Damage Type:===
{{Table3610|
*Defines the damage type that this weapon uses. All armor effects are applied after shield and have no function against shockwave or subsystem damage. '''REQUIRES ADDITIONAL TABLE'''.
*Syntax: '''''String''''', name of the damage type as defined in [[armor.tbl]]}}

===$Arm time:===
{{Table3610|
*Defines the time after the launch that is required before the weapon comes hot
*If the time has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', seconds}}

===$Arm distance:===
{{Table3610|
*Defines the distance from the firing ships that is required before the weapon comes hot
*If the distance has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', meters}}

===$Arm radius:===
{{Table3610|
*Defines the distance from the target where the weapon will arm itself
*Syntax: '''''Float''''', meters}}

===$Detonation Range:===
{{Table3610|
*Defines the distance from the point in space that the weapon was launched where the weapon will detonate
*Syntax: '''''Float''''', meters}}

===$Detonation Radius:===
{{Table3610|
*Defines the distance between the target center point point and the weapon which detonates the weapon.
*Syntax: '''''Float''''', meters}}

===$Shockwave damage:===
{{Table3610|
*Override for the damage caused by shockwaves
*Syntax: '''''Float''''', damage}}

===$Shockwave Damage Type:===
{{Table3610|
*'''REQUIRES ADDITIONAL TABLE'''. Defines the damage type used for the weapon explosions
*Syntax: '''''String''''', name as defined in [[armor.tbl]]}}

===$Blast Force:===
*The intensity of the kinetic blast effect when ship is within the outer radius of the explosion. Comes in effect only if inner and outer radius are defined.
*Syntax: '''''Float''''', blast effect

===$Inner Radius:===
*Radius at which the full explosion damage is done. Marks the line where damage attenuation begins.
*Syntax: '''''Float''''', meters

===$Outer Radius:===
*Maximum radius at which any damage is done
*Also defines the size of the shockwave (if shockwave speed is > 0)
*Syntax: '''''Float''''', meters

===$Shockwave Speed:===
*Speed shockwave expands at. Zero means no shockwave and that damage is applied immediately
*Syntax: '''''Float''''', meters per second

===$Shockwave rotation:===
{{Table3610|
*Defines how the 3D shockwave is rotated.
*Syntax: '''''Angle''''', three values, pitch, bank, heading respectively, in degrees}}

===$Shockwave model:===
{{Table3610|
*Defines the model file (.pof) used as a shockwave for the 3D shockwaves.
*Syntax: '''''String.pof''''', model filename}}

===$Shockwave name:===
{{Table3610|
*Defines the name of the animation used for the 2D shockwave
*Syntax: '''''String''''', filename}}

===$Dinky shockwave:===
{{Table3610|
*Dinky shockwave are used if the weapon is shot down before arming or if the conditions marked at '''Arm time''' and '''Arm distance''' are not reached before impact
*It uses exactly same entries as the standard shockwaves
*'''''+Shockwave damage:'''''
*'''''+Shockwave damage type:'''''
*'''''+Blast Force:'''''
*'''''+Inner Radius:'''''
*'''''+Outer Radius:'''''
*'''''+Shockwave Speed:'''''
*'''''+Shockwave Rotation:'''''
*'''''+Shockwave Model:'''''
*'''''+Shockwave Name:'''''}}

===$Armor Factor:===
*Multiplier for the damage done to armor
*Syntax: '''''Float''''', damage multiplier

===$Shield Factor:===
*Multiplier for the damage done to shields
*Syntax: '''''Float''''', damage multiplier

===$Subsystem Factor:===
*Multiplier for the damage done to subsystems
*Syntax: '''''Float''''', damage multiplier

===$Lifetime Min:===
{{Table3610|
*Defines the minimum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime Max:===
{{Table3610|
*Defines the maximum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime:===
*Time before the standard primaries fizzle out and secondaries self destruct. Multiply this by the speed to get the range. If values are too low (below framerate) then the collision detection and graphic effects may suffer.
*This field has no effect for the beams apart from weapon range and AI beam targeting with certain beam types
*Syntax: '''''Float''''', seconds

===$Energy Consumed:===
*The amount of energy each bolt drains firing ship. Has no effect on turretted weapons.
*Syntax: '''''Float'''''

===$Cargo Size:===
*Cargo size, is not used with non-ballistic primaries.
*Amount of missiles available = Bank capacity / Cargo Size.
*Syntax: '''''Float'''''

===$Homing:===
*Only for secondaries. You can't have homing primaries. If this is set to YES with primaries, then the bolts turn to face their target but keep moving in the same direction. If the field is set to NO then following fields are not required in the table.
*Defines if the missiles in question is homing
*Syntax: '''''Boolean''''', yes or no
*'''+Type:'''
**Defines the homing method
**Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table3610| An additional option, ''JAVELIN'', has been added. This behaves like an aspect missile but automatically only locks onto the engines of a target, and only if the engines are in sight.}}
*'''+Turn Time:'''
**Defines how well missile maneuvers. Number of seconds it takes the missile to do a 360 degree circle
**Syntax: '''''Float''''', seconds
*'''+View Cone:'''
**'''Heat-seeking missiles only''', this is then number of degrees the missile sees. Value / 2 gives the angle from the missile's centerline.
**Syntax: '''''Float''''', degrees
{{Table3610| Has been enabled also to aspect seekers as an option.}}

*'''+Min Lock Time:'''
**'''For aspect/javelin missiles only''', the minimum number of seconds to gain target lock
**Syntax: '''''Float''''', seconds
*'''+Lock Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels the aspect triangle moves per second while attempting lock-on
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels moved per second while attempting to catch up to the target
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Penalty:'''
**'''For aspect/javelin missiles only''', extra pixels to move after catching up ????
**Syntax: '''''Integer''''', pixels
{{Table3610|
*'''+Seeker Strength:'''
**Defines the seeking ability of the homing system. Default of heat seekers is 3 and for aspect seekers 2. Spoofing change is defined as '''cm type effectiveness'''/'''seeker strength'''.
**Syntax: '''''Float''''', seeker strength}}
{{Table3611|
*'''+Target Lead Scaler:'''
**Defines the type of pursuit course the missile tries to obtain.
**Values < 0 give lag pursuit, values ~ 0 give pure pursuit, values > 0 give lead pursuit.
**Syntax: '''''Float''''', default for heat seekers: 0, default for aspect or javelin seekers: 1.}}

===$Swarm:===
*The number of missiles to fire per volley if it's a swarm missile
*Can be issued to Standard primaries also. Causes single part turrets to malfunction but causes multi part turrets to fire only on their barrel line. Can be used for 'burst fire weapons'. Does not work with player weapons.
*Is incompatible with "Corkscrew" option.
*Syntax: '''''Integer''''', number of shots in a swarm
{{Table3610|
*'''+SwarmWait:'''
**Defines the time between weapons fired in a swarm
**Syntax: '''''Float''''', seconds
***Default: 0.150}}

===$Free Flight Time:===
{{Table3610|
*Defines the free flight time of homing weapons. During this time weapon flies at 1/4 of its velocity + firing ships velocity in a straight line.
*Syntax: '''''Float''''', seconds
**Default: 0.25}}

===$Free Flight Speed:===
{{Table3613|
*Defines the speed that the weapon will be travelling at during the free flight segment (see above).
*Syntax: '''''Float''''', Multiplier for the actual speed, minimum 0.01.
**Default: 0.25}}

===$PreLaunchSnd:===
{{Table3613|
*Defines the one-shot sound effect to play at the beginning of a firing stream. Currently only has an effect on primary weapons.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
**Default: No Sound}}

===+PreLaunchSnd Min Interval:===
{{Table3613|
*Defines Minimum interval between when the player stops firing and the next time the pre-launch sound can play, as a limiter in case the player is pumping the trigger.
*Syntax: '''''Integer''''', Minimum delay in milliseconds between the end of the previous firing sequence and the next time the pre-launch sound effect will be played.
**Default: 0 (play pre-launch sound at the beginning of every firing sequence, if present)}}

===$LaunchSnd:===
*Corresponding sound effect when the weapon is launched.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$ImpactSnd:===
*Sound the weapon makes when it hits a hull.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Disarmed ImpactSnd:===
{{Table3610|
*Sound the weapon makes when it hits a hull before being armed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$FlyBySnd:===
*The sound this weapon makes if it narrowly misses you. -1 is no sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]], usually -1

===$Model:===
{{Table3610|
*Defines used model file. Included for compatibility with countermeasures as they have been merged with weapons in the code.
*Syntax: '''''String.pof''''', model filename}}

===$Rearm Rate:===
*Defines the rate the weapons are loaded to the ship
*Syntax: '''''Float''''', missiles loaded per second

===+Weapon Range:===
*Defines the range to the target where the weapons under AI will start firing.
*Syntax: '''''Float''''', meters

===+Weapon Min Range:===
{{Table3610|
*Defines the minimum range to the target where the weapons under AI will still fire.
*Implemented before FS_Open 3.6.5
*Syntax: '''''Float''''', meters}}

===$Flags:===
*See [[Weapons.tbl#Weapons.tbl_Flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the weapon
**Example: ( "Player allowed" "in tech database" )

{{Table3610|
*Can be followed by '''+override''' option in order to reset the weapon flags before parsing in the new ones
*Using this option will erase all '''homing'''-related flags as well as '''swarm''', '''variable lead''', '''trail''', '''TAG''', and '''transparent''' settings in addition to the listed flags. All these should be set again - if they are required - when this option is used.

**Syntax: '''''+override'''''}}

===$Trail:===
*This is used if you want your weapon to have a trail. Trail is often used only with secondaries though it works with standard primaries as well.
*'''+Start Width:'''
**How wide the head of the trail is.
**Syntax: '''''Float''''', meters
*'''+End Width:'''
**How wide the tail of the trail is.
**Syntax: '''''Float''''', meters
*'''+Start Alpha:'''
**The opacity of the trail head.
**Syntax: '''''Float''''', value between 0 and 1
*'''+End Alpha:'''
**The opacity of the trail tail.
**Syntax: '''''Float''''', value between 0 and 1
*'''+Max Life:'''
**How long the trail lasts.
**Syntax: '''''Float''''', seconds
*'''+Bitmap:'''
**The graphic file to use for the trail.
**Syntax: '''''String''''', filename
{{Table3611|
*'''+Faded Out Sections:'''
**Defines the number of the trail sections (counting from the leading edge) which are gradually faded out.
**Syntax: '''''Integer''''', number of trail sections}}

===$Icon:===
*Loadout icon used in the weapons selection screen.
*Syntax: '''''String''''', filename

===$Anim:===
*Green grid animation used on the weapons screen.
*Syntax: '''''String''''', filename

===$Collide Ship:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Collide Weapon:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Impact Explosion:===
*Impact explosion used. Must be defined in weapon_expl.tbl,
*Syntax: '''''String''''', filename or ''none''

===$Impact Explosion Radius:===
*Radius of the defined impact explosion.
*Syntax: '''''Float''''', meters

===$Dinky impact explosion:===
{{Table3610|
*Same as Impact explosion but for Dinky (not armed) explosions
*Syntax: '''''String''''', filename or ''none''}}

===$Dinky impact explosion radius:===
{{Table3610|
*Same as Impact explosion radius but for Dinky explosions
*Syntax: '''''Float''''', meters}}

===$Piercing Impact Explosion:===
{{Table3611|
*Defines the effect used for events when weapon pierces the target
*Syntax: '''''String''''', filename or ''none''}}

===$Piercing Impact Radius:===
{{Table3611|
*Defines the base radius of the effect used for piercing weapon impacts
*Syntax: '''''Float'''''}}

===$Piercing Impact Velocity:===
{{Table3611|
*Defines the base velocity for the particles piercing the target
*Syntax: '''''Float'''''}}

===$Piercing Impact Splash Velocity:===
{{Table3611|
*Defines the base velocity for the particles splashing from the target (secondary piercing effects
*Negative value causes the second batch or particles to splash to opposite direction
*Syntax: '''''Float'''''}}

===$Piercing Impact Variance:===
{{Table3611|
*Defines the variance added to the particles
*Values near 0 cause very little variance and values close to 1 cause extreme dispersal.
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the lifetime of the effect for single frame effects
*For multiple frame effects the lifetime is the lifetime of the animation used
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the number of particles released per impact
*Syntax: '''''Integer'''''}}

===$Piercing Impact Draw Modifier:===
{{Table3611|
*Defines the multiplier applied to the ships piercing effect limit percentage
*Syntax: '''''Float'''''}}
*Option removed in 3.6.12. Use [[armor.tbl]] to finetune piercing effects.

===$Muzzleflash:===
*Normally only with flak cannons.
*Defines the muzzle flash the weapon uses
*Syntax: '''''String''''', muzzleflash name, as defined in [[mflash.tbl]]

===$EMP Intensity:===
**If it has an EMP effect, how deeply it scrambles your electronics
**Syntax: '''''Float'''''

===$EMP Time:===
**Duration of the EMP effect
**Syntax: '''''Float''''', seconds

===$Leech Weapon:===
**The amount of weapon energy to drain with each hit
**Syntax: '''''Float'''''

===$Leech Afterburner:===
**The amount of afterburner fuel to drain with each hit
**Syntax: '''''Float'''''

===$Corkscrew:===
{{Table3610|
*Allow corkscrew parameters to be defined
*'''+Num Fired:'''
**Defines the number of weapons fired in sequence. Same as the standard swarm entry but for corkscrew missiles
**Syntax: '''''Integer''''', number of missiles
*'''+Radius:'''
**Defines the radius used in the corkscrew motion
**Syntax: '''''Float''''', meters
*'''+Fire Delay:'''
**Defines the delay between missile firings
**Syntax: '''''Integer''''', milliseconds
*'''+Counter rotate:'''
**Defines if every other missile rotates to a different direction (clockwise / anticlockwise)
**Syntax: '''''Boolean''''', ''0'' or ''1'', no or yes
*'''+Twist:'''
**Defines the speed of rotation movement on the radius of corkscrew motion.
**Syntax: '''''Float''''', radians per second}}

===$Electronics:===
{{Table3610|
*Defines the weapons effect against electronics. Requires [[weapons.tbl#"Electronics"|"electronics"]] flag. '''+New Style:''' and '''+Old Style:''' options are mutually exclusive.
*'''+New Style:'''
**Defines that the electronics use the new style which enables more options.
*'''+Old Style:'''
**Defines that the electronics use the old style. The old style was the way the D-Missile worked in Descent: FreeSpace.
*'''+Intensity:'''
**May only be used with '''+New Style:''' electronics. '''''Has been deprecated'''''.
**Syntax: '''''Float'''''
*'''+Lifetime:'''
**Syntax: '''''Integer''''', milliseconds
*'''+Engine Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for engine subsystems.
**Syntax: '''''Float'''''
*'''+Weapon Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for non-beam turrets.
**Syntax: '''''Float'''''
*'''+Beam Turret Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for beam turrets.
**Syntax: '''''Float'''''
*'''+Sensors Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for sensor subsystems.
**Syntax: '''''Float'''''
*'''+Randomness Time:'''
**Defines the randomness of duration target suffers from the electronics hit. A random number between 0 and this time will be added or subtracted from the disruption time.
**Syntax: '''''Integer''''', milliseconds

* Without any electronics parameters, a weapon with the "electronics" flag will default to the ''Old Style'' mode with a lifetime of 6000 milliseconds and a randomness of 4000 milliseconds. Thus any ship that gets hit can get disrupted for anywhere between 2 to 10 seconds.

*''WARNING: Putting +Old Style doesn't seem to work either.
To have a working electronics weapon just put the electronics flag in the weapon and make sure it has a big shockwave radius and a shockwave speed of 0.''
}}

===$Spawn Angle:===
{{Table3610|
*Defines the cone (with an angle) where the spawned weapons appear. ''Value'' gives the angle from the missiles centerline. The maximum possible angle between any two child weapons would be ''Value*2''.
*Spawn angle can be defined as many times as the carrier missile has child weapons defined for it (up to 5).
*Syntax: '''''Float''''', degrees}}

===$Local SSM:===
{{Table3610|
*Defines the local SSM (Subspace Missile). In effect missile moves via subspace to a position close to the target and starts homing.
*Weapon must be '''''aspect seeking missile''''' and must have '''''[[Weapons.tbl#"local ssm"|local ssm]]''''' flag.
*'''+Warpout Delay:'''
**Defines the time between the missile launch and the subspace jump.
**Syntax: '''''Integer''''', milliseconds
*'''+Warpin Delay:'''
**Defines the time missile stays in subspace before exiting.
**Syntax: '''''Integer''''', milliseconds
*'''+Stage 5 Velocity:'''
**Defines the velocity of the missile after the subspace jump.
**Syntax: '''''Float''''', meters per second
*'''+Warpin Radius:'''
**Defines how far from the SSM will appear from the outer radius of the target.
**Syntax: '''''Float''''', meters
*'''+Lock Range:'''
**Defines the maximum range where SSM can achieve target lock
**Syntax: '''''Float''''', meters}}

===$Countermeasure:===
{{Table3610|
*Defines the countermeasure effectiveness and radius
*'''+Heat Effectiveness:'''
**Defines the countermeasures effectiveness against heat seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Aspect Effectiveness:'''
**Defines the countermeasures effectiveness against aspect seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Effective Radius:'''
**Defines the countermeasures effective radius
**Syntax: '''''Float''''', meters
***Default: 300}}

===$BeamInfo:===
*'''+Type:'''
**Defines the type of beam in question. Beam types: 0 is a standard non-slashing type beam. 1 is a slashing type beam. 2 is a targeting beam that is used to trigger SSMs. 3 is a beam type that fires pulses in anti-fighter role and acts like type 0 beam in other roles. 4 is a beam that is restricted to what is directly in front of it, along turrets firepoints normal.
**Syntax: '''''Integer''''',, only values from 0 to 4 are legal
*'''+Life:'''
**How long it lasts once the beam is actually firing.
**Syntax: '''''Float''''', seconds
*'''+Warmup:'''
**Warmup time
**Syntax: '''''Integer''''', milliseconds
*'''+Warmdown:'''
**Warmdown time
**Syntax: '''''Integer''''', milliseconds
*'''+Radius:'''
**Muzzle glow radius
**Syntax: '''''Float''''', meters
*'''+PCount:'''
**Particles spewed every interval. ??
**Syntax: '''''Integer'''''
*'''+PRadius:'''
**Particle radius
**Syntax: '''''Float''''', meters
*'''+PAngle:'''
**Defines the random "cone" where the particles are generated
**Syntax: '''''Float''''', angle of the cone
*'''+PAni:'''
**Animation used to represent the particles
**Syntax: '''''String''''', filename
*'''+Miss Factor:'''
**The higher the numbers, the more likely that this beam will miss. One value for every difficulty level
**Syntax: '''''Miss Factor''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5
{{Table3613|
*'''IFF specific miss factors'''
**Identical to the preceding entry but IFF specific. Replace the <IFF> with the name of the IFF from [[iff_defs.tbl]]
**Syntax: '''''+<IFF> Miss Factor:''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5}}
*'''+BeamSound:'''
**Corresponding looping sound effect when the beam is firing.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmupSound:'''
**Corresponding sound effect when the beam is beam warmed up.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmdownSound:'''
**Corresponding sound effect when the beam is warming down.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Muzzleglow:'''
**Defines the bitmap used to create the muzzle glow
**Syntax: '''''String''''', filename
*'''+Shots:'''
**Defines into how may invidual shots the type 3 (AAA) beams are divided. Note total firing is the same as the +Life:
**Syntax: '''''Integer'''''
*'''+ShrinkFactor:'''
**What percentage of lifetime where beam starts shrinking (0.1 == 10% life left)
**Syntax: '''''Float'''''
*'''+ShrinkPct:'''
**What percentage of max width we subtract per second
**Syntax: '''''Float'''''
{{Table3610|
*'''+Range:'''
**Defines the maximum range where the beam still has any effect.
**Syntax: '''''Float''''', meters
*'''+Attenuation:'''
**Defines the point where the damage caused by the beam starts to attenuate. At maximum range damage is zero.
**Syntax: '''''Float''''', from 0 - firing point to 1 - no effect
***Default: 1}}
{{Table3611|
*'''+BeamWidth:'''
**Defines the width of the beam for collision test purposes instead of using widest beam section.
**Syntax: '''''Float''''
*'''+Beam Flash Effect:'''
**Defines the additional impact flash effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Flash Radius:'''
**Defines the radius for the additional impact flash effect.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect:'''
**Defines the beam piercing (bursting flames) effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Piercing Radius:'''
**Defines the average radius used for the beam piercing effects.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Velocity:'''
**Defines the base velocity for the piercing effects
**Syntax: '''''Float'''''
*'''+Beam Piercing Splash Effect Velocity:'''
**Defines the base velocity for the secondary piercing effects
**Negative velocity causes the particles to move to opposite direction
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Variance:'''
**Defines the variances of the particles from the main path
**Values close to 0 cause minimum variance, higher values cause higher variances
**Syntax: '''''Float'''''}}

*'''$Section:'''
**Beams are made up of up to five sections layered atop one another to create the effect. Each section has its own parameters.
{{Table3610|
:*'''+Index:'''
:**Field used to define with [[Modular Tables]] the beam section which is edited.
:**Only needed when editing beams that already exist in other tables.
:**Syntax: '''''Integer''''', index number legal values are from 0 to 5
:*'''+remove'''
:**Removes the set beam section.
:*'''+nocreate'''
:**Does not create new section for the beam}}

:*'''+Width:'''
:**Width of the section
:**Syntax: '''''Float''''', meters
:*'''+Texture:'''
:**Texture for the section
:**Syntax: '''''String''''', filename
:*'''+RGBA Inner:'''
:**Defines the color and transparency of the center of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 255 255 255 255
:*'''+RGBA Outer:'''
:**Defines the color and transparency of the edges of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 150 150 150 10
:*'''+Flicker:'''
:**Defines how much the section flickers
:**Syntax: '''''Float''''', value from 0 to 1
:*'''+Zadd:'''
:**Defines the 'thickness' of the section. The higher the Zadd, the closer the section appears to be.
:**Syntax: '''''Float'''''
{{Table3610|
:*'''+Tile Factor:'''
:**Defines the beam texture tiling factor. Second number defines the tiling type. Type 0 tiles the graphic in the beam as many times as defined by the 1st number. Type 1 uses the 1st value as the lenght of the tile.
:**Syntax: '''''Float''''', '''''Integer'''''
:*'''+Translation:'''
:**Defines the speed of translation of the beam, a positive value moves from the impact point to the firing point, while a negative value moves away from the firing point towards the impact point. Measured in tiles per second, where the tile count is defined in the "+Tile Factor:" field above.
:**Syntax: '''''Float'''''}}

===$Pspew:===
{{Table3610|
*Defines a particle spew effect for the given weapon
}}{{Table3613|
*'''+Index:'''
**indicates which spewer to add/edit/delete. may be 0-3. used for xmt compatibility.
**Syntax: '''''Integer'''''
*'''+Remove'''
**removes spewer at +Index: (requires +index:)
*'''+Type:'''
**type of particle spew
**Syntax: '''''String'', Default, Helix, Sparkler, Ring, or Plume '''
}}{{Table3610|
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created (at each +Time: interval)
**Syntax: '''''Integer'''''
*'''+Time:'''
**Defines the time in milliseconds between next particle(s) spewed
**Syntax: '''''Integer''''', milliseconds
*'''+Vel:'''
**Defines the created particles velocity as percentage of the weapons velocity
**Syntax: '''''Float'''''
*'''+Radius:'''
**Defines the size of the created particles
**Syntax: '''''Float''''', meters
*'''+Life:'''
**Defines how long the particles last.
**Syntax: '''''Float''''', seconds
*'''+Scale:'''
**Defines the particle spread. Small value will make particles group together
**typically controls how big the effect is or how fast it moves away from the weapon path on a perpendicular (or sometimes arbitrary) axis.
**helical spews and rings use this value to control how fast the particle helix moves away from the central axis.
**sparklers use this to control how fast particles move away from the spawn point, in any direction
**plumes use this to set the diameter of the disk across which particles are spawned
**Syntax: '''''Float'''''
}}{{Table3613|
*'''+Z Scale:'''
**for sparklers, allows you to elongate the effect to surround other effects, like lasers. essentially a length multiplier
**for plume, it multiplies against +scale to set the plume to spread or converge, zero would be full convergence, 1 would be straight flight, and bigger numbers would cause particles to diverge from the disk.
**Syntax: '''''Float'''''
*'''+Rotation Rate:'''
**used only by helical spews, controls how many rotations per second the helix makes
**Syntax: '''''Float'', may be negative, useful for setting up 2 spews that spin in opposite directions'''
*'''+Offset:'''
**position of effect with regards to the weapon center
**Syntax: '''''Vector'''''
*'''+Initial Velocity:'''
**to indicate both direction and speed of particle effects regards to the weapon velocity and +scale:
**Syntax: '''''Vector'''''
}}{{Table3610|
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

===$Tag:===
*Allowed for secondary weapons
{{Table3610|
*Allowed for primary weapons and secondary weapons}}

*Sets this weapon as a TAG missile, level 1, 2, or 3. The second number is the duration in seconds.
*TAG Level 1 will illuminate hidden targets such as stealth fighters or ships normally obscured by nebula conditions.
*TAG Level 2 illiminates targets much like TAG Level 1, but turrets will prefer to shoot at them over other ships.
*TAG Level 3 has no effect in retail.
{{Table3610|
*TAG Level 3 allows the weapon to trigger [[Weapon.tbl#$SSM:|SSMs]]}}

*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively

===$SSM:===
{{Table3610|
*Defines the weapons SSM index number.
*Requires [[Weapons.tbl#$Tag:|TAG level 3]] or a targeting beam.
*Syntax: '''''Integer'''''}}

===$FOF:===
{{Table3610|
*Defines the field of fire for the weapon. Causes weapon to fire into a firing cone instead of direct firing line thus causing light inaccuracy
*Syntax: '''''Float''''', degrees}}

===$Shots:===
{{Table3610|
*Defines the number of shots every time the weapon is fired.
*Works only for primary weapons
*Syntax: '''''Integer''''', number of shots}}

===$decal:===
{{Table3610|
*Defines impact decals if they are in use
*'''+texture:'''
**Defines the texture used for impact decals (can use '''''-burn''''' and '''''-glow''''' textures)
**Syntax: '''''String''''', filename
*'''+backface texture:'''
**Defines ???
**Syntax: '''''String''''', filename
*'''+radius:'''
**Defines the size of the impact decals on target
**Syntax: '''''Float''''', meters
*'''+burn time:'''
**Defines the time the '''''-burn''''' texture appears on the target
**Syntax: '''''Integer''''', milliseconds}}
{{Table3613|
*Feature removed - table parsing retained to maintain compatibility}}

===$Transparent:===
{{Table3610|
*Defines weapon effect as transparent. Enables optional fields for 'alpha animations'
*'''+Alpha:'''
**Defines the strenght of the alpha (transparency). And also the maximum value for the alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Min:'''
**Defines the minimum alpha value for alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Cycle:'''
**Defines the change in alpha per frame, between '''Alpha''' and '''Alpha Min''' values
**Syntax: '''''Float'''''}}

===$Weapon Hitpoints:===
{{Table3611|
*Defines the amount of hitpoints a weapon has.
*Weapons with '''"bomb"''' flag have 50 hitpoints by default
*Giving weapon hitpoints makes it possible for the weapon to be shot down or be destroyed by EMP.
**Syntax: '''''Integer'''''
}}

===$Burst Shots:===
{{Table3611|
*Defines the number of shots in a burst
*Shots in a burst use shorter ( '''$Burst Delay:''' ) delay than usually
**Syntax: '''''Integer'''''}}

===$Burst Delay:===
{{Table3611|
*Defines the time in milliseconds between the shots in a burst
**Syntax: '''''Integer'''''}}

===$Burst Flags:===
{{Table3611|
*Defines the flags used to define the burst firing behaviour
**Syntax: ( '''''String''''' '''''String''''' ), list of flags
**Available burst flags:
***'''"fast firing"''', acts as if '''same turret cooldown''' flag would be used between the shots in the burst.
***'''"random length"''', makes AI to fire burst of random length (from 1 to burst shots).}}

===$Thruster Flame Effect:===
{{Table3611|
*Defines the filename of the effect used on the modeled thruster of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Effect:===
{{Table3611|
*Defines the filename of the effect used on the glow type effect of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Radius Factor:===
{{Table3611|
*Defines the radius multiplier for the thruster's glow type effect
**Syntax: '''''Float'''''}}

===$Substitute:===
{{Table3613|
*Defines a pattern of ammo to substitute for primary or secondary weapons. '''$substitute:''' can be repeated any number of times. ''+period'' and ''+index'' will grow the pattern array anytime something does not fit so any whole number will be accepted. If neither ''+period'' or ''+index'' is specified, it is assumed to be equivalent to ''+index: '''0'''''.
**Syntax: '''''Weapon Name'''''
*'''+period:'''
*Substitute '''Weapon Name''' every ''period'' shots. '''Mutually exclusive with ''+index'''''
**Syntax: '''''Positive Integer'''''
*'''+offset:'''
*Shift period pattern ''offset'' shots. '''Must be used with ''+frequency'''''
**Syntax: '''''Positive Integer'''''
*'''+index:'''
*Substitute the '''Weapon Name''' at ''index'' in the shot pattern. '''Mutually exclusive with ''+period'''''
**Syntax: '''''Positive Integer'''''
}}

==Weapons.tbl Flags==

==="Electronics"===
*Will seize up the weapons and engines systems of any ship for a short period of time.

==="Spawn ''Name'',''Value''"===
*Will spawn the specified number of defined missiles upon detonation.
{{Table3610|
*Multiple spawn types can be defined for a single 'carrier' weapon up to maximum of 5 different weapons}}

==="Remote Detonate"===
*Can be triggered remotely via a second press on the trigger

==="Big Ship"===
*These weapons cannot be mounted on small ships like fighters, bombers, sentry guns etc.

==="Huge"===
*Allows this weapon to do the final 10% damage to a ship with the "Big Damage" flag. Also the AI will not try to hit fighters with it.

==="Supercap"===
*Allows this weapon to do the final 75% damage to a ship with the "supercap" flag.

==="Bomber+"===
*The AI will prefer to use this weapon against bombers

==="child"===
*Cannot be set as a weapon on any ship, but is instead a child of a weapon. Usually defined with "Spawn ''Name'',''Value''"

==="Bomb"===
*Makes this weapon targetable with the B key, and the AI prefers to use it against large ships

==="No Dumbfire"===
*Missile will not fire without a lock

==="in tech database"===
*Has the weapon in the tech database at the start of the campaign

==="Player allowed"===
*Allows this weapon as a player weapon.
{{Table3610|
*'''EXTREMELY IMPORTANT NOTE:'''
**Whenever you plan to use a weapon as a player one in your campaign or missions, '''USE THIS FLAG'''.
**Not using it can cause problems within fs_open and it's a BAD MOD DESIGN.
**In the future, fs_open will maybe be able to avoid these problems but, nevertheless, it's still a BAD DESIGN.
**As another possible example: be careful to update "retail" tables if you plan to use Shivan weapons in player fighters.}}

==="Particle Spew"===
*Makes the weapon projectile spew out particles
{{Table3610|
*Can be defined with [[Weapons.tbl#$Pspew:|Particle Spew parameters]]}}

==="EMP"===
*This weapon will have an EMP effect on any ship within the blast radius
*Can be defined with [[Weapons.tbl#$EMP_Intensity:|EMP Intensity]] and [[Weapons.tbl#$EMP_Time:|EMP Time]]

==="Esuck"===
*Drains the target's energy banks
*Can be defined with [[Weapons.tbl#$Leech_Weapon:|Leech Weapon]] and [[Weapons.tbl#$Leech_Afterburner:|Leech Afterburner]]

==="Flak"===
*Makes this weapon a [[weapons.tbl#Flak_Guns|flak gun]]

==="Corkscrew"===
*Makes this weapon spiral AND swarm 4.
{{Table3610|
*Can be defined with [[Weapons.tbl#$Corkscrew:|Corkscrew parameters]]}}

==="Shudder"===
*Makes your ship shudder while you're firing the weapon

==="lockarm"===
*Requires a target lock in order to arm its warhead. In other words weapon causes less damage if it hits the target without target lock.

==="beam"===
*Makes this weapon a [[weapons.tbl#Beam Cannons|beam cannon]]

==="stream"===
* Does nothing

==="puncture"===
*Reduces hull damage by 75%
The AI will prefer these weapons for anti-subsystem use

==="countermeasure"===
{{Table3610|
*Defines the weapon as a countermeasure}}

==="Ballistic"===
{{Table3610|
*Defines the weapon as a ballistic weapon that needs ammunition.
*Make sure you define the size and reload rate for ballistic weapons}}

==="pierce shields"===
{{Table3610|
*Causes weapons to penetrate shield without causing damage to it.}}

==="no pierce shields"===
{{Table3610|
*Prevents weapons (beams) from piercing shields causing shields to be damaged by weapons first.}}

==="local ssm"===
{{Table3610| }}

==="tagged only"===
{{Table3610|
*Weapon can only be fired at tagged targets}}

==="beam no whack"===
{{Table3610|
*Disables beam whacking (push). Practically same as setting beam mass to zero.}}

==="cycle"===
{{Table3610|
*Causes weapon to alternate between firing points}}

==="small only"===
{{Table3610|
*Causes AI to use the weapon only on small targets (fighters, bombers etc.)}}

==="same turret cooldown"===
{{Table3610|
*Forces the turrets to fire on the designated rate of fire on all difficulty levels and all AI levels}}

==="apply no light"===
{{Table3610|
*Prevents light from being applied to the weapon model.}}

==="training"===
{{Table3610|
*Sets weapon to be of training weapon type. ?}}

==="smart spawn"===
{{Table3611|
*Forces turret fired spawn weapon of this type to be fired like normal weapons.}}

==="inherit parent target"===
{{Table3611|
*Sets spawned 'child' weapons to use parent weapon's target.}}

==="no emp kill"===
{{Table3611|
*Defines the weapon (with hitpoints) to be immune to automatic EMP destruction.}}

==="untargeted heat seeker"===
{{Table3611|
*Defines the weapon as a heatseeker type missile which acquires its target by itself.}}

==="no radius doubling"===
{{Table3611|
*Prevents weapon radius from being doubled when doing collision test. Makes bombs harder to intercept.}}

==="no subsystem homing"===
{{Table3611|
*Prevents weapon from acquiring a subsystem as its target. Missile homing points are spread over the target ship.}}

==="no lifeleft penalty"===
{{Table3611|
*Prevents weapon lifetime from being penalized if the angle to the target is too big.}}

==="can be targeted"===
{{Table3611|
*Allows weapon to be targeted by player. Does not influence AI}}

==="show on radar"===
{{Table3611|
*Allows weapon to be visible on the radar}}

==="show friendly on radar"===
{{Table3611|
*Allows friendly, otherwise visible to radar weapon, to be visible on player radar}}

==="capital+"===
{{Table3613|
*Tells AI to use this weapon only on capital ships}}

==="chain external model fps"===
{{Table3613|
*Tells game to keep switching external model firingpoints when firing}}

==="external model launcher"===
{{Table3613|
*Tells game that the external model is a launcher so that it would be kept static without loading motion}}

==="takes blast damage"===
{{Table3613|
*Weapon takes damage from weapon blasts}}

==="takes shockwave damage"===
{{Table3613|
*Weapon takes damage from shockwaves}}

==Countermeasures==
*Usually not altered. Only one can exist
{{Table3610|
*More than one can exist}}

===$Name:===
*Name of the countermeasure
*Syntax: '''''String''''', name

===$Velocity:===
*Defines the speed of the countermeasure, relative to the ship.
*Syntax: '''''Float''''', meter per second

===$Fire Wait:===
*Definies the minumum time between the countermeasure launches
*Syntax: '''''Float''''', seconds

===Lifetime===
*Countermeasure's life time is defined between with minimum and maximum lifetime
*'''$Lifetime Min:'''
**Syntax: '''''Float''''', seconds
*'''$Lifetime Max:'''
**Syntax: '''''Float''''', seconds

===$LaunchSnd:===
*Defines the sound for the countermeasure launch
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Model:===
*Defines the used model file (.pof)
*Syntax: '''''String.pof''''', model filename

==Player Weapon Precedence==
*First the primary weapons are defined, from most powerful to least powerful, and then the same for secondaries
*Syntax: ( '''''"String" "String"'''''), names of the weapons
*Example:

<pre>
$Player Weapon Precedence: (
"UD-8 Kayser"
"Prometheus R"
"Subach HL-7"
"Harpoon"
"Tempest"
"Rockeye" )
</pre>

==Sample==

<pre>
#Primary Weapons

$Name: @Subach HL-7
+Title: XSTR("GTW Subach HL-7", 3243)
+Description:
XSTR( "Standard Issue
Level 3 Hull Damage
Level 2 Shield Damage", 3244)
$end_multi_text
+Tech Title: XSTR("Subach HL-7", 146)
+Tech Anim: Tech_Subach_HL-7
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: none
@Laser Bitmap: newglo9
@Laser Glow: 2_laserglow03
@Laser Color: 250, 0, 0
@Laser Color2: 0, 0, 250
@Laser Length: 10.0
@Laser Head Radius: 0.90
@Laser Tail Radius: 0.90
$Mass: 0.2
$Velocity: 450.0
$Fire Wait: 0.2
$Damage: 15
$Armor Factor: 0.9
$Shield Factor: 0.7
$Subsystem Factor: 0.3
$Lifetime: 2.0
$Energy Consumed: 0.20
$Cargo Size: 0.0
$Homing: NO
$LaunchSnd: 76
$ImpactSnd: 85
$Flags: ( "in tech database"
"player allowed"
"stream")
$Icon: iconSD4
$Anim: SD4
$Impact Explosion: none

#End

#Secondary Weapons

$Name: EMP Adv.
+Title: XSTR("GTM-14 EMP Adv.", 3396)
+Description:
XSTR( "Advanced Missile
Electromagnetic Pulse Weapon
General Purpose Suppression", 3397)
$end_multi_text
+Tech Title: XSTR("GTM-14 EM Pulse Adv.", 3398)
+Tech Anim: Tech_EMP
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: EMPulse2.pof
$Mass: 15.0
$Velocity: 275.0
$Fire Wait: 2.0
$Damage: 45
$Blast Force: 20.0
$Inner Radius: 80.0
$Outer Radius: 300.0
$Shockwave Speed: 120.0
$Armor Factor: 1.0
$Shield Factor: 0.8
$Subsystem Factor: 0.5
$Lifetime: 5.0
$Energy Consumed: 0.0
$Cargo Size: 4.0
$Homing: YES
+Type: ASPECT
+Turn Time: 1.0
+Min Lock Time: 2.0
+Lock Pixels/Sec: 70
+Catch-up Pixels/Sec: 100
+Catch-up Penalty: 30
$LaunchSnd: 118
$ImpactSnd: 88
$FlyBySnd: -1
$Rearm Rate: 2.0
$Flags: ( "player allowed"
"EMP")
$Trail:
+Start Width: 0.25
+End Width: 0.75
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.5
+Bitmap: MissileTrail04
$Icon: iconEMPulse
$Anim: ecm
$Impact Explosion: ExpMissileHit1
$Impact Explosion Radius: 10.0
$EMP Intensity: 375.0
$EMP Time: 20.0

#End

$Player Weapon Precedence: (
"Subach HL-7"
"EMP Adv." )
</pre>

[[Category:Tables]]

.tbm

2011-08-06T15:40:28Z

IssMneur: Redirect .tbm to the tables page

#REDIRECT [[Tables#.tbm_files]]

.tbl

2011-08-06T15:38:50Z

IssMneur: Make a redirect for .tbl

#REDIRECT [[Tables]]

Various Terms

2011-08-06T15:35:38Z

IssMneur: /* File extensions */ Link .tbl and .tbm to their corrisponding pages

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*[[.tbl]] - Table file
*[[.tbm]] - Modular table
*.vp - Volition Pack files

===In-game Terminology===
*'''ETS''' - [[Energy Transfer System]]
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e.g. radars, engines.
*'''TSM''' - Training Simulator Module

====Designation Prefixes====
* '''GT_''' - [[Galactic Terran Alliance|Galactic Terran]]
* '''NT_''' - [[Neo-Terran Front|Neo-Terran]]
* '''GV_''' - Galactic Vasudan
* '''PV_''' - [[Parliamentary Vasudan Empire|Parliamentary Vasudan]]
* '''GTV_''' - [[Galactic Terran-Vasudan Alliance|Galactic Terran-Vasudan]]
* '''S_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_T''' - Transport
* '''_W''' - Weapon ([[Weapon Comparison (FS1)|FreeSpace 1]])([[Weapon Comparison (FS2)|FreeSpace 2]])

===Fighter Units and Roles===
*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. Wing labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===
* '''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.
* '''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.
* '''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.
* '''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.
* '''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.
* '''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.
* '''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''HL_''' - [[Hammer of Light]]

====Designation Suffixes====
* '''_BS''' or '''_Bs''' or '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''' - Frigate
* '''_Ff''' - Frigate
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.
* '''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Retail''' - The original, unaltered version of FreeSpace 2. (=not FreeSpace Open)
* '''RTB''' - Return to Base. Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''V''' or '''[V]''' - [[Volition]], Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FSU''' - The FreeSpace Upgrade Project
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''' - The Scroll of Antankharzim
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''WCS''' - [[Wing Commander Saga]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
* '''EMP''' - The EMP missile
* '''Fire''' - The Infyrno missile
* '''Fish''' - The Piranha missile
* '''Lag''' - Latency. This refers to the "jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly mitigated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''' - Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''Lock/Unlock''' - Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''Low''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

==Terms related to modelling==
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''HTL''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

[[Category:Lists]]
[[Category:Multiplayer]]

Tables

2011-08-06T15:31:50Z

IssMneur: /* Accessing table files */ VPs are Volition Packs not Packages

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

{| 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]]
| '''/mission/'''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"| [[Post_processing.tbl]]
| '''/graphics/'''gropenglpostprocessing.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
|-
|}

==Accessing table files==
Volition used a special kind of packaging method called .vp (Volition Pack) for the FreeSpace games. Table files are stored in Root_fs2.vp. To open and extract files from a VP, you must use a VP editing program such as [[VPView32]]. For more details about VP files and how to work with them, consult [[*.VP|this article]].

For some further information about where to put modified files, consult [[FreeSpace 2 directory structure]].

==Table files==
Table files are customarily edited using Notepad, but any text editor that can save in a pure text format will do.

===.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 table 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>{{Table3610| text}}</nowiki>''' gives 3.6.10 box
{{Table3610| text}}
:*'''<nowiki>{{Table3611| text}}</nowiki>''' gives 3.6.11 box
{{Table3611| text}}
*For full list of table related pages and links see [[:Category:Tables]]

[[Category:Tables|*]]

[[Category:Modding]]

[[Category:File Types]]

Various Terms

2011-08-06T15:30:09Z

IssMneur: /* File extensions */ vps are Pack files

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*.tbl - Table file
*.tbm - Modular table
*.vp - Volition Pack files

===In-game Terminology===
*'''ETS''' - [[Energy Transfer System]]
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e.g. radars, engines.
*'''TSM''' - Training Simulator Module

====Designation Prefixes====
* '''GT_''' - [[Galactic Terran Alliance|Galactic Terran]]
* '''NT_''' - [[Neo-Terran Front|Neo-Terran]]
* '''GV_''' - Galactic Vasudan
* '''PV_''' - [[Parliamentary Vasudan Empire|Parliamentary Vasudan]]
* '''GTV_''' - [[Galactic Terran-Vasudan Alliance|Galactic Terran-Vasudan]]
* '''S_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_T''' - Transport
* '''_W''' - Weapon ([[Weapon Comparison (FS1)|FreeSpace 1]])([[Weapon Comparison (FS2)|FreeSpace 2]])

===Fighter Units and Roles===
*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. Wing labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===
* '''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.
* '''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.
* '''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.
* '''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.
* '''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.
* '''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.
* '''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''HL_''' - [[Hammer of Light]]

====Designation Suffixes====
* '''_BS''' or '''_Bs''' or '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''' - Frigate
* '''_Ff''' - Frigate
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.
* '''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Retail''' - The original, unaltered version of FreeSpace 2. (=not FreeSpace Open)
* '''RTB''' - Return to Base. Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''V''' or '''[V]''' - [[Volition]], Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FSU''' - The FreeSpace Upgrade Project
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''' - The Scroll of Antankharzim
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''WCS''' - [[Wing Commander Saga]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
* '''EMP''' - The EMP missile
* '''Fire''' - The Infyrno missile
* '''Fish''' - The Piranha missile
* '''Lag''' - Latency. This refers to the "jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly mitigated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''' - Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''Lock/Unlock''' - Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''Low''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

==Terms related to modelling==
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''HTL''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

[[Category:Lists]]
[[Category:Multiplayer]]

Mod.ini (old)

2011-07-24T15:57:37Z

IssMneur: /* Multimod */ Note how to add multiple mods to the list

==Introduction==
Mod.ini defines the options for a given mod.
The core use for these is to allow a mod to easily use assets from another mod, such as the MediaVPs.

The file must be called "mod.ini" and be in the main folder of the mod.
It must be in ASCII text format (not Unicode) and use Windows-style end-of-line markers.
::: '''''PLEASE NOTE''': '''Launcher v 5.4''' or later, '''must be used'''. Earlier versions had some bugs that would cause this explanation about mod.ini to fail.''

==Sections==
===Launcher===
<pre>[launcher]</pre>
Information about the mod, displayed in the Launcher.

Attributes:
*modname = ''Name of the mod'';
*image255x112 = ''Mod bitmap.bmp'';
*infotext = ''Information about the mod'';
*website = ''URL to the mod's website, if applicable'';
*forum = ''URL to the mod's forum, if applicable'';
*mantis = ''URL to the mod's bugtracker, if applicable'';

The mod bitmap is displayed in the Launcher, under the "MOD" tab, when the mod is selected.
===Multimod===
<pre>[multimod]</pre>
Defines other mods that are used at the same time.

Attributes:
*primarylist = ''list of mods'';
**These mods will override assets in the current mod. Primarylist is needed very rarely. Currently only [[Silent Threat: Reborn]] requires the use of primarylist. Multiple mods are separated by commas.
*secondarylist = ''list of mods'';
**These mods will be added to the assets for the current mod, and may be overridden by data in the current mod. Multiple mods are separated by commas.

===Settings===
<pre>[settings]</pre>
Defines other required settings.

Attributes:
*flags = ''list of additional commandline flags'';

==Examples==
Below are examples of different mod.inis in various situations.
===MediaVPs 3.6.10===
The mod.ini provided with the MediaVPs doesn't use any other mods, as the MediaVPs are selected as a mod only when the player wants to play the regular FS2 campaign with better graphics. The mod.ini does, however, provide a Launcher image and links to Hard Light Productions.
<pre>
[launcher]
image255x112 = FSU-MVP.bmp;
infotext = Freespace II - 3.6.10 MediaVPs;
website = http://www.hard-light.net/;
forum = http://www.hard-light.net/forums;
mantis = http://www.hard-light.net/mantis;

[multimod]
primarylist = ;
secondarylist = ;
</pre>
===Derelict===
The [[Derelict]] mod.ini contains a reference to the MediaVPs, because many users want to play Derelict, and other mods, with better graphics provided by the MediaVPs. Also, the person who originally created the mod.ini deemed it necessary to include the -spec flag, though most people already have it turned on in their Launchers.
<pre>
[launcher]
image255x112 = Derelict.bmp;
infotext = Five years have passed since the jump node to the Capella system was collapsed...;
website = http://www.3dap.com/hlp/hosted/ce/;
forum = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist = ;
secondarylist = mediavps;

[settings]
flags = -spec;
</pre>

===Cardinal Spear===
[[Cardinal Spear]] is a mod that requires FSPort. Therefore, the secondarylist includes "fsport" in addition to "mediavps".
<pre>
[launcher]
image255x112 = CardinalSpear.bmp;
infotext = In the tenth year of our war against the Vasudans, humanity had attempted one last desperate strike to end the war outright - a spear in the dark. The Cardinal Fleet had been laid ruin, and the crew of the GTD Agamemnon was being hunted by a Vasudan general. It was too late for victory, but not too late for vengeance...;
website = http://fsport.hard-light.net/;
forum = http://www.hard-light.net/forums/index.php/board,39.0.html;

[multimod]
secondarylist = fsport,mediavps;
</pre>

===Silent Threat: Reborn===
Due to some design issues, Silent Threat: Reborn doesn't work correctly with the MediaVPs, if it is designated as the primary mod, with the other mods being of a secondary nature. The FSPort MediaVPs have to be read before ST:R for ST:R to function correctly. Therefore, "fsport-mediavps" is entered into the primarylist line.
<pre>
[launcher]
modname = Silent Threat: Reborn v1.0;
image255x112 = fsport-str.bmp;
infotext = As the Great War rages on, you've been commissioned by Galactic Terran Intelligence for special intelligence operations. Your objectives are to contain the Shivan onslaught and preserve the fragile Terran-Vasudan alliance. But a series of suspicious events cloud the GTI's spotless record. Is the GTI setting you up or are the Shivans spreading their evil rage?;
website = http://fsport.hard-light.net/website/str/;
forum = http://www.hard-light.net/forums/index.php/board,140.0.html;

[multimod]
primarylist = fsport-mediavps;
secondarylist = fsport,mediavps;
</pre>

[[Category:Modding]]

Weapons.tbl

2011-01-27T05:34:17Z

IssMneur: Add $substitute

{{Fileversion|6978}}

==Special Case Weapons==
===Beam Cannons===
*'''REQUIRES: "beam" flag'''
*'''REQUIRES: [[weapons.tbl#$BeamInfo:|$BeamInfo:]]'''
===Flak Guns===
*'''REQUIRE: "flak" and "particle spew" flags'''
*Must have inner and outer radius defined to have any effect.
*Does not use any model or weapon effect though model must be defined, usually Hornet.pof. Instead it uses [[Weapons.tbl#$Pspew:|particle spew]]. Trails can also be added.

==Weapons Table==

==General Format==
*The weapons table consist of several sections
*All sections beginning with <nowiki>#</nowiki> need <nowiki>#</nowiki>'''End''' before the next section.
**<nowiki>#</nowiki>'''Primary Weapons'''
***Defines all '''standard primaries weapons''' as well as '''beam cannons''' and '''flak cannons'''.
**<nowiki>#</nowiki>'''Secondary Weapons'''
***Defines all '''secondary weapons'''.
**<nowiki>#</nowiki>'''Beam Weapons'''
***I haven't got any ideas for this one.
**<nowiki>#</nowiki>'''[[Weapons.tbl#Countermeasures|Countermeasures]]'''
***Defines the used countermeasure.
**'''$Player Weapon Precedence'''
***Player Weapon Precedence is used in weapon selection when a default specified by the mission designer is not available to the player. The next weapon on the list is used in its place (assuming that weapon is allowed for the player).

==Core Table==

===$Name:===
*This is the name of the weapon. If it's going to be used by the player, keep it under 12 characters so it doesn't spill over the HUD box. Two special characters can be used in the name: '''#''' and '''@'''. Their usage details are the very same than inside the [[Ships.tbl#.24Name:_2|$Name field from Ships.tbl]].
*Syntax: '''''String'''''

====+nocreate====
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===$Alt Name:===
{{Table3611|
*An alternative name that can be referenced instead of $Name:
*Syntax: '''''String'''''}}

===$Subtype:===
{{Table3610| }}

===+Title:===
*This is the title of the weapon in the Weapons loadout screen. Only needed for player allowed weapons. Title may be anything. Numerical value is a reference to translations in [[Tstrings.tbl]]
*Syntax: XSTR('''''"String"''''', -1)

===+Description:===
*This is the description you see in the weapons loadout screen. Again, these aren't based on any hard numbers, just approximations. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

'''Example'''

<pre>
XSTR(
"''Standard Issue
''Level 3 Hull Damage
''Level 2 Shield Damage''", -1)
$end_multi_text
</pre>

===+Tech Title:===
*Title of the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: XSTR('''''"String"''''', -1)

===+Tech Anim:===
*Animation used for the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: '''''String''''', animation filename
**Example: ''Tech_Subach_HL-7''

===+Tech Description:===
*Descriptive text you see in the tech room. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

'''Example'''

<pre>
XSTR(
"''The Subach-Innes HL-7...''", 3245)
$end_multi_text
</pre>

===$Tech Model:===
{{Table3610|
*Defines model used in wing loadout screen and in Tech Room for the weapon.
*Syntax: '''''String.pof''''', model filename}}

===$HUD Image:===
{{Table3610|
*Defines the picture used to represent the weapon in HUD loadout list
*Syntax: '''''String''''', filename}}

===$Model File:===
*Filename of the model file (.pof) at data/models folder. Additional fields beginning from '''''@Laser Bitmap:''''' and ending to '''''@Laser Tail Radius:''''' are not needed if a model has been defined for the weapon.
*Standard primaries and beam cannons do not use specific models so for those the name is 'none'.
*Flak weapons and secondaries use models, though the exact model is not important with the flak weapons.
*Syntax: '''''String.pof''''' or ''none'', model filename
**Example: ''none''

===$POF target LOD:===
{{Table3610|
*Defines the LOD (Level-Of-Detail) of the model used in HUD targetting view
*Syntax: '''''Integer'''''}}

===$Detail Distance:===
{{Table3613|
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers are (from left to right): 1/8, 1/4, 1, 4, 8
*Optional. If not defined the game uses the formula ((radius * 20.0 + 20.0) * LOD)
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''}}

===$External Model File:===
{{Table3610|
*Defines the models shown on the gunpoint, used with Bobb's external-visible-weapon code.
*Syntax: '''''String.pof''''', model filename}}

===$Submodel Rotation Speed:===
{{Table3610|
*Defines the rotation speed of the external weapon model
*Syntax: '''''Float'''''}}

===$Submodel Rotation Acceleration:===
{{Table3610|
*Defines the rotation acceleration of the external weapon model
*Syntax: '''''Float'''''}}

===@Laser Bitmap:===
**The graphic file to be used as the weapon effect if no model is defined.
**Syntax: '''''String''''', filename

===@Laser Glow:===
**The graphic file that determines the glow of the weapon effect if no model is defined. The color in which this gets drawn is determined by @Laser Color and @Laser Color2.
**Syntax: '''''String''''', filename

===@Laser Color:===
**The color of the glow effect when you fire the weapon.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''250, 0, 0''

===@Laser Color2:===
**The color of the glow effect at the weapon's maximum range.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''0, 0, 250''

===@Laser Length:===
**Length of the weapon effect.
**Syntax: '''''Float''''', meters

===@Laser Head Radius:===
**Width of the head of the weapon effect.
**Syntax: '''''Float''''', meters

===@Laser Tail Radius:===
**Width of the tail of the weapon effect.
**Syntax: '''''Float''''', meters

===$Mass:===
*How much of a kinetic effect this weapon has on its target. 3+ gives you the Flail effect. Set it to 10 and you can knock cruisers around.
*This is somehow multiplied by the speed. ie ''$Mass: 3'' and ''$Velocity: 200'' has much weaker kinetic effect than ''$Mass: 3'' and ''$Velocity: 1000''. Also $Mass is used to calculate intensity of "shudder" effect if flagged.
*Syntax: '''''Float''''', blast effect

===$Velocity:===
*How fast the weapon travels. Is also used to define the weapon range, '''''$Velocity x $Lifetime = range'''''.
*Beams travel instantly so this field has effect only on weapon range and AI beam targetting with certain beam types. $Velocity of beam also applies to its kinetic effect along with $Mass.
*Syntax: '''''Float''''', meters per second

===$Fire Wait:===
*Time in seconds between firings
*Note that Fire wait will be reset to 1 if it is set over 5 for non turreted primary weapons
*Syntax: '''''Float''''', seconds

===$Damage:===
*Base damage this weapon does. The actual damage is this number multiplied by the factors below.
*Base damage this beam does is continuous damage, damage is 5.5 times the damage value per second. The actual damage is this number multiplied by one of the factors below.
*Syntax: '''''Float''''', damage

===$Damage Type:===
{{Table3610|
*Defines the damage type that this weapon uses. All armor effects are applied after shield and have no function against shockwave or subsystem damage. '''REQUIRES ADDITIONAL TABLE'''.
*Syntax: '''''String''''', name of the damage type as defined in [[armor.tbl]]}}

===$Arm time:===
{{Table3610|
*Defines the time after the launch that is required before the weapon comes hot
*If the time has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', seconds}}

===$Arm distance:===
{{Table3610|
*Defines the distance from the firing ships that is required before the weapon comes hot
*If the distance has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', meters}}

===$Arm radius:===
{{Table3610|
*Defines the distance from the target where the weapon will arm itself
*Syntax: '''''Float''''', meters}}

===$Detonation Range:===
{{Table3610|
*Defines the distance from the point in space that the weapon was launched where the weapon will detonate
*Syntax: '''''Float''''', meters}}

===$Detonation Radius:===
{{Table3610|
*Defines the distance between the target center point point and the weapon which detonates the weapon.
*Syntax: '''''Float''''', meters}}

===$Shockwave damage:===
{{Table3610|
*Override for the damage caused by shockwaves
*Syntax: '''''Float''''', damage}}

===$Shockwave Damage Type:===
{{Table3610|
*'''REQUIRES ADDITIONAL TABLE'''. Defines the damage type used for the weapon explosions
*Syntax: '''''String''''', name as defined in [[armor.tbl]]}}

===$Blast Force:===
*The intensity of the kinetic blast effect when ship is within the outer radius of the explosion. Comes in effect only if inner and outer radius are defined.
*Syntax: '''''Float''''', blast effect

===$Inner Radius:===
*Radius at which the full explosion damage is done. Marks the line where damage attenuation begins.
*Syntax: '''''Float''''', meters

===$Outer Radius:===
*Maximum radius at which any damage is done
*Also defines the size of the shockwave (if shockwave speed is > 0)
*Syntax: '''''Float''''', meters

===$Shockwave Speed:===
*Speed shockwave expands at. Zero means no shockwave and that damage is applied immediately
*Syntax: '''''Float''''', meters per second

===$Shockwave rotation:===
{{Table3610|
*Defines how the 3D shockwave is rotated.
*Syntax: '''''Angle''''', three values, pitch, bank, heading respectively, in degrees}}

===$Shockwave model:===
{{Table3610|
*Defines the model file (.pof) used as a shockwave for the 3D shockwaves.
*Syntax: '''''String.pof''''', model filename}}

===$Shockwave name:===
{{Table3610|
*Defines the name of the animation used for the 2D shockwave
*Syntax: '''''String''''', filename}}

===$Dinky shockwave:===
{{Table3610|
*Dinky shockwave are used if the weapon is shot down before arming or if the conditions marked at '''Arm time''' and '''Arm distance''' are not reached before impact
*It uses exactly same entries as the standard shockwaves
*'''''+Shockwave damage:'''''
*'''''+Shockwave damage type:'''''
*'''''+Blast Force:'''''
*'''''+Inner Radius:'''''
*'''''+Outer Radius:'''''
*'''''+Shockwave Speed:'''''
*'''''+Shockwave Rotation:'''''
*'''''+Shockwave Model:'''''
*'''''+Shockwave Name:'''''}}

===$Armor Factor:===
*Multiplier for the damage done to armor
*Syntax: '''''Float''''', damage multiplier

===$Shield Factor:===
*Multiplier for the damage done to shields
*Syntax: '''''Float''''', damage multiplier

===$Subsystem Factor:===
*Multiplier for the damage done to subsystems
*Syntax: '''''Float''''', damage multiplier

===$Lifetime Min:===
{{Table3610|
*Defines the minimum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime Max:===
{{Table3610|
*Defines the maximum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime:===
*Time before the standard primaries fizzle out and secondaries self destruct. Multiply this by the speed to get the range. If values are too low (below framerate) then the collision detection and graphic effects may suffer.
*This field has no effect for the beams apart from weapon range and AI beam targeting with certain beam types
*Syntax: '''''Float''''', seconds

===$Energy Consumed:===
*The amount of energy each bolt drains firing ship. Has no effect on turretted weapons.
*Syntax: '''''Float'''''

===$Cargo Size:===
*Cargo size, is not used with non-ballistic primaries.
*Amount of missiles available = Bank capacity / Cargo Size.
*Syntax: '''''Float'''''

===$Homing:===
*Only for secondaries. You can't have homing primaries. If this is set to YES with primaries, then the bolts turn to face their target but keep moving in the same direction. If the field is set to NO then following fields are not required in the table.
*Defines if the missiles in question is homing
*Syntax: '''''Boolean''''', yes or no
*'''+Type:'''
**Defines the homing method
**Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table3610| An additional option, ''JAVELIN'', has been added. This behaves like an aspect missile but automatically only locks onto the engines of a target, and only if the engines are in sight.}}
*'''+Turn Time:'''
**Defines how well missile maneuvers. Number of seconds it takes the missile to do a 360 degree circle
**Syntax: '''''Float''''', seconds
*'''+View Cone:'''
**'''Heat-seeking missiles only''', this is then number of degrees the missile sees. Value / 2 gives the angle from the missile's centerline.
**Syntax: '''''Float''''', degrees
{{Table3610| Has been enabled also to aspect seekers as an option.}}

*'''+Min Lock Time:'''
**'''For aspect/javelin missiles only''', the minimum number of seconds to gain target lock
**Syntax: '''''Float''''', seconds
*'''+Lock Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels the aspect triangle moves per second while attempting lock-on
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels moved per second while attempting to catch up to the target
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Penalty:'''
**'''For aspect/javelin missiles only''', extra pixels to move after catching up ????
**Syntax: '''''Integer''''', pixels
{{Table3610|
*'''+Seeker Strength:'''
**Defines the seeking ability of the homing system. Default of heat seekers is 3 and for aspect seekers 2. Spoofing change is defined as '''cm type effectiveness'''/'''seeker strength'''.
**Syntax: '''''Float''''', seeker strength}}
{{Table3611|
*'''+Target Lead Scaler:'''
**Defines the type of pursuit course the missile tries to obtain.
**Values < 0 give lag pursuit, values ~ 0 give pure pursuit, values > 0 give lead pursuit.
**Syntax: '''''Float''''', default for heat seekers: 0, default for aspect or javelin seekers: 1.}}

===$Swarm:===
*The number of missiles to fire per volley if it's a swarm missile
*Can be issued to Standard primaries also. Causes single part turrets to malfunction but causes multi part turrets to fire only on their barrel line. Can be used for 'burst fire weapons'. Does not work with player weapons.
*Is incompatible with "Corkscrew" option.
*Syntax: '''''Integer''''', number of shots in a swarm
{{Table3610|
*'''+SwarmWait:'''
**Defines the time between weapons fired in a swarm
**Syntax: '''''Float''''', seconds
***Default: 0.150}}

===$Free Flight Time:===
{{Table3610|
*Defines the free flight time of homing weapons. During this time weapon flies at 1/4 of its velocity + firing ships velocity in a straight line.
*Syntax: '''''Float''''', seconds
**Default: 0.25}}

===$Free Flight Speed:===
{{Table3613|
*Defines the speed that the weapon will be travelling at during the free flight segment (see above).
*Syntax: '''''Float''''', Multiplier for the actual speed, minimum 0.01.
**Default: 0.25}}

===$LaunchSnd:===
*Corresponding sound effect when the weapon is launched.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$ImpactSnd:===
*Sound the weapon makes when it hits a hull.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Disarmed ImpactSnd:===
{{Table3610|
*Sound the weapon makes when it hits a hull before being armed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$FlyBySnd:===
*The sound this weapon makes if it narrowly misses you. -1 is no sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]], usually -1

===$Model:===
{{Table3610|
*Defines used model file. Included for compatibility with countermeasures as they have been merged with weapons in the code.
*Syntax: '''''String.pof''''', model filename}}

===$Rearm Rate:===
*Defines the rate the weapons are loaded to the ship
*Syntax: '''''Float''''', missiles loaded per second

===+Weapon Range:===
*Defines the range to the target where the weapons under AI will start firing.
*Syntax: '''''Float''''', meters

===+Weapon Min Range:===
{{Table3610|
*Defines the minimum range to the target where the weapons under AI will still fire.
*Implemented before FS_Open 3.6.5
*Syntax: '''''Float''''', meters}}

===$Flags:===
*See [[Weapons.tbl#Weapons.tbl_Flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the weapon
**Example: ( "Player allowed" "in tech database" )

{{Table3610|
*Can be followed by '''+override''' option in order to reset the weapon flags before parsing in the new ones
*Using this option will erase all '''homing'''-related flags as well as '''swarm''', '''variable lead''', '''trail''', '''TAG''', and '''transparent''' settings in addition to the listed flags. All these should be set again - if they are required - when this option is used.

**Syntax: '''''+override'''''}}

===$Trail:===
*This is used if you want your weapon to have a trail. Trail is often used only with secondaries though it works with standard primaries as well.
*'''+Start Width:'''
**How wide the head of the trail is.
**Syntax: '''''Float''''', meters
*'''+End Width:'''
**How wide the tail of the trail is.
**Syntax: '''''Float''''', meters
*'''+Start Alpha:'''
**The opacity of the trail head.
**Syntax: '''''Float''''', value between 0 and 1
*'''+End Alpha:'''
**The opacity of the trail tail.
**Syntax: '''''Float''''', value between 0 and 1
*'''+Max Life:'''
**How long the trail lasts.
**Syntax: '''''Float''''', seconds
*'''+Bitmap:'''
**The graphic file to use for the trail.
**Syntax: '''''String''''', filename
{{Table3611|
*'''+Faded Out Sections:'''
**Defines the number of the trail sections (counting from the leading edge) which are gradually faded out.
**Syntax: '''''Integer''''', number of trail sections}}

===$Icon:===
*Loadout icon used in the weapons selection screen.
*Syntax: '''''String''''', filename

===$Anim:===
*Green grid animation used on the weapons screen.
*Syntax: '''''String''''', filename

===$Collide Ship:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Collide Weapon:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Impact Explosion:===
*Impact explosion used. Must be defined in weapon_expl.tbl,
*Syntax: '''''String''''', filename or ''none''

===$Impact Explosion Radius:===
*Radius of the defined impact explosion.
*Syntax: '''''Float''''', meters

===$Dinky impact explosion:===
{{Table3610|
*Same as Impact explosion but for Dinky (not armed) explosions
*Syntax: '''''String''''', filename or ''none''}}

===$Dinky impact explosion radius:===
{{Table3610|
*Same as Impact explosion radius but for Dinky explosions
*Syntax: '''''Float''''', meters}}

===$Piercing Impact Explosion:===
{{Table3611|
*Defines the effect used for events when weapon pierces the target
*Syntax: '''''String''''', filename or ''none''}}

===$Piercing Impact Radius:===
{{Table3611|
*Defines the base radius of the effect used for piercing weapon impacts
*Syntax: '''''Float'''''}}

===$Piercing Impact Velocity:===
{{Table3611|
*Defines the base velocity for the particles piercing the target
*Syntax: '''''Float'''''}}

===$Piercing Impact Splash Velocity:===
{{Table3611|
*Defines the base velocity for the particles splashing from the target (secondary piercing effects
*Negative value causes the second batch or particles to splash to opposite direction
*Syntax: '''''Float'''''}}

===$Piercing Impact Variance:===
{{Table3611|
*Defines the variance added to the particles
*Values near 0 cause very little variance and values close to 1 cause extreme dispersal.
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the lifetime of the effect for single frame effects
*For multiple frame effects the lifetime is the lifetime of the animation used
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the number of particles released per impact
*Syntax: '''''Integer'''''}}

===$Piercing Impact Draw Modifier:===
{{Table3611|
*Defines the multiplier applied to the ships piercing effect limit percentage
*Syntax: '''''Float'''''}}
*Option removed in 3.6.12. Use [[armor.tbl]] to finetune piercing effects.

===$Muzzleflash:===
*Normally only with flak cannons.
*Defines the muzzle flash the weapon uses
*Syntax: '''''String''''', muzzleflash name, as defined in [[mflash.tbl]]

===$EMP Intensity:===
**If it has an EMP effect, how deeply it scrambles your electronics
**Syntax: '''''Float'''''

===$EMP Time:===
**Duration of the EMP effect
**Syntax: '''''Float''''', seconds

===$Leech Weapon:===
**The amount of weapon energy to drain with each hit
**Syntax: '''''Float'''''

===$Leech Afterburner:===
**The amount of afterburner fuel to drain with each hit
**Syntax: '''''Float'''''

===$Corkscrew:===
{{Table3610|
*Allow corkscrew parameters to be defined
*'''+Num Fired:'''
**Defines the number of weapons fired in sequence. Same as the standard swarm entry but for corkscrew missiles
**Syntax: '''''Integer''''', number of missiles
*'''+Radius:'''
**Defines the radius used in the corkscrew motion
**Syntax: '''''Float''''', meters
*'''+Fire Delay:'''
**Defines the delay between missile firings
**Syntax: '''''Integer''''', milliseconds
*'''+Counter rotate:'''
**Defines if every other missile rotates to a different direction (clockwise / anticlockwise)
**Syntax: '''''Boolean''''', ''0'' or ''1'', no or yes
*'''+Twist:'''
**Defines the speed of rotation movement on the radius of corkscrew motion.
**Syntax: '''''Float''''', radians per second}}

===$Electronics:===
{{Table3610|
*Defines the weapons effect against electronics. Requires [[weapons.tbl#"Electronics"|"electronics"]] flag. '''+New Style:''' and '''+Old Style:''' options are mutually exclusive.
*'''+New Style:'''
**Defines that the electronics use the new style which enables more options.
*'''+Old Style:'''
**Defines that the electronics use the old style. The old style was the way the D-Missile worked in Descent: FreeSpace.
*'''+Intensity:'''
**May only be used with '''+New Style:''' electronics. '''''Has been deprecated'''''.
**Syntax: '''''Float'''''
*'''+Lifetime:'''
**Syntax: '''''Integer''''', milliseconds
*'''+Engine Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for engine subsystems.
**Syntax: '''''Float'''''
*'''+Weapon Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for non-beam turrets.
**Syntax: '''''Float'''''
*'''+Beam Turret Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for beam turrets.
**Syntax: '''''Float'''''
*'''+Sensors Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for sensor subsystems.
**Syntax: '''''Float'''''
*'''+Randomness Time:'''
**Defines the randomness of duration target suffers from the electronics hit. A random number between 0 and this time will be added or subtracted from the disruption time.
**Syntax: '''''Integer''''', milliseconds

* Without any electronics parameters, a weapon with the "electronics" flag will default to the ''Old Style'' mode with a lifetime of 6000 milliseconds and a randomness of 4000 milliseconds. Thus any ship that gets hit can get disrupted for anywhere between 2 to 10 seconds.

*''WARNING: Putting +Old Style doesn't seem to work either.
To have a working electronics weapon just put the electronics flag in the weapon and make sure it has a big shockwave radius and a shockwave speed of 0.''
}}

===$Spawn Angle:===
{{Table3610|
*Defines the cone (with an angle) where the spawned weapons appear. ''Value'' gives the angle from the missiles centerline. The maximum possible angle between any two child weapons would be ''Value*2''.
*Spawn angle can be defined as many times as the carrier missile has child weapons defined for it (up to 5).
*Syntax: '''''Float''''', degrees}}

===$Local SSM:===
{{Table3610|
*Defines the local SSM (Subspace Missile). In effect missile moves via subspace to a position close to the target and starts homing.
*Weapon must be '''''aspect seeking missile''''' and must have '''''[[Weapons.tbl#"local ssm"|local ssm]]''''' flag.
*'''+Warpout Delay:'''
**Defines the time between the missile launch and the subspace jump.
**Syntax: '''''Integer''''', milliseconds
*'''+Warpin Delay:'''
**Defines the time missile stays in subspace before exiting.
**Syntax: '''''Integer''''', milliseconds
*'''+Stage 5 Velocity:'''
**Defines the velocity of the missile after the subspace jump.
**Syntax: '''''Float''''', meters per second
*'''+Warpin Radius:'''
**Defines how far from the SSM will appear from the outer radius of the target.
**Syntax: '''''Float''''', meters
*'''+Lock Range:'''
**Defines the maximum range where SSM can achieve target lock
**Syntax: '''''Float''''', meters}}

===$Countermeasure:===
{{Table3610|
*Defines the countermeasure effectiveness and radius
*'''+Heat Effectiveness:'''
**Defines the countermeasures effectiveness against heat seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Aspect Effectiveness:'''
**Defines the countermeasures effectiveness against aspect seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Effective Radius:'''
**Defines the countermeasures effective radius
**Syntax: '''''Float''''', meters
***Default: 300}}

===$BeamInfo:===
*'''+Type:'''
**Defines the type of beam in question. Beam types: 0 is a standard non-slashing type beam. 1 is a slashing type beam. 2 is a targetting beam that doesn't seem to have much of an effect on anything. 3 is a beam type that fires pulses in anti-fighter role and acts like type 0 beam in other roles. 4 is a beam that is restricted to what is directly in front of it, along turrets firepoints normal.
**Syntax: '''''Integer''''',, only values from 0 to 4 are legal
*'''+Life:'''
**How long it lasts once the beam is actually firing.
**Syntax: '''''Float''''', seconds
*'''+Warmup:'''
**Warmup time
**Syntax: '''''Integer''''', milliseconds
*'''+Warmdown:'''
**Warmdown time
**Syntax: '''''Integer''''', milliseconds
*'''+Radius:'''
**Muzzle glow radius
**Syntax: '''''Float''''', meters
*'''+PCount:'''
**Particles spewed every interval. ??
**Syntax: '''''Integer'''''
*'''+PRadius:'''
**Particle radius
**Syntax: '''''Float''''', meters
*'''+PAngle:'''
**Defines the random "cone" where the particles are generated
**Syntax: '''''Float''''', angle of the cone
*'''+PAni:'''
**Animation used to represent the particles
**Syntax: '''''String''''', filename
*'''+Miss Factor:'''
**The higher the numbers, the more likely that this beam will miss. One value for every difficulty level
**Syntax: '''''Miss Factor''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5
{{Table3613|
*'''IFF specific miss factors'''
**Identical to the preceding entry but IFF specific. Replace the <IFF> with the name of the IFF from [[iff_defs.tbl]]
**Syntax: '''''+<IFF> Miss Factor:''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5}}
*'''+BeamSound:'''
**Corresponding looping sound effect when the beam is firing.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmupSound:'''
**Corresponding sound effect when the beam is beam warmed up.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmdownSound:'''
**Corresponding sound effect when the beam is warming down.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Muzzleglow:'''
**Defines the bitmap used to create the muzzle glow
**Syntax: '''''String''''', filename
*'''+Shots:'''
**Defines into how may invidual shots the type 3 (AAA) beams are divided. Note total firing is the same as the +Life:
**Syntax: '''''Integer'''''
*'''+ShrinkFactor:'''
**What percentage of lifetime where beam starts shrinking (0.1 == 10% life left)
**Syntax: '''''Float'''''
*'''+ShrinkPct:'''
**What percentage of max width we subtract per second
**Syntax: '''''Float'''''
{{Table3610|
*'''+Range:'''
**Defines the maximum range where the beam still has any effect.
**Syntax: '''''Float''''', meters
*'''+Attenuation:'''
**Defines the point where the damage caused by the beam starts to attenuate. At maximum range damage is zero.
**Syntax: '''''Float''''', from 0 - firing point to 1 - no effect
***Default: 1}}
{{Table3611|
*'''+BeamWidth:'''
**Defines the width of the beam for collision test purposes instead of using widest beam section.
**Syntax: '''''Float''''
*'''+Beam Flash Effect:'''
**Defines the additional impact flash effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Flash Radius:'''
**Defines the radius for the additional impact flash effect.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect:'''
**Defines the beam piercing (bursting flames) effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Piercing Radius:'''
**Defines the average radius used for the beam piercing effects.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Velocity:'''
**Defines the base velocity for the piercing effects
**Syntax: '''''Float'''''
*'''+Beam Piercing Splash Effect Velocity:'''
**Defines the base velocity for the secondary piercing effects
**Negative velocity causes the particles to move to opposite direction
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Variance:'''
**Defines the variances of the particles from the main path
**Values close to 0 cause minimum variance, higher values cause higher variances
**Syntax: '''''Float'''''}}

*'''$Section:'''
**Beams are made up of up to five sections layered atop one another to create the effect. Each section has its own parameters.
{{Table3610|
:*'''+Index:'''
:**Field used to define with [[Modular Tables]] the beam section which is edited.
:**Syntax: '''''Integer''''', index number legal values are from 0 to 5
:*'''+remove'''
:**Removes the set beam section.
:*'''+nocreate'''
:**Does not create new section for the beam}}

:*'''+Width:'''
:**Width of the section
:**Syntax: '''''Float''''', meters
:*'''+Texture:'''
:**Texture for the section
:**Syntax: '''''String''''', filename
:*'''+RGBA Inner:'''
:**Defines the color and transparency of the center of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 255 255 255 255
:*'''+RGBA Outer:'''
:**Defines the color and transparency of the edges of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 150 150 150 10
:*'''+Flicker:'''
:**Defines how much the section flickers
:**Syntax: '''''Float''''', value from 0 to 1
:*'''+Zadd:'''
:**Defines the 'thickness' of the section. The higher the Zadd, the closer the section appears to be.
:**Syntax: '''''Float'''''
{{Table3610|
:*'''+Tile Factor:'''
:**Defines the beam texture tileing factor. Second number defines the tileing type. Type 0 tiles the graphic in the beam as many times as defined by the 1st number. Type 1 uses the 1st value as the lenght of the tile.
:**Syntax: '''''Float''''', '''''Integer'''''
:*'''+Translation:'''
:**Defines the speed of translation of the beam, a positive value moves from the impact point to the firing point, while a negative value moves away from the firing point towards the impact point. Measured in tiles per second, where the tile count is defined in the "+Tile Factor:" field above.
:**Syntax: '''''Float'''''}}

===$Pspew:===
{{Table3610|
*Defines a particle spew effect for the given weapon
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created
**Syntax: '''''Integer'''''
*'''+Time:'''
**Defines the time in milliseconds between next particle(s) spewed
**Syntax: '''''Integer''''', milliseconds
*'''+Vel:'''
**Defines the created particles velocity as percentage of the weapons velocity
**Syntax: '''''Float'''''
*'''+Radius:'''
**Defines the size of the created particles
**Syntax: '''''Float''''', meters
*'''+Life:'''
**Defines how long the particles last.
**Syntax: '''''Float''''', seconds
*'''+Scale:'''
**Defines the particle spread. Small value will make particles group together
**Syntax: '''''Float'''''
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

===$Tag:===
*Allowed for secondary weapons
*Location: After $Impact Explosion Radius:
*Sets this weapon as a TAG missile, level 1, 2, or 3. The second number is the duration in seconds.
*TAG Level 1 will illuminate hidden targets such as stealth fighters or ships normally obscured by nebula conditions.
*TAG Level 2 illiminates targets much like TAG Level 1, but turrets will prefer to shoot at them over other ships.
*TAG Level 3 has no effect in retail.
*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively

===$SSM:===
{{Table3610|
*Defines the weapons SSM index number:
*Syntax: '''''Integer'''''}}

===$FOF:===
{{Table3610|
*Defines the field of fire for the weapon. Causes weapon to fire into a firing cone instead of direct firing line thus causing light inaccuracy
*Syntax: '''''Float''''', degrees}}

===$Shots:===
{{Table3610|
*Defines the number of shots every time the weapon is fired.
*Works only for primary weapons
*Syntax: '''''Integer''''', number of shots}}

===$decal:===
{{Table3610|
*Defines impact decals if they are in use
*'''+texture:'''
**Defines the texture used for impact decals (can use '''''-burn''''' and '''''-glow''''' textures)
**Syntax: '''''String''''', filename
*'''+backface texture:'''
**Defines ???
**Syntax: '''''String''''', filename
*'''+radius:'''
**Defines the size of the impact decals on target
**Syntax: '''''Float''''', meters
*'''+burn time:'''
**Defines the time the '''''-burn''''' texture appears on the target
**Syntax: '''''Integer''''', milliseconds}}
{{Table3613|
*Feature removed - table parsing retained to maintain compatibility}}

===$Transparent:===
{{Table3610|
*Defines weapon effect as transparent. Enables optional fields for 'alpha animations'
*'''+Alpha:'''
**Defines the strenght of the alpha (transparency). And also the maximum value for the alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Min:'''
**Defines the minimum alpha value for alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Cycle:'''
**Defines the change in alpha per frame, between '''Alpha''' and '''Alpha Min''' values
**Syntax: '''''Float'''''}}

===$Weapon Hitpoints:===
{{Table3611|
*Defines the amount of hitpoints a weapon has.
*Weapons with '''"bomb"''' flag have 50 hitpoints by default
*Giving weapon hitpoints makes it possible for the weapon to be shot down or be destroyed by EMP.
**Syntax: '''''Integer'''''
}}

===$Burst Shots:===
{{Table3611|
*Defines the number of shots in a burst
*Shots in a burst use shorter ( '''$Burst Delay:''' ) delay than usually
**Syntax: '''''Integer'''''}}

===$Burst Delay:===
{{Table3611|
*Defines the time in milliseconds between the shots in a burst
**Syntax: '''''Integer'''''}}

===$Burst Flags:===
{{Table3611|
*Defines the flags used to define the burst firing behaviour
**Syntax: ( '''''String''''' '''''String''''' ), list of flags
**Available burst flags:
***'''"fast firing"''', acts as if '''same turret cooldown''' flag would be used between the shots in the burst.
***'''"random length"''', makes AI to fire burst of random length (from 1 to burst shots).}}

===$Thruster Flame Effect:===
{{Table3611|
*Defines the filename of the effect used on the modeled thruster of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Effect:===
{{Table3611|
*Defines the filename of the effect used on the glow type effect of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Radius Factor:===
{{Table3611|
*Defines the radius multiplier for the thruster's glow type effect
**Syntax: '''''Float'''''}}

===$Substitute:===
{{Table3613|
*Defines a pattern of ammo to substitute for primary or secondary weapons. '''$substitute:''' can be repeated any number of times. ''+frequency'' and ''+index'' will grow the pattern array anytime something does not fit so any whole number will be accepted.
**Syntax: '''''Weapon Name'''''
*'''+frequency:'''
*Substitute '''Weapon Name''' every ''frequency'' shots. '''Mutually exclusive with ''+index'''''
**Syntax: '''''Positive Integer'''''
*'''+offset:'''
*Shift frequency pattern ''offset'' shots. '''Must be used with ''+frequency'''''
**Syntax: '''''Positive Integer'''''
*'''+index:'''
*Substitute the '''Weapon Name''' at ''index'' in the shot pattern. '''Mutually exclusive with ''+frequency'''''
**Syntax: '''''Positive Integer'''''
}}

==Weapons.tbl Flags==

==="Electronics"===
*Will seize up the weapons and engines systems of any ship for a short period of time.

==="Spawn ''Name'',''Value''"===
*Will spawn the specified number of defined missiles upon detonation.
{{Table3610|
*Multiple spawn types can be defined for a single 'carrier' weapon up to maximum of 5 different weapons}}

==="Remote Detonate"===
*Can be triggered remotely via a second press on the trigger

==="Big Ship"===
*These weapons cannot be mounted on small ships like fighters, bombers, sentry guns etc.

==="Huge"===
*Allows this weapon to do the final 10% damage to a ship with the "Big Damage" flag. Also the AI will not try to hit fighters with it.

==="Supercap"===
*Allows this weapon to do the final 75% damage to a ship with the "supercap" flag.

==="Bomber+"===
*The AI will prefer to use this weapon against bombers

==="child"===
*Cannot be set as a weapon on any ship, but is instead a child of a weapon. Usually defined with "Spawn ''Name'',''Value''"

==="Bomb"===
*Makes this weapon targetable with the B key, and the AI prefers to use it against large ships

==="No Dumbfire"===
*Missile will not fire without a lock

==="in tech database"===
*Has the weapon in the tech database at the start of the campaign

==="Player allowed"===
*Allows this weapon as a player weapon.
{{Table3610|
*'''EXTREMELY IMPORTANT NOTE:'''
**Whenever you plan to use a weapon as a player one in your campaign or missions, '''USE THIS FLAG'''.
**Not using it can cause problems within fs_open and it's a BAD MOD DESIGN.
**In the future, fs_open will maybe be able to avoid these problems but, nevertheless, it's still a BAD DESIGN.
**As another possible example: be careful to update "retail" tables if you plan to use Shivan weapons in player fighters.}}

==="Particle Spew"===
*Makes the weapon projectile spew out particles
{{Table3610|
*Can be defined with [[Weapons.tbl#$Pspew:|Particle Spew parameters]]}}

==="EMP"===
*This weapon will have an EMP effect on any ship within the blast radius
*Can be defined with [[Weapons.tbl#$EMP_Intensity:|EMP Intensity]] and [[Weapons.tbl#$EMP_Time:|EMP Time]]

==="Esuck"===
*Drains the target's energy banks
*Can be defined with [[Weapons.tbl#$Leech_Weapon:|Leech Weapon]] and [[Weapons.tbl#$Leech_Afterburner:|Leech Afterburner]]

==="Flak"===
*Makes this weapon a [[weapons.tbl#Flak_Guns|flak gun]]

==="Corkscrew"===
*Makes this weapon spiral AND swarm 4.
{{Table3610|
*Can be defined with [[Weapons.tbl#$Corkscrew:|Corkscrew parameters]]}}

==="Shudder"===
*Makes your ship shudder while you're firing the weapon

==="lockarm"===
*Requires a target lock in order to arm its warhead. In other words weapon causes less damage if it hits the target without target lock.

==="beam"===
*Makes this weapon a [[weapons.tbl#Beam Cannons|beam cannon]]

==="stream"===
* Does nothing

==="puncture"===
*Reduces hull damage by 75%
The AI will prefer these weapons for anti-subsystem use

==="countermeasure"===
{{Table3610|
*Defines the weapon as a countermeasure}}

==="Ballistic"===
{{Table3610|
*Defines the weapon as a ballistic weapon that needs ammunition.
*Make sure you define the size and reload rate for ballistic weapons}}

==="pierce shields"===
{{Table3610|
*Causes weapons to penetrate shield without causing damage to it.}}

==="no pierce shields"===
{{Table3610|
*Prevents weapons (beams) from piercing shields causing shields to be damaged by weapons first.}}

==="local ssm"===
{{Table3610| }}

==="tagged only"===
{{Table3610|
*Weapon can only be fired at tagged targets}}

==="beam no whack"===
{{Table3610|
*Disables beam whacking (push). Practically same as setting beam mass to zero.}}

==="cycle"===
{{Table3610|
*Causes weapon to alternate between firing points}}

==="small only"===
{{Table3610|
*Causes AI to use the weapon only on small targets (fighters, bombers etc.)}}

==="same turret cooldown"===
{{Table3610|
*Forces the turrets to fire on the designated rate of fire on all difficulty levels and all AI levels}}

==="apply no light"===
{{Table3610|
*Prevents light from being applied to the weapon model.}}

==="training"===
{{Table3610|
*Sets weapon to be of training weapon type. ?}}

==="smart spawn"===
{{Table3611|
*Forces turret fired spawn weapon of this type to be fired like normal weapons.}}

==="inherit parent target"===
{{Table3611|
*Sets spawned 'child' weapons to use parent weapon's target.}}

==="no emp kill"===
{{Table3611|
*Defines the weapon (with hitpoints) to be immune to automatic EMP destruction.}}

==="untargeted heat seeker"===
{{Table3611|
*Defines the weapon as a heatseeker type missile which acquires its target by itself.}}

==="no radius doubling"===
{{Table3611|
*Prevents weapon radius from being doubled when doing collision test. Makes bombs harder to intercept.}}

==="no subsystem homing"===
{{Table3611|
*Prevents weapon from acquiring a subsystem as its target. Missile homing points are spread over the target ship.}}

==="no lifeleft penalty"===
{{Table3611|
*Prevents weapon lifetime from being penalized if the angle to the target is too big.}}

==="can be targeted"===
{{Table3611|
*Allows weapon to be targeted by player. Does not influence AI}}

==="show on radar"===
{{Table3611|
*Allows weapon to be visible on the radar}}

==="show friendly on radar"===
{{Table3611|
*Allows friendly, otherwise visible to radar weapon, to be visible on player radar}}

==="capital+"===
{{Table3613|
*Tells AI to use this weapon only on capital ships}}

==="chain external model fps"===
{{Table3613|
*Tells game to keep switching external model firingpoints when firing}}

==="external model launcher"===
{{Table3613|
*Tells game that the external model is a launcher so that it would be kept static without loading motion}}

==="takes blast damage"===
{{Table3613|
*Weapon takes damage from weapon blasts}}

==="takes shockwave damage"===
{{Table3613|
*Weapon takes damage from shockwaves}}

==Countermeasures==
*Usually not altered. Only one can exist
{{Table3610|
*More than one can exist}}

===$Name:===
*Name of the countermeasure
*Syntax: '''''String''''', name

===$Velocity:===
*Defines the speed of the countermeasure, relative to the ship.
*Syntax: '''''Float''''', meter per second

===$Fire Wait:===
*Definies the minumum time between the countermeasure launches
*Syntax: '''''Float''''', seconds

===Lifetime===
*Countermeasure's life time is defined between with minimum and maximum lifetime
*'''$Lifetime Min:'''
**Syntax: '''''Float''''', seconds
*'''$Lifetime Max:'''
**Syntax: '''''Float''''', seconds

===$LaunchSnd:===
*Defines the sound for the countermeasure launch
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Model:===
*Defines the used model file (.pof)
*Syntax: '''''String.pof''''', model filename

==Player Weapon Precedence==
*First the primary weapons are defined, from most powerful to least powerful, and then the same for secondaries
*Syntax: ( '''''"String" "String"'''''), names of the weapons
*Example:

<pre>
$Player Weapon Precedence: (
"UD-8 Kayser"
"Prometheus R"
"Subach HL-7"
"Harpoon"
"Tempest"
"Rockeye" )
</pre>

==Sample==

<pre>
#Primary Weapons

$Name: @Subach HL-7
+Title: XSTR("GTW Subach HL-7", 3243)
+Description:
XSTR( "Standard Issue
Level 3 Hull Damage
Level 2 Shield Damage", 3244)
$end_multi_text
+Tech Title: XSTR("Subach HL-7", 146)
+Tech Anim: Tech_Subach_HL-7
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: none
@Laser Bitmap: newglo9
@Laser Glow: 2_laserglow03
@Laser Color: 250, 0, 0
@Laser Color2: 0, 0, 250
@Laser Length: 10.0
@Laser Head Radius: 0.90
@Laser Tail Radius: 0.90
$Mass: 0.2
$Velocity: 450.0
$Fire Wait: 0.2
$Damage: 15
$Armor Factor: 0.9
$Shield Factor: 0.7
$Subsystem Factor: 0.3
$Lifetime: 2.0
$Energy Consumed: 0.20
$Cargo Size: 0.0
$Homing: NO
$LaunchSnd: 76
$ImpactSnd: 85
$Flags: ( "in tech database"
"player allowed"
"stream")
$Icon: iconSD4
$Anim: SD4
$Impact Explosion: none

#End

#Secondary Weapons

$Name: EMP Adv.
+Title: XSTR("GTM-14 EMP Adv.", 3396)
+Description:
XSTR( "Advanced Missile
Electromagnetic Pulse Weapon
General Purpose Suppression", 3397)
$end_multi_text
+Tech Title: XSTR("GTM-14 EM Pulse Adv.", 3398)
+Tech Anim: Tech_EMP
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: EMPulse2.pof
$Mass: 15.0
$Velocity: 275.0
$Fire Wait: 2.0
$Damage: 45
$Blast Force: 20.0
$Inner Radius: 80.0
$Outer Radius: 300.0
$Shockwave Speed: 120.0
$Armor Factor: 1.0
$Shield Factor: 0.8
$Subsystem Factor: 0.5
$Lifetime: 5.0
$Energy Consumed: 0.0
$Cargo Size: 4.0
$Homing: YES
+Type: ASPECT
+Turn Time: 1.0
+Min Lock Time: 2.0
+Lock Pixels/Sec: 70
+Catch-up Pixels/Sec: 100
+Catch-up Penalty: 30
$LaunchSnd: 118
$ImpactSnd: 88
$FlyBySnd: -1
$Rearm Rate: 2.0
$Flags: ( "player allowed"
"EMP")
$Trail:
+Start Width: 0.25
+End Width: 0.75
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.5
+Bitmap: MissileTrail04
$Icon: iconEMPulse
$Anim: ecm
$Impact Explosion: ExpMissileHit1
$Impact Explosion Radius: 10.0
$EMP Intensity: 375.0
$EMP Time: 20.0

#End

$Player Weapon Precedence: (
"Subach HL-7"
"EMP Adv." )
</pre>

[[Category:Tables]]

-mod

2010-10-31T04:42:06Z

IssMneur: Redirected page to Command-Line Reference#-mod

#redirect [[Command-Line_Reference#-mod]]

Collateral Damage

2010-10-27T16:07:46Z

IssMneur: /* Walkthrough */ Typo fix.

{{Mission|previous=The Cost of War|next=Post Meridian|campaign=Blue Planet: War in Heaven Campaign Walkthrough}}

'''MISSION 02''' 
'''ACT 1, MISSION 02'''

'''Fighter squadron:''' 170th Fighting Navajas

'''Description:''' Third Fleet's Exodus continues. Two ships are out of communication, and the Navajas are sent to investigate.

----
==Background==
After a twenty-minute break following [[The Cost of War|their last mission]], Alpha wing of the Navajas receives a situation report on the evacuation of Third Fleet and new orders from Captain Tefler.

Flight operations to cover Third Fleet's remaining assets are in full swing and have achieved limited success. While two additional cruisers have been recovered, the [[Galactic Terran-Vasudan Alliance|Alliance]] managed to destroy six haulers. Beta wing of the Navajas is in the midst of launching to cover evacuation operations at Jovian storm platforms.

Alpha wing is now deployed to one of a number of likely misjump sites to locate two missing frigates, the [[UEFg Karuna|''Karuna''-class]] ''Akula'' and the [[UEFg Narayana|''Narayana''-class]] ''Ranvir''. These two ships are part of a flotilla that crash-jumped from Europa orbit while under heavy fire. Their course was vectored by reconnaissance, but their eventual exit point is not known. Alpha wing's job is to sweep the area where they are most likely to end up in and find them before the Alliance does so.

Sensors have also detected a pack of Allied corvettes sweeping the area as well. The evacuation effort means that the ''Solaris'''s assets are severely limited for this sortie. Although the 12th Shuduhune are on standby to intercept Allied warship targets, they will not be deployed except under the most dire circumstances.

==Walkthrough==
You can only pilot the [[UEF Uhlan|UEF ''Uhlan'']] in this mission. As with the previous mission, the default loadout should suffice, but feel free to change your loadout as you see fit.

This mission begins with Brie yelling an order to turn hard left and hit afterburners as you jump right into the flak and AAA range of the ''Cho'', an [[GTC Aeolus|''Aeolus''-class cruiser]]. As you recover, you see the two missing frigates on your escort list and radar being besieged by three [[GTCv Deimos|''Deimos''-class corvette]]s. The ''Ranvir'' is able to hold off the ''Idomeneus'' on its own, but because of the corvette, it is unable to assist the less powerful ''Akula'', which is under attack from the ''Cardinal'' and ''Regensburg'' some ten klicks away because of considerable damage to her navigation systems. Brie attempts to call the ''Solaris'' for reinforcements, but he realises that there is massive jamming in place, preventing anyone from requesting outside help.

The ''Ranvir'' will chase the ''Idomeneus'' off eventually, and the ''Cho'' will follow suit not too long after. Almost immediately, Brie alerts you and Kassim about a wing of [[GTF Aurora|''Aurora''-class fighters]] setting up a subspace missile strike on the ''Ranvir''. The ''Ranvir'' acknowledges this transmission. As it bears down on the two corvettes attacking the ''Akula'', the subspace missiles—numerous Eos torpedoes—arrive from subspace. Intercept as many as you can. This will be followed soon after by a wing of four [[GTB Artemis D.H.|''Artemis D.H.'' bombers]]. Destroy them quickly, as they pack numerous Cyclops torpedoes that will whittle away at the ''Ranvir'''s hull if left unchecked.

With the added firepower of the ''Ranvir'', both the ''Cardinal'' and ''Regensburg'' are eventually forced to jump out. As the battlefield falls silent, the jamming clears, and the ''Ranvir'' and ''Akula'' finally make contact with Second Fleet HQ. HQ plots an exit path for both ships, as they are still capable of making a jump to subspace under their own power if given proper navigation coordinates and enough time to recharge their jump drives. The two frigates follow HQ's instructions, with the ''Akula'', well over eight klicks ahead of the ''Ranvir'', taking point.

The ''Argus'', a hostile [[GTA Charybdis|''Charybdis''-class AWACS]], will jump in about forty-five klicks away not too long after. Brie orders you and Kassim to ignore it and stay close to the ''Ranvir'', as the ''Argus'' is most likely vectoring in additional attack waves. All too soon, a wing of [[GTF Ares|''Ares''-class fighters]] jump in about four klicks away. Brie predicts an anti-fighter Trebuchet sweep. True enough, the fighter wing departs right after releasing one round of Trebuchet missiles. Keep the lock indicator as far left or right to the reticle as you can and pay attention to the lock alert. When it starts to drastically increase in frequency, release your countermeasures and hit your afterburners. Done correctly, you should be able to evade the Trebuchet missiles locked onto your ship without having to mash your Countermeasure key.

The ''Ranvir'' signals your wing after the Trebuchet threat has passed on. It is concerned that the ''Argus'' may vector in heavier forces, like a bomber wing or warship. Just then, the ''Akula'' detects another wing of ''Ares'' fighters attempting to gain targeting lock on her. Brie immediately orders you to intercept the fighters, but you are too far away. As you watch, you see numerous subspace wormholes forming all around the ''Akula''—more than you can count. From them emerge countless Eos torpedoes heading directly for the frigate. The torpedoes hit home as the fighter wing jumps out, and the ''Akula'' is completely and utterly destroyed. Your scan of the debris field returned no survivors.

No less than thirty seconds after this, Command alerts your wing and the ''Ranvir'' that their listening posts have detected a massive subspace transit into the immediate vicinity, and are scrambling reinforcements to assist. The ''Ranvir'' prepares to make another crash-jump.

And then, they arrive.

Three corvettes—two [[GTCv Chimera|''Chimera''-classes]], designated ''Hydra'' and ''Pilum'' and a [[GTCv Bellerophon|''Bellerophon''-class]], designated ''Marcus Glaive''—emerge a few klicks away and well within beam range. The ''Ranvir'' loses her composure for a moment before she sends out the following transmission:

<center>'''''"It's Serkr Team, Steele's war dogs, the ones who took ''Artemis''. Alpha, clear our blast zone. You've done all you can."'''''</center>

The ''Ranvir'' barely manages to send out this message before the three corvettes charge their frontal beam cannons—nine in all. As one, and with a sound that could almost make your ears bleed, they annihilate the ''Ranvir'' with their combined firepower.

Two wings from the 12th Shuduhune arrive on the battlefield just as the frigate disintegrates into a debris field. ''Shuduhune Alpha 1'' identifies herself as Captain Lila Zhiyan and immediately commences a heavy strike attack with her wingmen. Brie gives her a status update before asking her about the rest of her strike force. Her reply: there are none. She and her three wings are given the near-suicidal task of delaying the corvette trio to prevent them from attacking other fleet assets. They are not expected to survive.

Brie gives new orders. You now have to protect Shuduhune Alpha, comprising of two [[UEB Durga|''Durga'' bombers]], Shuduhune Beta, consisting of four [[UEF Uriel|''Uriel'' gunships]], and Shuduhune Gamma, a wing of two ''Uriel'' gunships, from enemy fighters. As the heavy fighters and bombers charge towards the corvette, three [[GTF Myrmidon|''Myrmidon''-class fighters]] show up, designated Cetus wing. Intercept them before they rip through the Shuduhune wings.

As the strike force nears the corvettes, Captain Zhiyan orders Brie, Kassim and you to disengage and withdraw to beyond the striking range of Serkr Team. The three of you can only watch as the three wings fly straight into a maelstrom of anti-fighter artillery. The corvette trio departs not too long afterwards.

As Serkr Team leaves, you realise that this mission is over. Brie was hopeful that the Shuduhune managed to slow the corvettes long enough for another frigate to make it to safety. Kassim is furious that the three of you were the only ships that stood between the ''Akula'' and ''Ranvir'' and countless tons of explosive warheads. Brie, however, acknowledges that the two frigates were already lost even before your intervention; the Alliance's plan of attack was far too great for three fighters to stop it.

Brie gives orders to return to base. Jump out.

==Notes==
* The ''Ranvir'' uses the Hydra Torpedo in this mission. This was originally necessary because the Apocalypse (the standard capital ship missile of the UEF) didn't have the turn radius to reliably engage the corvette. In-universe, the Hydra is a swarm weapon that is designed to penetrate thick point defenses by saturating the enemy with missiles, but at the cost of lower overall damage output. The intent here is to show that the ''Ranvir'' has run out of Apocalypse missiles, and has to resort to secondary loadouts.
* The ''Cardinal'' and ''Regensburg'' not only sport new pulse weaponry in addition to the normal loadout of a GTCv ''Deimos'', but are also assigned the dreaded ''BALLS OF STEELE'' AI class, the most competent AI class ever made for War in Heaven that can do everything a normal human pilot is capable of and more.
* This is also the first mission in War in Heaven where the ''BALLS OF STEELE'' AI class is used.
* The ''Hydra'' and ''Pilum'' are normal ''Chimera''-class corvettes with more powerful weaponry, befitting Captain Tefler's description of Serkr Team.
* Strangely enough, the GTCv ''Hydra'' did not make an appearance in [[Artemis Station]] despite being part of Serkr Team.

==Total number of forces==
{{total_numbers_2
|belligerent_1 =[[United Earth Federation|UEF]]
|belligerent_2 =[[Galactic Terran-Vasudan Alliance|GTVA]]
|ship_1 =
* 1 [[UEFg Narayana|UEFg ''Narayana'']]
** ''Ranvir''

* 1 [[UEFg Karuna|UEFg ''Karuna'']]
** ''Akula''
|ship_2 =
* '''Serkr Team'''
** 1 [[GTCv Bellerophon|GTCv ''Bellerophon'']]
*** ''Marcus Glaive''
** 2 [[GTCv Chimera|GTCv ''Chimera'']]
*** ''Hydra''
*** ''Pilum''

* 3 [[GTCv Deimos|GTCv ''Deimos'']]
** ''Cardinal''
** ''Idomeneus''
** ''Regensburg''

* 1 [[GTC Aeolus|GTC ''Aeolus'']]
** ''Cho''

* 1 [[GTA Charybdis|GTA ''Charybdis'']]
** ''Argus''
|strikecraft_1 =
* 7 [[UEF Uhlan|UEF ''Uhlan'']]
** ''Alpha 1''
*** Brie
** ''Alpha 2''
*** Kassim
** ''Alpha 3''
*** Laporte
** ''Upsilon'' (4)

* 6 [[UEF Uriel|UEF ''Uriel'']]
** ''Shuduhune Beta'' (4)
** ''Shuduhune Gamma'' (2)

* 2 [[UEB Durga|UEB ''Durga'']]
** ''Shuduhune Alpha'' (2)
|strikecraft_2 =
* 2 [[GTF Aurora|GTF ''Aurora'']]
** ''Auriga 4''
** ''Eridan 6''

* 3 [[GTF Myrmidon|GTF ''Myrmidon'']]
** ''Cetus'' (3)

* 3 [[GTF Hercules Mark II|GTF ''Hercules Mark II'']]
** ''Auriga'' (3)

* 10 [[GTF Ares|GTF ''Ares'']]
** ''Corvus'' (5)
** ''Eridan'' (5)
|casualties_1 =
* 1 [[UEFg Narayana|UEFg ''Narayana'']]
** ''Ranvir''

* 1 [[UEFg Karuna|UEFg ''Karuna'']]
** ''Akula''

* 0-4 [[UEF Uhlan|UEF ''Uhlan'']]
** ''Upsilon'' (4)

* 0-6 [[UEF Uriel|UEF ''Uriel'']]
** ''Shuduhune Beta'' (4)
** ''Shuduhune Gamma'' (2)

* 0-2 [[UEB Durga|UEB ''Durga'']]
** ''Shuduhune Alpha'' (2)
|casualties_2 =
* 0-1 [[GTF Aurora|GTF ''Aurora'']]
** ''Auriga 4''

* 0-3 [[GTF Myrmidon|GTF ''Myrmidon'']]
** ''Cetus'' (3)

* 0-3 [[GTF Hercules Mark II|GTF ''Hercules Mark II'']]
** ''Auriga'' (3)
}}

[[Category:Blue Planet]]

Fs2 open on Linux/Installing the Development Libraries

2010-10-02T22:43:25Z

IssMneur: Fix package list for ubuntu

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Installing the Development Libraries|Installing the Development Libraries|
PrevPage=[[Fs2_open on Linux/Installing Subversion|Installing Subversion]]|
NextPage=[[Fs2_open on Linux/Acquiring_the_Code|Acquiring_the_Code]]}}

{{Note| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}

{{Note|: Redhat, Slackware, Archlinux, SuSE, and all the other distributions should have their instructions on installing the needed libraries added here, if your distribution is not listed below and you are familiar with how to install the needed libraries on it, please add it to this section. }}

You will also need [http://www.libsdl.org/ SDL], [http://www.openal.org/ OpenAL], [http://vorbis.com/ libvorbis], [http://www.theora.org/ libtheora], readline, [http://www.lua.org liblua >= 5.1.3], and OpenGL(most likely provided with your video card driver) development packages. And of course the [http://gcc.gnu.org/ GNU Compiler Collection] and required [http://sourceware.org/autobook/ make] tools.
 
'''Ubuntu''' users want to:
{{Note| The [http://packages.debian.org/unstable/devel/build-essential build-essential] package is a meta package that install the essential build tools. Follow the link for information.}}
$ apt-get install libopenal-dev libvorbis-dev build-essential automake1.10 autoconf libsdl1.2-dev libtheora-dev libreadline6-dev libpng12-dev liblua5.1-0-dev

'''Debian''' users want to:
{{Note| The [http://packages.debian.org/unstable/devel/build-essential build-essential] package is a meta package that install the essential build tools. Follow the link for information.}}
$ apt-get install libopenal-dev libvorbis-dev build-essential automake1.10 autoconf libsdl1.2-dev libtheora-dev libreadline6-dev libpng12-dev liblua5.1-0-dev

'''Fedora Core''' users (and most likely Redhat users too) want to:
$ yum install openal-devel libvorbis-devel gcc gcc-c++ automake autoconf SDL-devel libtheora-devel readline-devel

'''Gentoo''' users want to:
{{Note| media-libs/openal needs the "alsa" USE-flag if you intend to use ALSA, and media-libs/libsdl needs the "X","opengl" and "xv" USE-flags.}}

$ emerge -va openal libvorbis libsdl libtheora readline

'''Mandriva''' users want to:
$ urpmi libsdl-devel libopenal-devel libvorbis-devel libtheora-devel gcc gcc-c++ automake autoconf

[[Category:FreeSpace Open on Linux|Installing the Development Libraries]]

Fs2 open on Linux/Quickstart

2010-08-09T06:24:31Z

IssMneur: Added note about non 32 bit rendering

Hi, [[User:Galemp|Galemp]] here. If, like me, you're new to Linux and have no idea how to compile code, I have a quick startup guide here. You should at least be familiar with basic file management like moving and renaming files. I also assume that you have an administrator account. Make sure your video card drivers are working properly; other sources can assist you with this.

This guide was written using Ubuntu Linux 9.04. Note that EVERYTHING in Linux is case sensitive, so if your folder is named <code>Games</code> and you enter <code>games</code> it won't work. Also pay close attention to SPACES and DOTS. <code>.fs2_open</code> is not the same as <code>fs2_open</code> or <code>fs2 open</code>!

'''Part 1. Getting the game running.'''
This assumes that you have access to a Windows installation of retail or GOG FS2, or otherwise have access to the original VPs. I copied mine from a mounted secondary hard drive that I boot Windows from.

# '''Copy the game data.''' If you're a Freespace modder, you install mods, or just like downloading new missions, it makes sense to put it in your Home folder. Create a new folder in your home directory, called <code>Games</code>, and a new folder in that called <code>freespace2</code>, and copy all .VP files in your original install folder there. If you have any mods installed, such as MediaVPs or FSPort, move those folders as well.
# '''Initial configuration.''' We're going to create a file that sets essential options for starting up Freespace. Browse to your home folder and press CTRL-H to unhide system files. Create a new folder called <code>.fs2_open</code> and inside that, create a plaintext file called <code>fs2_open.ini</code>. On the first line, put <code>[Default]</code> and on the second line put <code>VideocardFs2open=OGL -(1024x768)x32 bit</code>. You can change the first two parameters to your native screen resolution. Save and close it. [[Note|Do not change from <code>32 bit</code> unless told otherwise by a Support Ninja.]]
# '''Download the Linux binaries.''' This is the actual game executable. The latest stable version as of this writing (8 August 2010) is [http://swc.fs2downloads.com/builds/LINUX/fs2_open_3_6_12_INF.tar.bz2 3.6.12]. If you'd like a newer build, or a specific one (such as a Wanderer, XT branch, or Inferno build) please see the [http://www.hard-light.net/forums/index.php/board,173.0.html Nightly Builds forum] and pick the most recent Linux build. Unpack the executables to the same folder where you put the Freespace VPs.
# '''Run a test.''' Now let's see if Freespace will run. In your game directory, run the binary you've just downloaded. If you've done everything correctly, you should have Freespace 2 up and running on Linux! Congratulations! From here you should be able to experience the game just as it was when it was released, and play online using [[Multiplayer Getting Started Guide|FS2Net]].

'''Part 2. Getting mods to work.'''
If you want to run mods, things get trickier. First, there are currently some issues with current builds not supporting mods; second, you'll want to install a launcher to switch between them. The Linux launcher, YAL, is non-portable, so we'll have to configure SVN (a tool for updating code databases) to download the latest code, configure it to work on your system, compile the code into a working executable, then move that to your Freespace directory. This is the most frustrating part of the whole process, but bear with me and we'll get through it. The Source Code Project team is working on an installer/launcher overhaul, so go bug them in the meantime.

# '''Install the fixed binary.''' For now, download and unpack [[http://www.joskus.jossain.com/fso_5395.zip this build]] into your Freespace directory. Or, try a build of your choosing.
# '''Install dependencies.''' Compiling the launcher requires a few external libraries to get going. We're going to install them as a super user (sudo) by using the get application command (apt-get.) Open Terminal under Applications > Accessories and enter this command: <code>sudo apt-get install build-essential automake1.9 autoconf libreadline5-dev subversion</code> You will need to enter your password when prompted.
# '''Download the launcher code.''' From Terminal, enter <code>cd $HOME</code> to navigate to your home folder, and enter <code>mkdir yal</code> to create a new folder named yal. This is where we'll put the code. Enter <code>cd yal</code> to navigate to that directory, then enter <code>svn checkout svn://vega.livecd.pl/yal/trunk</code> to download the latest launcher code.
# '''Compile the launcher code.''' Enter <code>./autogen.sh</code> then <code>make</code> and in a moment it should compile a new binary. Move this to your Freespace directory by entering <code>mv fs2_launcher $HOME/Games/freespace2</code>.
# '''Test the launcher.''' Now you can try running the FS2 Launcher app in your Freespace 2 directory, choosing the fixed binary above and the mod of your choice. In all respects this should work like the Windows launcher, except that only a few tabs will be working.

Well, that worked for me. The_E and I are working on a script to automate some of this, so stay tuned.

[[Category:FreeSpace Open on Linux]]

Fs2 open on Linux/Quickstart

2010-08-09T06:19:47Z

IssMneur: New binary release

Hi, [[User:Galemp|Galemp]] here. If, like me, you're new to Linux and have no idea how to compile code, I have a quick startup guide here. You should at least be familiar with basic file management like moving and renaming files. I also assume that you have an administrator account. Make sure your video card drivers are working properly; other sources can assist you with this.

This guide was written using Ubuntu Linux 9.04. Note that EVERYTHING in Linux is case sensitive, so if your folder is named <code>Games</code> and you enter <code>games</code> it won't work. Also pay close attention to SPACES and DOTS. <code>.fs2_open</code> is not the same as <code>fs2_open</code> or <code>fs2 open</code>!

'''Part 1. Getting the game running.'''
This assumes that you have access to a Windows installation of retail or GOG FS2, or otherwise have access to the original VPs. I copied mine from a mounted secondary hard drive that I boot Windows from.

# '''Copy the game data.''' If you're a Freespace modder, you install mods, or just like downloading new missions, it makes sense to put it in your Home folder. Create a new folder in your home directory, called <code>Games</code>, and a new folder in that called <code>freespace2</code>, and copy all .VP files in your original install folder there. If you have any mods installed, such as MediaVPs or FSPort, move those folders as well.
# '''Initial configuration.''' We're going to create a file that sets essential options for starting up Freespace. Browse to your home folder and press CTRL-H to unhide system files. Create a new folder called <code>.fs2_open</code> and inside that, create a plaintext file called <code>fs2_open.ini</code>. On the first line, put <code>[Default]</code> and on the second line put <code>VideocardFs2open=OGL -(1024x768)x32 bit</code>. You can change these parameters to your native screen resolution. Save and close it.
# '''Download the Linux binaries.''' This is the actual game executable. The latest stable version as of this writing (8 August 2010) is [http://swc.fs2downloads.com/builds/LINUX/fs2_open_3_6_12_INF.tar.bz2 3.6.12]. If you'd like a newer build, or a specific one (such as a Wanderer, XT branch, or Inferno build) please see the [http://www.hard-light.net/forums/index.php/board,173.0.html Nightly Builds forum] and pick the most recent Linux build. Unpack the executables to the same folder where you put the Freespace VPs.
# '''Run a test.''' Now let's see if Freespace will run. In your game directory, run the binary you've just downloaded. If you've done everything correctly, you should have Freespace 2 up and running on Linux! Congratulations! From here you should be able to experience the game just as it was when it was released, and play online using [[Multiplayer Getting Started Guide|FS2Net]].

'''Part 2. Getting mods to work.'''
If you want to run mods, things get trickier. First, there are currently some issues with current builds not supporting mods; second, you'll want to install a launcher to switch between them. The Linux launcher, YAL, is non-portable, so we'll have to configure SVN (a tool for updating code databases) to download the latest code, configure it to work on your system, compile the code into a working executable, then move that to your Freespace directory. This is the most frustrating part of the whole process, but bear with me and we'll get through it. The Source Code Project team is working on an installer/launcher overhaul, so go bug them in the meantime.

# '''Install the fixed binary.''' For now, download and unpack [[http://www.joskus.jossain.com/fso_5395.zip this build]] into your Freespace directory. Or, try a build of your choosing.
# '''Install dependencies.''' Compiling the launcher requires a few external libraries to get going. We're going to install them as a super user (sudo) by using the get application command (apt-get.) Open Terminal under Applications > Accessories and enter this command: <code>sudo apt-get install build-essential automake1.9 autoconf libreadline5-dev subversion</code> You will need to enter your password when prompted.
# '''Download the launcher code.''' From Terminal, enter <code>cd $HOME</code> to navigate to your home folder, and enter <code>mkdir yal</code> to create a new folder named yal. This is where we'll put the code. Enter <code>cd yal</code> to navigate to that directory, then enter <code>svn checkout svn://vega.livecd.pl/yal/trunk</code> to download the latest launcher code.
# '''Compile the launcher code.''' Enter <code>./autogen.sh</code> then <code>make</code> and in a moment it should compile a new binary. Move this to your Freespace directory by entering <code>mv fs2_launcher $HOME/Games/freespace2</code>.
# '''Test the launcher.''' Now you can try running the FS2 Launcher app in your Freespace 2 directory, choosing the fixed binary above and the mod of your choice. In all respects this should work like the Windows launcher, except that only a few tabs will be working.

Well, that worked for me. The_E and I are working on a script to automate some of this, so stay tuned.

[[Category:FreeSpace Open on Linux]]

Command-Line Reference

2010-07-19T20:11:36Z

IssMneur: /* -mod */ updated information regarding FRED and fixed some typos

The following command-line options can be chosen from the launcher.

===Graphics===
====-spec====
Enables specular mapping. Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).

====-env====
Enables environment mapping. It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). At the time of this writing (build 3.6.9 RC7), environment mapping only works when the video mode is OpenGL. [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]

====-glow====
Enables glowmapping. Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)

====-jpgtga====
{{Note | This option is not present in builds after 3.6.9 and is now always on.}}
Enables the use of TGA and JPG file formats for image files. If a ship is showing up partially invisible, select this option.

====-pcx32====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}

{{Warning|This will not improve the rendering of any ships in-game, and is usually more of a burden on performance than is worthwhile. Use at your own risk.}}
Enables PCX files to be loaded into 32-bit memory.

====-mipmap====
Enables mipmapping generation within GPU on certain kind of texture formats, (IIRC, DDS formatted textures with a power of 2 size in both width and height). 
Since the use of already mipmapped DDS textures has become common, it has become depreciated.
The quality of the generated mipmaps depends on each GPU and used driver. It is normally used with [[Command-Line_Reference#-img2dds|-img2dds]] flag.

====-nomotiondebris====
Disables motion debris.

====-2d_poof====
{{Note| This option is not present in builds post version 3.6.9.}}
Applies nebula poofs in 2d, effectively preventing them from forming intersections with ships.

====-noscalevid====
Disables fullscreen scaling of video clips.

====-missile_lighting====
Applies lighting to missiles.

====-normal====
Enables normal maps. It needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed.

====-3dshockwave====
Enables 3D Shockwaves. This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-rlm====
{{Note| This option is not present in builds after [http://tinyurl.com/2yndle 2005/09/30] and is now always on.}}
Enables more accurate lighting model for OpenGL mode.

----

===Game Speed===
====-img2dds====
Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
Disables vertical sync.

====-cache_bitmaps====
Caches bitmaps between missions, which will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
Adds a second pair of scanning lines to the target window when scanning an object.
====-targetinfo====
Displays target info, such as name and class, beside the targeted object.
====-orbradar====
Enables 3D radar (the Orb). 3D radar will replace the standard 2D version.
====-ballistic_gauge====
Adds an ammo gauge to the HUD when armed with a ballistic weapon.
====-rearm_timer====
Displays time remaining until rearm and repair from a support ship is complete.

===Gameplay===
====-smart_shields====
{{Note| This option has been moved to [[Ai_profiles.tbl]] table since 3.6.9. builds. It doesn't exist as a flag anymore.}}
Enables "smart" shield recharging. Shield recharge is distributed to the most damaged shield quadrant instead of being distributed equally across the entire shield and be wasted when a quadrant is full.
====-ship_choice_3d====
Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.
====-weapon_choice_3d====
Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.
====-3dwarp====
Use full geometry for the subspace warp effect.
====-warp_flash====
Enable a flash at warp in and warp out.
====-no_ap_interrupt====
Tells the game to not allow players to interrupt an autopilot already-in-progress.
====-tbp====
Enable feature set for The Babylon Project. This option also forces the Enable 3d Shockwave and Use 3d Models for Weapon Selection options as of 3.6.10 testing builds r4983 or higher.
====-wcsaga====
Enable feature set for The Wing Commander Saga. 
It does the following changes to the normal FS2 engine behavior:
* It removes -class name in the briefing ship render window, (the window that appears when ship icons are clicked).
* It removes enemy names ingame for wings of ships.
* Enemies can scream when dying. (Without the flag only friendlies scream).

===Audio===
====-snd_preload====
Preload mission sounds. Useful in preventing game stuttering when sounds are played for the first time.
====-nosound====
Disables all sounds.
====-nomusic====
Disables music only.

===Multiplayer===
====-standalone====
Creates a standalone server.
====-startgame====
Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder—or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
Disables return to the flight deck screen after a mission completes.

===Troubleshooting===
====-fixbugs====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-nocrash====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-oldfire====
This feature is not available in current builds.

====-nohtl====
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
Disables the gamma settings in the options screen.
====-nomovies====
Disables all video playback.
====-noparseerrors====
Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.
====-safeloading====
Loads missions the old way. Typically safer, but slower.
====-query_speech====
Determines if the current build includes text-to-speech.
====-d3d_bad_tsys====
Enable inefficient texture system.
====-novbo====
Disables OpenGL VBO.
====-noibx====
Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.
====-loadallweps====
Load all weapons, even those not used.
====-no_glsl====
Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

===Experimental===
====-ingame_join====
Enables ingame joining in multiplayer. FIXME: Host option?
====-voicer====
Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

====-alpha_env====
{{Note| This option is not present in builds post version 3.6.9. In current builds this effect is always on}}
Enables alpha environment mapping. OpenGL only. Environment mapping intensity will be determined from the alpha channel of specular maps.
====-decals====
Enables damage decals. 
(Decals have been disabled in builds after May 4, 2006)
====-tga16====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/yr8tub 2006/04/05]).}}
Originally used to converts TGA images to 16-bits in order to reduce memory footprint (at the expense of image quality), superseded by [[Command-Line_Reference#-closed|-img2dds]].
----

===Development Tools===
====-fps====
Displays current frames per second.
====-pos====
Displays current position coordinates of camera.
====-window====
Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.
====-timerbar====
Displays a timing bar across the top of the screen. Timebar format varies by build.
====-stats====
Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
Shows coordinates of the mouse cursor.
====-show_mem_usage====
Shows detailed RAM usage in HUD.

The meaning of the info displayed in the upper right corner is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod. 
Details for each object are output to a pofspew.txt file created in the data folder. 
Otherwise, ibx files are created in game before each mission.

====-tablecrcs====
{{Sectstub}}

====-missioncrcs====
{{Sectstub}}

====-dis_collisions====
Disables all collisions.
====-dis_weapons====
Disables weapons rendering.
====-output_sexps====
Outputs SEXPs to sexps.html.
====-output_scripting====
Outputs scripting to scripting.html.
====-nograb====
Unix only. Disables focus grabbing in a window.
==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

===Lighting===
These factors can dramatically alter the atmosphere of the game. [[Sample Lighting Settings|This page]] has some sample lighting settings with screenshots.

====-ambient_factor====
This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra-realistic dark looking.

====-spec_exp====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16. However, 11 is recommended. This is a relative value.

====-spec_point====
This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0. However, 0.6 is recommended. This is a relative value.

====-spec_static====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, is 0.8 recommended. This is a relative value.

====-spec_tube====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, 0.4 is recommended. This is a relative value.

====-ogl_spec====
'''''OpenGL Only'''''. Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focued and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

===Graphics===

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-res====
Allows you to specify a resolution if the desired one cannot be set in the Launcher.
For example, -res 1920x1080 would run the game in 1920 x 1080 resolution. Since it requires an argument, it needs to be entered as a custom flag when using the Launcher. The "Run at specified resolution" option the Launcher gives is essentially this, but without being able to actually specify a resolution, it doesn't work.

===Gameplay===
====-mod====
{{Note| Please note that the ''[[mod.ini]]'' file is a feature exclusive to the Windows Launcher.}}
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behavior, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and [[mod.ini]] file.

Within the Launcher's MOD tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''.
If ''Freespace2/moddir/[[mod.ini]]'' exists it will be used to modify the -mod flag, too.

For further details, see '''[[mod.ini]]'''

'''Data precedence'''

As already said, within the different directories, the data precedence is set by the specified order in the -mod flag. The lowest priority goes to the Freespace2 installation directory.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are "similar" to zip archives. They just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order, so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter that this ''Mission.fs2'' is also inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhanced ones adding them in a higher priority place.

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

{{Warning| '''Priority and Texture Formats'''

''Obsolete behavior - Until FS2_open v3.6.9.:''

FS2_Open can use several file formats in textures: [http://en.wikipedia.org/wiki/PCX PCX], [http://en.wikipedia.org/wiki/DirectDraw_Surface DDS], [http://en.wikipedia.org/wiki/JPG JPG] and [http://en.wikipedia.org/wiki/TGA TGA]. Make sure you keep the format when you update your texture. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

The reason to do this is that, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. This behavior can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one.

''New behavior - From FS2_open v3.6.10. (including previous beta testing releases):''

The former issue has been fixed. Now texture format priority is only applied within the same location. In this ''strange'' situation it goes DDS -> TGA -> JPG -> PCX. Examples:
* ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.dds'' is loaded instead of ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.tga''.
* But your improved ''/Freespace2/data/maps/MyTexture.xxx'' will override them both despite of its format.
In this way, when you update any texture, you don't have to pay attention to its original format. Just place it in a higher priority place.

Nevertheless, global priority is kept between animated and static textures. Because of their management, animated textures (ANIs and EFFs) are looked for BEFORE static ones. In this way there's no way to update an animated texture with a static one (an obsolete ANI is always going to be loaded before the newer DDS version). The solution: use an updated EFF with just one frame.

}}

====-fov====
Specifies the Field of View for the player eyepoint.

Takes one argument decimal specifying the angle of the viewing cone in radians, from 0 to 2*pi

You can set the cone of view making things look bigger/smaller. The problem with this is that if you choose a small FOV, you will have a squashed look on the edges of your screen - stretched edges with a too high FOV. It is recommended to change the FOV as FS2 normally has some perspective distortion at the screen edges (FOV too high). Set the FOV to something like 0.39 - it will fix the distortion problem, and (as a nice side-effect) will make everything look bigger and more realistic scale-wise. On the other hand, it also stretches the backgrounds - this is usually not a big issue, but it does get annoying if using a skybox.
The default is 0.75, if you go higher, you'll get the fish-eye effect. Feel free to experiment. This must be entered into the "Custom flags" field

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a standalone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a standalone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a standalone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}

====-timeout====
{{Sectstub}}

====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low, then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

[[Category:Lists]]
[[Category:Source Code Project]]

Battle of Deneb (2335)

2010-07-14T04:06:08Z

IssMneur:

:''This article is about the first battle of Deneb. For other uses, see [[Battle of Deneb]].''

{| border=0 align=right
|

{|border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#3C1E1E; font-size: 150%" |
'''First Battle of Deneb'''

|- align="left"
| style="width:160px" |
* Date
* Location
* Result
| style="width:160px" |
* 2/20/2335
* Deneb system
* Shivan victory
|- align="center"

|- align="center"
| colspan=2 style="background:#202020"| '''Belligerents'''
|- align="left"
| style="width:160px" |[[GTA]] / [[PVN]]
| style="width:160px" |[[Shivans]]
|- align="center"

|- align="center"
| colspan=2 style="background:#202020"| '''Commanders'''
|- align="left"
| style="width:160px" |
*Admiral Shima
*Admiral Wolf
| style="width:160px" |Unknown
|- align="center"

|- align="center"
| colspan=2 style="background:#202020"| '''Strength'''
|- align="left"
| style="width:160px" |
* [[GTD Galatea|GTD ''Galatea'']]
* [[GTD Bastion|GTD ''Bastion'']]
* [[GTD Legion|GTD ''Legion'']]
* 4+ [[GTC Fenris|GTC ''Fenris'']]
* 1+ [[GTSC Faustus|GTSC ''Faustus'']]
* 2+ [[PVD Typhon|PVD ''Typhon'']]
* 2+ [[PVC Aten|PVC ''Aten'']]

| style="width:160px" |
* [[SD Lucifer|SD ''Lucifer'']]
* [[SD Eva|SD ''Eva'']]
* SC ''Raja''
* 6+ [[SC Cain|SC ''Cain'']] / [[SC Lilith|SC ''Lilith'']]
|- align="center"

|- align="center"
| colspan=2 style="background:#202020"| '''Casualties'''
|- align="left"
| style="width:160px" |
* [[GTD Galatea|GTD ''Galatea'']]
* [[GTD Legion|GTD ''Legion'']]
* Multiple small ships
| style="width:160px" |
* SD ''Eva''
* SC ''Raja''
* Miscellaneous small ships
|- align="center"
|}

|}

During the first [[Great War]], a [[Shivan]] fleet centered around the [[SD Lucifer|SD ''Lucifer'']] and the destroyer [[SD Eva|SD ''Eva'']] made use of an unknown jump node to bypass the GTA blockade in [[Antares]] and reach [[Deneb]]. After [[Alpha 1]] made [[Playing Judas|a reconnaissance]] of the Shivan arrival in Deneb, the Shivan battle group and a [[Terran]]/[[Vasudan]] fleet, including the [[GTD Galatea|GTD ''Galatea'']] and [[GTD Legion|GTD ''Legion'']], engaged in battle. The FS2 intro cutscene and two FS1 missions, [[Evangelist]] and [[Doomsday]], show the the Battle of Deneb (2335) from different perspectives.

The FS1 failure debrief for Evangelist claims that there are only two Shivan destroyers in the system, the ''Eva'' and the ''Lucifer'', but the player destroys the ''Eva'' if he successfully completes Evangelist. However, the FS2 cutscene clearly shows a Shivan [[SD Demon|''Demon'']]-class destroyer present after the ''Galatea'' has been destroyed. As the ''Eva'' is implied to be the only Shivan ''Demon''-class destroyer in the system, this is an inconsistency unless we assume that either the ''Eva'' was not destroyed or another Shivan destroyer arrived in-system ''during'' the battle. Also, the FS2 intro cutscene shows many cruisers and destroyers present during the Battle of Deneb probably after the destruction of the ''Galatea'', and the destruction of another Terran [[GTD Orion|''Orion'']]-class destroyer. As [[Volition]] has allegedly stated that the ''Orion'' in the FS2 intro was not ''Galatea'', the community has labeled this unknown destroyer the GTD ''Legion''.

For more information on the introduction cutscene's inconsistencies, see the [[FreeSpace Trivia#Cutscene quirks|FreeSpace Trivia]] page.

[[Category:History|Deneb, Battle of, 2335]]

Autopilot.tbl

2010-07-13T21:09:49Z

IssMneur:

{{SCP_table}}

{{TableVersion|5211|5264}}

'''Autopilot.tbl''' is used to define the autopilot behavior for a mod. This table is not found in the retail game.

==General Structure==
*Table consists of autopilot section
*Starts with '''<nowiki>#</nowiki>Autopilot'''
*Ends with '''<nowiki>#</nowiki>END'''

==Table Contents==
{{Table3610|
*Table works only with new builds}}

===$Link Distance:===
{{Table3610|
*Defines the maximum distance for autopilot link
*Syntax: '''''Integer'''''}}

===$Interrupt autopilot if enemy within distance:===
{{Table3612|
*Defines the minimum distance that an enemy has to be from the player at autopilot start and the minimum distance that enemies have to be from the autopilot flight leader in meters. '''Default is 5000 meters'''.
*Syntax: '''''Integer'''''}}

===$Interrupt autopilot if asteroid within distance:===
{{Table3612|
*Defines the minimum distance that an asteroid has to be from the player for the autopilot to engage and is the minimum distance that an asteroid has to be from the autopilot flight leader in meters. '''Default is 1000 meters'''.
*Syntax: '''''Integer'''''}}

===$Lock weapons during autopilot:===
{{Table3612|
*Disables all weapons of all ships involved in the cinematic autopilot sequence. '''Default is NO'''.
*Syntax: '''''Boolean'''''}}

===+No_Cutscene_Bars===
{{Table3610|
*Turns the cutscene bars off for the autopilot duration}}

===+No_Autopilot_Interrupt===
{{Table3610|
*Forces autopilot to ignore interrupts}}

===Events===
{{Table3610|
*Table allows for setting both message and sound file for certain events
*Allowed events:
::'''$No Nav Selected:'''
::*Triggered if no navpoint has been selected when autopilot is activated.
::'''$Gliding:'''
::*Triggered if autopilot is activated while in glide mode.
::'''$Too Close:'''
::*Triggered if selected navpoint is too close when autopilot is activated.
::'''$Hostiles:'''
::*Triggered if hostiles are within 5000 meters when autopilot is activated.
{{Table3612|
::*Triggered when the player is within '''$Interrupt autopilot if enemy within distance:''' meters of an enemy.}}
::'''$Linked:'''
::*Triggered when the player links his autopilot to another ship by flying within '''$Link Distance:'''. See NAV_NEEDS_LINK.
::'''$Hazard:'''
::*Triggered if the autopilot is activated when too close to a hazard (namely an asteroid)
{{Table3612|
::*Triggered when the player is within '''$Interrupt autopilot if enemy within distance:''' meters of an asteroid.}}
{{Table3612|
::'''$Support Present:'''
::*Triggered when any friendly support ship within range but engine is unable to dismiss the support ship for an unknown reason.
::'''$Support Working:'''
::*Triggered when any friendly support ship within range has an outstanding repair/rearm order.
}}
*For each defined event both message and sound file has to be set
*'''+Msg:'''
**Defines the message displayed on screen
**Syntax: '''''String'''''
*'''+Snd File:'''
**Defines the sound played
**Syntax: '''''String''''', has to include file extension}}

==Example==

<pre>
#Autopilot

$Link Distance: 100

$No Nav Selected:
+Msg: none
+Snd File: none.wav

#END
</pre>

[[Category:Tables]]

Engine limitations

2010-06-25T15:57:06Z

IssMneur: Added some sub-weapon type limits

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, developed to boost engine limits. Starting with FS2_Open 3.6.10 these builds can be used in Multiplayer, older builds are not capable of joining the servers due to several incompatibilities. In addition, Inferno and regular builds are incompatible to each other in Multiplayer; someone using an Inferno build will not be able to play with someone using a regular build and vice versa. Those builds are named after the [[Inferno]] mod, but are extensively used by many other projects, like [[The Babylon Project|TBP]].
Inferno builds will become the standard, starting at FS2_Open revision 3.7, with 3.6.12 being the last version to be distributed both in normal and Inferno variants.

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| 300
|- align="center"
| Beam Shots
| colspan=2| 5
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=2| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=2|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=2| 5
|- align="center"
| [[Cutscenes.tbl|Cutscenes]]
| colspan=2| 10
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=2| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=2| 30
|- align="center"
| Debriefing
| colspan=2| 2,000 Characters per Stage
|}

{{Table3612|
*The number of Intelligence Entries in species.tbl has been increased to 75}}

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 1000
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 350
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20
|- align="center"
| Waypoint Paths
| 32
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|}

==Sub-Weapon Types==

The maximums for the sub types of weapons.

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Type'''
| style="background:#300505; width:75px"| '''Max Instances'''
|- align="center"
| Corkscrew Missiles
| 64
|- align="center"
| Swarm Missiles
| 100
|}

[[Category:Source Code Project]]

Engine limitations

2010-05-16T20:24:56Z

IssMneur: be not bee

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, developed to boost engine limits. Starting with FS2_Open 3.6.10 these builds can be used in Multiplayer, older builds are not capable of joining the servers due to several incompatibilities. In addition, Inferno and regular builds are incompatible to each other in Multiplayer; someone using an Inferno build will not be able to play with someone using a regular build and vice versa. Those builds are named after the [[Inferno]] mod, but are extensively used by many other projects, like [[The Babylon Project|TBP]].
Inferno builds will become the standard, starting at FS2_Open revision 3.7, with 3.6.12 being the last version to be distributed both in normal and Inferno variants.

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| 300
|- align="center"
| Beam Shots
| colspan=2| 5
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=2| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=2|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=2| 5
|- align="center"
| [[Cutscenes.tbl|Cutscenes]]
| colspan=2| 10
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=2| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=2| 30
|}

{{Table3612|
*The number of Intelligence Entries in species.tbl has been increased to 75}}

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 1000
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 350
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20
|- align="center"
| Waypoint Paths
| 32
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|}

[[Category:Source Code Project]]

Fs2 open on Linux/Installing the Development Libraries

2010-03-25T06:19:38Z

IssMneur: Added liblua to the page for Ubuntu

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Installing the Development Libraries|Installing the Development Libraries|
PrevPage=[[Fs2_open on Linux/Installing Subversion|Installing Subversion]]|
NextPage=[[Fs2_open on Linux/Acquiring_the_Code|Acquiring_the_Code]]}}

{{Note| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}

{{Note|: Redhat, Slackware, Archlinux, SuSE, and all the other distributions should have their instructions on installing the needed libraries added here, if your distribution is not listed below and you are familiar with how to install the needed libraries on it, please add it to this section. }}

You will also need [http://www.libsdl.org/ SDL], [http://www.openal.org/ OpenAL], [http://vorbis.com/ libvorbis], [http://www.theora.org/ libtheora], readline, [http://www.lua.org liblua >= 5.1.3], and OpenGL(most likely provided with your video card driver) development packages. And of course the [http://gcc.gnu.org/ GNU Compiler Collection] and required [http://sourceware.org/autobook/ make] tools.
 
'''Debian/Ubuntu''' users want to:
{{Note| The [http://packages.debian.org/unstable/devel/build-essential build-essential] package is a meta package that install the essential build tools. Follow the link for information.}}
$ apt-get install libopenal-dev libvorbis-dev build-essential automake1.9 autoconf libsdl-dev libtheora-dev libreadline5-dev libpng12-dev liblua5.1-dev

'''Fedora Core''' users (and most likely Redhat users too) want to:
$ yum install openal-devel libvorbis-devel gcc gcc-c++ automake autoconf SDL-devel libtheora-devel readline-devel

'''Gentoo''' users want to:
{{Note| media-libs/openal needs the "alsa" USE-flag if you intend to use ALSA, and media-libs/libsdl needs the "X","opengl" and "xv" USE-flags.}}

$ emerge -va openal libvorbis libsdl libtheora readline

'''Mandriva''' users want to:
$ urpmi libsdl-devel libopenal-devel libvorbis-devel libtheora-devel gcc gcc-c++ automake autoconf

[[Category:FreeSpace Open on Linux|Installing the Development Libraries]]