Obsidian Conflict Wiki - User contributions [en]

Dedicated Server Setup 2

2012-08-07T01:38:11Z

TESLA-X4: Updated to address minor change to SRCDS

{{wip}}
This page was created since I can't update the one [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths (i.e. <tt>orangebox/hl2</tt> refers to the folder <tt>hl2</tt> ''inside'' <tt>orangebox</tt>, not both the folders), and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
||''This could help : <nowiki>http://planethalflife.gamespy.com/View.php?view=HL2Guides.Detail&id=4&game=3</nowiki>''|.
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Merge the two <tt>hl2</tt> folders by copying the contents of the <tt>hl2</tt> folder (the one outside) into the <tt>orangebox/hl2</tt> folder. This may take a while since it totals to about 1.5 GBs.

If you're impatient or tight on time / space, consider doing the inverse instead, i.e. moving the <tt>orangebox/hl2</tt> to the <tt>hl2</tt> folder (the one outside), and then moving that folder back into the <tt>orangebox</tt> folder. This will be significantly faster since move operations are faster than copies.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>xcopy /s /e hl2 orangebox\hl2</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>cp -R hl2 orangebox/hl2</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators with Remote Desktop access to their servers since they can simply install Steam on their servers and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half-Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V {{Todo|Further elaboration needed.}}
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

==Additional Game Content==
'''Note:''' If you download any of the following (sans ''Portal'') using the ''HLDS Update Tool'' after downloading <tt>orangebox</tt>, <span style="color:red;">you will be forced to download a new set of engine binaries incompatible with the current release of Obsidian Conflict</span>. A telltale sign that this has occurred is when you see an engine error along the lines of ''SetupArrayProps_R: array prop '(null)' is at index zero'' or ''Host_Error: IDLLFunctions::DLLInit returned false'' when you try to start the server. To workaround that, simply rename the <tt>bin</tt> folder (inside <tt>orangebox</tt>) to something else (e.g. <tt>bin_se2007</tt>) '''before''' downloading the game's files. On completion, delete the newly created <tt>bin</tt> folder and rename the old one back to <tt>bin</tt>.

For the curious, the reason for this is that almost all official Valve games now run on [http://developer.valvesoftware.com/wiki/Source_Engine_2009 Source Engine 2009], but most mods (sans ''Garry's Mod'') continue to run on the older ''Source Engine 2007'' (Source SDK Base 2007). These two versions are incompatible with each other, and Valve has yet to release a version of ''Source SDK Base'' for ''Source Engine 2009''.
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

==Downloading And Installing Obsidian==
Copy the <tt>obsidian</tt> folder from a fresh install of Obsidian Conflict into your dedicated server's <tt>orangebox</tt> folder.
{{Todo|Further elaboration needed.}}

==Mounting Content==
Content mounts are controlled by a set of files in the <tt>obsidian/mount</tt> folder. Each file determines whether or not the respective game's content is mounted. These files are merely blank files without any extensions - their contents do not matter since the mod merely checks if the file is there, mounting the content if the file is present.
Valid file names are:
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
<tt>css</tt> ↔ Counter-Strike: Source

<tt>dod</tt> ↔ Day of Defeat: Source

<tt>ep2</tt> ↔ Half-Life 2: Episode Two

<tt>episodic</tt> ↔ Half-Life 2: Episode One

<tt>hls</tt> ↔ Half-Life: Source

<tt>lostcoast</tt> ↔ Half-Life 2: Lost Coast
</div>
{{Todo|Further elaboration needed.}}

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

[[Category:ServerOP]]

How to make OC playermodels

2012-04-10T15:44:16Z

TESLA-X4:

Originally written by [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=458 fug4life], with tips and tricks from [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=1667 Maestro Fénix] and [http://obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=1305 TESLA-X4].

In this tutorial, you will learn how to make a player model for Obsidian Conflict.

==Prerequisites==

*'''Source Development Kit (Source SDK)''': Available in ''Steam → Library → Tools''. This is required as a base for the model decompiler program, and to recompile models.

*'''GCFScape (Optional, unless you intend to modify a model from an official Valve game)''': Allows you to browse and extract the contents of [http://developer.valvesoftware.com/wiki/GCF Game Cache Files (GCFs)]. http://nemesis.thewavelength.net/index.php?p=26

*'''MDLDecompiler''': Self-explanatory. http://www.chaosincarnate.net/cannonfodder/mdldecompiler.php

*'''GUI StudioMDL''': This program is a GUI front end for the [http://developer.valvesoftware.com/wiki/Studiomdl Studiomdl] tool in the Source SDK. http://www.wunderboy.org/apps/guistudiomdl2.php

*'''Notepad++ (Optional only for models for [http://developer.valvesoftware.com/wiki/Source_Engine_2006 Source Engine 2006] and below)''': You can use this or any other hex editor. http://notepad-plus.sourceforge.net/uk/site.htm

*'''VTFEdit''': http://nemesis.thewavelength.net/index.php?c=178

*'''An Image Editor''' (such as ''Paint.NET'', ''Adobe Photoshop'', ''Paint Shop Pro'' or others).

==Preparing The Materials==
First, you will need to create the folder of the new model that you are going to make. Go to your client's <tt>obsidian</tt> folder (inside <tt>Steam/steamapps/sourcemods</tt> for the uninitiated) and proceed to navigate to <tt>materials/models/player</tt>. Create a new folder (with the name of your model) inside this folder (right-click an empty area → ''New'' → ''Folder''). Copy your model's materials into the new folder you created, then open their <tt>.vmt</tt> files.

You should see something like this, in typical [http://developer.valvesoftware.com/wiki/KeyValues KeyValues] format:
<pre>"VertexLitGeneric"
{
"$baseTexture" "Models/player/Mossman/mossman_sheet"
"$envmap" "env_cubemap"
"$bumpmap" "models/player/Mossman/Mossman_normal"
"$normalmapalphaenvmapmask" "1"
"$envmapcontrast" ".20"
"$envmapsaturation" "0.9"
"$envmaptint" "[ .36 .36 .36 ]"
"$halflambert" "1"
"$nodecal" "1"
}</pre>

Go to the <tt>$baseTexture</tt> line, and change <tt>Models/player/Mossman/mossman_sheet</tt> to point to where your textures (i.e. the [http://developer.valvesoftware.com/wiki/VTF .vtf]s) are located.
In the case of the above example, it would become <tt>Models/player/<span style="color:red;"><your model name></span>/mossman_sheet</tt>, where <tt><span style="color:red;"><your model name></span></tt> is the name of your model.

We're not done yet - you will also need to replace all occurences of <tt>Models/player/Mossman/</tt> with <tt>Models/player/<span style="color:red;"><your model name></span>/</tt> in that <tt>.vmt</tt> file. To illustrate, in the above example, the line <tt>$bumpmap</tt> also needs to be changed from <tt>models/player/Mossman/Mossman_normal</tt> to <tt>models/player/<span style="color:red;"><your model name></span>/Mossman_normal</tt>.

'''Note:''' If you reference an invalid path, your model will have the infamous error texture (a purple and black checkerboard texture will be seen instead of the original).

After you have modified all the <tt>.vmt</tt> files for your model, you are ready to convert the model for use as a player model.

==Converting The Model==
Go to the model files, and open the [http://developer.valvesoftware.com/wiki/MDL .mdl] file with ''Notepad++'' (or your favorite hex editor). The first four bytes in the file should be <tt>IDST</tt> (hexadecimal sequence: <tt>0x49</tt>, <tt>0x44</tt>, <tt>0x53</tt>, <tt>0x54</tt>). Now, verify that the fifth byte (immediately after the <tt>T</tt>) is a <tt>,</tt> (comma, hexadecimal: <tt>0x2C</tt>). If it is, then you can safely close the program; nothing else needs to be done. If it is something else, such as a <tt>0</tt> (zero, hexadecimal: <tt>0x30</tt>) or a <tt>-</tt> (minus sign, hexadecimal: <tt>0x2D</tt>), you will need to change it back to a comma (i.e. <tt>IDST0</tt> → <tt>IDST,</tt>).

'''Note:''' This workaround is required because the model decompiler was written before games on [http://developer.valvesoftware.com/wiki/Source_Engine_2007 Source Engine 2007 and 2009] were released, and was never updated for forward compatibility by its author.

Open ''MDLDecompiler'', then select the model that you wish to decompile and select the folder where you wish to put the decompiled files. After starting the decompile process, wait for a prompt to appear, informing you of a successful recompile.

'''Note:''' If the decompiler crashes for some unknown reason, attempt another 3-4 tries. If it still fails to work, you may wish to attempt to decompile it with [http://www.chaosincarnate.net/cannonfodder/cftools.php?program=studiocompiler StudioCompiler], or [http://developer.valvesoftware.com/wiki/User:Erix920 Erix920]'s [http://kathar.net/other/mdldecompiler.exe modified version of MDLDecompiler] instead.

<span style="color:red;">'''Additional Note:''' In certain cases, MDLDecompiler will seem to work perfectly fine - no crashes or error messages are generated - but will actually generate corrupted [http://developer.valvesoftware.com/wiki/SMD .smd] files, which when viewed in a modeling program such as ''XSI Mod Tool'' will have no mesh at all. A telltale sign of this is when the file sizes of most of the <tt>.smd</tt> files are unusually small (< 1 MB), coupled with an unusually large physics model <tt>.smd</tt> (> 1 MB). There is no known solution for this issue at the time of writing, apart from contacting the creator of the model and asking (nicely!) for the model sources.</span>

Go to the folder where the resulting files are. You will see several files with the <tt>.smd</tt> extension and a file <tt>mdldecompiler.qc</tt>. Open the [http://developer.valvesoftware.com/wiki/Qc .qc] file with ''Notepad++'' or your favorite text editor, for example Wordpad (but not a word processor like ''Microsoft Word''!).

This script file determines the Studiomdl configuration for the model. A snippet is provided below:

<pre>$cd "C:\Users\User\Desktop\New folder"
$modelname "player\Flandre.mdl"
$model "body" "ref.smd"
$cdmaterials "models\player\Flandre\"
$hboxset "default"
// Model uses material "txFlanFace.vmt"
// Model uses material "txFlandre.vmt"
$includemodel "player/female_shared.mdl"
$includemodel "player/female_ss.mdl"
$includemodel "player/female_gestures.mdl"
$includemodel "player/female_postures.mdl"
$surfaceprop "flesh"
$illumposition 0.016 0.578 34.522
$sequence ragdoll "ragdoll" ACT_DIERAGDOLL 1 fps 30.00
$ikchain rhand ValveBiped.Bip01_R_Hand knee 0.707 0.707 0.000
$ikchain lhand ValveBiped.Bip01_L_Hand knee 0.707 0.707 0.000
$ikchain rfoot ValveBiped.Bip01_R_Foot knee 0.707 -0.707 0.000
$ikchain lfoot ValveBiped.Bip01_L_Foot knee 0.707 -0.707 0.000
$collisionjoints "phymodel.smd" {

$mass 60.0
$inertia 10.00
$damping 0.01
$rotdamping 1.50
$rootbone "valvebiped.bip01_pelvis"
$jointmerge "ValveBiped.Bip01_Pelvis" "ValveBiped.Bip01_Spine1"
</pre>

A breakdown of the important components of the script:

*<tt>$cd</tt>: A pointer to the folder where the <tt>.smd</tt> files reside in. If you moved these files elsewhere after decompiling the model, modify this to reflect that change.

*<tt>$modelname</tt>: This command determines where the resulting model will be placed in, with respect to the <tt>models</tt> folder. Using the above snippet as an example, the resulting (compiled) model will be located at <tt>models/player/Flandre.mdl</tt>.

*<tt>$cdmaterials</tt>: A pointer to the folder where the materials for the model reside in, with respect to the <tt>materials</tt> folder. Using the above snippet as an example, the full path will be <tt>materials/models/player/Flandre/</tt>. Ensure that the path is valid or your model will end up with purple and black checkerboard textures instead.

*<tt>$includemodel</tt>: This command determines which model files are 'included' into the model. In layman's terms, this determines which animation libraries are referenced by the model. An Obsidian Conflict player model requires a different set of animation libraries depending on the character's gender:
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a male model''':<br />
<tt>$includemodel "player/male_shared.mdl"<br />
$includemodel "player/male_ss.mdl"<br />
$includemodel "player/male_gestures.mdl"<br />
$includemodel "player/male_postures.mdl"</tt>
</div>
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a female model''':<br />
<tt>$includemodel "player/female_shared.mdl"<br />
$includemodel "player/female_ss.mdl"<br />
$includemodel "player/female_gestures.mdl"<br />
$includemodel "player/female_postures.mdl"</tt>
</div>

*<tt>$surfaceprop</tt>: Used to define the physical surface properties the model will have. The default is <tt>flesh</tt> (organic-human). The complete list is available [http://developer.valvesoftware.com/wiki/Material_surface_properties here].
'''Note:''' If this command was used in the <tt>.vmt</tt> files to define multiple surface types and is also present in the <tt>.qc</tt> script, the values set in the <tt>.vmt</tt> files will be ignored. If this behavior is not desired, either delete this command from the <tt>mdldecompiler.qc</tt> script, or specify the value as <tt>default</tt> instead.

This is all that you will typically need to modify in order to make a player model compatible with Obsidian Conflict.

==Finishing Touches==
Save the script file and open ''GUI StudioMDL''. Select <tt>OrangeBox</tt> for <tt>SDK Version</tt> and for <tt>Target Mod or "GameInfo" path</tt> select <tt>Obsidian Conflict</tt> (you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this). Go to ''File'' → ''Load .qc file'' and load the <tt>.qc</tt> file, then click on the <tt>Compile</tt> button.

When ''GUI StudioMDL'' finishes compiling the model (you should see <tt>Completed "mdldecompiler.qc"</tt>), open the ''Source SDK'', select <tt>Source 2007</tt> in the <tt>Engine Version:</tt> combo box and select <tt>Obsidian Conflict</tt> in the <tt>Current Game:</tt> combo box (once again, you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this), then click on <tt>Model Viewer</tt>. When ''Half-Life Model Viewer'' loads up, go to ''File'' → ''Load model...'' and select your model.

If all went well, you should now see your model, complete with working animations.

Once you have verified that your model is in working condition, go to where the model files are located in your client's folder and create a new text file with the name of your model, but with the <tt>.txt</tt> extension. Using the previous snippet as an example, the file would be <tt>models/player/Flandre.<span style="color:red;">txt</span></tt>.
Paste the following inside the file (don't forget to alter the gender of the <tt>base model rig</tt> and <tt>voice</tt> as necessary):
<pre>ModelSettings
{
//Use this option to choose a base script to use instead.
"usefile" "none"

//Base model rig to use (doubles up as a fallback if loading fails). Use either Male_01 or Female_01 for best results.
"basemodel" "Male_01"

//Voice Sound 0=none, 1=male, 2=female, 3=combine
"voice" "1"

//Footstep Sound 1=shoe, 2=combine boots
"footsteps" "1"

//Gibs, 1 = generic human, 2 = generic alien, 3 = human rebel ragdoll gibs, 4 = Ragdoll only
"Gibs" "4"

//Determines if this model should be considered anime-related, 0 = no, 1 = yes
"anime" "0"
}</pre>
With this file, you can configure the voice, footstep sounds and gibs of the model.

<span style="color:red;">'''Note:''' At the time of writing, the <tt>anime</tt> keyvalue is ignored. It will only take effect with the next release of Obsidian Conflict, but applying it now is highly recommended for forward compatibility.</span>

Finally, head over to <tt>obsidian/materials/VGUI/playermodels/player</tt> and create a new <tt>.vmt</tt> and <tt>.vtf</tt> file with the same name as your model's <tt>.mdl</tt> file.

'''Note:''' The path after <tt>obsidian/materials/VGUI/playermodels/</tt> '''must''' reflect the path to the model, i.e. if the model is at <tt>models/player/somemodelname/somemodel.mdl</tt>, the two files will be <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vmt</tt> and <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vtf</tt>.

In the <tt>.vmt</tt> file (you can make a copy of an existing one and clear it for use), paste the following:
<pre>UnlitGeneric
{
"$translucent" "1"
"$basetexture" "vgui\playermodels\player\Hostage_01"
"$vertexcolor" "1"
"$vertexalpha" "1"
"$no_fullbright" "1"
"$ignorez" "1"
"$decalscale" "0.250"
}</pre>

On the <tt>$basetexture</tt> line, change <tt>Hostage_01</tt> to point to your accompanying <tt>.vtf</tt> file.

To create that <tt>.vtf</tt> file, take a screenshot in ''Half-Life Model Viewer'' then save it as a <tt>.tga</tt> file and open that in ''VTFEdit'', then save it in the <tt>.vtf</tt> format. Give it the same name as your model.

Once you have placed the two files into your client's <tt>obsidian/materials/VGUI/playermodels/player</tt> folder, test it all out in-game. If all works well (animations, textures, sounds, preview image), pat yourself on the back - you've successfully created a new player model.
*To test the model's preview image, start the game, then go to <tt>Options</tt> → <tt>Multiplayer</tt> tab, and select your model from the combo box.
*To test the model's animations and textures, select the model, then start a local server and turn on <tt>sv_cheats</tt>. Execute the <tt>thirdperson</tt> command.

== Extra ==

OC playermodels are compatible with faceposing, jigglebones and particles. If your model have them, you will be able to see their effects in game. Also, in the next version, it will support multiple skins and bodygroups.

==Tips And Tricks==
===Creating The VGUI Preview Image===
====Using Paint Shop Pro====
You will also need to download and install a [http://nemesis.thewavelength.net/index.php?p=39 VTF Plugin for Paint Shop Pro] beforehand (Information about how to use it and what programs can use it [http://developer.valvesoftware.com/wiki/Photoshop_VTF_Plugin here]).

So, Open Paint Shop Pro and open the screenshot (.tga file) you took in SDK Model Viewer earlier.
(Prefebably you want the model holding an oc weapon and you can use centre view to get the model where you want it.
To look around in SDK Model Viewer use: Right mouse click - zoom in/out.
Left mouse click to rotate. Hold shift and use left click mouse to move the model up/down/left/right).

Also in Paint Shop Pro it helps to add a grid (view/grid, size dosen't matter)it just helps when working.

So lets move on to converting/working on the screenshot.

First we will use the Crop tool to cut the picture just so that we have the top half of the body. Make sure you use free form and have the box size that you are cropping set to 256x200, position in the centre of the top half of the body (showing the head, chest and shoulders), and then crop.

Now, click layers and select new mask layer/show all.

You will see the picture has a mask-raster 1 layer, right click and select delete and then yes.

Select the Magic Wand tool set up with something like mode = replace
matchmode = RGB value tolerance = 1 use all layers and use contiguous also use Anti-alias and select outside from dropdown box.
Click on the background on the image and not the model to use the Magic Wand.
(Baically you want to delete the back ground and not the model itself).
So if the the whole box and around the model is selected, its ok to delete.

Once the background is deleted, with the Magic Wand tool still open change the matchmode to = All opaque and this time click on the model in the image and it should change the Magic Wand from around the edges and around the model to actually now just around the model only.

Click layers select new mask layer/form image, make sure source opacity is checked and everything else is unchecked, click ok.

Now we are going to cut the highlighted model onto a new image. So with the Magic Wand still highlighting around the model on the image change to the Pan tool and right click on the highlighted model and select: copy merged.

Go to File and create a new image with these properties:

<pre>width =256 pixels
height =256 pixels
resolution =72,000 pixels/inch</pre>

Choose Rastor Background
image depth =RGB - 8bits/channel

And check the Transparent box.

Paste your copied image onto your new image, so, right click on your new image and paste as a new selection. Position into the top left hand corner as much as possible and then just left click.

Now we need to give an alpha channel so go to selections select load/save selection and choose save selection to alpha channel and clcik ok/save in the pop-up.

Finally now click File and save copy as and name it Hostage_01.png using the .PNG file format and press yes to the pop-up. (this is so you have a nice image to upload to the forums).

Click File and save copy as again and this time name it nameofthemodel.vtf using the .VTF file format and press yes/ok to the pop-up.

It´s time to use the VTF plugin. Set the properties as:

<pre>Template = Compressed Texture With Alpha
Format = DXT5 (Common Format)
Mipmap Filter = Box
Sharpen Filter = Sharpen Soft</pre>

Check/tick Mipmaps and Thumbnail.

And from the list just make sure Eight Bit Alpha (Format Specific) and Nice Filter are both checked/ticked. Everything else should be unchecked/unticked, then press ok.

Finally add it to your obsidian/materials/VGUI/playermodels/player directory to finish.

Example image:

[[File:Hostage01.png|frame|Example image: Hostage_01]]

====Using Paint.NET====

# Get the image (you know, "impr. pant" or another way to take a photo of your model).
# Prepare the image. If you are used "impr. pant", use the rectangule selection and select "cut selected" (after go to edit->paste as a new image). Only will have the image that it was inside of the rectangule. Use the "wand" tool and put the tolerancy level to 10% or less. Delete everything that surround the model.
# Go to "Image" and select "change size". Deactivate "keep relation size" and set the image in 200x200.
# Back to "Image" and select "change canvas size". Set 256x256 and select "upper left position".
# Save the image in .tga format with the name of the model.
# Drag and drop the .tga file into VTFedit. Press "ok" and save as .vtf format. Must have the same name of the model.
# Create the .vmt coping another .vmt from the materials/VGUI/playermodels/Player folder if you don´t want write it, change the directory of the image and put it in materials/VGUI/playermodels/Player.
# Sucess.

===Fixing the facemap bug===

Some models like [http://img17.imageshack.us/img17/7545/badfacemap.jpg this] can present this bug after compiling the model. To fix this, go to the materials folder and edit the facemap material VTF (this model in particular uses the: art_facemap.VTF).

You will need to use the VTF Edit program to open the art_facemap.VTF file.

Once in the program and file is open, under the 'Image' tab is a list of check boxes, we need to un-check (un-tick). The: <tt>Clamp S</tt> and the <tt>Clamp T</tt> parameters. Save the file and check back in SDK Model Viewer by 'refreshing' the model and you'll see the face is now fixed.

===Recommendations===

All this tutorial is made for models with the Valvebiped skeleton (a.k.a. HL2 biped skeleton). If the model have different names in the bones or a different structure of the skeleton it will give problems.

In this case, open the refencial SMD file of the model in a Model editor program such as 3DS Max, XSI, Blender or others, and fix it changing the name of the bones or directly re-rigging the model with a new skeleton.

After do this, remember modificate too the phymodel and the ragdoll (and the animations file if the model have too).

If you are making a playermodel directly from a ragdoll (a model that doesnt have a HL2 skeleton), and you have problems when you try compile it, try adding the following to the .qc file:

<pre>$poseparameter move_yaw -180.00 180.00
$poseparameter body_pitch -90.00 90.00
$poseparameter body_yaw -90.00 90.00

$attachment "grenade0" "ValveBiped.Bip01_Spine" 5.99 0.39 7.59 rotate 76.91 71.22 57.14
$attachment "grenade1" "ValveBiped.Bip01_Spine" 6.24 -2.34 6.66 rotate 62.97 100.42 87.46
$attachment "grenade2" "ValveBiped.Bip01_Spine" -0.35 2.21 -8.34 rotate -75.89 92.68 95.17
$attachment "grenade3" "ValveBiped.Bip01_Spine" 1.22 -1.11 -7.34 rotate -78.22 82.38 102.13
$attachment "pistol" "ValveBiped.Bip01_R_Thigh" 0.05 3.84 -6.30 rotate 0.08 -2.59 79.96
$attachment "primary" "ValveBiped.Bip01_Spine2" 10.44 -5.10 -4.88 rotate -11.71 179.79 3.52
$attachment "defusekit" "ValveBiped.Bip01_Pelvis" 0.00 1.22 -6.66 rotate -73.06 90.93 179.75
$attachment "eholster" "ValveBiped.Bip01_L_Thigh" 5.36 0.02 4.90 rotate 8.31 -91.56 99.67
$attachment "lfoot" "ValveBiped.Bip01_L_Foot" -0.00 5.20 -0.00 rotate -0.00 0.00 -0.00
$attachment "rfoot" "ValveBiped.Bip01_R_Foot" 0.00 5.20 0.00 rotate 0.00 0.00 0.00
$attachment "muzzle_flash" "ValveBiped.Bip01_L_Hand" -0.00 -0.00 -0.00 rotate 0.00 -0.00 -0.00</pre>

Not always fix the problem, but at least you will have an another chance to get it work.

If HLMV (Half-Life model view) crashes when you load your model, try compiling it without the animations (add // or delete the lines of $$includemodel). You will be able to see it (but without animations), useful to search possible bugs. Normally, this happen when the skeleton isnt the HL2 biped type, or if you committed an error when you rigged the model.

If your model is invisible in HLMV (completely, doesnt proyect shadow), there is a problem with the rig of the model. Try re-rigging it again.

If only when the model got the "ragdoll" pose, and when you go to the "physics" tab, the model is screwed, then you will have to remade again the ragdoll SMD file (get the original referencial model, and export it to SMD as a sequence).

This [http://kathar.net/hl2modding/errors.php page] it will be very useful if you have an error with some of the programs that we use in this tutorial. It explains all about the problem, why it happens and how to fix it.

To add jigglebones to a model, follow this [http://www.youtube.com/watch?v=tmfK-xlNn88 video]. More information about $jigglebone command [http://developer.valvesoftware.com/wiki/$jigglebone here].

If you have the following error when you are compiling the model in GUIStudioMDL:

<pre>ERROR: Too many materials used, max 32</pre>

Significates that you reach the limit of textures of the model. Try deleting the bodygroups of the model (if it have) or re-make the UVmapping.

If you use 3DS Max to modify a model, remember check in the SMD exporter plugin <tt>alternate normals export method</tt> to avoid make your model "polygonal". [http://img585.imageshack.us/img585/2839/21223383.jpg example photo] (only when you are going to export the referencial model, for the ragdoll use the <tt>sequence</tt> option).

If you are going to do a model hack (for example, using the head of a model in a different body), it must have both the same skeleton. If not, remember rig the new part, or you will get bugs like [http://img543.imageshack.us/img543/5624/56712636.jpg this].

If you made a phymodel ([http://developer.valvesoftware.com/wiki/Jointed_collision_model Collision model]), remember rig it with the skeleton, or you will have [http://img228.imageshack.us/img228/2781/33368549.jpg this bug].

Just before start the rigging of a model, make sure that the skeleton and the mesh are correctly sized. Use the male_01 or female_01 reference (copy the original model to another folder, decompile it and compare the referencial model inside your model editor with your model). A wrong size will cause deformations on the model like [http://img63.imageshack.us/img63/518/10321754.png this].

Don´t know about how to rig models? No problem, follow the complete guide about how to do it made by MarioKart64n [http://www.facepunch.com/showthread.php?t=542906 here].

Ask '''always''' permission if you are going to port/modify a model created for another person. If he/she accepts your request, don´t forget give credit him/her.

If after all you continue having problems or doubts about something, go to the forums to ask help ([http://obsidianconflict.net/forums/viewforum.php?f=7 Modeling help forum]). We will be always give you help (if you first respect us, obiously).

[[Category:Miscellaneous_Tutorials]]

Obsidian Conflict FAQ

2011-12-28T03:07:16Z

TESLA-X4: Added SetupArrayProps_R engine error article to page

{{Languages}}

{{catup|Obsidian_Conflict|Obsidian Conflict|center}}
This is a directory of Frequently Asked Questions about [[Obsidian_Conflict|Obsidian Conflict]].

== Setting Up Obsidian Conflict ==

* [[Obsidian_Conflict_Setup|How do I play other games in Obsidian Conflict (mount games)?]]
* [[Supported_Games|What games can I play cooperatively in Obsidian Conflict?]]

== General Troubleshooting ==
* [[Lobby_Map_Error|Why does a map not load in the lobby?]]
* [[FAQ_More_Help|Where can i look for more help?]]
* [[Bug_Report|I found a bug or crashed. How can I report it?]]

== Common Error Messages ==
* [[MountFilesystem_Failed|MountFilesystem( ### ) failed: SteamMountFilesystem(###,###,###) failed with error]]
* [[Invalid_Steam_ID_Ticket|Invalid STEAM UserID Ticket]]
* [[Account_Used_In_Another_Location|Disconnect: This Steam account is being used in another location]]
* [[SetupArrayProps_R:_array_prop_'(null)'_is_at_index_zero|SetupArrayProps_R: array prop '(null)' is at index zero]]

== General Obsidian Conflict information ==

SetupArrayProps R: array prop '(null)' is at index zero

2011-12-28T03:03:21Z

TESLA-X4: Created page with "==Definition== If you get this engine error after startup, you're starting ''Obsidian Conflict'' with the incorrect set of engine binaries (for the curious, ''Source Engine 2009'..."

==Definition==
If you get this engine error after startup, you're starting ''Obsidian Conflict'' with the incorrect set of engine binaries (for the curious, ''Source Engine 2009'' instead of ''Source Engine 2007''. ''Obsidian Conflict'' runs on ''Source SDK Base 2007'' since Valve has yet to release ''Source SDK Base 2009'' for public consumption).

==Resolution==
To resolve this issue, open <tt>gameinfo.txt</tt> ('''not to be confused with <tt>[[Obsidian SDK Setup|gameconfig.txt]]</tt>''') inside your client's <tt>obsidian</tt> folder (inside <tt>Steam/steamapps/sourcemods</tt> for the uninitiated).
You should see the following:
<pre>"GameInfo"
{
game "Obsidian Conflict 1.35"
title "OBSIDIAN CONFLICT 1.35"
title2 "OBSIDIAN CONFLICT 1.35"
type multiplayer_only
nomodels 0
nohimodel 1
nocrosshair 1
hidden_maps
{
"test_speakers" 1
"test_hardware" 1
}

developer "Obsidian Conflict Team"
developer_url "http://obsidianconflict.net"
manual "http://wiki.obsidianconflict.net"
icon "resource/obsidian"

FileSystem
{
SteamAppId 218 // This will mount all the GCFs we need (240=CS:S, 220=HL2).
ToolsAppId 211 // Tools will load this (ie: source SDK caches) to get things like materials\debug, materials\editor, etc.

//
// The code that loads this file automatically does a few things here:
//
// 1. For each "Game" search path, it adds a "GameBin" path, in <dir>\bin
// 2. For each "Game" search path, it adds another "Game" path in front of it with _<langage> at the end.
// For example: c:\hl2\cstrike on a french machine would get a c:\hl2\cstrike_french path added to it.
// 3. For the first "Game" search path, it adds a search path called "MOD".
// 4. For the first "Game" search path, it adds a search path called "DEFAULT_WRITE_PATH".
//

//
// Search paths are relative to the base directory, which is where hl2.exe is found.
//
// |gameinfo_path| points at the directory where gameinfo.txt is.
// We always want to mount that directory relative to gameinfo.txt, so
// people can mount stuff in c:\mymod, and the main game resources are in
// someplace like c:\program files\valve\steam\steamapps\half-life 2.
//
SearchPaths
{
Game |gameinfo_path|.
Game |all_source_engine_paths|hl2
}
}
}</pre>

===Step One===
This first thing to check is the <tt>AppId</tt> mounts. This refers to the following block in the file:
<pre> FileSystem
{
SteamAppId 218 // This will mount all the GCFs we need (240=CS:S, 220=HL2).
ToolsAppId 211 // Tools will load this (ie: source SDK caches) to get things like materials\debug, materials\editor, etc.</pre>
<tt>SteamAppId</tt> should '''only''' be <span style="color:red;">218</span>, and not anything else. If it is not, change it back to this value.

<tt>ToolsAppId</tt> should '''only''' be <span style="color:red;">211</span>, and not anything else. If it is not, change it back to this value.

'''Note:''' <tt>AdditionalContentID</tt>, if present, is ignored by ''Obsidian Conflict''.

===Step Two===
Next, check the search path configuration. This refers to the following block in the file:
<pre> SearchPaths
{
Game |gameinfo_path|.
Game |all_source_engine_paths|hl2
}</pre>
This block defines how ''Obsidian Conflict'' searches for a file to load. For the sample above, the mod will first search for the file inside the <tt>obsidian</tt> folder, before falling back to the GCFs.

Only the above two lines should be listed in this block (the only exception will be the use of the ''Metamod: Source'' plugin, but that is beyond the scope of this article). If there are excess lines, remove them to return to this configuration.

===Step Three===
Once both the above blocks are checked and reverted to their proper values, save the file and '''restart ''Steam'''''. The issue should now be resolved.

Talk:How to make rappeling combine

2011-05-12T01:38:30Z

TESLA-X4: Created page with "I think you could target the particular NPC that was spawned by the maker with <tt>!activator</tt> instead of blanket-targetting all spawned instances with the same name - ~~~~"

I think you could target the particular NPC that was spawned by the maker with <tt>!activator</tt> instead of blanket-targetting all spawned instances with the same name - [[User:TESLA-X4|TESLA-X4]] 03:38, 12 May 2011 (CEST)

Dedicated Server Setup 2

2011-04-08T17:07:04Z

TESLA-X4: Added page to ServerOP category

{{wip}}
This page was created since I can't update the one [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths (i.e. <tt>orangebox/hl2</tt> refers to the folder <tt>hl2</tt> ''inside'' <tt>orangebox</tt>, not both the folders), and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Delete the <tt>orangebox/hl2</tt> folder and copy the <tt>hl2</tt> folder (the one outside) in its place.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>rmdir /s orangebox\hl2
|xcopy /s /e hl2 orangebox</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>rm -R orangebox/hl2</tt>
|<tt>cp -R hl2 orangebox</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators with Remote Desktop access to their servers since they can simply install Steam on their servers and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half-Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V {{Todo|Further elaboration needed.}}
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

==Additional Game Content==
'''Note:''' If you download any of the following (sans ''Portal'') using the ''HLDS Update Tool'' after downloading <tt>orangebox</tt>, <span style="color:red;">you will be forced to download a new set of engine binaries incompatible with the current release of Obsidian Conflict</span>. A telltale sign that this has occurred is when you see an engine error along the lines of ''SetupArrayProps_R: array prop '(null)' is at index zero'' or ''Host_Error: IDLLFunctions::DLLInit returned false'' when you try to start the server. To workaround that, simply rename the <tt>bin</tt> folder (inside <tt>orangebox</tt>) to something else (e.g. <tt>bin_se2007</tt>) '''before''' downloading the game's files. On completion, delete the newly created <tt>bin</tt> folder and rename the old one back to <tt>bin</tt>.

For the curious, the reason for this is that almost all official Valve games now run on [http://developer.valvesoftware.com/wiki/Source_Engine_2009 Source Engine 2009], but most mods (sans ''Garry's Mod'') continue to run on the older ''Source Engine 2007'' (Source SDK Base 2007). These two versions are incompatible with each other, and Valve has yet to release a version of ''Source SDK Base'' for ''Source Engine 2009''.
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

==Downloading And Installing Obsidian==
Copy the <tt>obsidian</tt> folder from a fresh install of Obsidian Conflict into your dedicated server's <tt>orangebox</tt> folder.
{{Todo|Further elaboration needed.}}

==Mounting Content==
Content mounts are controlled by a set of files in the <tt>obsidian/mount</tt> folder. Each file determines whether or not the respective game's content is mounted. These files are merely blank files without any extensions - their contents do not matter since the mod merely checks if the file is there, mounting the content if the file is present.
Valid file names are:
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
<tt>css</tt> ↔ Counter-Strike: Source

<tt>dod</tt> ↔ Day of Defeat: Source

<tt>ep2</tt> ↔ Half-Life 2: Episode Two

<tt>episodic</tt> ↔ Half-Life 2: Episode One

<tt>hls</tt> ↔ Half-Life: Source

<tt>lostcoast</tt> ↔ Half-Life 2: Lost Coast
</div>
{{Todo|Further elaboration needed.}}

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

[[Category:ServerOP]]

How to make OC playermodels

2011-04-08T16:52:51Z

TESLA-X4: Re-added the missing Paint.NET section

{{wip}}

__TOC__

Originally written by [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=458 fug4life], with tips and tricks from [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=1667 Maestro Fénix].

In this tutorial, you will learn how to make a player model for Obsidian Conflict.

==Prerequisites==

*'''Source Development Kit (Source SDK)''': Available in ''Steam → Library → Tools''. This is required as a base for the model decompiler program, and to recompile models.

*'''GCFScape (Optional, unless you intend to modify a model from an official Valve game)''': Allows you to browse and extract the contents of [http://developer.valvesoftware.com/wiki/GCF Game Cache Files (GCFs)]. http://nemesis.thewavelength.net/index.php?p=26

*'''MDLDecompiler''': Self-explanatory. http://www.chaosincarnate.net/cannonfodder/mdldecompiler.php

*'''GUI StudioMDL''': This program is a GUI front end for the [http://developer.valvesoftware.com/wiki/Studiomdl Studiomdl] tool in the Source SDK. http://www.wunderboy.org/apps/guistudiomdl2.php

*'''Notepad++ (Optional only for models for [http://developer.valvesoftware.com/wiki/Source_Engine_2006 Source Engine 2006] and below)''': You can use this or any other hex editor. http://notepad-plus.sourceforge.net/uk/site.htm

*'''VTFEdit (Optional if you intend to use ''Notepad++'' to open [http://developer.valvesoftware.com/wiki/Vmt .vmt] files instead)''': http://nemesis.thewavelength.net/index.php?c=178

*'''An Image Editor''' (such as ''Paint.NET'', ''Adobe Photoshop'', ''Paint Shop Pro'')

==Preparing The Materials==
First, you will need to create the folder of the new model that you are going to make. Go to your client's <tt>obsidian</tt> folder (inside <tt>Steam/steamapps/sourcemods</tt> for the uninitiated) and proceed to navigate to <tt>materials/models/player</tt>. Create a new folder (with the name of your model) inside this folder (right-click an empty area → ''New'' → ''Folder''). Copy your model's materials into the new folder you created, then open their <tt>.vmt</tt> files.

You should see something like this, in typical [http://developer.valvesoftware.com/wiki/KeyValues KeyValues] format:
<pre>"VertexLitGeneric"
{
"$baseTexture" "Models/player/Mossman/mossman_sheet"
"$envmap" "env_cubemap"
"$bumpmap" "models/player/Mossman/Mossman_normal"
"$normalmapalphaenvmapmask" "1"
"$envmapcontrast" ".20"
"$envmapsaturation" "0.9"
"$envmaptint" "[ .36 .36 .36 ]"
"$halflambert" "1"
"$nodecal" "1"
}</pre>

Go to the <tt>$baseTexture</tt> line, and change <tt>Models/player/Mossman/mossman_sheet</tt> to point to where your textures (i.e. the [http://developer.valvesoftware.com/wiki/VTF .vtf]s) are located.
In the case of the above example, it would become <tt>Models/player/<span style="color:red;"><your model name></span>/mossman_sheet</tt>, where <tt><span style="color:red;"><your model name></span></tt> is the name of your model.

We're not done yet - you will also need to replace all occurences of <tt>Models/player/Mossman/</tt> with <tt>Models/player/<span style="color:red;"><your model name></span>/</tt> in that <tt>.vmt</tt> file. To illustrate, in the above example, the line <tt>$bumpmap</tt> also needs to be changed from <tt>models/player/Mossman/Mossman_normal</tt> to <tt>models/player/<span style="color:red;"><your model name></span>/Mossman_normal</tt>.

'''Note:''' If you reference an invalid path, your model will have the infamous error texture (i.e. a purple and black checkerboard texture will be seen instead).

After you have modified all the <tt>.vmt</tt> files for your model, you are ready to convert the model for use as a player model.

==Converting The Model==
Go to the model files, and open the [http://developer.valvesoftware.com/wiki/MDL .mdl] file with ''Notepad++'' (or your favorite hex editor). The first four bytes in the file should be <tt>IDST</tt> (hexadecimal sequence: <tt>0x49</tt>, <tt>0x44</tt>, <tt>0x53</tt>, <tt>0x54</tt>). Now, verify that the fifth byte (immediately after the <tt>T</tt>) is a <tt>,</tt> (comma, hexadecimal: <tt>0x2C</tt>). If it is, then you can safely close the program; nothing else needs to be done. If it is something else, such as a <tt>0</tt> (zero, hexadecimal: <tt>0x30</tt>) or a <tt>-</tt> (minus sign, hexadecimal: <tt>0x2D</tt>), you will need to change it back to a comma (i.e. <tt>IDST0</tt> → <tt>IDST,</tt>).

'''Note:''' This workaround is required because the model decompiler was written before games on [http://developer.valvesoftware.com/wiki/Source_Engine_2007 Source Engine 2007 and 2009] were released, and was never updated for forward compatibility by its author.

Open ''MDLDecompiler'', then select the model that you wish to decompile and select the folder where you wish to put the decompiled files. After starting the decompile process, wait for a prompt to appear, informing you of a successful recompile.

'''Note:''' If the decompiler crashes for some unknown reason, attempt another 3-4 tries. If it still fails to work, you may wish to attempt to decompile it with [http://www.chaosincarnate.net/cannonfodder/cftools.php?program=studiocompiler StudioCompiler], or [http://developer.valvesoftware.com/wiki/User:Erix920 Erix920]'s [http://kathar.net/other/mdldecompiler.exe modified version of MDLDecompiler] instead.

<span style="color:red;">'''Additional Note:''' In certain cases, MDLDecompiler will seem to work perfectly fine - no crashes or error messages are generated - but will actually generate corrupted [http://developer.valvesoftware.com/wiki/SMD .smd] files, which when viewed in a modeling program such as ''XSI Mod Tool'' will have no mesh at all. A telltale sign of this is when the file sizes of most of the <tt>.smd</tt> files are unusually small (< 1 MB), coupled with an unusually large physics model <tt>.smd</tt> (> 1 MB). There is no known solution for this issue at the time of writing, apart from contacting the creator of the model and asking (nicely!) for the model sources.</span>

Go to the folder where the resulting files are. You will see several files with the <tt>.smd</tt> extension and a file <tt>mdldecompiler.qc</tt>. Open the [http://developer.valvesoftware.com/wiki/Qc .qc] file with ''Notepad++'' or your favorite text editor (but not a word processor like ''Wordpad'' or ''Microsoft Word''!).

This script file determines the Studiomdl configuration for the model. A snippet is provided below:

<pre>$cd "C:\Users\User\Desktop\New folder"
$modelname "player\Flandre.mdl"
$model "body" "ref.smd"
$cdmaterials "models\player\Flandre\"
$hboxset "default"
// Model uses material "txFlanFace.vmt"
// Model uses material "txFlandre.vmt"
$includemodel "player/female_shared.mdl"
$includemodel "player/female_ss.mdl"
$includemodel "player/female_gestures.mdl"
$includemodel "player/female_postures.mdl"
$surfaceprop "flesh"
$illumposition 0.016 0.578 34.522
$sequence ragdoll "ragdoll" ACT_DIERAGDOLL 1 fps 30.00
$ikchain rhand ValveBiped.Bip01_R_Hand knee 0.707 0.707 0.000
$ikchain lhand ValveBiped.Bip01_L_Hand knee 0.707 0.707 0.000
$ikchain rfoot ValveBiped.Bip01_R_Foot knee 0.707 -0.707 0.000
$ikchain lfoot ValveBiped.Bip01_L_Foot knee 0.707 -0.707 0.000
$collisionjoints "phymodel.smd" {

$mass 60.0
$inertia 10.00
$damping 0.01
$rotdamping 1.50
$rootbone "valvebiped.bip01_pelvis"
$jointmerge "ValveBiped.Bip01_Pelvis" "ValveBiped.Bip01_Spine1"
</pre>

A breakdown of the important components of the script:

*<tt>$cd</tt>: A pointer to the folder where the <tt>.smd</tt> files reside in. If you moved these files elsewhere after decompiling the model, modify this to reflect that change.

*<tt>$modelname</tt>: This command determines where the resulting model will be placed in, with respect to the <tt>models</tt> folder. Using the above snippet as an example, the resulting (compiled) model will be located at <tt>models/player/Flandre.mdl</tt>.

*<tt>$cdmaterials</tt>: A pointer to the folder where the materials for the model reside in, with respect to the <tt>materials</tt> folder. Using the above snippet as an example, the full path will be <tt>materials/models/player/Flandre/</tt>. Ensure that the path is valid or your model will end up with purple and black checkerboard textures instead.

*<tt>$includemodel</tt>: This command determines which model files are 'included' into the model. In layman's terms, this determines which animation libraries are referenced by the model. An Obsidian Conflict player model requires a different set of animation libraries depending on the character's gender:
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a male model''':<br />
<tt>$includemodel "player/male_shared.mdl"<br />
$includemodel "player/male_ss.mdl"<br />
$includemodel "player/male_gestures.mdl"<br />
$includemodel "player/male_postures.mdl"</tt>
</div>
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a female model''':<br />
<tt>$includemodel "player/female_shared.mdl"<br />
$includemodel "player/female_ss.mdl"<br />
$includemodel "player/female_gestures.mdl"<br />
$includemodel "player/female_postures.mdl"</tt>
</div>

*<tt>$surfaceprop</tt>: Used to define the physical surface properties the model will have. The default is <tt>flesh</tt> (organic-human). The complete list is available [http://developer.valvesoftware.com/wiki/Material_surface_properties here].
'''Note:''' If this command was used in the <tt>.vmt</tt> files to define multiple surface types and is also present in the <tt>.qc</tt> script, the values set in the <tt>.vmt</tt> files will be ignored. If this behavior is not desired, either delete this command from the <tt>mdldecompiler.qc</tt> script, or specify the value as <tt>default</tt> instead.

This is all that you will typically need to modify in order to make a player model compatible with Obsidian Conflict.

==Finishing Touches==
Save the script file and open ''GUI StudioMDL''. Select <tt>OrangeBox</tt> for <tt>SDK Version</tt> and for <tt>Target Mod or "GameInfo" path</tt> select <tt>Obsidian Conflict</tt> (you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this). Go to ''File'' → ''Load .qc file'' and load the <tt>.qc</tt> file, then click on the <tt>Compile</tt> button.

When ''GUI StudioMDL'' finishes compiling the model (you should see <tt>Completed "mdldecompiler.qc"</tt>), open the ''Source SDK'', select <tt>Source 2007</tt> in the <tt>Engine Version:</tt> combo box and select <tt>Obsidian Conflict</tt> in the <tt>Current Game:</tt> combo box (once again, you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this), then click on <tt>Model Viewer</tt>. When ''Half-Life Model Viewer'' loads up, go to ''File'' → ''Load model...'' and select your model.

If all went well, you should now see your model, complete with working animations.

Once you have verified that your model is in working condition, go to where the model files are located in your client's folder and create a new text file with the name of your model, but with the <tt>.txt</tt> extension. Using the previous snippet as an example, the file would be <tt>models/player/Flandre.<span style="color:red;">txt</span></tt>.
Paste the following inside the file (don't forget to alter the gender of the <tt>base model rig</tt> and <tt>voice</tt> as necessary):
<pre>ModelSettings
{
//Use this option to choose a base script to use instead.
"usefile" "none"

//base model rig to use. Use either Male_01 or Female_01 for best results.
"basemodel" "Male_01"

//Voice Sound 0=none, 1=male, 2=female, 3=combine
"voice" "1"

//Footstep Sound 1=shoe, 2=combine boots
"footsteps" "1"

//Gibs, 1 = generic human, 2 = generic alien, 3 = human rebel ragdoll gibs, 4 = Ragdoll only
"Gibs" "4"
}</pre>
With this file, you can configure the voice, footstep sounds and gibs of the model.

Finally, head over to <tt>obsidian/materials/VGUI/playermodels/player</tt> and create a new <tt>.vmt</tt> and <tt>.vtf</tt> file with the same name as your model's <tt>.mdl</tt> file.

'''Note:''' The path after <tt>obsidian/materials/VGUI/playermodels/</tt> '''must''' reflect the path to the model, i.e. if the model is at <tt>models/player/somemodelname/somemodel.mdl</tt>, the two files will be <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vmt</tt> and <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vtf</tt>.

In the <tt>.vmt</tt> file (you can make a copy of an existing one and clear it for use), paste the following:
<pre>UnlitGeneric
{
"$translucent" "1"
"$basetexture" "vgui\playermodels\player\Hostage_01"
"$vertexcolor" "1"
"$vertexalpha" "1"
"$no_fullbright" "1"
"$ignorez" "1"
"$decalscale" "0.250"
}</pre>

On the <tt>$basetexture</tt> line, change <tt>Hostage_01</tt> to point to your accompanying <tt>.vtf</tt> file.

To create that <tt>.vtf</tt> file, take a screenshot in ''Half-Life Model Viewer'' then save it as a <tt>.tga</tt> file and open that in ''VTFEdit'', then save it in the <tt>.vtf</tt> format. Give it the same name as your model.

Once you have placed the two files into your client's <tt>obsidian/materials/VGUI/playermodels/player</tt> folder, test it all out in-game. If all works well (animations, textures, sounds, preview image), pat yourself on the back - you've successfully created a new player model.
*To test the model's preview image, start the game, then go to <tt>Options</tt> → <tt>Multiplayer</tt> tab, and select your model from the combo box.
*To test the model's animations and textures, select the model, then start a local server and turn on <tt>sv_cheats</tt>. Execute the <tt>thirdperson</tt> command.

==Tips And Tricks==
===Creating The VGUI Preview Image===
====Using Paint Shop Pro====
You will also need to download and install a '''http://nemesis.thewavelength.net/index.php?p=39 VTF Plugin for Paint Shop Pro''' beforehand (Information about how to use it and what programs can use it '''http://developer.valvesoftware.com/wiki/Photoshop_VTF_Plugin here''').

So, Open Paint Shop Pro and open the screenshot (.tga file) you took in SDK Model Viewer earlier.
(Prefebably you want the model holding an oc weapon and you can use centre view to get the model where you want it.
To look around in SDK Model Viewer use: Right mouse click - zoom in/out.
Left mouse click to rotate. Hold shift and use left click mouse to move the model up/down/left/right).

Also in Paint Shop Pro it helps to add a grid (view/grid, size dosen't matter)it just helps when working.

So lets move on to converting/working on the screenshot.

First we will use the Crop tool to cut the picture just so that we have the top half of the body. Make sure you use free form and have the box size that you are cropping set to 256x200, position in the centre of the top half of the body (showing the head, chest and shoulders), and then crop.

Now, click layers and select new mask layer/show all.

Now you will see the picture has a mask-raster 1 layer, right click and select delete and then yes.

Now select the Magic Wand tool set up with something like mode = replace
matchmode = RGB value tolerance = 1 use all layers and use contiguous also use Anti-alias and select outside from dropdown box.
Click on the background on the image and not the model to use the Magic Wand.
(Baically you want to delete the back ground and not the model itself).
So if the the whole box and around the model is selected, its ok to delete.

Once the background is deleted, with the Magic Wand tool still open change the matchmode to = All opaque and this time click on the model in the image and it should change the Magic Wand from around the edges and around the model to actually now just around the model only.

Now click layers select new mask layer/form image, make sure source opacity is checked and everything else is unchecked, click ok.

Now we are going to cut the highlighted model onto a new image. So with the Magic Wand still highlighting around the model on the image change to the Pan tool and right click on the highlighted model and select: copy merged.

Now go to File and create a new image with these properties:

<pre>width =256 pixels
height =256 pixels
resolution =72,000 pixels/inch</pre>

Choose Rastor Background
image depth =RGB - 8bits/channel

And check the Transparent box.

Now to paste your copied image onto your new image, so, right click on your new image and paste as a new selection. Position into the top left hand corner as much as possible and then just left click.

Now we need to give an alpha channel so go to selections select load/save selection and choose save selection to alpha channel and clcik ok/save in the pop-up.

Finally now click File and save copy as and name it Hostage_01.png using the .PNG file format and press yes to the pop-up. (this is so you have a nice image to upload to the forums).

Now click File and save copy as again and this time name it nameofthemodel.vtf using the .VTF file format and press yes/ok to the pop-up.

Now here we are using the VTF plugin. Set the properties as:

<pre>Template = Compressed Texture With Alpha
Format = DXT5 (Common Format)
Mipmap Filter = Box
Sharpen Filter = Sharpen Soft</pre>

check/tick Mipmaps and Thumbnail.

And from the list just make sure Eight Bit Alpha (Format Specific) and Nice Filter are both checked/ticked. Everything else should be unchecked/unticked, then press ok.

Finally add it to your obsidian/materials/VGUI/playermodels/player directory to finish.

Example image:

[[File:Hostage01.png|frame|Example image: Hostage_01]]

====Using Paint.NET====
# Get the image (you know, "impr. pant" or another way to take a photo of your model).
# Prepare the image. If you are used "impr. pant", use the rectangule selection and select "cut selected" (after go to edit->paste as a new image). Only will have the image that it was inside of the rectangule. Use the "wand" tool and put the tolerancy level to 10% or less. Delete everything that surround the model.
# Go to "Image" and select "change size". Deactivate "keep relation size" and set the image in 200x200.
# Back to "Image" and select "change canvas size". Set 256x256 and select "upper left position".
# Save the image in .tga format with the name of the model.
# Drag and drop the .tga file into VTFedit. Press "ok" and save as .vtf format. Must have the same name of the model.
# Create the .vmt coping another .vmt from the materials/VGUI/playermodels/Player folder if you don´t want write it, change the directory of the image and put it in materials/VGUI/playermodels/Player.
# Sucess.

[[Category:Miscellaneous_Tutorials]]

Dedicated Server Setup 2

2011-04-08T16:39:02Z

TESLA-X4:

{{wip}}
This page was created since I can't update the one [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths (i.e. <tt>orangebox/hl2</tt> refers to the folder <tt>hl2</tt> ''inside'' <tt>orangebox</tt>, not both the folders), and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Delete the <tt>orangebox/hl2</tt> folder and copy the <tt>hl2</tt> folder (the one outside) in its place.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>rmdir /s orangebox\hl2
|xcopy /s /e hl2 orangebox</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>rm -R orangebox/hl2</tt>
|<tt>cp -R hl2 orangebox</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators with Remote Desktop access to their servers since they can simply install Steam on their servers and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half-Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V {{Todo|Further elaboration needed.}}
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

==Additional Game Content==
'''Note:''' If you download any of the following (sans ''Portal'') using the ''HLDS Update Tool'' after downloading <tt>orangebox</tt>, <span style="color:red;">you will be forced to download a new set of engine binaries incompatible with the current release of Obsidian Conflict</span>. A telltale sign that this has occurred is when you see an engine error along the lines of ''SetupArrayProps_R: array prop '(null)' is at index zero'' or ''Host_Error: IDLLFunctions::DLLInit returned false'' when you try to start the server. To workaround that, simply rename the <tt>bin</tt> folder (inside <tt>orangebox</tt>) to something else (e.g. <tt>bin_se2007</tt>) '''before''' downloading the game's files. On completion, delete the newly created <tt>bin</tt> folder and rename the old one back to <tt>bin</tt>.

For the curious, the reason for this is that almost all official Valve games now run on [http://developer.valvesoftware.com/wiki/Source_Engine_2009 Source Engine 2009], but most mods (sans ''Garry's Mod'') continue to run on the older ''Source Engine 2007'' (Source SDK Base 2007). These two versions are incompatible with each other, and Valve has yet to release a version of ''Source SDK Base'' for ''Source Engine 2009''.
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

==Downloading And Installing Obsidian==
Copy the <tt>obsidian</tt> folder from a fresh install of Obsidian Conflict into your dedicated server's <tt>orangebox</tt> folder.
{{Todo|Further elaboration needed.}}

==Mounting Content==
Content mounts are controlled by a set of files in the <tt>obsidian/mount</tt> folder. Each file determines whether or not the respective game's content is mounted. These files are merely blank files without any extensions - their contents do not matter since the mod merely checks if the file is there, mounting the content if the file is present.
Valid file names are:
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
<tt>css</tt> ↔ Counter-Strike: Source

<tt>dod</tt> ↔ Day of Defeat: Source

<tt>ep2</tt> ↔ Half-Life 2: Episode Two

<tt>episodic</tt> ↔ Half-Life 2: Episode One

<tt>hls</tt> ↔ Half-Life: Source

<tt>lostcoast</tt> ↔ Half-Life 2: Lost Coast
</div>
{{Todo|Further elaboration needed.}}

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

How to make OC playermodels

2011-04-08T16:04:13Z

TESLA-X4:

{{wip}}

__TOC__

Original tutorial written by [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=458 fug4life], with tips and tricks from [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=1667 Maestro Fénix].

In this tutorial, you will learn how to make a player model for Obsidian Conflict.

==Prerequisites==

*'''Source Development Kit (Source SDK)''': Available in ''Steam → Library → Tools''. This is required as a base for the model decompiler program, and to recompile models.

*'''GCFScape (Optional, unless you intend to modify a model from an official Valve game)''': Allows you to browse and extract the contents of [http://developer.valvesoftware.com/wiki/GCF Game Cache Files (GCFs)]. http://nemesis.thewavelength.net/index.php?p=26

*'''MDLDecompiler''': Self-explanatory. http://www.chaosincarnate.net/cannonfodder/mdldecompiler.php

*'''GUI StudioMDL''': This program is a GUI front end for the [http://developer.valvesoftware.com/wiki/Studiomdl Studiomdl] tool in the Source SDK. http://www.wunderboy.org/apps/guistudiomdl2.php

*'''Notepad++ (Optional only for models for [http://developer.valvesoftware.com/wiki/Source_Engine_2006 Source Engine 2006] and below)''': You can use this or any other hex editor. http://notepad-plus.sourceforge.net/uk/site.htm

*'''VTFEdit (Optional if you intend to use ''Notepad++'' to open [http://developer.valvesoftware.com/wiki/Vmt .vmt] files instead)''': http://nemesis.thewavelength.net/index.php?c=178

*'''An Image Editor''' (such as ''Paint.NET'', ''Adobe Photoshop'', ''Paint Shop Pro'')

==Preparing The Materials==
First, you will need to create the folder of the new model that you are going to make. Go to your client's <tt>obsidian</tt> folder (inside <tt>Steam/steamapps/sourcemods</tt> for the uninitiated) and proceed to navigate to <tt>materials/models/player</tt>. Create a new folder (with the name of your model) inside this folder (right-click an empty area → ''New'' → ''Folder''). Copy your model's materials into the new folder you created, then open their <tt>.vmt</tt> files.

You should see something like this, in typical [http://developer.valvesoftware.com/wiki/KeyValues KeyValues] format:
<pre>"VertexLitGeneric"
{
"$baseTexture" "Models/player/Mossman/mossman_sheet"
"$envmap" "env_cubemap"
"$bumpmap" "models/player/Mossman/Mossman_normal"
"$normalmapalphaenvmapmask" "1"
"$envmapcontrast" ".20"
"$envmapsaturation" "0.9"
"$envmaptint" "[ .36 .36 .36 ]"
"$halflambert" "1"
"$nodecal" "1"
}</pre>

Go to the <tt>$baseTexture</tt> line, and change <tt>Models/player/Mossman/mossman_sheet</tt> to point to where your textures (i.e. the [http://developer.valvesoftware.com/wiki/VTF .vtf]s) are located.
In the case of the above example, it would become <tt>Models/player/<span style="color:red;"><your model name></span>/mossman_sheet</tt>, where <tt><span style="color:red;"><your model name></span></tt> is the name of your model.

We're not done yet - you will also need to replace all occurences of <tt>Models/player/Mossman/</tt> with <tt>Models/player/<span style="color:red;"><your model name></span>/</tt> in that <tt>.vmt</tt> file. To illustrate, in the above example, the line <tt>$bumpmap</tt> also needs to be changed from <tt>models/player/Mossman/Mossman_normal</tt> to <tt>models/player/<span style="color:red;"><your model name></span>/Mossman_normal</tt>.

'''Note:''' If you reference an invalid path, your model will have the infamous error texture (i.e. a purple and black checkerboard texture will be seen instead).

After you have modified all the <tt>.vmt</tt> files for your model, you are ready to convert the model for use as a player model.

==Converting The Model==
Go to the model files, and open the [http://developer.valvesoftware.com/wiki/MDL .mdl] file with ''Notepad++'' (or your favorite hex editor). The first four bytes in the file should be <tt>IDST</tt> (hexadecimal sequence: <tt>0x49</tt>, <tt>0x44</tt>, <tt>0x53</tt>, <tt>0x54</tt>). Now, verify that the fifth byte (immediately after the <tt>T</tt>) is a <tt>,</tt> (comma, hexadecimal: <tt>0x2C</tt>). If it is, then you can safely close the program; nothing else needs to be done. If it is something else, such as a <tt>0</tt> (zero, hexadecimal: <tt>0x30</tt>) or a <tt>-</tt> (minus sign, hexadecimal: <tt>0x2D</tt>), you will need to change it back to a comma (i.e. <tt>IDST0</tt> → <tt>IDST,</tt>).

'''Note:''' This workaround is required because the model decompiler was written before games on [http://developer.valvesoftware.com/wiki/Source_Engine_2007 Source Engine 2007 and 2009] were released, and was never updated for forward compatibility by its author.

Open ''MDLDecompiler'', then select the model that you wish to decompile and select the folder where you wish to put the decompiled files. After starting the decompile process, wait for a prompt to appear, informing you of a successful recompile.

'''Note:''' If the decompiler crashes for some unknown reason, attempt another 3-4 tries. If it still fails to work, you may wish to attempt to decompile it with [http://www.chaosincarnate.net/cannonfodder/cftools.php?program=studiocompiler StudioCompiler], or [http://developer.valvesoftware.com/wiki/User:Erix920 Erix920]'s [http://kathar.net/other/mdldecompiler.exe modified version of MDLDecompiler] instead.

<span style="color:red;">'''Additional Note:''' In certain cases, MDLDecompiler will seem to work perfectly fine - no crashes or error messages are generated - but will actually generate corrupted [http://developer.valvesoftware.com/wiki/SMD .smd] files, which when viewed in a modeling program such as ''XSI Mod Tool'' will have no mesh at all. A telltale sign of this is when the file sizes of most of the <tt>.smd</tt> files are unusually small (< 1 MB), coupled with an unusually large physics model <tt>.smd</tt> (> 1 MB). There is no known solution for this issue at the time of writing, apart from contacting the creator of the model and asking (nicely!) for the model sources.</span>

Go to the folder where the resulting files are. You will see several files with the <tt>.smd</tt> extension and a file <tt>mdldecompiler.qc</tt>. Open the [http://developer.valvesoftware.com/wiki/Qc .qc] file with ''Notepad++'' or your favorite text editor (but not a word processor like ''Wordpad'' or ''Microsoft Word''!).

This script file determines the Studiomdl configuration for the model. A snippet is provided below:

<pre>$cd "C:\Users\User\Desktop\New folder"
$modelname "player\Flandre.mdl"
$model "body" "ref.smd"
$cdmaterials "models\player\Flandre\"
$hboxset "default"
// Model uses material "txFlanFace.vmt"
// Model uses material "txFlandre.vmt"
$includemodel "player/female_shared.mdl"
$includemodel "player/female_ss.mdl"
$includemodel "player/female_gestures.mdl"
$includemodel "player/female_postures.mdl"
$surfaceprop "flesh"
$illumposition 0.016 0.578 34.522
$sequence ragdoll "ragdoll" ACT_DIERAGDOLL 1 fps 30.00
$ikchain rhand ValveBiped.Bip01_R_Hand knee 0.707 0.707 0.000
$ikchain lhand ValveBiped.Bip01_L_Hand knee 0.707 0.707 0.000
$ikchain rfoot ValveBiped.Bip01_R_Foot knee 0.707 -0.707 0.000
$ikchain lfoot ValveBiped.Bip01_L_Foot knee 0.707 -0.707 0.000
$collisionjoints "phymodel.smd" {

$mass 60.0
$inertia 10.00
$damping 0.01
$rotdamping 1.50
$rootbone "valvebiped.bip01_pelvis"
$jointmerge "ValveBiped.Bip01_Pelvis" "ValveBiped.Bip01_Spine1"
</pre>

A breakdown of the important components of the script:

*<tt>$cd</tt>: A pointer to the folder where the <tt>.smd</tt> files reside in. If you moved these files elsewhere after decompiling the model, modify this to reflect that change.

*<tt>$modelname</tt>: This command determines where the resulting model will be placed in, with respect to the <tt>models</tt> folder. Using the above snippet as an example, the resulting (compiled) model will be located at <tt>models/player/Flandre.mdl</tt>.

*<tt>$cdmaterials</tt>: A pointer to the folder where the materials for the model reside in, with respect to the <tt>materials</tt> folder. Using the above snippet as an example, the full path will be <tt>materials/models/player/Flandre/</tt>. Ensure that the path is valid or your model will end up with purple and black checkerboard textures instead.

*<tt>$includemodel</tt>: This command determines which model files are 'included' into the model. In layman's terms, this determines which animation libraries are referenced by the model. An Obsidian Conflict player model requires a different set of animation libraries depending on the character's gender:
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a male model''':<br />
<tt>$includemodel "player/male_shared.mdl"<br />
$includemodel "player/male_ss.mdl"<br />
$includemodel "player/male_gestures.mdl"<br />
$includemodel "player/male_postures.mdl"</tt>
</div>
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a female model''':<br />
<tt>$includemodel "player/female_shared.mdl"<br />
$includemodel "player/female_ss.mdl"<br />
$includemodel "player/female_gestures.mdl"<br />
$includemodel "player/female_postures.mdl"</tt>
</div>

*<tt>$surfaceprop</tt>: Used to define the physical surface properties the model will have. The default is <tt>flesh</tt> (organic-human). The complete list is available [http://developer.valvesoftware.com/wiki/Material_surface_properties here].
'''Note:''' If this command was used in the <tt>.vmt</tt> files to define multiple surface types and is also present in the <tt>.qc</tt> script, the values set in the <tt>.vmt</tt> files will be ignored. If this behavior is not desired, either delete this command from the <tt>mdldecompiler.qc</tt> script, or specify the value as <tt>default</tt> instead.

This is all that you will typically need to modify in order to make a player model compatible with Obsidian Conflict.

==Finishing Touches==
Save the script file and open ''GUI StudioMDL''. Select <tt>OrangeBox</tt> for <tt>SDK Version</tt> and for <tt>Target Mod or "GameInfo" path</tt> select <tt>Obsidian Conflict</tt> (you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this). Go to ''File'' → ''Load .qc file'' and load the <tt>.qc</tt> file, then click on the <tt>Compile</tt> button.

When ''GUI StudioMDL'' finishes compiling the model (you should see <tt>Completed "mdldecompiler.qc"</tt>), open the ''Source SDK'', select <tt>Source 2007</tt> in the <tt>Engine Version:</tt> combo box and select <tt>Obsidian Conflict</tt> in the <tt>Current Game:</tt> combo box (once again, you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this), then click on <tt>Model Viewer</tt>. When ''Half-Life Model Viewer'' loads up, go to ''File'' → ''Load model...'' and select your model.

If all went well, you should now see your model, complete with working animations.

Once you have verified that your model is in working condition, go to where the model files are located in your client's folder and create a new text file with the name of your model, but with the <tt>.txt</tt> extension. Using the previous snippet as an example, the file would be <tt>models/player/Flandre.<span style="color:red;">txt</span></tt>.
Paste the following inside the file (don't forget to alter the gender of the <tt>base model rig</tt> and <tt>voice</tt> as necessary):
<pre>ModelSettings
{
//Use this option to choose a base script to use instead.
"usefile" "none"

//base model rig to use. Use either Male_01 or Female_01 for best results.
"basemodel" "Male_01"

//Voice Sound 0=none, 1=male, 2=female, 3=combine
"voice" "1"

//Footstep Sound 1=shoe, 2=combine boots
"footsteps" "1"

//Gibs, 1 = generic human, 2 = generic alien, 3 = human rebel ragdoll gibs, 4 = Ragdoll only
"Gibs" "4"
}</pre>
With this file, you can configure the voice, footstep sounds and gibs of the model.

Finally, head over to <tt>obsidian/materials/VGUI/playermodels/player</tt> and create a new <tt>.vmt</tt> and <tt>.vtf</tt> file with the same name as your model's <tt>.mdl</tt> file.

'''Note:''' The path after <tt>obsidian/materials/VGUI/playermodels/</tt> '''must''' reflect the path to the model, i.e. if the model is at <tt>models/player/somemodelname/somemodel.mdl</tt>, the two files will be <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vmt</tt> and <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vtf</tt>.

In the <tt>.vmt</tt> file (you can make a copy of an existing one and clear it for use), paste the following:
<pre>UnlitGeneric
{
"$translucent" "1"
"$basetexture" "vgui\playermodels\player\Hostage_01"
"$vertexcolor" "1"
"$vertexalpha" "1"
"$no_fullbright" "1"
"$ignorez" "1"
"$decalscale" "0.250"
}</pre>

On the <tt>$basetexture</tt> line, change <tt>Hostage_01</tt> to point to your accompanying <tt>.vtf</tt> file.

To create that <tt>.vtf</tt> file, take a screenshot in ''Half-Life Model Viewer'' then save it as a <tt>.tga</tt> file and open that in ''VTFEdit'', then save it in the <tt>.vtf</tt> format. Give it the same name as your model.

Once you have placed the two files into your client's <tt>obsidian/materials/VGUI/playermodels/player</tt> folder, test it all out in-game. If all works well (animations, textures, sounds, preview image), pat yourself on the back - you've successfully created a new player model.
*To test the model's preview image, start the game, then go to <tt>Options</tt> → <tt>Multiplayer</tt> tab, and select your model from the combo box.
*To test the model's animations and textures, select the model, then start a local server and turn on <tt>sv_cheats</tt>. Execute the <tt>thirdperson</tt> command.

==Tips And Tricks==
===Creating The VGUI Preview Image===
====Using Paint Shop Pro====
You will also need to download and install a '''http://nemesis.thewavelength.net/index.php?p=39 VTF Plugin for Paint Shop Pro''' beforehand (Information about how to use it and what programs can use it '''http://developer.valvesoftware.com/wiki/Photoshop_VTF_Plugin here''').

So, Open Paint Shop Pro and open the screenshot (.tga file) you took in SDK Model Viewer earlier.
(Prefebably you want the model holding an oc weapon and you can use centre view to get the model where you want it.
To look around in SDK Model Viewer use: Right mouse click - zoom in/out.
Left mouse click to rotate. Hold shift and use left click mouse to move the model up/down/left/right).

Also in Paint Shop Pro it helps to add a grid (view/grid, size dosen't matter)it just helps when working.

So lets move on to converting/working on the screenshot.

First we will use the Crop tool to cut the picture just so that we have the top half of the body. Make sure you use free form and have the box size that you are cropping set to 256x200, position in the centre of the top half of the body (showing the head, chest and shoulders), and then crop.

Now, click layers and select new mask layer/show all.

Now you will see the picture has a mask-raster 1 layer, right click and select delete and then yes.

Now select the Magic Wand tool set up with something like mode = replace
matchmode = RGB value tolerance = 1 use all layers and use contiguous also use Anti-alias and select outside from dropdown box.
Click on the background on the image and not the model to use the Magic Wand.
(Baically you want to delete the back ground and not the model itself).
So if the the whole box and around the model is selected, its ok to delete.

Once the background is deleted, with the Magic Wand tool still open change the matchmode to = All opaque and this time click on the model in the image and it should change the Magic Wand from around the edges and around the model to actually now just around the model only.

Now click layers select new mask layer/form image, make sure source opacity is checked and everything else is unchecked, click ok.

Now we are going to cut the highlighted model onto a new image. So with the Magic Wand still highlighting around the model on the image change to the Pan tool and right click on the highlighted model and select: copy merged.

Now go to File and create a new image with these properties:

<pre>width =256 pixels
height =256 pixels
resolution =72,000 pixels/inch</pre>

Choose Rastor Background
image depth =RGB - 8bits/channel

And check the Transparent box.

Now to paste your copied image onto your new image, so, right click on your new image and paste as a new selection. Position into the top left hand corner as much as possible and then just left click.

Now we need to give an alpha channel so go to selections select load/save selection and choose save selection to alpha channel and clcik ok/save in the pop-up.

Finally now click File and save copy as and name it Hostage_01.png using the .PNG file format and press yes to the pop-up. (this is so you have a nice image to upload to the forums).

Now click File and save copy as again and this time name it nameofthemodel.vtf using the .VTF file format and press yes/ok to the pop-up.

Now here we are using the VTF plugin. Set the properties as:

<pre>Template = Compressed Texture With Alpha
Format = DXT5 (Common Format)
Mipmap Filter = Box
Sharpen Filter = Sharpen Soft</pre>

check/tick Mipmaps and Thumbnail.

And from the list just make sure Eight Bit Alpha (Format Specific) and Nice Filter are both checked/ticked. Everything else should be unchecked/unticked, then press ok.

Finally add it to your obsidian/materials/VGUI/playermodels/player directory to finish.

Example image:

[[File:Hostage01.png|frame|Example image: Hostage_01]]

[[Category:Miscellaneous_Tutorials]]

How to make OC playermodels

2011-04-08T15:52:27Z

TESLA-X4: Refined the contents and structure of the page

{{wip}}

__TOC__

Original tutorial written by [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=458 fug4life], with tips and tricks from [http://www.obsidianconflict.net/forums/memberlist.php?mode=viewprofile&u=1667 Maestro Fénix].

In this tutorial, you will learn how to make a player model for Obsidian Conflict.

==Prerequisites==

*'''Source Development Kit (Source SDK)''': Available in ''Steam → Library → Tools''. This is required as a base for the model decompiler program, and to recompile models.

*'''GCFScape (Optional, unless you intend to modify a model from a game)''': Allows you to browse and extract the contents of [http://developer.valvesoftware.com/wiki/GCF Game Cache Files (GCFs)]. http://nemesis.thewavelength.net/index.php?p=26

*'''MDLDecompiler''': Self-explanatory. http://www.chaosincarnate.net/cannonfodder/mdldecompiler.php

*'''GUI StudioMDL''': This program is a GUI front end for the [http://developer.valvesoftware.com/wiki/Studiomdl Studiomdl] tool in the Source SDK. http://www.wunderboy.org/apps/guistudiomdl2.php

*'''Notepad++ (Optional only for models for [http://developer.valvesoftware.com/wiki/Source_Engine_2006 Source Engine 2006] and below)''': You can use this or any other hex editor. http://notepad-plus.sourceforge.net/uk/site.htm

*'''VTFEdit (Optional if you intend to use ''Notepad++'' to open [http://developer.valvesoftware.com/wiki/Vmt .vmt] files instead)''': http://nemesis.thewavelength.net/index.php?c=178

*'''An Image Editor''' (such as ''Paint.NET'', ''Adobe Photoshop'', ''Paint Shop Pro'')

==Preparing The Materials==
First, you will need to create the folder of the new model that you are going to make. Go to your client's <tt>obsidian</tt> folder (inside <tt>Steam/steamapps/sourcemods</tt> for the uninitiated) and proceed to navigate to <tt>materials/models/player</tt>. Create a new folder (with the name of your model) inside this folder (right-click an empty area → ''New'' → ''Folder''). Copy your model's materials into the new folder you created, then open their <tt>.vmt</tt> files.

You should see something like this, in typical [http://developer.valvesoftware.com/wiki/KeyValues KeyValues] format:
<pre>"VertexLitGeneric"
{
"$baseTexture" "Models/player/Mossman/mossman_sheet"
"$envmap" "env_cubemap"
"$bumpmap" "models/player/Mossman/Mossman_normal"
"$normalmapalphaenvmapmask" "1"
"$envmapcontrast" ".20"
"$envmapsaturation" "0.9"
"$envmaptint" "[ .36 .36 .36 ]"
"$halflambert" "1"
"$nodecal" "1"
}</pre>

Go to the <tt>$baseTexture</tt> line, and change <tt>Models/player/Mossman/mossman_sheet</tt> to point to where your textures (i.e. the [http://developer.valvesoftware.com/wiki/VTF .vtf]s) are located.
In the case of the above example, it would become <tt>Models/player/<span style="color:red;"><your model name></span>/mossman_sheet</tt>, where <tt><span style="color:red;"><your model name></span></tt> is the name of your model.

We're not done yet - you will also need to replace all occurences of <tt>Models/player/Mossman/</tt> with <tt>Models/player/<span style="color:red;"><your model name></span>/</tt> in that <tt>.vmt</tt> file. To illustrate, in the above example, the line <tt>$bumpmap</tt> also needs to be changed from <tt>models/player/Mossman/Mossman_normal</tt> to <tt>models/player/<span style="color:red;"><your model name></span>/Mossman_normal</tt>.

'''Note:''' If you reference an invalid path, your model will have the infamous error texture (i.e. a purple and black checkerboard texture will be seen instead).

After you have modified all the <tt>.vmt</tt> files for your model, you are ready to convert the model for use as a player model.

==Converting The Model==
Go to the model files, and open the [http://developer.valvesoftware.com/wiki/MDL .mdl] file with ''Notepad++'' (or your favorite hex editor). The first four bytes in the file should be <tt>IDST</tt> (hexadecimal sequence: <tt>0x49</tt>, <tt>0x44</tt>, <tt>0x53</tt>, <tt>0x54</tt>). Now, verify that the fifth byte (immediately after the <tt>T</tt>) is a <tt>,</tt> (comma, hexadecimal: <tt>0x2C</tt>). If it is, then you can safely close the program; nothing else needs to be done. If it is something else, such as a <tt>0</tt> (zero, hexadecimal: <tt>0x30</tt>) or a <tt>-</tt> (minus sign, hexadecimal: <tt>0x2D</tt>), you will need to change it back to a comma (i.e. <tt>IDST0</tt> → <tt>IDST,</tt>).

'''Note:''' This workaround is required because the model decompiler was written before games on [http://developer.valvesoftware.com/wiki/Source_Engine_2007 Source Engine 2007 and 2009] were released, and was never updated for forward compatibility by its author.

Open ''MDLDecompiler'', then select the model that you wish to decompile and select the folder where you wish to put the decompiled files. After starting the decompile process, wait for a prompt to appear, informing you of a successful recompile.

'''Note:''' If the decompiler crashes for some unknown reason, attempt another 3-4 tries. If it still fails to work, you may wish to attempt to decompile it with [http://www.chaosincarnate.net/cannonfodder/cftools.php?program=studiocompiler StudioCompiler], or [http://developer.valvesoftware.com/wiki/User:Erix920 Erix920]'s [http://kathar.net/other/mdldecompiler.exe modified version of MDLDecompiler] instead.

<span style="color:red;">'''Additional Note:''' In certain cases, MDLDecompiler will seem to work perfectly fine - no crashes or error messages are generated - but will actually generate corrupted [http://developer.valvesoftware.com/wiki/SMD .smd] files, which when viewed in a modeling program such as ''XSI Mod Tool'' will have no mesh at all. A telltale sign of this is when the file sizes of most of the <tt>.smd</tt> files are unusually small (< 1 MB), coupled with an unusually large physics model <tt>.smd</tt> (> 1 MB). There is no known solution for this issue at the time of writing, apart from contacting the creator of the model and asking (nicely!) for the model sources.</span>

Go to the folder where the resulting files are. You will see several files with the <tt>.smd</tt> extension and a file <tt>mdldecompiler.qc</tt>. Open the [http://developer.valvesoftware.com/wiki/Qc .qc] file with ''Notepad++'' or your favorite text editor (but not a word processor like ''Wordpad'' or ''Microsoft Word''!).

This script file determines the Studiomdl configuration for the model. A snippet is provided below:

<pre>$cd "C:\Users\User\Desktop\New folder"
$modelname "player\Flandre.mdl"
$model "body" "ref.smd"
$cdmaterials "models\player\Flandre\"
$hboxset "default"
// Model uses material "txFlanFace.vmt"
// Model uses material "txFlandre.vmt"
$includemodel "player/female_shared.mdl"
$includemodel "player/female_ss.mdl"
$includemodel "player/female_gestures.mdl"
$includemodel "player/female_postures.mdl"
$surfaceprop "flesh"
$illumposition 0.016 0.578 34.522
$sequence ragdoll "ragdoll" ACT_DIERAGDOLL 1 fps 30.00
$ikchain rhand ValveBiped.Bip01_R_Hand knee 0.707 0.707 0.000
$ikchain lhand ValveBiped.Bip01_L_Hand knee 0.707 0.707 0.000
$ikchain rfoot ValveBiped.Bip01_R_Foot knee 0.707 -0.707 0.000
$ikchain lfoot ValveBiped.Bip01_L_Foot knee 0.707 -0.707 0.000
$collisionjoints "phymodel.smd" {

$mass 60.0
$inertia 10.00
$damping 0.01
$rotdamping 1.50
$rootbone "valvebiped.bip01_pelvis"
$jointmerge "ValveBiped.Bip01_Pelvis" "ValveBiped.Bip01_Spine1"
</pre>

A breakdown of the important components of the script:

*<tt>$cd</tt>: A pointer to the folder where the <tt>.smd</tt> files reside in. If you moved these files elsewhere after decompiling the model, modify this to reflect that change.

*<tt>$modelname</tt>: This command determines where the resulting model will be placed in, with respect to the <tt>models</tt> folder. Using the above snippet as an example, the resulting (compiled) model will be located at <tt>models/player/Flandre.mdl</tt>.

*<tt>$cdmaterials</tt>: A pointer to the folder where the materials for the model reside in, with respect to the <tt>materials</tt> folder. Using the above snippet as an example, the full path will be <tt>materials/models/player/Flandre/</tt>. Ensure that the path is valid or your model will end up with purple and black checkerboard textures instead.

*<tt>$includemodel</tt>: This command determines which model files are 'included' into the model. In layman's terms, this determines which animation libraries are referenced by the model. An Obsidian Conflict player model requires a different set of animation libraries depending on the character's gender:
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a male model''':<br />
<tt>$includemodel "player/male_shared.mdl"<br />
$includemodel "player/male_ss.mdl"<br />
$includemodel "player/male_gestures.mdl"<br />
$includemodel "player/male_postures.mdl"</tt>
</div>
<br />
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
'''For a female model''':<br />
<tt>$includemodel "player/female_shared.mdl"<br />
$includemodel "player/female_ss.mdl"<br />
$includemodel "player/female_gestures.mdl"<br />
$includemodel "player/female_postures.mdl"</tt>
</div>

*<tt>$surfaceprop</tt>: Used to define the physical surface properties the model will have. The default is <tt>flesh</tt> (organic-human). The complete list is available [http://developer.valvesoftware.com/wiki/Material_surface_properties here].
'''Note:''' If this command was used in the <tt>.vmt</tt> files to define multiple surface types and is also present in the <tt>.qc</tt> script, the values set in the <tt>.vmt</tt> files will be ignored. If this behavior is not desired, either delete this command from the <tt>mdldecompiler.qc</tt> script, or specify the value as <tt>default</tt> instead.

This is all that you will typically need to modify in order to make a player model compatible with Obsidian Conflict.

==Finishing Touches==
Save the script file and open ''GUI StudioMDL''. Select <tt>OrangeBox</tt> for <tt>SDK Version</tt> and for <tt>Target Mod or "GameInfo" path</tt> select <tt>Obsidian Conflict</tt> (you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this). Go to ''File'' → ''Load .qc file'' and load the <tt>.qc</tt> file, then click on the <tt>Compile</tt> button.

When ''GUI StudioMDL'' finishes compiling the model (you should see <tt>Completed "mdldecompiler.qc"</tt>), open the ''Source SDK'', select <tt>Source 2007</tt> in the <tt>Engine Version:</tt> combo box and select <tt>Obsidian Conflict</tt> in the <tt>Current Game:</tt> combo box (once again, you will need to [[Obsidian SDK Setup|configure the Source SDK for Obsidian Conflict]] prior to this), then click on <tt>Model Viewer</tt>. When ''Half-Life Model Viewer'' loads up, go to ''File'' → ''Load model...'' and select your model.

If all went well, you should now see your model, complete with working animations.

Once you have verified that your model is in working condition, go to where the model files are located in your client's folder and create a new text file with the name of your model, but with the <tt>.txt</tt> extension. Using the previous snippet as an example, the file would be <tt>models/player/Flandre.<span style="color:red;">txt</span></tt>.
Paste the following inside the file (don't forget to alter the gender of the <tt>base model rig</tt> and <tt>voice</tt> as necessary):
<pre>ModelSettings
{
//Use this option to choose a base script to use instead.
"usefile" "none"

//base model rig to use. Use either Male_01 or Female_01 for best results.
"basemodel" "Male_01"

//Voice Sound 0=none, 1=male, 2=female, 3=combine
"voice" "1"

//Footstep Sound 1=shoe, 2=combine boots
"footsteps" "1"

//Gibs, 1 = generic human, 2 = generic alien, 3 = human rebel ragdoll gibs, 4 = Ragdoll only
"Gibs" "4"
}</pre>
With this file, you can configure the voice, footstep sounds and gibs of the model.

Finally, head over to <tt>obsidian/materials/VGUI/playermodels/player</tt> and create a new <tt>.vmt</tt> and <tt>.vtf</tt> file with the same name as your model's <tt>.mdl</tt> file.

'''Note:''' The path after <tt>obsidian/materials/VGUI/playermodels/</tt> '''must''' reflect the path to the model, i.e. if the model is at <tt>models/player/somemodelname/somemodel.mdl</tt>, the two files will be <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vmt</tt> and <tt>obsidian/materials/VGUI/playermodels/player/somemodelname/somemodel.vtf</tt>.

In the <tt>.vmt</tt> file (you can make a copy of an existing one and clear it for use), paste the following:
<pre>UnlitGeneric
{
"$translucent" "1"
"$basetexture" "vgui\playermodels\player\Hostage_01"
"$vertexcolor" "1"
"$vertexalpha" "1"
"$no_fullbright" "1"
"$ignorez" "1"
"$decalscale" "0.250"
}</pre>

On the <tt>$basetexture</tt> line, change <tt>Hostage_01</tt> to point to your accompanying <tt>.vtf</tt> file.

To create that <tt>.vtf</tt> file, take a screenshot in ''Half-Life Model Viewer'' then save it as a <tt>.tga</tt> file and open that in ''VTFEdit'', then save it in the <tt>.vtf</tt> format. Give it the same name as your model.

Once you have placed the two files into your client's <tt>obsidian/materials/VGUI/playermodels/player</tt> folder, test it all out in-game. If all works well (animations, textures, sounds, preview image), pat yourself on the back - you've successfully created a new player model.
*To test the model's preview image, start the game, then go to <tt>Options</tt> → <tt>Multiplayer</tt> tab, and select your model from the combo box.
*To test the model's animations and textures, select the model, then start a local server and turn on <tt>sv_cheats</tt>. Execute the <tt>thirdperson</tt> command.

==Tips And Tricks==
===Creating The VGUI Preview Image===
*'''Using Paint Shop Pro:'''
You will also need to download and install a '''http://nemesis.thewavelength.net/index.php?p=39 VTF Plugin for Paint Shop Pro''' beforehand (Information about how to use it and what programs can use it '''http://developer.valvesoftware.com/wiki/Photoshop_VTF_Plugin here''').

So, Open Paint Shop Pro and open the screenshot (.tga file) you took in SDK Model Viewer earlier.
(Prefebably you want the model holding an oc weapon and you can use centre view to get the model where you want it.
To look around in SDK Model Viewer use: Right mouse click - zoom in/out.
Left mouse click to rotate. Hold shift and use left click mouse to move the model up/down/left/right).

Also in Paint Shop Pro it helps to add a grid (view/grid, size dosen't matter)it just helps when working.

So lets move on to converting/working on the screenshot.

First we will use the Crop tool to cut the picture just so that we have the top half of the body. Make sure you use free form and have the box size that you are cropping set to 256x200, position in the centre of the top half of the body (showing the head, chest and shoulders), and then crop.

Now, click layers and select new mask layer/show all.

Now you will see the picture has a mask-raster 1 layer, right click and select delete and then yes.

Now select the Magic Wand tool set up with something like mode = replace
matchmode = RGB value tolerance = 1 use all layers and use contiguous also use Anti-alias and select outside from dropdown box.
Click on the background on the image and not the model to use the Magic Wand.
(Baically you want to delete the back ground and not the model itself).
So if the the whole box and around the model is selected, its ok to delete.

Once the background is deleted, with the Magic Wand tool still open change the matchmode to = All opaque and this time click on the model in the image and it should change the Magic Wand from around the edges and around the model to actually now just around the model only.

Now click layers select new mask layer/form image, make sure source opacity is checked and everything else is unchecked, click ok.

Now we are going to cut the highlighted model onto a new image. So with the Magic Wand still highlighting around the model on the image change to the Pan tool and right click on the highlighted model and select: copy merged.

Now go to File and create a new image with these properties:

<pre>width =256 pixels
height =256 pixels
resolution =72,000 pixels/inch</pre>

Choose Rastor Background
image depth =RGB - 8bits/channel

And check the Transparent box.

Now to paste your copied image onto your new image, so, right click on your new image and paste as a new selection. Position into the top left hand corner as much as possible and then just left click.

Now we need to give an alpha channel so go to selections select load/save selection and choose save selection to alpha channel and clcik ok/save in the pop-up.

Finally now click File and save copy as and name it Hostage_01.png using the .PNG file format and press yes to the pop-up. (this is so you have a nice image to upload to the forums).

Now click File and save copy as again and this time name it nameofthemodel.vtf using the .VTF file format and press yes/ok to the pop-up.

Now here we are using the VTF plugin. Set the properties as:

<pre>Template = Compressed Texture With Alpha
Format = DXT5 (Common Format)
Mipmap Filter = Box
Sharpen Filter = Sharpen Soft</pre>

check/tick Mipmaps and Thumbnail.

And from the list just make sure Eight Bit Alpha (Format Specific) and Nice Filter are both checked/ticked. Everything else should be unchecked/unticked, then press ok.

Finally add it to your obsidian/materials/VGUI/playermodels/player directory to finish.

Example image:

[[File:Hostage01.png|frame|Example image: Hostage_01]]

[[Category:Miscellaneous_Tutorials]]

Dedicated Server Setup 2

2011-04-07T14:46:16Z

TESLA-X4:

{{wip}}
This page was created since I can't update the one [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths (i.e. <tt>orangebox/hl2</tt> refers to the folder <tt>hl2</tt> ''inside'' <tt>orangebox</tt>, not both the folders), and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Delete the <tt>orangebox/hl2</tt> folder and copy the <tt>hl2</tt> folder (the one outside) in its place.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>rmdir /s orangebox\hl2
|xcopy /s /e hl2 orangebox</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>rm -R orangebox/hl2</tt>
|<tt>cp -R hl2 orangebox</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators with Remote Desktop access to their servers since they can simply install Steam on their servers and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half-Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

==Additional Game Content==
'''Note:''' If you download any of the following (sans ''Portal'') using the ''HLDS Update Tool'' after downloading <tt>orangebox</tt>, <span style="color:red;">you will be forced to download a new set of engine binaries incompatible with the current release of Obsidian Conflict</span>. A telltale sign that this has occurred is when you see an engine error along the lines of ''SetupArrayProps_R: array prop '(null)' is at index zero'' or ''Host_Error: IDLLFunctions::DLLInit returned false'' when you try to start the server. To workaround that, simply rename the <tt>bin</tt> folder (inside <tt>orangebox</tt>) to something else (e.g. <tt>bin_se2007</tt>) '''before''' downloading the game's files. On completion, delete the newly created <tt>bin</tt> folder and rename the old one back to <tt>bin</tt>.
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Incompatible at the time of writing.''
</div>

==Downloading And Installing Obsidian==
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Copy the <tt>obsidian</tt> folder from a fresh install of Obsidian Conflict into your dedicated server's <tt>orangebox</tt> folder.
{{Todo|Further elaboration needed.}}
</div>

==Mounting Content==
Content mounts are controlled by a set of files in the <tt>obsidian/mount</tt> folder. Each file determines whether or not the respective game's content is mounted. These files are merely blank files without any extensions - their contents do not matter since the mod merely checks if the file is there, mounting the content if the file is present.
Valid file names are:
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
<tt>css</tt>

<tt>dod</tt>

<tt>ep2</tt>

<tt>episodic</tt>

<tt>hls</tt>

<tt>lostcoast</tt>
</div>
{{Todo|Further elaboration needed.}}

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

Dedicated Server Setup 2

2011-04-03T13:43:17Z

TESLA-X4:

{{wip}}
This page was created since I can't update the one [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths, and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Delete the <tt>orangebox/hl2</tt> folder and copy the <tt>hl2</tt> folder (the one outside) in its place.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>rmdir /s orangebox\hl2
|xcopy /s /e hl2 orangebox</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>rm -R orangebox/hl2</tt>
|<tt>cp -R hl2 orangebox</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators since they can simply install Steam on it and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

==Additional Game Content==
'''Note:''' If you download any of the following using the ''HLDS Update Tool'' after downloading <tt>orangebox</tt>, <span style="color:red;">you will be forced to download a new set of engine binaries incompatible with the current release of Obsidian Conflict</span>. A telltale sign that this has occurred is when you see an engine error along the lines of ''SetupArrayProps_R: array prop '(null)' is at index zero'' or ''Host_Error: IDLLFunctions::DLLInit returned false'' when you try to start the server. To workaround that, simply rename the <tt>bin</tt> folder (inside <tt>orangebox</tt>) to something else (e.g. <tt>bin_se2007</tt>) '''before''' downloading the game's files. On completion, delete the newly created <tt>bin</tt> folder and rename the old one back to <tt>bin</tt>.
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
{{Todo|Downloadable with the HLDS Update Tool, elaboration needed.}}
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

==Downloading And Installing Obsidian==
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
???
</div>

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

Dedicated Server Setup 2

2011-04-03T12:35:28Z

TESLA-X4:

{{wip}}
This page was created since I can't update the page [[Dedicated Server Setup|here]]. I'm still working on it (but don't have enough time to do it all at once), so it may seem incomplete. - [[User:TESLA-X4|TESLA-X4]] 12:01, 3 April 2011 (CEST)

__TOC__

==Prerequisites==
* A basic understanding of filesystem paths, and the different path representations between Windows and *nix (i.e. <tt>\</tt> in Windows is the same as <tt>/</tt> in UNIX[-like] operating systems).
* A basic understanding of the operating system's command-line interface (i.e. [[Wikipedia:Command Prompt|Command Prompt]] for Windows and Terminals for [[Wikipedia:GNOME Terminal|Linux]] and [[Wikipedia::Apple Terminal|Mac OS]]).
* A fast broadband connection (preferably one without a data transfer limit) to prevent premature aging waiting for the uploads to complete.

<span style="color:red;">'''Note:''' At the time of writing, no binaries are publicly available for Linux and Mac OS.</span>

==Base Server Install==
===Step 1: Download The HLDS Update Tool===
{{Windows|Download this file to a temporary location: '''http://www.steampowered.com/download/hldsupdatetool.exe'''}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In a ''Terminal (On Ubuntu: Applications → Accessories → Terminal)'' window, execute the following commands:
|<tt>mkdir srcds_l</tt>
|<tt>cd srcds_l</tt>
|<tt>wget <nowiki>http://www.steampowered.com/download/hldsupdatetool.bin</nowiki></tt>}}

{{Mac|''Unavailable at time of writing.''}}

===Step 2: Install The HLDS Update Tool===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|Double-click on <tt>hldsupdatetool.exe</tt> and follow the instructions given by the wizard.
|For the purpose of this tutorial, we will assume that you have installed the server to <tt>c:\srcds</tt>.
|Open a ''Command Prompt (Start → Accessories → Command Prompt)'' window and execute the following commands:
|<tt>c:</tt>
|<tt>cd srcds</tt>
|<tt>hldsupdatetool</tt>|
|An updated version of ''hldsupdatetool'' will now be downloaded to replace the one installed by the wizard.}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the same ''Terminal'' window as [[#Step 1: Download The HLDS Update Tool|Step 1]], execute the following commands:
|<tt>chmod +x hldsupdatetool.bin</tt>
|<tt>./hldsupdatetool.bin</tt>
|<tt>./steam</tt>|
|An updated version of ''steam'' (the executable) will now be downloaded to replace the one extracted when you ran <tt>./hldsupdatetool.bin</tt>.}}

{{Mac|''Unavailable at time of writing.''}}

===Step 3: Download The Base Server Files===
{{Windows|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093</nowiki>''|
|In the same ''Command Prompt'' window as [[#Step 2: Install The HLDS Update Tool|Step 2]], execute the following command:
|<tt>hldsupdatetool.exe -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>hldsupdatetool.exe</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''hldsupdatetool'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Linux|''Adapted from <nowiki>http://www.srcds.com/db/engine.php?subaction=showfull&id=1098643920</nowiki>''|
|In the existing ''Terminal'' window from Steps 1 and 2, execute the following command:
|<tt>./steam -command update -game "orangebox" -dir .</tt>|
|A breakdown of the command:
|<tt>./steam</tt>: The executable to run.
|<tt>-command update</tt>: Omnipresent, never omit this.
|<tt>-game "<game>"</tt>: The set of files to download, specify ''list'' instead to see what can be downloaded.
|<tt>-dir <nowiki><directory|.></nowiki></tt>: The directory to install the files in, specify '.' to automatically use the directory ''steam'' is located in.|
|The base server files will now be downloaded. It will take a while, so don't go staring at the window waiting for it to complete. ;)}}

{{Mac|''Unavailable at time of writing.''}}

===Step 4: Setting Up The Folder Structure===
After [[#Step 3: Download The Base Server Files|Step 3]] completes, you should end up with something like this:

{{Windows|<tt>hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds.exe
|orangebox\steam_appid.txt
|ClientRegistry.blob
|HldsUpdateTool.exe
|HldsUpdateTool_<tool version>.mst
|InstallRecord.blob</tt>}}

{{Linux|<tt>.steam\
|.steam\clientregistry.blob
|hl2\
|orangebox\
|orangebox\bin\
|orangebox\hl2\
|orangebox\platform\
|orangebox\reslists\
|orangebox\hlds_steamgames.vdf
|orangebox\srcds_linux
|orangebox\srcds_run
|orangebox\steam_appid.txt
|hldsupdatetool.bin
|InstallRecord.blob
|steam
|test1.so
|test2.so
|test3.so</tt>}}

{{Mac|''Unavailable at time of writing.''}}

Now, because Valve didn't set up the files properly on their server, you'll need to fix it yourself.

'''GUI Approach:'''
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Delete the <tt>orangebox/hl2</tt> folder and copy the <tt>hl2</tt> folder (the one outside) in its place.
</div>

'''Command-Line Approach:'''

{{Windows|In the existing ''Command Prompt'' window from the earlier steps, execute the following commands:
|<tt>rmdir /s orangebox\hl2
|xcopy /s /e hl2 orangebox</tt>}}

{{Linux|In the existing ''Terminal'' window from the earlier steps, execute the following commands:
|<tt>rm -R orangebox/hl2</tt>
|<tt>cp -R hl2 orangebox</tt>}}

{{Mac|''Unavailable at time of writing.''}}

==Campaign Content==
Campaign content is stored only in GCFs downloadable only via the Steam client, so be prepared to upload the extracted files to your server. You will need [http://nemesis.thewavelength.net/index.php?p=25 this application] in order to proceed.

Things are a little easier for Windows server operators since they can simply install Steam on it and do everything directly there.

'''Note:''' The Obsidian Team might offer to copy the extracted GCF content onto servers via their Windows server to save upload time in future, in which case you can safely ignore this section.

===Half-Life: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life source.gcf====
Extract everything from the <tt>hl1</tt> folder (in the GCF) to your dedicated server's <tt>orangebox/hl1</tt> folder, creating the folder if it doesn't exist.
</div>

===Half Life Deathmatch: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

===Half-Life 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====half-life 2 content.gcf====
Extract the <tt>maps</tt> folder from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder.
====source 2007 binaries.gcf====
====source 2007 shared materials.gcf====
====source 2007 shared models.gcf====
====source 2007 shared sounds.gcf====
====half-life 2 2007 base content.gcf====
For all of the above GCFs (<u>in given order</u>, with <tt>source 2007 binaries.gcf</tt> being extracted first and <tt>half-life 2 2007 base content.gcf</tt> being last), extract the <tt>hl2</tt> folder (in the GCFs) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Lost Coast===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
Huh? :V
</div>

===Half-Life 2: Episode One===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode 1 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, creating the folder if it doesn't exist.
====half-life 2 episode one.gcf====
Extract the <tt>maps</tt> folder from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder.
====episodic 2007 shared.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, overwriting if prompted to do so.
====episode one 2007 content.gcf====
Extract everything from the <tt>episodic</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/episodic</tt> folder, and everything from the <tt>hl2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/hl2</tt> folder, overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Two===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
====episode two content.gcf====
====episode two maps.gcf====
====episode two materials.gcf====
For all of the above GCFs (<u>in given order</u>), extract everything from the <tt>ep2</tt> folder (in the GCF) into your dedicated server's <tt>orangebox/ep2</tt> folder, creating the folder if it doesn't exist and overwriting if prompted to do so.
</div>

===Half-Life 2: Episode Three===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
You must be living in the future.
</div>

===Portal===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

==Additional Game Content==
===Counter-Strike: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
???
</div>

===Day of Defeat: Source===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
???
</div>

===Team Fortress 2===
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
''Not useable at time of writing.''
</div>

==Downloading And Installing Obsidian==
<div style="padding: 0.5em 1em 0.5em 1em; border: 1px dashed #2f6fab; color: black; background-color: #f9f9f9; line-height: 1.1em;">
???
</div>

<pre style="color:grey">Still in progress, give me more time, will ya?</pre>

Dedicated Server Setup 2

2011-04-03T10:01:08Z

TESLA-X4: Created page with "{{wip}} This page was created since I can't update the page here. I'm still working on it (but don't have enough time to do it all at once), so it may ..."