Hard Light Productions Forums

Announcements => Getting Started => Topic started by: jg18 on October 20, 2011, 10:04:33 pm

Title: Instructions for manually installing FreeSpace Open and mods (Windows)
Post by: jg18 on October 20, 2011, 10:04:33 pm
This installation method is the one where you download everything yourself and then put things where they should go. It may sound scary, but it really isn't.

These instructions are for Windows only.

If you use Linux or Mac OS X, please see the other installation methods:


QUICK START

If you don't have FreeSpace 2, get it from Good Old Games (GOG) (http://www.gog.com/en/gamecard/freespace_2).

The instructions in orange are required. Everything else is optional.

If you encounter problems, please read the Troubleshooting FAQ (http://www.hard-light.net/forums/index.php?topic=56279.0).

Step 1) Install FS2
"C:\Games\FreeSpace2\" is the install location used by the original retail disc release of FS2.
The GOG version will default to installing to "C:\Program Files (x86)" (especially for 64-bit versions of Vista/Win 7) and we do not want that location.
Why? Because it's a protected operating system folder that is covered by UAC and will therefore make it very difficult, if not impossible, for you to use mods or make changes to your install.

Step 2) Get OpenAL

Step 3) Get the latest official FSO build and the launcher
In general, the FSO builds and the non-wxLauncher are the only things that should ever be added to the "root" FS2 folder unless otherwise mentioned.
If you want to try a more recent but possibly unstable build called a "nightly build," see the notes at the end.

Step 4) Move the cutscenes to \FreeSpace2\data\movies\
The other files in those two folders are unnecessary and can even cause problems.
Want to save a little disk space with the cutscenes? See the notes at the end.

Step 5) Set things up

If you don't want to download another 500 MB for the graphical enhancements right now, then just go and play using the retail assets and effects. Otherwise, continue to Step 6.

Step 6) Get the MediaVPs (recommended)

Hurray! You have now successfully installed FreeSpace Open.
NOW GO AND PLAY! :) You can read the rest later if you want.

2012-05-01: Added a note to the cutscene part that it is indeed possible for users to create new folders. --Jeff Vader
Title: Re: Instructions for manually installing FreeSpace Open and mods (Windows)
Post by: jg18 on November 14, 2011, 02:19:31 am
UPDATES AND MODS

To update FSO, the launcher, or the MediaVPs:

Installing mods
Note: Before installing mods, download and install 7-Zip (http://www.7-zip.org/download.html), which is a free program that will allow you to open the .7z and .rar file types that many mods use for their downloads.

Installing mods is very much like installing the MediaVPs. Any recent mod should have accurate installation instructions in its release thread, but if this is not the case, or if you run into problems, you can always follow the instructions below.

Important: To keep your pilot files from getting corrupted, create a new pilot for every mod that you play. At the first menu that appears when you start FSO, either create a new pilot or clone an existing one. Cloning a pilot copies the pilot's settings (including key bindings) but not its stats.

Also important: When you start the game, go to the campaign room and select the mod's campaign (in this example, the Wings of Dawn campaign), because the main FS2 campaign is selected by default.
Title: Re: Instructions for manually installing FreeSpace Open and mods (Windows)
Post by: jg18 on November 14, 2011, 02:20:26 am
NOTES

Everything in this section is optional.

If you must install FS2 to somewhere other than C:\Games\FreeSpace2\
Note that

Nightly builds
If you want to try the Source Code Project's latest version of FreeSpace Open, grab the latest nightly build from the nightly builds board (http://www.hard-light.net/forums/index.php?board=173.0). The most recent versions of FSO might have new features, bug fixes, or even improved performance, but they might also have new bugs. If you see SSE or NO_SSE and don't know what they mean, see the release thread (http://www.hard-light.net/forums/index.php?topic=83889.0) for an explanation.

You'll need to download and install 7-Zip (http://www.7-zip.org/download.html) to uncompress the nightly builds download. Once you've downloaded your build of choice, find it in Windows Explorer, right-click on it, select 7-Zip then "Extract files...", click on the "..." button on the right, choose your FreeSpace 2 directory, then click OK.

Saving a little space with the cutscenes
Download the cutscenes in .ogg format (http://www.freespacemods.net/download.php?view.128), put them in \FreeSpace2\data\movies\, and either delete the .mve files or move them to somewhere else. Note that the .ogg cutscenes only work with FSO; retail FS2 requires the .mve files.

FSO build differences (or what the "DEBUG" means)
When viewing the builds in your \FreeSpace2\ folder, you'll notice that there always seems to be a pair of builds, with a difference of a few characters between them. If the file name contains the word "DEBUG", it means that that build is a "debug" build (for example, fs2_open_3_6_18_DEBUG.exe). Debug builds are used for generating debug logs (called fs2_open.log) (http://www.hard-light.net/forums/index.php?topic=56279.msg1180359#msg1180359) when you run into problems using FSO. They are NOT meant for casual playing. Also, contrary to popular belief, debug builds do NOT magically solve whatever problem you're facing.

The builds that are not debug builds are "release" builds. Release builds have file names where the "DEBUG" is missing (for example, fs2_open_3_6_18.exe). Release builds are the ones that you should be using if all you want to do is play the game. So unless you need to generate a debug log, go for a "release" build, NOT a debug build.


Thanks to Fineus and Jeff Vader for writing an earlier version of these instructions.
Special thanks to jr2 for his help with revising the previous version and for pointing out that the instructions needed to be rewritten.
Special thanks also to Zacam for his help with writing the Quick Start.