Source SDK Known Issues

This is a list of known and verified issues with the Source SDK release, and potential workarounds.

Direct shortcuts to hammer will not work

With this version of the SDK you will get an error if you attempt to run hammer.exe from the 'sourcesdk\bin' directory. Here is the best way to work around this issue:

1. Right-click on the Source SDK item on the Tools tab in Steam.
2. Select Create desktop shortcut.
3. Add -runhammer to the end of the steam.exe command line.

   For example: C:\Program Files\Valve\Steam\Steam.exe -applaunch 211 -runhammer

4. Rename the desktop shortcut to something appropriate, such as "Hammer Editor".

This has the added benefit of actually launching the SDK Launcher before Hammer, making sure it is the latest version.

Also, you can create shortcuts to Model Viewer and Face Poser by creating other shortcuts and adding these command line arguments:

-runmodelviewer

-runfaceposer

SDK Launcher Will Terminate if No 'gameinfo.txt' Exists In A MOD Directory

In order to remind MOD makers choose the correct SteamAppId the SDK Launcher will inspect all installed MODs and attempt to load their 'gameinfo.txt' files. If a MOD directory does not contain a 'gameinfo.txt' file then the user will see the following message and the SDK Launcher will terminate.

Unfortunately, the SDK Launcher will attempt this check each time it is launched until the check is successful. This issue can be worked around in the following ways:

• Move the offending MOD directory, run the SDK Launcher, and then copy it back after the SDK Launcher starts successfully.
• Bypass this check altogether by creating a file named 'show_deprecatedappid_marker.txt' at '%Steam Root%\SteamApps\%Steam User%\sourcesdk\launcher'.
• Adding a 'gameinfo.txt' to the offending MOD's directory.

See also

• Source SDK Release Notes