A Team Fortress mod on the Source Engine
A Team Fortress mod on the Source Engine (Source SDK 2006)
Fortress Forever must be compiled using Visual C++ 2005. The following instructions are an updated version of Microsoft's old Using Visual C++ 2005 Express Edition with the Microsoft Platform SDK guide
C:\Program Files\Microsoft Platform SDK\Bin
C:\Program Files\Microsoft Platform SDK\Include
C:\Program Files\Microsoft Platform SDK\Lib
VCProjectEngine.dll.express.config
file located in the \vc\vcpackages
subdirectory of the Visual C++ Express install location. Please make sure that you also delete the file vccomponents.dat
located in the %USERPROFILE%\Local Settings\Application Data\Microsoft\VCExpress\8.0
directory if it exists before restarting Visual C++ Express Edition.corewin_express.vsprops
file found in C:\Program Files (x86)\Microsoft Visual Studio 8\VC\VCProjectDefaults
.
corewin_express.vsprops
in the text editor of your choice.
AdditionalDependencies="kernel32.lib"
to
AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib"
corewin_express.vsprops
and select Properties. Open the Security tab and click the Edit... button. Select the Users (computername\User) group and check Write in the Allow column, then click OK twiceGame_Scratch-2005.sln
and run Build Solution
<SteamDirectory>\SteamApps\common\Fortress Forever\FortressForever\bin
The Microsoft registration servers for VC++ 2005 Express edition are no longer online, so the only way to register your copy is to edit the registry. Simply save the following text as register_vc.reg
and run it:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VCExpress\8.0\Registration]
"Params"="487A8D4D0000000001000000010000009F6A4D0000000000"
To start the game from within VS debugger, right click client_ff
or server_ff
project (whichever you are working on)
and click properties
. Navigate to the 'Debugging' section.
Set command to the 'hl2.exe' in your fortress forever installation directory. On a default steam installation it will look like this:
C:\Program Files (x86)\Steam\steamapps\common\Fortress Forever\hl2.exe
-game "FortressForever" -allowdebug -dev
C:\Program Files (x86)\Steam\steamapps\common\Fortress Forever\
(you will need to set this up for both client/server, or whatever you need to debug)
Now you can smack F5 to start the game with debugging ready to go. I recommend adding eg, +map ff_2fort
to parameters save time.
Here is an example with nonstandard steam path:
-allowdebug
in steam)hl2.exe
in the list and click Attach
fortressforever\bin\server.dll
and fortressforever\bin\client.dll
. If not, you'll probably need to copy the dump file to a directory containing the correct .dll and .pdb files for the version of the game that the crash occurred on.<SteamDirectory>/dumps
directory, and will be named something like assert_hl2.exe_<datetime>_1.dmp