FreeSpace Wiki - User contributions [en]

Manually Installing FreeSpace 2 Open

2017-02-12T19:10:26Z

Mongoose: /* Step Three: Choosing a build */

This page covers installing FSO and associated mods by hand. You may want to use the [[FreeSpace Open Installer]] as it considerably streamlines and automates the whole process.
   

This guide assumes you already have a working copy of FreeSpace 2 installed. If not, see [[Installing FreeSpace 2]].

== Step One: Understanding what you need ==
There are three main components that you need to get the most out of fs2_open.

* First, you need to install the retail data from [[Installing FreeSpace 2|FreeSpace 2]]
* Second, the '''fs2_open build'''. This is the core game engine, a single executable file.
* Next, the '''Launcher'''. This lets you configure the fs2_open executable for your particular system, in much the same way the original FreeSpace 2 launcher is used to configure it.
* Finally, the '''MediaVPs'''. These contain all sorts of graphical improvements and are highly recommended. Version numbers of mediaVPs generally agree with the fs2_open build that they're supposed to be used with.

== Step Two: Getting the Launcher ==

Unless you are using an extremely old build, you will want to get the appropriate launcher for your OS. It may be bundled with your release but the direct download link is below.

Windows: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] (highly recommended) or [http://swc.fs2downloads.com/files/Launcher55g.zip Launcher 5.5g] (does not work on Windows 8/10)

OS X: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] unless you are using Tiger or a PowerPC Mac, in which case use Soulstorm's [http://www.hard-light.net/forums/index.php?topic=51391.0 OS X Launcher 3.0] ([[Soulstorm's OS X Launcher|instructions]])

Linux: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] (build it from source; see the [http://code.google.com/p/wxlauncher/source/browse/ReadMe.txt readme] for instructions)

== Step Three: Choosing a build ==
There are two main types of fs2_open builds, at the time of this writing. A "build" is any executable built from source code. Any build may also be a debug build. (Debug builds usually have names that end with "_d" or "_dbg" or somesuch) If you don't know why you'd want to use a debug build, you're almost certainly better off not using one.

All builds should be extracted to your main FreeSpace 2 folder.

=== Official Releases ===
The first type is the "stable" release build. Additionally, some official release builds are available with installers. It's a good idea to get the most recent official release, even if you end up deciding to get a recent build anyway. Current official release is '''FreeSpace Open 3.7.4'''.

[http://www.hard-light.net/forums/index.php?topic=92181.0 FreeSpace Open 3.7.4 release thread]

=== Test Builds ===
Recent Builds are ones that individual coders release. Most of the time they're released to either test or showcase some particular new feature. If you're curious about how reliable a build is, your best bet is to check the original thread it was posted in and see what people's responses were.

[http://www.hard-light.net/forums/index.php/board,97.0.html Test builds forum]

[http://www.hard-light.net/forums/index.php/board,113.0.html Cross Platform Development forum (for Linux/OS X builds)]

=== Nightly Builds ===

In addition to recent builds, nightly builds are built every evening after any changes have been applied to the source code. These are put out so that the code base can be quickly verified for general stability. Testing nightly builds on a regular basis and reporting bugs helps ensure a stable code base is maintained.

[http://www.hard-light.net/forums/index.php/board,173.0.html Nightly builds forum]

== Step Four: MediaVPs ==

With the release of the 2014 MediaVPs, there is once again only one set of recommended MediaVPs available. The detailed instructions for installing and the current links can currently be found in the MediaVPs Release Thread linked below.

MediaVPs should be installed in a new 'mediavps_2014' directory under the main FreeSpace directory (\freespace2\mediavps_2014) This preserves the possibility to play with either with retail FreeSpace 2 vp files if this is desired (for example in multiplayer) and using the retail FreeSpace 2 executive files and requires minimal extra time to set up. (See step six for further details).

[http://www.hard-light.net/forums/index.php?topic=86475.0 2014 MediaVPs Release Thread]

== Step Five: Configuring Everything ==

=== Basic setup ===

At this point, you have one final stage remaining before fs2_open is ready to go. Open up the Launcher. (It should be in your main FreeSpace 2 folder). Select the EXE you'd like to use by clicking the "Browse..." button at the top of the Launcher. There are two types typically for any build release:
* a debug build with the name containing 'd' or 'debug' right after the version number. For example, fs2_open_3_6_10'''d'''.exe.
* a regular/release build with the name containing 'r' or nothing right after the version number. For example, fs2_open_3_6_10.exe or fs2_open_3_6_11'''r'''_sse2-20100131_r5862.exe.

For normal play you will want to use a regular build but for any testing, development, or bug reporting you definitely want to use a 'd' build. For example, fs2_open_3_6_10d.exe vs fs2_open_3_6_10.exe.

Next, ensure that the "Audio/Joystick" and "Network" tabs have the proper settings.

=== Speech setup ===

If you are using Windows XP, or have the Speech API installed, fs2_open will be able to read briefings, techroom descriptions, and even ingame messages to you using computer-generated voices. Although no match for real voice acting, it is convenient when valid plot points are mentioned in the middle of combat. Speech in the various locations can be turned on and off by checking and unchecking the check boxes; you can choose which of the installed voices to use in fs2_open by changing the drop-down menu. As of this writing, fs2_open will only use the voice you choose for everything. Text to Speech is typically only available in stable release builds. Recent Builds from a coder's test branch will usually not have it, nor will Nightly Builds.

=== Video setup ===

On the "Video" tab, you can choose choose various graphics options. Here, you can set the resolution as well as the colour depth. It is recommended to use a resolution greater or equal to 1024x768 at 32 bits of colour depth. The other options, especially the anisotropic filter and antialiasing sliders, should not be altered.

=== Features setup ===

This tab is where most of fs2_open's options can be toggled on and off. At the top is a readout of your current command line; you should include this in any debugging reports you make.

The next box, with the buttons "Select mod" and "No mod" allow you to choose a mod directory to use; files in the mod directory will be given precedence over other files, so you can easily switch between mods by installing them to different directories.

"Custom flags" allows you to add any command line flags that don't show up in the Launcher. This may be because they require additional arguments, as is the case with the "-fov" command line argument. For more information, see the [[Command-Line Reference]] page.

Finally, the two boxes below this let you toggle the various new features in fs2_open, many of which are graphical improvements. Recommended options for midrange systems are "Enable specular", "Enable glowmaps", "Enable Environment Maps", and "Enable normal maps". (You may have to choose a different section in the drop-down box to get to some of these options). There are many, many more options, but these should get you started.

[http://www.hard-light.net/wiki/index.php/Command-Line_Reference Command line Flags]

=== Language Setup ===

Freespace & Freespace 2 supported non-English languages such as French, German & Polish. Some mods (most notably Freespace Port) also support non-English languages. The steps required to change the language differ depending on which OS FSO is running on.

Note that due to pilot file limitations, pilots can only be used with '''one''' language. If you switch languages you need to have multiple pilots.

To set the language, modify the Language entry in the [[Getting_started_with_FreeSpace_2#Registry|registry or the [Default] section of the .ini file]].

e.g.

<code>
[Default]

...

Language=French
</code>

== Step Six: Cutscenes ==

Depending on how you installed the game, the cutscenes might not be in the proper location. If you bought your copy of FS2 from Good Old Games, the cutscenes (ten .mve files) are somewhere in \freespace2\data2\ or \freespace2\data3\ . You can get them working by moving them to \freespace2\data\movies\ . Create the directory if it does not exist. You can also download either the [http://www.freespacemods.net/download.php?view.124 original MVE cutscenes] or [http://freespacemods.net/download.php?view.128 OGG-encoded versions] from FreeSpaceMods.net. If you have the game CDs/DVD, you can copy the cutscenes from them to the FreeSpace2/data/movies/ folder. The OGG cutscenes are smaller but might not perform as well on older hardware that could run the MVEs without problem. Now you should have the full gamut of updated and retail content installed!

Note: If you've found the AVI versions of the cutscenes, do not use them. Support for AVI has been removed in FSO versions 3.6.10 and higher.

[[Category:Source Code Project]]

Manually Installing FreeSpace 2 Open

2017-02-12T19:09:03Z

Mongoose: /* Step Two: Getting the Launcher */

This page covers installing FSO and associated mods by hand. You may want to use the [[FreeSpace Open Installer]] as it considerably streamlines and automates the whole process.
   

This guide assumes you already have a working copy of FreeSpace 2 installed. If not, see [[Installing FreeSpace 2]].

== Step One: Understanding what you need ==
There are three main components that you need to get the most out of fs2_open.

* First, you need to install the retail data from [[Installing FreeSpace 2|FreeSpace 2]]
* Second, the '''fs2_open build'''. This is the core game engine, a single executable file.
* Next, the '''Launcher'''. This lets you configure the fs2_open executable for your particular system, in much the same way the original FreeSpace 2 launcher is used to configure it.
* Finally, the '''MediaVPs'''. These contain all sorts of graphical improvements and are highly recommended. Version numbers of mediaVPs generally agree with the fs2_open build that they're supposed to be used with.

== Step Two: Getting the Launcher ==

Unless you are using an extremely old build, you will want to get the appropriate launcher for your OS. It may be bundled with your release but the direct download link is below.

Windows: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] (highly recommended) or [http://swc.fs2downloads.com/files/Launcher55g.zip Launcher 5.5g] (does not work on Windows 8/10)

OS X: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] unless you are using Tiger or a PowerPC Mac, in which case use Soulstorm's [http://www.hard-light.net/forums/index.php?topic=51391.0 OS X Launcher 3.0] ([[Soulstorm's OS X Launcher|instructions]])

Linux: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] (build it from source; see the [http://code.google.com/p/wxlauncher/source/browse/ReadMe.txt readme] for instructions)

== Step Three: Choosing a build ==
There are two main types of fs2_open builds, at the time of this writing. A "build" is any executable built from source code. Any build may also be a debug build. (Debug builds usually have names that end with "_d" or "_dbg" or somesuch) If you don't know why you'd want to use a debug build, you're almost certainly better off not using one.

All builds should be extracted to your main FreeSpace 2 folder.

=== Official Releases ===
The first type is the "stable" release build. Additionally, some official release builds are available with installers. It's a good idea to get the most recent official release, even if you end up deciding to get a recent build anyway. Current official release is '''FreeSpace Open 3.7.0'''.

[http://www.hard-light.net/forums/index.php?topic=85435.0 FreeSpace Open 3.7.0 release thread]

=== Test Builds ===
Recent Builds are ones that individual coders release. Most of the time they're released to either test or showcase some particular new feature. If you're curious about how reliable a build is, your best bet is to check the original thread it was posted in and see what people's responses were.

[http://www.hard-light.net/forums/index.php/board,97.0.html Test builds forum]

[http://www.hard-light.net/forums/index.php/board,113.0.html Cross Platform Development forum (for Linux/OS X builds)]

=== Nightly Builds ===

In addition to recent builds, nightly builds are built every evening after any changes have been applied to the source code. These are put out so that the code base can be quickly verified for general stability. Testing nightly builds on a regular basis and reporting bugs helps ensure a stable code base is maintained.

[http://www.hard-light.net/forums/index.php/board,173.0.html Nightly builds forum]

== Step Four: MediaVPs ==

With the release of the 2014 MediaVPs, there is once again only one set of recommended MediaVPs available. The detailed instructions for installing and the current links can currently be found in the MediaVPs Release Thread linked below.

MediaVPs should be installed in a new 'mediavps_2014' directory under the main FreeSpace directory (\freespace2\mediavps_2014) This preserves the possibility to play with either with retail FreeSpace 2 vp files if this is desired (for example in multiplayer) and using the retail FreeSpace 2 executive files and requires minimal extra time to set up. (See step six for further details).

[http://www.hard-light.net/forums/index.php?topic=86475.0 2014 MediaVPs Release Thread]

== Step Five: Configuring Everything ==

=== Basic setup ===

At this point, you have one final stage remaining before fs2_open is ready to go. Open up the Launcher. (It should be in your main FreeSpace 2 folder). Select the EXE you'd like to use by clicking the "Browse..." button at the top of the Launcher. There are two types typically for any build release:
* a debug build with the name containing 'd' or 'debug' right after the version number. For example, fs2_open_3_6_10'''d'''.exe.
* a regular/release build with the name containing 'r' or nothing right after the version number. For example, fs2_open_3_6_10.exe or fs2_open_3_6_11'''r'''_sse2-20100131_r5862.exe.

For normal play you will want to use a regular build but for any testing, development, or bug reporting you definitely want to use a 'd' build. For example, fs2_open_3_6_10d.exe vs fs2_open_3_6_10.exe.

Next, ensure that the "Audio/Joystick" and "Network" tabs have the proper settings.

=== Speech setup ===

If you are using Windows XP, or have the Speech API installed, fs2_open will be able to read briefings, techroom descriptions, and even ingame messages to you using computer-generated voices. Although no match for real voice acting, it is convenient when valid plot points are mentioned in the middle of combat. Speech in the various locations can be turned on and off by checking and unchecking the check boxes; you can choose which of the installed voices to use in fs2_open by changing the drop-down menu. As of this writing, fs2_open will only use the voice you choose for everything. Text to Speech is typically only available in stable release builds. Recent Builds from a coder's test branch will usually not have it, nor will Nightly Builds.

=== Video setup ===

On the "Video" tab, you can choose choose various graphics options. Here, you can set the resolution as well as the colour depth. It is recommended to use a resolution greater or equal to 1024x768 at 32 bits of colour depth. The other options, especially the anisotropic filter and antialiasing sliders, should not be altered.

=== Features setup ===

This tab is where most of fs2_open's options can be toggled on and off. At the top is a readout of your current command line; you should include this in any debugging reports you make.

The next box, with the buttons "Select mod" and "No mod" allow you to choose a mod directory to use; files in the mod directory will be given precedence over other files, so you can easily switch between mods by installing them to different directories.

"Custom flags" allows you to add any command line flags that don't show up in the Launcher. This may be because they require additional arguments, as is the case with the "-fov" command line argument. For more information, see the [[Command-Line Reference]] page.

Finally, the two boxes below this let you toggle the various new features in fs2_open, many of which are graphical improvements. Recommended options for midrange systems are "Enable specular", "Enable glowmaps", "Enable Environment Maps", and "Enable normal maps". (You may have to choose a different section in the drop-down box to get to some of these options). There are many, many more options, but these should get you started.

[http://www.hard-light.net/wiki/index.php/Command-Line_Reference Command line Flags]

=== Language Setup ===

Freespace & Freespace 2 supported non-English languages such as French, German & Polish. Some mods (most notably Freespace Port) also support non-English languages. The steps required to change the language differ depending on which OS FSO is running on.

Note that due to pilot file limitations, pilots can only be used with '''one''' language. If you switch languages you need to have multiple pilots.

To set the language, modify the Language entry in the [[Getting_started_with_FreeSpace_2#Registry|registry or the [Default] section of the .ini file]].

e.g.

<code>
[Default]

...

Language=French
</code>

== Step Six: Cutscenes ==

Depending on how you installed the game, the cutscenes might not be in the proper location. If you bought your copy of FS2 from Good Old Games, the cutscenes (ten .mve files) are somewhere in \freespace2\data2\ or \freespace2\data3\ . You can get them working by moving them to \freespace2\data\movies\ . Create the directory if it does not exist. You can also download either the [http://www.freespacemods.net/download.php?view.124 original MVE cutscenes] or [http://freespacemods.net/download.php?view.128 OGG-encoded versions] from FreeSpaceMods.net. If you have the game CDs/DVD, you can copy the cutscenes from them to the FreeSpace2/data/movies/ folder. The OGG cutscenes are smaller but might not perform as well on older hardware that could run the MVEs without problem. Now you should have the full gamut of updated and retail content installed!

Note: If you've found the AVI versions of the cutscenes, do not use them. Support for AVI has been removed in FSO versions 3.6.10 and higher.

[[Category:Source Code Project]]

User:Mongoose

2016-08-13T01:43:18Z

Mongoose: Created page with "A guy! Who posts stuff!"

A guy! Who posts stuff!

Talk:Getting FreeSpace

Mongoose:

(Taken from [http://www.hard-light.net/forums/index.php/topic,37643.0.html post] by feature creator RandomTiger)

== Overview ==
BEFORE RUNNING THIS YOU MUST TRAIN THE VOICE SYSTEM.
This feature is for the PC only and is activated with -voicer in the command line.

In XP (and possibly 2000) in control panel there should be a Speech->Speech Recognition option. Run through 'Configure Mic' and 'Train Profile'. If the Speech Recognition option isn't available, you'll need to install the Microsoft Speech Recognition Engine. See [http://www.microsoft.com/windowsxp/using/setup/expert/moskowitz_02september23.mspx this support article] for more details.

The system has limitations; it only understands set commands (most in the menu) and most Greek alphabet wing names, so no custom ship names are going to be understood. Also, running this may slow down the game, as it has to spend CPU time processing your speech.

Sometimes the menu pops up with stuff it shouldn't, but I've found the speech recognition to be fairly good and I'm not even using a proper mic, just headphones plugged into the mic socket.

== Recognized Commands ==

=== Wings ===

* Wing

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

=== Numbers ===

* One
* Two
* Three
* Four
* Five
* Six
* Seven
* Eight
* Nine

=== Menu Options ===

* Ships
* Wings
* All fighters
* All wings
* Reinforcements

=== Support ===

* Support ship
* Rearm
* Repair
* Abort

=== Commands ===

* Cancel
* Command

* Destroy my target
* Disable my target
* Disarm my target
* Destroy subsystem
* Protect my target
* Ignore my target
* Form on my wing
* Cover me
* Engage enemy
* Attack
* Depart

[[Category:Source_Code_Project]]

Voice Recognition

2009-08-10T05:56:13Z

Mongoose:

Voice Recognition

2009-08-10T05:55:11Z

Mongoose:

2008-12-20T20:58:09Z

Mongoose:

There are several different ways of getting your hands on FreeSpace 2.

== Buy it ==

===[http://www.gog.com/en/frontpage Good Old Games] (GOG)===

A new digital distribution service for classic games, including both FreeSpace titles, which launched in late 2008. GOG is selling both games for $5.99 (USD) with no digital rights management strings attached. Definitely the most highly-recommended means of obtaining the games at the present time.

==[http://www.gametap.com GameTap]==

GameTap allows premium users to play both FreeSpace 1 and FreeSpace 2. However, the service does not support mods of either game (meaning no FS2 Open) or online play.

===Physical Copies===

There are still copies of FS2 floating around, but finding them is not always easy.

So where could you grab a copy?
* [http://search.ebay.com/FreeSpace-2 There are usually some up for sale on eBay].
* A Bargain Bin.

FreeSpace 2 has not been mass-produced for several years, so checking places that sell used software is your only recourse if you need to buy locally. The original FreeSpace has been out-of-print (so to speak) for even longer, but luckily for you you can play FS1 by getting [[The FreeSpace Port]], but you'll need FS2 set up first.





[[Category:Acquiring FreeSpace]]
[[Category:Source Code Project]]

Talk:Getting FreeSpace

2008-12-20T20:48:08Z

Mongoose: /* Organization */

Talk:Getting FreeSpace

2008-12-20T20:46:47Z

Mongoose: /* Organization */

2008-12-20T20:44:34Z

Mongoose:

Installing fs2 open

2008-12-20T02:46:56Z

Mongoose:

This guide assumes you already have a working copy of Freespace 2 installed. If not, see [[Installing Freespace 2]]. Also, this build assumes you do not use an installer. If you do, skip down to the part where it talks about configuring fs2_open.

== Quick Start: Using the Online Installer ==

You can use the excellent installer by Turey, that should give you a baseline of everything you need to play. The rest of this guide is full of information if you want to start tweaking things, or tackle things manually. However, for most players, you can stop with this step.

* [http://www.fsoinstaller.com/files/installer/FreeSpaceOpenInstaller.zip Windows Installer (Zipped .exe, 19 MB)] (Doesn't need Java, get this one if you are unsure and are using Windows)
* [http://www.fsoinstaller.com/files/installer/java/FreeSpaceOpenInstaller.jar Win/Linux/Mac Installer (.jar, 26 KB)] (Requires Java 1.5)

You can also get the Installer [http://www.fsoinstaller.com/files/installer/java/ source code here.]

This Installer is known to work on Windows, Linux(tested on Gentoo and Fedora, should work on others), and Mac (OSX Panther, with a hacked install of Java 1.5)

The most recent Installer includes:

* FreeSpace Open 3.6.9 Final (regular and debug)
* FreeSpace Open 3.6.10 Experimental (regular and debug)
* FRED2 Open 3.6.9 Final (regular and debug)
* Launcher 5.5a
* launcher6.ini
* Mac Executables
* Soulstorm's OSX Launcher
* fs2open_pxo.cfg
* The OpenAL Installer (optional)
* 3.6.8 Zeta MediaVPs (optional, includes the 710 patches)
* 3.6.8 Zeta adveffects (only for those with high-power systems, requires regular MediaVPs, includes 710 patch)
* .OGG Cutscenes
* Derelict SCP Version (With optional voice)
* Just Another Day 1, 2 & 3 (separate options for each)
* FreeSpace Port
* Awakenings
* Homesick
* Transcend
* Sync

=== Requirements and Notes ===
You can update your installation by simply running the Installer again. It will download files that are out of date.

The Installer requires an internet connection to install. This is because:
* It checks to see if it is out of date by pulling the number of the most recent version off of the web.
* It automatically takes you to the download page of the most recent version if your version is out of date.
* It checks that all the files are up-to-date.

Source:
[http://www.hard-light.net/forums/index.php/topic,42854.0.html Original thread by Turey]

== Step One: Understanding what you need ==
There are three main components that you need to get the most out of fs2_open.

If Turey's installer is down, or if you want to assemble it all yourself, you need the following components, the rest of this guide tells you about those components and various inner workings of hte SCP:

* First, the '''Launcher'''. This lets you configure the fs2_open executable for your particular system, in much the same way the original Freespace 2 launcher is used to configure it.
* Next, the '''fs2_open build'''. This is the core game engine, a single executable file.
* Finally, the '''MediaVPs'''. These contain all sorts of graphical improvements and are highly recommended. Version numbers of mediaVPs generally agree with the fs2_open build that they're supposed to be used with.

== Step Two: Getting the Launcher ==

Unless you are using an extremely old build, you will want to get Launcher 5.5 which is bundled with the FreeSpace Open 3.6.9 release but download link to is provided below.

[http://fs2source.warpcore.org/exes/Launcher55d.rar Launcher 5.5d download]

== Step Three: Choosing a build ==
There are two main types of fs2_open builds, at the time of this writing. A "build" is any executable built from source code. Any build may also be a debug build. (Debug builds usually have names that end with "_d" or "_dbg" or somesuch) If you don't know why you'd want to use a debug build, you're almost certainly better off not using one.

All builds should be extracted to your main Freespace 2 folder.

=== Official Releases ===
The first type is the "stable" release build. Additionally, some official release builds are available with installers. It's a good idea to get the most recent official release, even if you end up deciding to get a recent build anyway. Current official release is '''FreeSpace Open 3.6.9'''.

[http://www.hard-light.net/forums/index.php/topic,44291.0.html FreeSpace Open 3.6.9 release thread]

[http://fs2source.warpcore.org/exes/3.6.9.rar Official 3.6.9 release download]

=== Recent Builds ===
Recent Builds are ones that individual coders release. Most of the time they're released to either test or showcase some particular new feature. If you're curious about how reliable a build is, your best bet is to check the original thread it was posted in and see what people's responses were.

[http://www.hard-light.net/forums/index.php/board,97.0.html Recent builds forum]

== Step Four: Choosing your MediaVPs ==

There are a variety of different [[MediaVP]]s available for download. No matter what system you have, it should be able to support '''mv_core''' with no degradation in performance. This will enable a few interface improvements that require extra art.

'''Basic installation''' usually includes:

[http://fs2source.warpcore.org/mvp368zeta/mv_zpack.zip ZPack] 
[http://fs2source.warpcore.org/mediavp/mp-710_effects.rar Effects 710 patch] 
[http://fs2source.warpcore.org/mediavp/mp-710_models.rar Models 710 patch]

'''Other recommended''' downloads include:

[http://fs2source.warpcore.org/mvp368zeta/mv_adveffects.zip Advanced Effects] 
[http://fs2source.warpcore.org/mediavp/mp-710_adveffects.rar Advanced Effects 710 patch]

Mediavps should be installed in a new 'mediavps' directory under the main FreeSpace directory (\freespace2\mediavps) This preserves both possibility to play with either with retail FreeSpace 2 vp files if this is desired (for example in multiplayer) or using the retail FreeSpace 2 executive files and requires minimal extra time to set up. (See step six for further details).

[http://www.hard-light.net/forums/index.php/topic,39905.0.html MediaVP download page]

== Step Five: Configuring Everything ==

=== Basic setup ===

At this point, you have one final stage remaining before fs2_open is ready to go. Open up the Launcher. (It should be in your main Freespace 2 folder). Select the EXE you'd like to use by clicking the "Browse..." button at the top of the Launcher.

Next, ensure that the "Audio/Joystick" and "Network" tabs have the proper settings. (If you have trouble with your joystick not working properly in fs2_open, you may try the "Force 0" or "Force 1" options, which will force fs2_open to use the first or second joysticks, respectively.

=== Speech setup ===

If you are using Windows XP, or have the Speech API installed, fs2_open will be able to read briefings, techroom descriptions, and even ingame messages to you using computer-generated voices. Although no match for real voice acting, it is convenient when valid plot points are mentioned in the middle of combat. Speech in the various locations can be turned on and off by checking and unchecking the check boxes; you can choose which of the installed voices to use in fs2_open by changing the drop-down menu. As of this writing, fs2_open will only use the voice you choose for everything.

=== Video setup ===

On the "Video" tab, you can choose which API to use (OpenGL or Direct3D), what resolution to run in, and whether to use anti-aliasing (Multisampling) or not. With FreeSpace Open 3.6.9 '''OpenGL''' is strongly recommended over the Direct3D

"Allow non standard modes" will let you choose resolutions other than 1024x768 and 640x480. There may be some small graphics alignment errors, but these are generally small and virtually unnoticeable.

=== Features setup ===

This tab is where most of fs2_open's options can be toggled on and off. At the top is a readout of your current command line; you should include this in any debugging reports you make.

The next box, with the buttons "Select mod" and "No mod" allow you to choose a mod directory to use; files in the mod directory will be given precedence over other files, so you can easily switch between mods by installing them to different directories.

"Custom flags" allows you to add any command line flags that don't show up in the Launcher. This may be because they require additional arguments, as is the case with the "-fov" command line argument. For more information, see the [[Command-Line Reference]] page.

Finally, the two boxes below this let you toggle the various new features in fs2_open, many of which are graphical improvements. Recommended options for midrange systems are "Enable specular", "Enable glowmaps", "Enable jpg,tga textures", "Enable more realistic lighting", and "Load only used weapons". (You may have to choose a different section in the drop-down box to get to some of these days). There are many, many more options, but these should get you started.

[http://www.hard-light.net/wiki/index.php/Command-Line_Reference Command line Flags]

== Step Six: (Optional) Preserving Freespace 2 ==

At this point, if you try to start the original Freespace 2 executables, they'll likely crash at some point or other. To prevent this, do the following:

=== Move the mediaVPs to a mod dir ===
You can take advantage of the SCP's -mod feature and move the mediaVPs to a folder inside your main Freespace 2 folder; this folder can be named anything you like, such as "mediavps". However, whenever you run Freespace 2, you must remember to select that folder as the current mod. If you want to play another mod, you must make use of the SCP's multiple mod feature.

=== Save any existing pilot files ===
Fs2_open upgraded the pilot files to allow for better mod handling in version 3.6.5. To prevent double entries from showing up, a new, upgraded version of the pilot file is created, and then the old one is deleted. To save your progress, copy all *.plr, *.csg, and *.css files that start with your pilot name. Then, rename the copies so that they're in the form of <your name>_scp. For example, my player file would be called "WMCoolmon_scp.plr". Then, only use the "_scp" versions when running fs2_open.

It's recommended you back up the originals as well, in case you accidentally click on the non-SCP version while in the SCP. (It should warn you that it's going to destructively convert them, however.)

[[Category:Source Code Project]]