Endgame

2013-12-03T04:59:55Z

Annorax: added minor info after destroying Iceni and being stuck

{{Mission|next=The Fog of War|previous=The Sicilian Defense|campaign=FreeSpace 2 Campaign Walkthrough}}

'''ACT 2, MISSION 6'''

'''Fighter squadron:''' [[64th Raptors]]

'''Description:''' Alpha wing of the 64th is sent to assist the warships guarding the Knossos.

----
==Background==
[[Aken Bosch|Admiral Bosch]] orders the remnants of his fleet to enter the [[Knossos]] portal, guarded by a few GTVA warships. Most of the NTF ships are destroyed, but the [[FreeSpace 2 Rebel Ship Database#NTC Alexandria|NTC ''Alexandria'']] broke through and entered the node. Alpha wing of the 64th is now deployed to assist in the blockade and fend off any ships until the arrival of the GTVA Colossus.

==Walkthrough==
A recommended loadout is the [[GTF Pegasus]] armed with the [[GTW Prometheus S|Prometheus S]], a bank of [[GTM Harpoon|Harpoon]]s and a bank of [[GTM Tornado|Tornado]]s, but if the low firepower and weak armoring of the Pegasus does not suit your flying style, you can try something else, such as the [[GTF Myrmidon]].

This is the last mission against the [[Neo-Terran Front|NTF]]. As you jump in, you can see the [[FreeSpace 2 Terran Ship Database#GTCv Monitor|''Monitor'']], a [[GTCv Deimos|Deimos-class corvette]] in front of you, and the [[FreeSpace 2 Terran Ship Database#GTC Fortune|''Fortune'']], a [[GTC Fenris|Fenris cuiser]], a short distance behind. The [[Knossos]] subspace portal is also located in the background.

After a short conversation, in which is said that the [[GTVA Colossus|GTVA ''Colossus'']] has taken down the [[FreeSpace_2_Rebel_Ship_Database#NTC_Vanguard|NTC Vanguard]], the Monitor is attacked by NTF fighters and bombers. Prioritize the bombers; the fighters escorting the bombers are practically harmless. Shortly after, the [[FreeSpace 2 Rebel Ship Database#NTC Loyola|NTC ''Loyola'']], an [[GTC Aeolus|Aeolus-class cruiser]], enters the area and attacks the Monitor. Ignore it; the cruiser is very dangerous to fighters and it isn't too much trouble for the Monitor. You can accomplish your mission by defending the Monitor from the first wave of fighters.

When the first wave of NTF fighters go down, the [[GTVA Colossus|''Colossus'']] jumps in and stops in front of and directly above the Knossos. From here, you don't have to do much. If you have the mood to, you can engage the incoming [[GTB Medusa|Medusa bombers]] to get kills. When the [[GTCv Deimos|Deimos corvette]] [[FreeSpace 2 Rebel Ship Database#NTCv Danton|NTCv ''Danton'']] jumps in, do not engage it. The Colossus will have no problems making mincemeat out of it.

The [[NTF Iceni|NTF ''Iceni'']] jumps in shortly after the Danton's destruction, and you get orders to destroy it. At that crucial moment in time, however, the Colossus experiences a temporary malfunction in its fire control and is unable to attack, giving the Iceni a window to escape, which it does. After it jumps out, you are ordered to return to base.

==Tips==
*You can order both the GTC Fortune and GTCv Monitor around. This is useful because otherwise the former won't fire on NTF ships. Order the Fortune to attack enemy warships, and the Monitor to attack the Loyola, and things will move slightly faster.

==Notes==
*This is the only mission in the main FreeSpace 2 campaign where you can fly the Pegasus stealth fighter without modifying the mission file.
*A few oversights can be seen by opening this mission in FRED. In particular, messages regarding the Iceni and the Danton are defined, but not called during the mission.
*In the briefing, the GTCv Monitor is mispronounced as GTA Monitor by the voice actor.
*The return to base objective is triggered by the Iceni jumping out; if you somehow manage to destroy the Iceni, you will not get a return to base directive and will be forced to restart the mission.

==Notable ships present==
* [[FreeSpace_2_Terran_Ship_Database#GTC_Fortune|GTC Fortune]]
* [[FreeSpace_2_Terran_Ship_Database#GTCv_Monitor|GTCv Monitor]]
* [[GTVA Colossus]]
* [[FreeSpace_2_Rebel_Ship_Database#NTC_Loyola|NTC Loyola]]
* [[FreeSpace_2_Rebel_Ship_Database#NTCv_Danton|NTCv Danton]]
* [[NTF Iceni]]

==Technical information==
{{MissionInfo|SM2-06.fs2|69.8 KB|Brad Johnson|48 (1 waypoint)|9|55|28|6: Joshua|Brief6}}

==Videos==
===QuantumDelta===
 <videoflash>I_CAFtrWuNo</videoflash> 
===TheOneTrueRenairen===
 <videoflash>2OvTpiObidg</videoflash> 

[[Category:Main FreeSpace 2 Campaign]]

Guide to FS Open on Linux

2006-03-21T14:24:34Z

Annorax: /* Installing CVS */ Spelling cleanup, Ubuntu commands not "?"

This HOWTO was written by ni1s to help Freespace fans get the latest bleeding-edge version of fs2_open from CVS, and also includes an introduction to configuring and running fs2_open provided by Spectre-7.

''Note: This tutorial assumes some fundamental command line knowledge.''

== Installing CVS ==
CVS stands for Concurrent Versions System and is a version control system used to record the changes in documents, such as source files. Developers use CVS so they can easily share their code changes among other developers. You will need this tool to download ("checkout" in CVS termology) fs2_open from the CVS server.

'''Debian/Ubuntu''' users want to:
apt-get install cvs
'''Gentoo''' users want to:
emerge cvs

'''NOTE: Redhat, Mandrake/Mandriva, Slackware and all the other distros should go here too,'''
'''but we have no knowledge on how these work, so if you do, please enlighten us.'''

== Installing the nessesary development libraries ==
You will also need SDL, OpenAL, libvorbis and OpenGL(most likely provided with your videocard driver) development packages. And ofcourse the GCC compiler and required make tools.
 
'''Debian/Ubuntu?''' users want to:
apt-get install libopenal-dev libvorbis-dev build-essential automake1.9 autoconf libsdl-dev
'''NOTE:''' The ''build-essential'' meta package installs GCC4. This should work, but if you feel safer with GCC 3.4(gcc-3.4), add it to the apt-get line above. 
'''Gentoo''' users want to:
emerge openal libvorbis libsdl
'''NOTE: Radhat, Mandrake,Slackware and all the other distros should go here too,'''
'''but we have no knowlage on how these work, so if you do, please enlighten us.'''

== Installing game data files ==
''This is all very icky on Linux. Someone should really look in to this.'' 
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

== Using the source ==

=== CVS Checkout ===
Before you begin, make sure you are situated in a a directory where you have write permissons. Your /home/user/ directory is pretty much a sure 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.

Now get the source. Run from a terminal:
cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login
and then
cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open
The first cvs command 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. The second command tells the CVS server on which we are now connected to that we want to checkout (co) the fs2_open module.
 
==== CVS Checkout and Update Script ====
The code on CVS is in a constant state of change, and bugs that exist one day may be gone the next. Because of this, you'll want to occasionally update to a newer version and recompile.
Running those cvs commands will fast grow to be a pain, so this little script was created to make your life abit easier. This script will checkout fs2_open if it can't find a fs2_open directory and update fs2_open, if it finds it.
The script will run until a successfull checkout or update has been achieved.
Copy and save this to a suitably named file like "get_fs2_open", and make it executable with the command, chmod +x <name of file>
#!/bin/bash
# CVS Checkout and Update Script for fs2_open
CVS_LINE="cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot"
if [ "$UID" = 0 ]; then
echo "You are root. If this is a checkout, all files \
will be created with root as the owner."
sleep 3
fi
if [ -e ./fs2_open ]; then
echo "Found fs2_open, We are updating an old checkout."
CVS_ATTEMPT=0
until [ $CVS_ATTEMPT = 1 ]; do
$CVS_LINE login && \
$CVS_LINE update fs2_open && \
let CVS_ATTEMPT=1
done
else
echo "No fs2_open found, This is a new checkout."
CVS_ATTEMPT=0
until [ $CVS_ATTEMPT = 1 ]; do
$CVS_LINE login && \
$CVS_LINE co fs2_open && \
let CVS_ATTEMPT=1
done
fi

=== Pre-Compile Configuration ===

Before you compile you need to configure it for your system. Run from
In the directory you ran the CVS command from, a new directory will appear, namely fs2_open.
If your fs2_open is a completly new checkout, you will first need to run the autogen.sh script.
Run from inside your newly created fs2_open directory:
./autogen.sh
autogen.sh is a script that will generate the required makefiles. You will see alot of "checking for this" and "checking for that", this is actually the "configure" script (which can be run with <tt>./configure</tt> if you need to change the options) examining and configuring fs2_open for your system. 
It is possible to give autogen.sh configure options aswell, autogen.sh will pass them along to configure.

A full list of configure options can be found by running the configure script with the '--help' option.
./configure --help

==== Optimizing fs2_open ====
Optimizing fs2_open might have little or no effect, or improve performace greatly, I honestly have no clue. 
A note of caution, if you are compiling a debug build, don't use the -fomit-frame-pointer CFLAG, it will make debugging impossible. 
You can specify your compiler flags with the configure script, se below.
./configure CFLAGS="<your desired flags>"
If you got a Athlon-XP and want to play it safe, a good set of CFLAGS would be
./configure CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer"
You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links. 
http://gcc.gnu.org/onlinedocs/gcc-3.4.1/gcc/Optimize-Options.html 
http://linuxreviews.org/howtos/compiling/safe-cflags/ 
http://en.wikipedia.org/wiki/CFLAGS

=== Compiling ===

Run from within your fs2_open directory:
make
Sit back and enjoy gcc work its magic.

==== Simple Compile Script ====
It's alot easier to use a scripts when dealing with constantly changing code. Copy and save this to a suitably named file like "compile_fs2_open", and make it executable with the command, chmod +x <name of file>
This script assumes the CVS checkout directory fs2_open is pressent in the same directory as the script itself.
#!/bin/bash
# fs2_open Compile Script
# These are only examples, uncomment to enable optimization.
#MY_CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -ftracer"
if [ -e ./fs2_open/ ]; then
cd fs2_open
if [ -e ./configure ]; then
make clean
./configure CFLAGS="$MY_CFLAGS" CXXFLAGS="$MY_CFLAGS"
make
else
./autogen.sh CFLAGS="$MY_CFLAGS" CXXFLAGS="$MY_CFLAGS"
make
fi
else
echo "No fs2_open directory found."
fi

You can add your options to the ./configure line.

== Using the Binaries ==

When the compile is done and if all went well, a binary executable will reside in the code directory ''fs2_open_r'' or ''fs2_open_d'' if you configured for a debug build. Copy the binary to directory where Freespace2 is installed, and you're all set to go.

=== Post-Compile Configuration ===
==== Changing Your Resolution ====

Odds are, you'll want to run fs2_open in a higher resolution than the default 640x480. Unfortunately, we Linux users don't have the swank launcher app that the Windows folks do. Instead, we'll be making a couple line changes to a config file. You will need to run fs2_open once before you can make the necessary changes, otherwise you won't have a configuration directory to work with.

The first thing we need to do is get into the fs2_open config directory, which is a hidden folder in your home directory. The fastest way to get there is to type the following in a console:
cd ~/.fs2_open

From here, open up fs2_open.ini in your text editor of choice (vi, EMACS, joe, pico, etc). You'll see something like the following:
[Default]
VideocardFs2open=OGL -(640x480)x16 bit
LastPlayer=MonkeyboyS
GammaD3D=1.0

Then change the Videocard line to the following:
VideocardFs2open=OGL -(1024x768)x32 bit

Save the file, and run fs2_open as you normally would. Voila! You're now in 1024x768 at 32bit color. Congratulations!

=== Creating a Start Up Script ===

In order to use all of the advanced engine features of fs2_open, you'll need to start the executable with a number of command line arguments. Instead of typing them in every time you want to start the game, why not create a script that does it for you?

Create a new file named start_freespace (or whatever you like) in your home directory. Open the file in your editor of choice, and paste the following:
#!/bin/sh
cd /path/to/your/freespace/
fs2_open_r -spec -glow -mipmap -jpgtga -orbradar -mod Media_VP

''Note: You will need to edit this script before it will work properly. The second line must point to the directory where you installed fs2_open.''

The last line starts fs2_open with a number of arguments that turn on extra features. In the example, the game will use specular highlights, glow-mapping, mipmapping, jpg and tga graphic files, the orb radar, and any MediaVPs installed to the /Media_VP directory. You should edit this line to use those features that your system supports.

More information about the available Command Line Arguments can be found at the [[Command-Line Reference]]

Once you've edited the file to your heart's content, make it executable:
chmod +x start_freespace

You can now type in start_freespace to start the game, or by clicking on start_freespace in your window manager. For convenience, you can copy it to your Desktop.

== Troubleshooting ==
=== Compile Errors ===
==== OpenGL Compile Errors ====

On some Linux distributions (''Slackware'' for instance), compiling fails because a GL related library doesn't have a link in the <tt>/usr/lib</tt> directory. If the compile fails because it can't find <tt>-lGLU</tt>, here are two ways to fix it:

===== Solution as Root =====

If you have root access to the system, you can create a link to the library in question with just a little bit of command line magic. Go to a console and enter:

ln -s /usr/X11R6/lib/libGLU.so /usr/lib/libGLU.so

After that, you can run make again and it should finish compiling.

===== Solution as a Non-Root user =====

You don't have root access? Never fear, we can still fix the problem. It'll just be a tad more difficult.

Navigate to the <tt>fs2_open/code</tt> directory and locate a file named <tt>Makefile</tt> (not Makefile.rm or Makefile.in or Makefile.anything). Open it in your favorite text editor and make the following changes.

Find this line (line 457 in mine):
FS2_LDFLAGS = -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lGLU -lopenal -logg -lvorbis -lvorbisfile

And replace it with this:
FS2_LDFLAGS = -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lopenal -logg -lvorbis -lvorbisfile -L/usr/X11R6/lib -lGLU

Also find this one (line 565 in mine):
AM_LDFLAGS = -g -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lGLU -lopenal -logg -lvorbis -lvorbisfile

And replace it with this:
AM_LDFLAGS = -g -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lGL -lopenal -logg -lvorbis -lvorbisfile -L/usr/X11R6/lib -lGLU

Then run <tt>make</tt> from the <tt>fs2_open</tt> directory, and watch the magic happen.
=== Runtime Errors ===
==== ERROR: "Web cursor bitmap not found." ====
ERROR: "Web cursor bitmap not found. This usually means that the executable is being run outside the directory
you installed Freespace2 to. Please move the executable to that directory and try again" at graphics/2d.cpp:1402
A common error. This happens when fs2_open can't find the .vp files or that your user doesn't have the permissions to access them. If you are using a start up script(like the one found here) it's most likly the a permission problem.
Have your user take owenership of the .vp files, run as root:
chown <user> /path/to/vpfiles/ -R

FreeSpace Wiki - User contributions [en]

Endgame

Guide to FS Open on Linux