FreeSpace Wiki - User contributions [en]

Portal:Multiplayer

2007-10-27T14:20:13Z

Castor:

{| border=0 align=center cellpadding=4 cellspacing=0 width=95% style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''The Freespace Multiplayer Portal'''
|}

{| border=0 align=right cellpadding=4 cellspacing=0 width=20% style="margin: 0 0 1em 1em; background: #302020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Technical'''''
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Getting Started Guide|Getting Started Guide]]
|-
! style="color: white; height: 30px; 70%;"|[[List of Supported Mods]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Troubleshooting|Troubleshooting]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer FAQ]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Gameplay'''''
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Medals and Awards|Medals & Awards]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Community'''''
|-
! style="color: white; height: 30px; 70%;"|[[:Category:Multiplayer Squadrons|Multiplayer Squadrons]]
|-
! style="color: white; height: 30px; 70%;"|[[Playing Tips (Multiplayer)|Playing Tips]]
|-
! style="color: white; height: 30px; 70%;"|[[Code of Conduct]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer lingo]]
|-
|}

Welcome to the Freespace Multiplayer portal. This section is dedicated to providing guides on how to set up, play, host and and enjoy multiplayer games, as well as useful information about the multiplayer community such as squadrons, codes of conduct and the like.

===Freespace Multiplayer===
[[Image:Create_game_screen.JPG|left|300px|thumb|Create Game Screen]]
Currently, the [[FSSCP Introduction|Freespace Open]] engine supports multiplayer games with up to 12 human participants as well as any number of AI players. Play can be both cooperative and head-to-head, and can consist of anything from single mission slugfests up to full-length cooperative campaigns.

All games are currently hosted by one of their participants. The host chooses the mission (''see image to the left''), and has the power to kick players, set priviledges, and the like.

The retail release of Freespace 2 in 1999 included a standalone server option, but due to changes in the multiplayer code since the time of release, it is currently not functioning. Work is ongoing on bringing it back, however, and once it returns information on using it will be available here.

An upgrade of the current multiplayer code is also in progress, and is tentatively slated for release with Freespace Open version 3.6.10.

===Connection Types===
There are two ways of playing online games using FSO:
*Connecting through [[FS2NetD]]. FS2NetD is a replacement for the Parralax Online service that has now been terminated. It acts as a lobby for multiplayer games, tracking servers and facilitating connections without users needing to worry about each other's IP addresses, and also tracks stats for games that are played using validated data and missions. It does not actually host the games that are played, acting merely as a middle man.

*Direct IP connection. It is also possible to play IP games, but doing this requires all participants to manually enter the IP of the server that hosts the game. This is also the option to use when playing LAN games.

Details of setting up FSO to use either of these two options are explained in the getting started guide.

===MODs and custom missions===
It is possible to use MODs and play custom missions using FSO. Mods will need to be distributed to all participating players in advance, but missions will be automatically distributed if any participants are missing them.

When playing on FS2NetD, note that while MODs and custom missions are allowed, stats will not be saved for games that use them. ''Only'' games using validated missions and data are counted. For IP games where stats are not saved anyway, there are no such considerations.

===Validated Missions===
A package containing all currently validated multiplayer missions for Freespace 2 is available from the downloads section below. A voice pack for those missions is also available. To use them, the best way is to place them in a seperate directory and select that as a mod from the launcher.

Do not place them in the mediaVPs directory if you intend to play for stats, as the current mediaVPs are not validated.
==External Links==
*[http://www.game-warden.com/forum/showthread.php?t=267 GameWarden Multiplayer FAQ & Getting started guide]
*[http://fs2netd.game-warden.com/ FS2NetD Website - Player stats & Information about current games]
*[http://www.hard-light.net/forums/index.php/board,135.0.html HLP Multiplayer Forum]
==Downloads==
*[http://www.fszmirror.com/files/multi-mission-pack.vp Validated missions package for Freespace 2]
*[http://www.fszmirror.com/files/multi-voice-pack.vp Voice package for the validated missions]
__NOTOC__
[[Category:Multiplayer]]

Portal:Multiplayer

2007-10-27T14:19:41Z

Castor: cosmetic

{| border=0 align=center cellpadding=4 cellspacing=0 width=95% style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''The Freespace Multiplayer Portal'''
|}

{| border=0 align=right cellpadding=4 cellspacing=0 width=20% style="margin: 0 0 1em 1em; background: #302020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Technical'''''
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Getting Started Guide|Getting Started Guide]]
|-
! style="color: white; height: 30px; 70%;"|[[List of Supported Mods]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Troubleshooting|Troubleshooting]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer FAQ]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Gameplay'''''
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Medals and Awards|Medals & Awards]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Community'''''
|-
! style="color: white; height: 30px; 70%;"|[[:Category:Multiplayer Squadrons|Multiplayer Squadrons]]
|-
! style="color: white; height: 30px; 70%;"|[[Playing Tips (Multiplayer)|Playing Tips]]
|-
! style="color: white; height: 30px; 70%;"|[[Code of Conduct]]
|-
! style="color: white; height: 30px; 70%;"|[[Multiplayer Lingo]]
|-
|}

Welcome to the Freespace Multiplayer portal. This section is dedicated to providing guides on how to set up, play, host and and enjoy multiplayer games, as well as useful information about the multiplayer community such as squadrons, codes of conduct and the like.

===Freespace Multiplayer===
[[Image:Create_game_screen.JPG|left|300px|thumb|Create Game Screen]]
Currently, the [[FSSCP Introduction|Freespace Open]] engine supports multiplayer games with up to 12 human participants as well as any number of AI players. Play can be both cooperative and head-to-head, and can consist of anything from single mission slugfests up to full-length cooperative campaigns.

All games are currently hosted by one of their participants. The host chooses the mission (''see image to the left''), and has the power to kick players, set priviledges, and the like.

The retail release of Freespace 2 in 1999 included a standalone server option, but due to changes in the multiplayer code since the time of release, it is currently not functioning. Work is ongoing on bringing it back, however, and once it returns information on using it will be available here.

An upgrade of the current multiplayer code is also in progress, and is tentatively slated for release with Freespace Open version 3.6.10.

===Connection Types===
There are two ways of playing online games using FSO:
*Connecting through [[FS2NetD]]. FS2NetD is a replacement for the Parralax Online service that has now been terminated. It acts as a lobby for multiplayer games, tracking servers and facilitating connections without users needing to worry about each other's IP addresses, and also tracks stats for games that are played using validated data and missions. It does not actually host the games that are played, acting merely as a middle man.

*Direct IP connection. It is also possible to play IP games, but doing this requires all participants to manually enter the IP of the server that hosts the game. This is also the option to use when playing LAN games.

Details of setting up FSO to use either of these two options are explained in the getting started guide.

===MODs and custom missions===
It is possible to use MODs and play custom missions using FSO. Mods will need to be distributed to all participating players in advance, but missions will be automatically distributed if any participants are missing them.

When playing on FS2NetD, note that while MODs and custom missions are allowed, stats will not be saved for games that use them. ''Only'' games using validated missions and data are counted. For IP games where stats are not saved anyway, there are no such considerations.

===Validated Missions===
A package containing all currently validated multiplayer missions for Freespace 2 is available from the downloads section below. A voice pack for those missions is also available. To use them, the best way is to place them in a seperate directory and select that as a mod from the launcher.

Do not place them in the mediaVPs directory if you intend to play for stats, as the current mediaVPs are not validated.
==External Links==
*[http://www.game-warden.com/forum/showthread.php?t=267 GameWarden Multiplayer FAQ & Getting started guide]
*[http://fs2netd.game-warden.com/ FS2NetD Website - Player stats & Information about current games]
*[http://www.hard-light.net/forums/index.php/board,135.0.html HLP Multiplayer Forum]
==Downloads==
*[http://www.fszmirror.com/files/multi-mission-pack.vp Validated missions package for Freespace 2]
*[http://www.fszmirror.com/files/multi-voice-pack.vp Voice package for the validated missions]
__NOTOC__
[[Category:Multiplayer]]

Multiplayer lingo

2007-10-27T14:17:37Z

Castor: Threw in a few quick terms for starters

Following lists some of the terms commonly seen on multiplayer chat screens.
*'''AI:''' Computer controlled ships
*'''EMP:''' The EMP missile
*'''Fire:''' The Infyrno missile
*'''Fish:''' The Piranha missile
*'''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 (object updates):''' Setting the "Object Updates" on "LOW" on the multiplayer options page - the preferred setting for MP clients. Limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone. Using something else tha LOW against host instructions may get you kicked! Later FS2 OPen builds provide a means for the host to force low object updates (the -cap_object_update flag).
*'''SD:''' Self Destruct (by pressing SHIFT+END)
*'''STD rules:''' Standard Rules - A set of rules commonly followed in TvT matches: no AI, no EMP, no Fire, no Fish, no SD allowed during the game.

Portal:Multiplayer

2007-10-27T13:35:04Z

Castor: Added "Multiplayer lingo" section

Fs2 open on Linux/Acquiring the Code

2007-10-27T10:02:58Z

Castor: spelling

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Acquiring the Code|Acquiring the Code|
PrevPage=[[Fs2_open on Linux/Installing the Development Libraries|Installing the Development Libraries]]|
NextPage=[[Fs2_open on Linux/Checkout Script|Checkout Script]]}}

{{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.}}
Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the CVS command, this way CVS will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have CVS installed on your system. See the [[Fs2_open_on_Linux/Installing CVS|Installing CVS]] chapter on installing CVS.

Now get the source. Run from a terminal:
$ cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login
This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.
 
Next, get the code from the server we just connected to, either from the development branch:
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open
..or from the "stable branch":
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
{{Note| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open", either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option. In the latter checkout we specified the branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.

Fs2 open on Linux/Acquiring the Code

2007-10-27T09:59:41Z

Castor: Stable branch clarifications

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Acquiring the Code|Acquiring the Code|
PrevPage=[[Fs2_open on Linux/Installing the Development Libraries|Installing the Development Libraries]]|
NextPage=[[Fs2_open on Linux/Checkout Script|Checkout Script]]}}

{{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.}}
Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the CVS command, this way CVS will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have CVS installed on your system. See the [[Fs2_open_on_Linux/Installing CVS|Installing CVS]] chapter on installing CVS.

Now get the source. Run from a terminal:
$ cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login
This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.
 
Next, get the code from the server we just connected to, either from the development branch:
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open
..or from the "stable branch":
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
{{Note| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option. In the latter checkout we specified the branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.

Fs2 open on Linux/Acquiring the Code

2007-10-26T20:21:48Z

Castor: Added instructions for stable branch co

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Acquiring the Code|Acquiring the Code|
PrevPage=[[Fs2_open on Linux/Installing the Development Libraries|Installing the Development Libraries]]|
NextPage=[[Fs2_open on Linux/Checkout Script|Checkout Script]]}}

{{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.}}
Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the CVS command, this way CVS will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have CVS installed on your system. See the [[Fs2_open_on_Linux/Installing CVS|Installing CVS]] chapter on installing CVS.

Now get the source. Run from a terminal:
$ cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login
This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login. 
Next, get the code from the server we just connected to, either from the development branch:
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open
..or from the "stable branch" (currently 3.6.9):
$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
{{Note| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option.

Fs2 open on Linux/Acquiring the Game Data

2007-09-23T15:32:58Z

Castor: Added: game data can be copied over from existing Win install

{{Page Navigation|
BookName=[[The fs2_open on Linux Guide]]|
CurrentPage=Acquiring the Game Data|Acquiring the Game Data|
PrevPage=[[Fs2_open on Linux/Compile Script|Compile Script]]|
NextPage=[[Fs2_open on Linux/Extracting data from CD|Extracting data from CD]]}}

This tutorial deals primarily with providing you with an executable, but in order to play the game you also need the game data. FreeSpace 2 game data is available from a number of sources, see this thread: http://www.hard-light.net/forums/index.php/topic,38195.0.html (or use Turey's installer, see above for a link)

Note that if you use the retail CD, you'll need to extract the files and to copy them on your drive, reproducing the same layout as in a working win32 installation (just make sure every file is lowercase). This thread on the SCP forum has some more info on it : http://scp.indiegames.us/forum_viewtopic.php?3.282

There are three ways of doing this,
* Copy the files over from an existing FS2 Windows install (by mounting the Win partition), or
* Use [http://www.winehq.org/ Wine] to install the game in the right directory, using the Setup.exe found on the first CD, or,
* Extract the files manually from the CD.

The third method is detailed below. The wine one is straightforward and you shouldn't need any specific instruction as it behaves like a Windows install, but you'll have to fix permissions and lowercase the filename as well, so keep reading.

Command-Line Reference

2006-08-02T13:07:20Z

Castor: /* -tga16 */

==Launcher Flags==
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 recieve 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. OpenGL only. Environment mapping intensity will be determined from the intensity of specular maps.

====-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====
Enables the use of TGA and JPG file formats for image files. If a ship is showing up partially invisible, select this option.
====-pcx32====
'''WARNING - HIGH MEMORY USAGE'''

Enables PCX files to be loaded into 32-bit memory. This will not imporove the rendering of any ships in-game, and is usually more of a burden on performance than is worthwhile. Use at your own risk. Removed from launcher options after 3.6.7.

====-cell====
Enables cell shading. This will make graphics appear more "cartoonish". For use with media in mv_cell.vp. Not considered a standard enhancement.
====-mipmap====
Enables mipmapping.

====-nomotiondebris====
Disables motion debris.
====-2d_poof====
Applies nebula poofs in 2d, effectively preventing them from forming intersections with ships.
====-noscalevid====
Disables scaling of video clips.
====-missile_lighting====
Applys lighting to missiles.
====-rlm====
'''Obsolete Argument'''


Enables more accurate lighting model for OpenGL mode. Always on in current builds, so this command-line option has been removed.

----

===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====
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====
Use ship and weapon models in ship selection and weapon loadout. Completely disables the standard ANI interface on those screens.
====-3dwarp====
Use full geometry for the subspace warp effect.
====-warp_flash====
Enable a flash at warp in and warp out.
====-UseNewAI====
Tells the game to use new AI routines. This argument alters mission balance and is not considered a standard feature.
====-tbp====
Enable feature set for The Babylon Project
====-wcsaga====
Enable feature set for The Wing Commander Saga

----

===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====
'''''What does this do?'''''
====-closed====
'''''What does this do?'''''
====-restricted====
'''''What does this do?'''''
====-multilog====
'''''What does this do?'''''
====-clientdamage====
'''''What does this do?'''''
====-mpnoreturn====
Disables return to the flight deck screen after a mission completes.

----

===Troubleshooting===
====-fixbugs====
'''Obsolete Argument - Removed in builds after 3.6.7'''


Originally used to disable certain crashing behavior as a stop-gap measure. This feature is not available in current builds.
====-nocrash====
'''Obsolete Argument - Removed in builds after 3.6.7'''


Originally used to disable certain crashing behavior as a stop-gap measure. This feature is not available in current builds.
====-oldfire====
'''''What does this do?'''''
====-nohtl====
'''WARNING - VERY SLOW'''

Reverts to software rendering mode. Does this work any more?
====-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.

----

===Experimental===
====-alpha_env====
Enables alpha environment mapping. OpenGL only. Environment mapping intensity will be determined from the alpha channel of specular maps.
====-decals====
Enables damage decals.
====-ingame_join====
Enables ingame joining in multiplayer. FIXME: Host option?
====-tga16====
'''Obsolete Argument - Removed in builds after 3.6.7'''


Originally used to converts TGA images to 16-bits in order to reduce memory footprint (at the expense of image quality), superseded by ''-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 is 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====
'''''What does this do?'''''
====-tablecrcs====
'''''What does this do?'''''
====-missioncrcs====
'''''What does this do?'''''
====-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 seperated by a space. The prototype for use in this case is "-option argument"
===Graphics===
====-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.

====-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. However, that is relative.

====-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. However, that is relative.

====-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. However, that is relative.

====-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. However, that is relative.

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

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

----

===Gameplay===
====-mod====

Specifies in which folders inside Freespace2 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 behaviour, 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/

:::Please note. Freespace Open doesn't like spaces in directories (in the full path) so do not install the game within ''Program Files/Freespace2'' or ''Games/Freespace 2'' and, of course, do not use spaces within mod directories (''dir1'' is OK but ''dir 1'' isn't).

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and mod.ini file. Within this Launcher 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, (its format must be plain text), it will be read and, inside it, the following section and lines can be used to modify the -mod flag too:

: [multimod] PrimaryList = Pri1,Pri2,...(the rest of desired directories)...,Prix; SecondaryList = Sec1,Sec2,...(the rest of desired directories)...,Secx;

(Please note the ending semicolon (;) in each list line). With these lines the following flag would be built:
: '''-mod Pri1,Pri2,...,Prix,moddir,Sec1,Sec2,...,Secx'''

If primary or secondary folders aren't used, their respective line can be erased or it can be typed as ''xxxxxxList = ;''.

::: '''''PLEASE NOTE''': '''Launcher v 5.4''', or later, '''must be used'''. Earlier versions had some bugs that would cause the previous explanation about mod.ini fail.''

::: The most common use of mod.ini and SecondaryList is sharing resources between mods. And the best example is the enhaced media vps from SCP crew. Most of the people install them in a folder called ''mediavps'' inside ''Freespace2''. In this way when running retail FS2 they do not interfere with this original game version that doesn't use this -mod flag feature. When using FS2_Open but without mods, you just need to select ''mediavps'' in Launcher MOD tab to use them. And if you want to enjoy that enhacements while playing any 'real' mod, you just need to put a mod.ini file inside its ''moddir'' with at least a ''SecondaryList = mediavps;'' line.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure.
#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 how this ''Mission.fs2'' is 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 enhaced ones adding them in a higher priority place.

As derived from 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.

:'''Additional notes'''

# This flag is also used by 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. No Launcher MOD tab available for this use. 
# 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.

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

''Because of an active bug, FOV can misalign target boxes, effects, etc. Please check [http://lore.maxgaming.net/~scp/mantis/bug_view_advanced_page.php?bug_id=0000083 Mantis bug 083 status]if you are going to change the default value.''

----

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by a stand-alone server.

Takes one argument string, the name to be assigned to the game being created.
====-password====
Specifies the password for a stand-alone server.

Takes one argument string, the required password for the game being created.
====-allowabove====
Specifies a player's minimum rank for joining a game on a stand-alone server.

Takes one argument integer, the points ranking above which a player must be to enter the game.
====-allowbelow====
Specifies a player's maximum rank for joining a game on a stand-alone server.

Takes one argument integer, the points ranking below which a player must be to enter the game.
====-port====
Specifies the port on which to run for a stand-alone server.

Takes one argument integer, the port which the game should use to connect.
====-connect====
'''''What does this do?'''''
====-clientdamage====
'''''What does this do?'''''
====-timeout====
'''''What does this do?'''''

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