SDK Installation: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
No edit summary
Line 12: Line 12:
* {{Game link|Counter-Strike: Global Offensive Authoring Tools}}
* {{Game link|Counter-Strike: Global Offensive Authoring Tools}}


== SteamPipe migration and abandonment of the Source SDK app ==
== SteamPipe migration ==


Valve in 2013 changed how authoring tools were distributed for [[Team Fortress 2]], [[Counter-Strike Source]], [[Day of Defeat: Source]], and  
Valve in 2013 changed how authoring tools were distributed for [[Team Fortress 2]], [[Counter-Strike Source]], [[Day of Defeat: Source]], and  
[[Half-Life 2: Deathmatch]].
[[Half-Life 2: Deathmatch]].


Previously these tools were distributed together under the "Source SDK" tool, which resided in a totally different folder from the games. Valve moved towards a model more similar to L4D and CS:GO.  The SDK tools are currently shipped with the game by default. Note that the tools are only available for Windows.
Previously these tools were distributed together under the "Source SDK" tool, which resided in a different folder than the games. Valve moved towards a model more similar to L4D and CS:GO.  The SDK tools or authoring tools are shipped with the game by default. Note that the tools are only available for Windows. {{note|Check if the tools are downloaded on mac, or if they just don't work}}


The tools are located in the respective bin folder for the game (e.g: <code>[steam]/steamapps/common/Team Fortress 2/bin</code>) and are meant to be launched from the following batch files:
The tools are located in the respective bin folder for the game (e.g: <code>[steam]/steamapps/common/Team Fortress 2/bin</code>) and are meant to be launched from the following batch files:
Line 29: Line 29:
{{note|If the tools do not launch, check the environment variables on your computer and change VProject to the directory where gameinfo.txt resides}}
{{note|If the tools do not launch, check the environment variables on your computer and change VProject to the directory where gameinfo.txt resides}}


== Installation of source code and launcher  ==
== Downloading the source code and launcher  ==


The following instructions are appropriate if you need to download Source code. If you only need the authoring tools, they probably do not apply to you.
The following instructions are appropriate if you need to download the source code. If you only need the authoring tools, then the instructions probably do not apply to you.


=== Source 2013 ===
=== Source 2013 ===
Line 38: Line 38:
=== Legacy branches ===
=== Legacy branches ===


{{Steam App Install|id=211|name=Source SDK}} For future reference, or if that doesn't work:
{{Steam App Install|id=211|name=Source SDK}}  
For future reference, or if that doesn't work:


# Open the Steam window.
# Open the Steam window.
Line 47: Line 48:
# The Source SDK will then be downloaded to your computer via Steam.
# The Source SDK will then be downloaded to your computer via Steam.


== Running ==
== Use ==


Once Steam has finished downloading you can launch the SDK from the Tools tab. You can also create a desktop shortcut by right-clicking on the SDK in the Tools tab and clicking '''Create desktop shortcut''' from the context menu that appears.
Once Steam has finished downloading you can launch the SDK from the Tools tab. You can also create a desktop shortcut by right-clicking on the SDK in the Tools tab and clicking '''Create desktop shortcut''' from the context menu that appears. (Recommended for quick access)


When you first run the SDK it will spend a long time extracting its downloaded archive to loose files on your disk. This will not happen again until the SDK is next updated.
When you first run the SDK it will spend a long time extracting its downloaded archive onto your disk. This will not happen again until the SDK is next updated.


After that, you will be able to select a game and run any of the tools provided by the launcher. '''However,''' you will run into problems unless the game you want to work with is fully up to date. You can make sure it is by launching the game and quitting once you get to the main menu.
After that, you will be able to select a game and run any of the tools provided by the launcher. '''However,''' you will run into problems unless the game you want to work with is fully up to date. You can make sure it is up to date by launching the game and quitting once you get to the main menu.


== Where do I go from here? ==
== Where do I go from here? ==

Revision as of 11:46, 17 November 2022

English (en)Deutsch (de)Español (es)Français (fr)Hrvatski (hr)Italiano (it)한국어 (ko)Polski (pl)Português do Brasil (pt-br)Русский (ru)Türkçe (tr)Українська (uk)Tiếng Việt (vi)中文 (zh)中文(臺灣) (zh-tw)Translate (Translate)

The Source SDK is freely available to all Steam users. It is used to develop mods and content for the Source 2006, Source 2007 and Source 2013 engine branches.

Valve games since 2008 onward started to have their own SDK or Authoring Tools, and are engine versions that have no source code available to the public (except Alien Swarm):

SteamPipe migration

Valve in 2013 changed how authoring tools were distributed for Team Fortress 2, Counter-Strike Source, Day of Defeat: Source, and Half-Life 2: Deathmatch.

Previously these tools were distributed together under the "Source SDK" tool, which resided in a different folder than the games. Valve moved towards a model more similar to L4D and CS:GO. The SDK tools or authoring tools are shipped with the game by default. Note that the tools are only available for Windows.

Note.pngNote:Check if the tools are downloaded on mac, or if they just don't work

The tools are located in the respective bin folder for the game (e.g: [steam]/steamapps/common/Team Fortress 2/bin) and are meant to be launched from the following batch files:

  • hammer.bat
  • faceposer.bat
  • hlmv.bat
  • stdudiomdl.bat
  • vtex.bat
Note.pngNote:If the tools do not launch, check the environment variables on your computer and change VProject to the directory where gameinfo.txt resides

Downloading the source code and launcher

The following instructions are appropriate if you need to download the source code. If you only need the authoring tools, then the instructions probably do not apply to you.

Source 2013

See: Source SDK 2013.

Legacy branches

Click here to install the Source SDK For future reference, or if that doesn't work:

  1. Open the Steam window.
  2. Go to the Library.
  3. Change the list to Tools.
  4. Find and double-click on the Source SDK item.
  5. Read over the dialog box and click Download and Install / Next to continue
  6. The Source SDK will then be downloaded to your computer via Steam.

Use

Once Steam has finished downloading you can launch the SDK from the Tools tab. You can also create a desktop shortcut by right-clicking on the SDK in the Tools tab and clicking Create desktop shortcut from the context menu that appears. (Recommended for quick access)

When you first run the SDK it will spend a long time extracting its downloaded archive onto your disk. This will not happen again until the SDK is next updated.

After that, you will be able to select a game and run any of the tools provided by the launcher. However, you will run into problems unless the game you want to work with is fully up to date. You can make sure it is up to date by launching the game and quitting once you get to the main menu.

Where do I go from here?

If you want to learn about how to create content for the Source Engine in general, the main page of the Source SDK documentation is a good place to start.

Bugs and Issues

See also